Christian Amsüss <christ...@amsuess.com> wrote:
> * Similarly, the query for ?rt=brski.jp returns a resource, when it is
> actually asking for a transport endpoint. Moreover, there *are*
> resources available that the pledge likely will need to discover (any
> of the brski.rv/vs/es). Before I can make any good statements or
> suggesions here, how is it currenlty envisioned that the pledge will
> find these resources?This is an interesting situation. I actually think that we've probably got this wrong! We should not ever do rt=brski.jp. We should be doing instead rt=brski*, as you say, because it's the rv/vs/es that we really are looking for. So it should look like: ~~~~ REQ: GET coap://[FF02::FD]/.well-known/core?rt=brski* RES: 2.05 Content <coaps://[2001:db8:0:abcd::52]:join-port/.well-known/brski/rv>;rt=brski.rv;ct=836, <coaps://[2001:db8:0:abcd::52]:join-port/.well-known/brski/vs>;rt=brski.vs;ct="50 60", <coaps://[2001:db8:0:abcd::52]:join-port/.well-known/brski/es>;rt=brski.es;ct="50 60", ~~~~ It would be nice if we could get back: <coaps://[2001:db8:0:abcd::52]:join-port/.well-known/est/sren>;ct=287 as well, but I don't know how/if we can ask for rt=est* as well as rt=brski* in a single operation. This is in section 6.1.1 of the -12. Maybe we just don't need brski.jp *AT ALL* The Join Proxy should answer as if it was the Registrar, with coaps: at the front. -- Michael Richardson <mcr+i...@sandelman.ca>, Sandelman Software Works -= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
