Re: [Roll] definition of "RPL Domain"

Hi,

On Nov 24, 2011, at 7:29 PM, Mukul Goyal wrote:

> Hi Jonathan, JP
> 
> Just wondering if you could confirm that the next version of the terminology draft will have this definition of RPL domain included. This would allow me to refer to the terminology draft for the definition of RPL domain in the p2p-measurement draft.
> 

Nice, I'll summarize the discussion and make sure that everybody agrees before submitting (soon).

Thanks.

JP.

> Thanks
> Mukul
> 
> ----- Original Message -----
> From: "Mukul Goyal" <mukul@uwm.edu>
> To: "Jonathan Hui" <jonhui@cisco.com>
> Cc: "roll" <roll@ietf.org>
> Sent: Thursday, November 17, 2011 9:10:07 PM
> Subject: Re: [Roll] definition of "RPL Domain"
> 
> I agree with this definition of RPL domain. The definition implies that RPL devices may have links/interfaces that are considered exterior to the RPL domain.
> 
> Thanks
> Mukul
> 
> ----- Original Message -----
> From: "Jonathan Hui" <jonhui@cisco.com>
> To: "Mukul Goyal" <mukul@uwm.edu>
> Cc: "JP Vasseur" <jpv@cisco.com>, "roll" <roll@ietf.org>
> Sent: Wednesday, November 16, 2011 7:37:32 AM
> Subject: Re: [Roll] definition of "RPL Domain"
> 
> 
> How about a definition derived from RFC 1629:
> A "RPL domain" is a routing domain, as stated in Section 3.2 of RFC 1629, where the common routing protocol is RPL.
> 
> The above definition would unambiguously give the following answers to your questions:
> 1) Given the definition above, devices that do not operate RPL are not a part of the RPL domain.
> 2) Because RPL devices may support more than one instance, a RPL domain may contain any number of instances.
> 
> The term seems to be used most often in draft-ietf-roll-p2p-measurement.  I suggest going through and verifying whether "RPL Instance" or "RPL domain" was intended.
> 
> Happy to see any alternative definitions you may have in mind.
> 
> --
> Jonathan Hui
> 
> On Nov 16, 2011, at 2:45 AM, Mukul Goyal wrote:
> 
>> Hi JP
>> 
>>> RPL domain: set of devices using RPL as a routing protocol.
>> 
>> I think this definition is little too vague. Some of the points that need clarification:
>> 
>> 1. It is clear that RPL hosts and routers (as defined towards the end of terminology section in RPL-19) are within an RPL domain but what about the RPL-unaware IPv6 hosts attached to an RPL router/host? I would imagine that such hosts are also within an RPL domain.
>> 
>> 2. Is an RPL domain same as an RPL instance? Or is an RPL domain a set of RPL instances in the LLN? Can multiple RPL domains exist within an LLN? Or is it that an RPL domain is same as an LLN using RPL as a routing protocol?
>> 
>> Thanks
>> Mukul  
>> 
>> ----- Original Message -----
>> From: "JP Vasseur" <jpv@cisco.com>
>> To: "Mukul Goyal" <mukul@UWM.EDU>
>> Cc: "roll" <roll@ietf.org>
>> Sent: Wednesday, November 16, 2011 2:33:50 AM
>> Subject: Re: definition of "RPL Domain"
>> 
>> Hi Mukul,
>> 
>> On Oct 18, 2011, at 3:05 AM, Mukul Goyal wrote:
>> 
>>> Hi JP
>>> 
>>> I was wondering if the term "RPL Domain" could be defined in the terminology draft. 
>>> 
>> 
>> How about
>> 
>> RPL domain: set of devices using RPL as a routing protocol.
>> 
>> Thanks.
>> 
>> JP.
>> 
>>> Thanks
>>> Mukul 
>>> 
>>> ----- Forwarded Message -----
>>> From: "Joseph Reddy" <jreddy@ti.com>
>>> To: ipv6@ietf.org
>>> Sent: Friday, October 14, 2011 7:15:05 PM
>>> Subject: Re: Fwd: I-D Action: draft-ietf-6man-rpl-option-04.txt
>>> 
>>> 
>>> 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 <jonhui@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-48F8CAFEB3EC@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-drafts@ietf.org
>>>> Date: October 11, 2011 10:17:15 PM PDT
>>>> To: i-d-announce@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
>>> --------------------------------------------------------------------
>> 
>> _______________________________________________
>> Roll mailing list
>> Roll@ietf.org
>> https://www.ietf.org/mailman/listinfo/roll
> 
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll