Re: [Roll] WGLC for draft-ietf-roll-efficient-npdao-03

"Liubing (Remy)" <remy.liubing@huawei.com> Tue, 07 August 2018 03:28 UTC

Return-Path: <remy.liubing@huawei.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 97F09130E27 for <roll@ietfa.amsl.com>; Mon, 6 Aug 2018 20:28:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kO8BypypOpF8 for <roll@ietfa.amsl.com>; Mon, 6 Aug 2018 20:28:54 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E023C130E52 for <roll@ietf.org>; Mon, 6 Aug 2018 20:28:53 -0700 (PDT)
Received: from lhreml708-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id A07F2F5B3EC1E for <roll@ietf.org>; Tue, 7 Aug 2018 04:28:46 +0100 (IST)
Received: from DGGEMM403-HUB.china.huawei.com (10.3.20.211) by lhreml708-cah.china.huawei.com (10.201.108.49) with Microsoft SMTP Server (TLS) id 14.3.399.0; Tue, 7 Aug 2018 04:28:47 +0100
Received: from DGGEMM526-MBS.china.huawei.com ([169.254.7.233]) by DGGEMM403-HUB.china.huawei.com ([10.3.20.211]) with mapi id 14.03.0399.000; Tue, 7 Aug 2018 11:28:44 +0800
From: "Liubing (Remy)" <remy.liubing@huawei.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>, "rahul.ietf@gmail.com" <rahul.ietf@gmail.com>
Thread-Topic: [Roll] WGLC for draft-ietf-roll-efficient-npdao-03
Thread-Index: AQHUE3sxUkAU3cL/ukeeKn95uU4yOqSz0WjQ
Date: Tue, 07 Aug 2018 03:28:44 +0000
Message-ID: <BB09947B5326FE42BA3918FA28765C2EE57330@dggemm526-mbs.china.huawei.com>
References: <CAP+sJUd16DitmEodnJ9Djee39kr3wV0O4h+xiwjq_w2+MHdZkw@mail.gmail.com>
In-Reply-To: <CAP+sJUd16DitmEodnJ9Djee39kr3wV0O4h+xiwjq_w2+MHdZkw@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.180.83]
Content-Type: multipart/alternative; boundary="_000_BB09947B5326FE42BA3918FA28765C2EE57330dggemm526mbschina_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/yl2A5-6ive3_KejWd3PXcSjvOrU>
Subject: Re: [Roll] WGLC for draft-ietf-roll-efficient-npdao-03
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.27
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: <https://mailarchive.ietf.org/arch/browse/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, 07 Aug 2018 03:28:57 -0000

Hello Roll, Rahul and co-authors,

After reading the draft-ietf-roll-efficient-04, I found this draft useful. The problems, motivation and solutions are described quite clearly.

I have some minor comments:


1.       Does this draft require a new MOP to distinguish the original storing mode MOP?

2.       In the second paragraph of section 4.1, “In this case, Node A which is the common ancestor node for node D along the two paths (previous and new), may generate a DCO which traverses downwards in the network.” “traverses downwards in the network” should be clarified as “traverses downwards along the previous route”.

3.       The title of section 4.2 might be misleading. It proposes an update of transit information option instead of the DAO body itself. When reading the second paragraph of this section, I thought there was update to the DAO message body. The term “transit container option” should be “transit information option”?

4.       In section 4.4.1, how do dependent nodes know that the route is changed, so that the ‘I’ bit is set correctly?

Best regards,
Remy

From: Roll [mailto:roll-bounces@ietf.org] On Behalf Of Ines Robles
Sent: Wednesday, July 04, 2018 5:41 PM
To: roll <roll@ietf.org>; consultancy@vanderstok.org
Subject: [Roll] WGLC for draft-ietf-roll-efficient-npdao-03

Dear all,

A Working Group Last call (WGLC) starts today (04/07) until 20/07 for draft-ietf-roll-efficient-npdao-03

The draft is available here:
https://datatracker.ietf.org/doc/draft-ietf-roll-efficient-npdao/

Please review this draft to see if you think that it is ready for publication and send comments to the list stating your view.


Thank you very much in advance,

Ines and Peter