Pascal, I think you're being a bit paranoid here. Let me try to correct some misunderstandings.
Again, I think you are fighting yourself here with regard to prefix dissemination. We have already agreed that nothing in nd-09 prevents RPL from disseminating the PIOs. In fact, it specifically says that if the routing protocol does that already, then great. Other routing protocol might need the prefix dissemination option in nd-09, thus the spec "stands on its own feet". So as far as the 6lowpan WG is concerned there is nothing to discuss. It is up to the ROLL working group to discuss if and how it wants to disseminate prefix information to RPL routers. Regarding InstanceIDs and other RPL specific host issues, there is nothing in nd-09 preventing that either. Nor can a 6lowpan document specify something for a host to do which is RPL related. If RPL wants to specify some ND option to be carried in RAs with regard to flow labels - then go for it. But don't complain about ND here... Regarding the extended LoWPAN functionality you are referring to below. The WG consensus after Hiroshima was to split the ND draft into a base draft (which was done in nd-08 already!) and a separate Extended LoWPAN draft. As I have told you, you need to find the time to write that extended LoWPAN draft (let's do it) and explain how to achieve these kinds of topologies. I'm happy to help, but my hands are full right now. The WG consensus in Anaheim was to make a clean re-write of the WG document integrating the NS/NA mechanism from nd-simple and the base mechanism of address registration from nd-08. This is what we did. I believe the result of this is a very good draft which specifies the host-router interface and definitely stands on its own feet as it is mesh-under, route-over and routing protocol independent as it should be. On May 10, 2010, at 12:06 , Pascal Thubert (pthubert) wrote: > > For all I know ND 09 is broken while ND 07 was not. The WG consensus was the opposite, sorry. > My suggestion to > resolve the issues I see: > > - put the whiteboard interaction back in the base spec so the spec is > standing on its own 2 feet. nd-09 does have the ability to do DAD to the edge of the LoWPAN... > - let the route over problem propagation to RPL (that's the PIO/RIO > propagation) It DOES!!!! Remember RPL is not *the* only routing protocol. I can implement DYMO on a LoWPAN and it will need the prefix dissemination method from nd-09. > - make a separate spec for the ND proxy piece. We have already text from > Zach, Carsten and I that can be used Pascal, you know very well that is your AP. This was also already decided by the working group already after Hiroshima. Argh, Zach -- Zach Shelby, Head of Research, Sensinode Ltd. http://zachshelby.org - My blog "On the Internet of Things" http://6lowpan.net - My book "6LoWPAN: The Wireless Embedded Internet" Mobile: +358 40 7796297 _______________________________________________ 6lowpan mailing list [email protected] https://www.ietf.org/mailman/listinfo/6lowpan
