Hi Erik: OSPFv3 has similar instances.
Traffic Engineering is all about mapping flows of traffic onto complex topologies that are designed for those flows. So nothing real new. RPL just makes that a bit less manual, because we have harder constraints in terms of scalability and so-called autonomicity. RPL dynamically builds its TE topologies and specifies the flow label interaction a bit deeper to automate the mapping of the flows onto those topologies. I see that as extension or evolution, but not revolution. A survival trait for the Internet Architecture, really. Pascal > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Erik Nordmark > Sent: Monday, May 10, 2010 9:01 AM > 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
