Pascal Thubert (pthubert) <[email protected]> wrote: >>> Suggestion: "default-jrc.6tisch.arpa". >> >> Why make it longer? Note that it's already to a unique Path-URI (/j), so we >> can add new things if it's CoAP.
> The point is that 6TiSCH.arpa doesn’t dénote what 6TISCH service we are
> after. There may be others in the future like a PCE.
I don't understand at all. Would a PCE provide enrollment services?
1) We specify the service we want with the Path-URI (/j for join).
We could have /p for a PCE, but, I'm not sure what it would do.
2) There is never an IP address associated with 6tisch.arpa, it's just
something to put into the Host part of the CoAP. Since we are talking
to a Join Proxy, and the Join Proxy points to the JRC, we get the JRC.
If we had something that wanted a PCE, what would it talk to get that?
Wouldn't the node already have enrolled?
How would it get the IP address of the PCE?
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] [email protected] http://www.sandelman.ca/ | ruby on rails [
signature.asc
Description: PGP signature
_______________________________________________ 6tisch mailing list [email protected] https://www.ietf.org/mailman/listinfo/6tisch
