Hi, There is already a "CoAP ping" described in RFC 7252 that can be used. It does not access any resource, just the CoAP server endpoint at CoAP message layer. As a side effect of this ping your DTLS stack will set up the connection which is handy.
So I don't think we need a resource at / that produces 2.05 , this is for the maintainer of the server to decide how to allocate that resource space. Besides we have already defined some well-known resources accessible with GET ( in core/est/brski) that the client could make use of to test connectivity. Even a non-existing resource in the /.well-known/X space could be used just to get a 4.04 which confirms the server is working properly. This is even better that trying to GET a resource of who knows how large size. Esko -----Original Message----- From: Anima <[email protected]> On Behalf Of Michael Richardson Sent: Tuesday, July 20, 2021 15:39 To: [email protected] Cc: [email protected] Subject: [Anima] constrained resources at root for debugging connectivity It was said in a private exchange: > There is no CoAP resource at the root / hence the 4.04. (Only the > MASA has a test HTTP resource at / ) I thought, what we need is a CoAP Ping/echo. And I remembered: https://www.ietf.org/archive/id/draft-ietf-core-echo-request-tag-13.html#section-2.2 but, this is for the server to validate that the client is really there. Should we recommend that Registrar put something at / that produces a 2.00? (lowercase recommend) -- Michael Richardson <[email protected]> . o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide _______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
