Yes, the assumption is still that a CoAP request made to the root resource (/) is valid and can be encoded by including 0 Uri-Path Options. Since the proposed CoAP message does not contain any Uri-Path option, it should be directed to the root resource. There could also be cases where the Registrar would configure another resource (e.g. /j or /join or whatever) and in such case a Uri-Path option would be needed.
I'm not 100% sure if for a resource at the root (/), one Uri-Path Option with 0 length is needed or if 0 Uri-Path Options can be used. Or if both methods would be valid. Esko -----Original Message----- From: Michael Richardson <[email protected]> Sent: Wednesday, October 26, 2022 16:53 To: Esko Dijk <[email protected]>; [email protected]; [email protected] Subject: Re: [Anima] [core] ANIMA constrained-join proxy revision to use CoAP Esko Dijk <[email protected]> wrote: >> The Proxy-Scheme option is set to "coap". Do I even need this? > I don't think we can use the Proxy-Scheme (or the Proxy-Uri) Option If we don't need it, then GREAT, that's six bytes we save. -- Michael Richardson <[email protected]>, Sandelman Software Works -= IPv6 IoT consulting =- _______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
