> Where can I find the architectural definition of "an RPL instance"? > > Is it in essence akin to a VLAN on an Ethernet?
It sounds like the same to me. With the difference that VLAN was created to simulate individual media over one wired infrastructure. With individual DODAGIDs this is already possible in RPL (?) If the rest of the Internet can live without this complex mechanism, why do we want to put that burden on much smaller nodes? My take is we should leave all this flow label stuff for the future if it appears that there really is a need for it. Internally RPL already has the OCP to do the same. just my $0.05 > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Erik Nordmark > Sent: Monday, May 10, 2010 09:01 > To: [email protected] > Subject: Re: [6lowpan] [Roll] how does a node get an IP address > > On 05/ 6/10 12:02 AM, Pascal Thubert (pthubert) wrote: > > > 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. > > Where can I find the architectural definition of "an RPL instance"? > > Is it in essence akin to a VLAN on an Ethernet? > > This sounds like a significant departure from the existing > Internet architecture. > > Erik > _______________________________________________ > 6lowpan mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/6lowpan > _______________________________________________ 6lowpan mailing list [email protected] https://www.ietf.org/mailman/listinfo/6lowpan
