Here another late comment (sorry), on Section 6.1.1: An EST/Registrar server running at address 2001:db8:0:abcd::52, with the JPY process on port 7634, and the stateful Registrar on port 5683 could reply to a multicast query as follows:
REQ: GET /.well-known/core?rt=brski* RES: 2.05 Content <coaps+jpy://[2001:db8:0:abcd::52]:7634>;rt=brski.rjp, <coaps://[2001:db8:0:abcd::52]/.well-known/brski/rv>;rt=brski.rv;ct=836, <coaps://[2001:db8:0:abcd::52]/.well-known/brski/vs>;rt=brski.vs;ct="50 60", <coaps://[2001:db8:0:abcd::52]/.well-known/brski/es>;rt=brski.es;ct="50 60", --> For completeness the server should also respond with the BRSKI root resource, which matches the filter. So: RES: 2.05 Content <coaps+jpy://[2001:db8:0:abcd::52]:7634>;rt=brski.rjp, <coaps://[2001:db8:0:abcd::52]/.well-known/brski>;rt=brski, <coaps://[2001:db8:0:abcd::52]/.well-known/brski/rv>;rt=brski.rv;ct=836, <coaps://[2001:db8:0:abcd::52]/.well-known/brski/vs>;rt=brski.vs;ct="50 60", <coaps://[2001:db8:0:abcd::52]/.well-known/brski/es>;rt=brski.es;ct="50 60", The motivation why to do this particular query is not so clear in the document. I assume the following was intended: 1. JP wanting to find out if stateful JP is supported in this network: it can send this (without the asterisk) REQ: GET /.well-known/core?rt=brski 2. JP wanting to find out if stateless JP is supported: REQ: GET /.well-known/core?rt=brski.rjp 3. JP wanting to find out both in a single query: REQ: GET /.well-known/core?rt=brski* In case 1 and 3 the JP may be looking for "rt=brski" in the response. Hence, in our example the rt=brski resource must be present. Otherwise, no interoperability. Note that the JP won't care about the details of the /rv, /vs, /es resources. It just needs Registrar address and port. Best regards Esko -----Original Message----- From: Michael Richardson <m...@sandelman.ca> Sent: Wednesday, September 21, 2022 12:31 To: Esko Dijk <esko.d...@iotconsultancy.nl> Cc: Anima WG <anima@ietf.org>; anima-cha...@ietf.org; stokcons <stokc...@bbhmail.nl> Subject: Re: [Anima] 2nd WGLC for draft-ietf-anima-constrained-join-proxy-12, ends September 20th 2022 Okay, thank you. I'll crunch through your comments on Friday. _______________________________________________ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
