Hi Robert and Richard:
We designed instances to enable to support multiple sorts of traffic with different requirements. The instance is the network response to the application needs. The application resides in the host, even if routers sometimes play both roles. The application needs to signal the instance one way or another in its packets, and we use flow labels for that. So far so good. What's missing: - The host also needs to join the RPL networks that support the instances that it needs. That must be signaled in the router to host interface. - The host also needs to be advertised in the RPL networks that support the instances that it needs. That must be signaled in the host to router interface. >From there I think you've got the logic reverse: You're correct that ROLL supports a host with no RPL extension using instance 0 / flow label 0. But still the host to router interface needs to be augmented for an application residing on the host to benefit from ROLL instances. What I'm reading below is "a host MUST be a router in order to comply with the ROLL MUST of supporting multiple types of traffic". Well, -1. Pascal From: Robert Cragie [mailto:[email protected]] Sent: Thursday, May 06, 2010 7:48 PM To: Richard Kelsey Cc: Pascal Thubert (pthubert); [email protected]; [email protected]; [email protected] Subject: Re: [Roll] [6lowpan] how does a node get an IP address +1 Robert Cragie (Pacific Gas & Electric) Gridmerge Ltd. 89 Greenfield Crescent, Wakefield, WF4 4WA, UK +44 (0) 1924 910888 http://www.gridmerge.com <http://www.gridmerge.com/> On 06/05/2010 1:16 PM, Richard Kelsey wrote: Date: Thu, 6 May 2010 09:02:28 +0200 From: "Pascal Thubert (pthubert)" <[email protected]> <mailto:[email protected]> [Pascal] 6LoWPAN ND needs some addition to enable RPL aware hosts. In particular around instance IDs. Pascal, I disagree with "needs". The ability to select an instance ID for a particular message is an optional extra. RPL works fine without it. I am okay with limiting instance ID selection to routers. -Richard Kelsey _______________________________________________ Roll mailing list [email protected] https://www.ietf.org/mailman/listinfo/roll
_______________________________________________ 6lowpan mailing list [email protected] https://www.ietf.org/mailman/listinfo/6lowpan
