Hi Carsten > -09 has significantly less functionality than -08 had. > (This may be a bit disappointing to some of us, but it clearly was the result of > IETF77.) I'm not sure how that more focused functionality makes it "not > support mesh under". > Did we lose some functionality that is required? > Please explain. [Pascal] this piece is not related to ROLL. This is about the multicast issue in mesh under. 6LoWPAN elected the backbone router draft to address that issue.
> > > It does not support route over either since it is not compatible with > > the only route over protocol in existence. > > Again, please explain. [Pascal] 6LoWPAN ND needs some addition to enable RPL aware hosts. In particular around instance IDs. > > > [...] work closely with RPL > > to build a consistent solution for route over. > > Yes! (That's why I kept ROLL on the CC.) If there is a technical issue, we need > to understand it, so please explain. > [Pascal] The RPL instance decision is end to end and matches the application requirements. A device might send traffic over multiple instances and it has to indicate that in the flow label. What I'm proposing is to recognize that a LoWPAN and an LLN are quite the same thing, and if they were not, make it so from now on. At that point we can accept that ROLL and split the job between RPL and ND, RPL doing the router to router piece and ND the interface to the hosts. On the RPL side, that means transporting RIO and PIO from the authoritative router acting as root down the RPL fabric within DIO messages. It's a simple replacement to the existing Destination Prefix option in DIO, no harm done. You'll note that RPL actually USES that information. On the ND side, it means opening the messages to RPL parameters, in particular the mapping between the flow label and the instance information. RAs should be able to advertise which instance is available from a given router for instance. We were almost there with ND 07. So sad. Also sad that you took me off the draft btw, won't help me internally. And then, ND can defer to 'an SGP such as RPL' for PIO/RIO dissemination and RPL routers can be configured to redistribute host information leant from ND into the SGP. > Gruesse, Carsten _______________________________________________ 6lowpan mailing list [email protected] https://www.ietf.org/mailman/listinfo/6lowpan
