Re: [Roll] [roll] #86: G flag: do we need that text?

Michael Richardson <mcr@sandelman.ca> Wed, 04 April 2012 16:28 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74AF521F8754 for <roll@ietfa.amsl.com>; Wed, 4 Apr 2012 09:28:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TW-Pi3Gsl6hE for <roll@ietfa.amsl.com>; Wed, 4 Apr 2012 09:28:58 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.252.184]) by ietfa.amsl.com (Postfix) with ESMTP id 8832821F8746 for <roll@ietf.org>; Wed, 4 Apr 2012 09:28:58 -0700 (PDT)
Received: from 10.200.181.228 (unknown [199.119.232.2]) by tuna.sandelman.ca (Postfix) with ESMTPSA id 766FF20168 for <roll@ietf.org>; Wed, 4 Apr 2012 12:34:24 -0400 (EDT)
Date: Wed, 04 Apr 2012 12:28:08 -0400
Message-ID: <rmdamo7xuqhaymlxq0llmkcn.1333556888603@email.android.com>
From: Michael Richardson <mcr@sandelman.ca>
To: roll@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
X-Mailman-Approved-At: Wed, 04 Apr 2012 14:39:00 -0700
Subject: Re: [Roll] [roll] #86: G flag: do we need that text?
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Apr 2012 16:28:59 -0000

I think we need to determine what a grounded DODAG is.
Does it mean that a node announcing such a thing is attached to the Internet? (In which case P2P usage should G=0)
Or does it mean that a node is attached to the resource named in the DIO? (In which case origin P2P should G=1)


Richard Kelsey <richard.kelsey@ember.com> wrote:

>> Date: Wed, 4 Apr 2012 08:54:52 -0500
>> From: Mukul Goyal <mukul@uwm.edu>
>> 
>> >The G flag is 0 if and only if the DODAG is floating.
>> 
>> I think that the G flag is 1 if and only if the DODAG is grounded.
>
>I agree.  G = 0 means floating, G = 1 means grounded.
>
>> The temporary DAGs used in P2P-RPL are not grounded, they are
>> temporary. I think that all transient/temporary DAGs are
>> floating by their very nature.
>
>This I don't follow at all.  If a device has a temporary need to
>send or receive data from many other devices, it makes perfect
>sense for it to create a a temporary, grounded DODAG.  If there
>is a lot of P2P traffic, it makes perfect sense to have permanent,
>floating DODAGs for routing that traffic.  
>
>                                         -Richard Kelsey
>
>> ----- Original Message -----
>> From: "Richard Kelsey" <richard.kelsey@ember.com>
>> To: roll@ietf.org
>> Cc: mukul@UWM.EDU, jpv@cisco.com, roll@ietf.org
>> Sent: Wednesday, April 4, 2012 8:36:50 AM
>> Subject: Re: [Roll] [roll] #86: G flag: do we need that text?
>> 
>> > From: roll issue tracker <trac+roll@trac.tools.ietf.org>
>> > Date: Wed, 4 Apr 2012 13:08:50 +0000
>> > 
>> > #86: G flag: do we need that text?
>> > 
>> >  Problem (resolition is proposed)
>> >  ------------------------------
>> >  Disagreement on the meaning of 'G' bit and imposed setting to 0;
>> > 
>> >  Proposed resolution
>> >  ---------------------------
>> >  The origin sets the G flag based on its perception of whether joining
>> >  how the flag's value would affect the rank calculation under the OF
>> >  being used. By default, the G flag is set to zero given the temporary
>> >  nature of the DAG being created.
>> 
>> I disagree with the proposed resolution.  It adds needless
>> confusion.  The G flag is 0 if and only if the DODAG is floating.
>> There is no point to allowing floating DODAGs with a P2P-RDO
>> option.  I suggest that the G bit be set to 1 and that routers be
>> explicitly prohibited from creating floating DODAGs with a
>> P2P-RDO option.
>>                                    -Richard Kelsey
>> 
>_______________________________________________
>Roll mailing list
>Roll@ietf.org
>https://www.ietf.org/mailman/listinfo/roll