Mališa Vučinić <[email protected]> wrote: > I did quite a bit of work in the document, including some CBOR wizardry, > and defined new parameters and IANA registries with the goal of > homogenizing the join for 6LBR and regular nodes. For now, I added an > optional "network prefix" parameter in the Join Response, carrying the IPv6 > prefix of the network for the 6LBR. If there are some pitfalls with this > that I forgot, we can remove it. Similarly, I also added the "network > identifier" parameter in the Join Response, carrying PAN ID for the > 6LBR.
https://goo.gl/GL4Pc5 has a diff against -05... I love rfcdiff :-) I see that you have an IANA registry for the Join Request and Join Response key values. These tables need to have names and the IANA instruction needs to ask them to create the tables, and then to populate them with the table From section 9. May I also suggest: 1) instead of "unsigned integer", that we just say integer. 2a) that the 1-byte positive and negative integers may be allocated by IETF Standard. 2b) that the 2-byte, 3-byte and 4-byte positive integers may be allocated by IANA First Come First Served (https://tools.ietf.org/html/rfc8126#section-4.4) 2c) that the 2-byte, 3-byte and 4-byte negative integers be reserved for as an experimental range. > 9.2.1.1. Link-Layer Key This probably needs an IANA Registry, even if it is closed to just IETF Standard Action. (I can write text next week on this) Did you see my "new-key-start" branch from last week, btw? On to 6LBR stuff: As a special case, when the pledge is configured to play the role of the 6LBR, and 6LBR is not co-located with the JRC, the pledge additionally needs to be provisioned with: okay, so I understand the situation. I think that such a 6LBR probably have two interfaces, one of them Ethernet, and that it does a join over ethernet. (It would probably also do a join request over 15.4 as well, since it might have no idea what's where) I'm fine with that, but in that case, we need to tell such a pledge how to find a Join Proxy and/or the actual JRC. At present, we use the 15.4 specific Enhanced Beacon. There a bunch of options: 1) DHCPv6 2) GRASP 3) mDNS (DNS-SD) 4) RA option -- ] 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
