Hi Jonathan, The draft uses the term "RPL domain" in several places and this is not clearly defined.
I would imagine that it includes all nodes that are downstream of the RPL border router. But can you clarify if Host nodes that are downstream of the border router but do not implement any part of RPL ( even as RPL Leaf nodes ) should be considered part of the "RPL domain" ? In section 5, the draft now says "..Datagrams destined to nodes outside the RPL domain are dropped if the outer-most IPv6 header contains a RPL Option..." This text would imply that any RPL node sending packets to nodes outside should always tunnel to the Root ? Is that the intention really or am I missing something here.. Also note that if non-RPL Host is not considered part of the RPL domain, then I am not sure that a forwarding router can know if the destination is inside the domain or not. -Regards, Joseph ------------------------------ Message: 5 Date: Tue, 11 Oct 2011 22:23:10 -0700 From: Jonathan Hui <jon...@cisco.com> To: IETF IPv6 Mailing List <ipv6@ietf.org> Subject: Fwd: I-D Action: draft-ietf-6man-rpl-option-04.txt Message-ID: <69acd1f4-d0fa-4b94-8648-48f8cafeb...@cisco.com> Content-Type: text/plain; charset=us-ascii This update is intended to address Jari Arkko's AD review. Summary of changes: - Clarify when the RPL Option is used. - Updated text on recommendations for avoiding fragmentation. - Specify skip-over-and-continue policy for unrecognized sub-TLVs. - Change use of IPv6-in-IPv6 tunneling from SHOULD to MUST. - Specify RPL Border Router operations in terms of forwarding decision outcomes. - Expand security section. -- Jonathan Hui Begin forwarded message: > From: internet-dra...@ietf.org > Date: October 11, 2011 10:17:15 PM PDT > To: i-d-annou...@ietf.org > Cc: ipv6@ietf.org > Subject: I-D Action: draft-ietf-6man-rpl-option-04.txt > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. This draft is a work item of the IPv6 Maintenance Working Group > of the IETF. > > Title : RPL Option for Carrying RPL Information in Data-Plane > Datagrams > Author(s) : Jonathan W. Hui > JP Vasseur > Filename : draft-ietf-6man-rpl-option-04.txt > Pages : 14 > Date : 2011-10-11 > > The RPL protocol requires data-plane datagrams to carry RPL routing > information that is processed by RPL routers when forwarding those > datagrams. This document describes the RPL Option for use within a > RPL domain. > > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-6man-rpl-option-04.txt > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > This Internet-Draft can be retrieved at: > ftp://ftp.ietf.org/internet-drafts/draft-ietf-6man-rpl-option-04.txt > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
