Re: [Roll] New Version Notification - draft-ietf-roll-minrank-hysteresis-of-07.txt

Matteo Paris <matteo@ember.com> Tue, 03 April 2012 13:44 UTC

Return-Path: <matteo@ember.com>
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 E8EB921F85B6 for <roll@ietfa.amsl.com>; Tue, 3 Apr 2012 06:44:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.37
X-Spam-Level:
X-Spam-Status: No, score=-3.37 tagged_above=-999 required=5 tests=[AWL=0.930, BAYES_00=-2.599, MANGLED_NAIL=2.3, 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 zJ9VQcTCtpvx for <roll@ietfa.amsl.com>; Tue, 3 Apr 2012 06:44:58 -0700 (PDT)
Received: from p01c11o148.mxlogic.net (p01c11o148.mxlogic.net [208.65.144.71]) by ietfa.amsl.com (Postfix) with ESMTP id 2659221F85B5 for <roll@ietf.org>; Tue, 3 Apr 2012 06:44:57 -0700 (PDT)
Received: from unknown [216.236.254.3] (EHLO p01c11o148.mxlogic.net) by p01c11o148.mxlogic.net(mxl_mta-6.13.0-3) with ESMTP id adefa7f4.2aaabfa05940.115682.00-563.220516.p01c11o148.mxlogic.net (envelope-from <matteo@ember.com>); Tue, 03 Apr 2012 07:44:58 -0600 (MDT)
X-MXL-Hash: 4f7afeda6f2b1065-fee6fa313787c60d6df68bbaa62cc1b941d265b1
Received: from unknown [216.236.254.3] (EHLO usmail.ember.com) by p01c11o148.mxlogic.net(mxl_mta-6.13.0-3) over TLS secured channel with ESMTP id 4defa7f4.0.115626.00-369.220370.p01c11o148.mxlogic.net (envelope-from <matteo@ember.com>); Tue, 03 Apr 2012 07:44:54 -0600 (MDT)
X-MXL-Hash: 4f7afed65883cd12-6732de025bc98d8b0f92b0b374ba77d2e8dd9373
Received: from USMAIL.hq.ember.com ([fe80::414:51ae:1b16:3f29]) by USMail.hq.ember.com ([fe80::414:51ae:1b16:3f29%10]) with mapi id 14.01.0355.002; Tue, 3 Apr 2012 09:46:29 -0400
From: Matteo Paris <matteo@ember.com>
To: Philip Levis <pal@cs.stanford.edu>
Thread-Topic: [Roll] New Version Notification - draft-ietf-roll-minrank-hysteresis-of-07.txt
Thread-Index: AQHNA7v6JbPKPVP/ZUe2ufcTZJGhzZaJe3oA
Date: Tue, 03 Apr 2012 13:46:28 +0000
Message-ID: <A0C5A83B-CF03-46A1-97C5-EBB2644B9874@ember.com>
References: <20120309180454.27147.28601.idtracker@ietfa.amsl.com> <D8AAF6F9-AE90-4AD0-B678-FF2505246D06@cs.stanford.edu> <0500582D-1326-4033-9A82-FD42BB47A29D@ember.com> <4FEF776A-4562-4FE1-9973-7627B12EDD43@cs.stanford.edu>
In-Reply-To: <4FEF776A-4562-4FE1-9973-7627B12EDD43@cs.stanford.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.81.68]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7C9F74034FF75E41850096B82003694E@ember.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <matteo@ember.com>
X-SOURCE-IP: [216.236.254.3]
X-AnalysisOut: [v=1.0 c=1 a=PvnVXCDccy0A:10 a=0lGxxKK5Fb8A:10 a=saA6nF2ZJa]
X-AnalysisOut: [AA:10 a=BLceEmwcHowA:10 a=kj9zAlcOel0A:10 a=xqWC_Br6kY4A:1]
X-AnalysisOut: [0 a=MYqPJgym4Kx47q1P90kooQ==:17 a=Y1xPKZcGYHaXi7A22PsA:9 a]
X-AnalysisOut: [=EaMLpzuPb1U7yo0XIrAA:7 a=CjuIK1q_8ugA:10]
Cc: "roll@ietf.org" <roll@ietf.org>
Subject: Re: [Roll] New Version Notification - draft-ietf-roll-minrank-hysteresis-of-07.txt
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: Tue, 03 Apr 2012 13:44:59 -0000

Hi Phil,

my question boils down to whether RPL requires members of the parent set to have lower DAGRank, or merely lower rank.  My reading of the RPL draft is that all parents must have lower DAGRank.

I get this from two clauses in the RPL draft that I quoted below.  Unfortunately both are confusingly worded.

RPL Section 3.5.1 says: "A node A has a rank less than the rank of a node B if DAGRank(A) is less than DAGRank(B)."  I believe the intention here was to say "if and only if", otherwise the clause is pointless (trivially true).

RPL Section 3.5.2 says "[F]or a node N, all parents in the DODAG parent set must be of rank less than DAGRank(N)."  Here, a rank is being compared with a DAGRank, which is nonsensical, unless "rank" actually means "DAGRank".  It would be much clearer if it said so explicitly, ie "must be of DAGRank less than DAGRank(N)."  

What is your interpretation -- are parents required to have lower rank or lower DAGRank? Perhaps the confusion is a result of some text accidentally left over from an older version of the draft.

Thanks,
Matteo

PS My emails have not been posting to the list. I'm working on it.

On Mar 16, 2012, at 5:29 PM, Philip Levis wrote:

> 
> On Mar 16, 2012, at 1:44 PM, Matteo Paris wrote:
> 
>> 
>> Hi Phil.  These changes were helpful.  But I am still unclear on the rank computation in section 3.3.  From the RPL draft:
>> 
>> RPL Section 3.5.1:  "DAGRank(rank) = floor(rank/MinHopRankIncrease)"
>> RPL Section 3.5.1:  "A node A has a rank less than the rank of a node B if DAGRank(A) is less than DAGRank(B)."
>> RPL Section 3.5.2:  "[F]or a node N, all parents in the DODAG parent set must be of rank less than DAGRank(N)."
>> RPL Section 8.2.1:  "A node's rank MUST be greater than all elements of its DODAG parent set."
>> 
>> The rank computation in MRHOF section 3.3 can result in parents P for which DAGRank(P) is not less than DAGRank(N),
>> which would seem to violate the third and fourth clauses above, given the definitions in the first two clauses.
> 
> How? I intended case 2 in 3.3 to cover this. Can you explain the edge case you see where it does not?
> 
>> 
>> One other minor question.  In the sentence, "The second case covers requirement 4..." of MRHOF section 3.3, do you mean requirement 5?
> 
> Yes! It should be requirement 5. I will fix this in the next revision. Thank you for catching it.
> 
> Phil