Re: [Roll] [roll] #86: G flag: do we need that text?
Mukul Goyal <mukul@uwm.edu> Wed, 04 April 2012 14:26 UTC
Return-Path: <prvs=43413a6b9=mukul@uwm.edu>
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 15CAD21F85C2 for <roll@ietfa.amsl.com>; Wed, 4 Apr 2012 07:26:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.649
X-Spam-Level:
X-Spam-Status: No, score=-4.649 tagged_above=-999 required=5 tests=[AWL=-0.216, BAYES_00=-2.599, FF_IHOPE_YOU_SINK=2.166, RCVD_IN_DNSWL_MED=-4]
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 FspX9tlJDnDQ for <roll@ietfa.amsl.com>; Wed, 4 Apr 2012 07:26:50 -0700 (PDT)
Received: from ip1mta.uwm.edu (ip1mta.uwm.edu [129.89.7.18]) by ietfa.amsl.com (Postfix) with ESMTP id 65E1D21F85B4 for <roll@ietf.org>; Wed, 4 Apr 2012 07:26:50 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap4EAPJZfE9/AAAB/2dsb2JhbABFhU61XgEBAQMBAQEBIEsEBwUHDxEDAQEBAwINFgMCKR8JCAYTiAQFC6goiFKJBQSBL44NgRgEiFiNC5AwgwWBNhc
Received: from localhost (localhost.localdomain [127.0.0.1]) by mta04.pantherlink.uwm.edu (Postfix) with ESMTP id 0B4E72B3F0A; Wed, 4 Apr 2012 09:26:38 -0500 (CDT)
X-Virus-Scanned: amavisd-new at mta04.pantherlink.uwm.edu
Received: from mta04.pantherlink.uwm.edu ([127.0.0.1]) by localhost (mta04.pantherlink.uwm.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Iua5yOzhZfPl; Wed, 4 Apr 2012 09:26:37 -0500 (CDT)
Received: from mail17.pantherlink.uwm.edu (mail17.pantherlink.uwm.edu [129.89.7.177]) by mta04.pantherlink.uwm.edu (Postfix) with ESMTP id C18802B3EF6; Wed, 4 Apr 2012 09:26:37 -0500 (CDT)
Date: Wed, 04 Apr 2012 09:26:37 -0500
From: Mukul Goyal <mukul@uwm.edu>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Message-ID: <1994083354.1808319.1333549597673.JavaMail.root@mail17.pantherlink.uwm.edu>
In-Reply-To: <BDF2740C082F6942820D95BAEB9E1A84015DE3B3@XMB-AMS-108.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [129.89.7.91]
X-Mailer: Zimbra 6.0.13_GA_2918 (ZimbraWebClient - IE8 (Win)/6.0.13_GA_2918)
X-Authenticated-User: mukul@uwm.edu
Cc: roll@ietf.org
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 14:26:51 -0000
>Floating vs. Grounded depends on the goal of the DODAG. I asked you and will ask again what is your goal? I am not sure there is a natural way to define this goal. Why is it that a route discovery should specify an application-level goal and that too in just one bit. My opinion is that the grounded bit is quite unnecessary even for core RPL. Connectivity to specific hosts via the root is specified using other means (the Route Information Option) and the relation to OF is not well defined and in my opinion artificial. >If you want to signal something to the OF using the G bit, leave it open. I have no problem leaving it open. But I think the reason has to be right. Richard, on the other hand, wants it to be closed in other direction (always set it to 1) (I dont agree with his reasoning though). Thanks Mukul ----- Original Message ----- From: "Pascal Thubert (pthubert)" <pthubert@cisco.com> To: "Mukul Goyal" <mukul@uwm.edu>, "Richard Kelsey" <richard.kelsey@ember.com> Cc: roll@ietf.org Sent: Wednesday, April 4, 2012 9:05:28 AM Subject: RE: [Roll] [roll] #86: G flag: do we need that text? Hello Mukul Floating vs. Grounded depends on the goal of the DODAG. I asked you and will ask again what is your goal? If the goal is to reach the root, then G is 1... If you want to signal something to the OF using the G bit, leave it open. Cheers, Pascal -----Original Message----- From: roll-bounces@ietf.org [mailto:roll-bounces@ietf.org] On Behalf Of Mukul Goyal Sent: mercredi 4 avril 2012 15:55 To: Richard Kelsey Cc: roll@ietf.org Subject: Re: [Roll] [roll] #86: G flag: do we need that text? >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. 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. Thanks Mukul ----- 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
- [Roll] [roll] #86: G flag: do we need that text? roll issue tracker
- Re: [Roll] [roll] #86: G flag: do we need that te… roll issue tracker
- Re: [Roll] [roll] #86: G flag: do we need that te… Richard Kelsey
- Re: [Roll] [roll] #86: G flag: do we need that te… Mukul Goyal
- Re: [Roll] [roll] #86: G flag: do we need that te… Pascal Thubert (pthubert)
- Re: [Roll] [roll] #86: G flag: do we need that te… Mukul Goyal
- Re: [Roll] [roll] #86: G flag: do we need that te… Richard Kelsey
- Re: [Roll] [roll] #86: G flag: do we need that te… Mukul Goyal
- Re: [Roll] [roll] #86: G flag: do we need that te… Mukul Goyal
- Re: [Roll] [roll] #86: G flag: do we need that te… Richard Kelsey
- Re: [Roll] [roll] #86: G flag: do we need that te… Pascal Thubert (pthubert)
- Re: [Roll] [roll] #86: G flag: do we need that te… Mukul Goyal
- Re: [Roll] [roll] #86: G flag: do we need that te… Michael Richardson
- Re: [Roll] [roll] #86: G flag: do we need that te… Philip Levis
- Re: [Roll] [roll] #86: G flag: do we need that te… Pascal Thubert (pthubert)
- Re: [Roll] [roll] #86: G flag: do we need that te… Mukul Goyal
- Re: [Roll] [roll] #86: G flag: do we need that te… Pascal Thubert (pthubert)
- Re: [Roll] [roll] #86: G flag: do we need that te… Mukul Goyal
- Re: [Roll] [roll] #86: G flag: do we need that te… Pascal Thubert (pthubert)
- Re: [Roll] [roll] #86: G flag: do we need that te… roll issue tracker
- Re: [Roll] [roll] #86: G flag: do we need that te… roll issue tracker
- Re: [Roll] [roll] #86: G flag: do we need that te… roll issue tracker
- Re: [Roll] [roll] #86: G flag: do we need that te… JP Vasseur