Re: [Roll] suggested addition to draft-ietf-roll-efficient-npdao

Rahul Arvind Jadhav <rahul.jadhav@huawei.com> Fri, 30 August 2019 07:04 UTC

Return-Path: <rahul.jadhav@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 90095120170 for <roll@ietfa.amsl.com>; Fri, 30 Aug 2019 00:04:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 CzrF_ZcdzlgV for <roll@ietfa.amsl.com>; Fri, 30 Aug 2019 00:04:06 -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 0B001120113 for <roll@ietf.org>; Fri, 30 Aug 2019 00:04:06 -0700 (PDT)
Received: from LHREML711-CAH.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id D2CECA55929A0B8C7B28 for <roll@ietf.org>; Fri, 30 Aug 2019 08:04:03 +0100 (IST)
Received: from lhreml713-chm.china.huawei.com (10.201.108.64) by LHREML711-CAH.china.huawei.com (10.201.108.34) with Microsoft SMTP Server (TLS) id 14.3.408.0; Fri, 30 Aug 2019 08:04:03 +0100
Received: from lhreml713-chm.china.huawei.com (10.201.108.64) by lhreml713-chm.china.huawei.com (10.201.108.64) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Fri, 30 Aug 2019 08:04:03 +0100
Received: from BLREML406-HUB.china.huawei.com (10.20.4.43) by lhreml713-chm.china.huawei.com (10.201.108.64) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1713.5 via Frontend Transport; Fri, 30 Aug 2019 08:04:03 +0100
Received: from BLREML503-MBX.china.huawei.com ([169.254.9.145]) by BLREML406-HUB.china.huawei.com ([10.20.4.43]) with mapi id 14.03.0439.000; Fri, 30 Aug 2019 12:33:55 +0530
From: Rahul Arvind Jadhav <rahul.jadhav@huawei.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: suggested addition to draft-ietf-roll-efficient-npdao
Thread-Index: AdVe/YcA7dtmnImrSGKYwVT3ZLHQqAAAaBpQ
Date: Fri, 30 Aug 2019 07:03:54 +0000
Message-ID: <982B626E107E334DBE601D979F31785C5DFBB52A@BLREML503-MBX.china.huawei.com>
References: <MN2PR11MB3565C4909E1E1327A640D6BDD8BD0@MN2PR11MB3565.namprd11.prod.outlook.com>
In-Reply-To: <MN2PR11MB3565C4909E1E1327A640D6BDD8BD0@MN2PR11MB3565.namprd11.prod.outlook.com>
Accept-Language: en-IN, zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.61.109.81]
Content-Type: multipart/alternative; boundary="_000_982B626E107E334DBE601D979F31785C5DFBB52ABLREML503MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/iBAtFzF3AO3CA2D9EHtAqeYGWLA>
Subject: Re: [Roll] suggested addition to draft-ietf-roll-efficient-npdao
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 30 Aug 2019 07:04:09 -0000

The DCO could be initiated for regular route invalidation due to path changes or because of management decision. The status code can help understand the reason for initiating the DCO. I like the idea of this.

However, I don't know, procedurally, what it means to changing the draft at this stage.

The changes to draft would include new IANA considerations for the status field.

From: Roll [mailto:roll-bounces@ietf.org] On Behalf Of Pascal Thubert (pthubert)
Sent: 30 August 2019 14:43
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Subject: [Roll] suggested addition to draft-ietf-roll-efficient-npdao

Dear all ;

I know it's late but I'd suggest an addition to draft-ietf-roll-efficient-npdao. There's a reserved field in the DCO.
My suggestion is to use it to transport RPL DAO-ACK status values as defined in RFC 6550. This way we can signal the reason of the DCO to the node.
This will become significant with the RPL-unaware leaves draft, so we can rebuild a NA(EARO) with a non-zero status based on a DCO.

Else the RUL draft will have to update efficient NP DAO, which does not look as good.

Any objection to this?

Pascal

   0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     | RPLInstanceID |K|D|   Flags   |   Reserved    | DCOSequence   |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                                                               |
     +                                                               +
     |                                                               |
     +                            DODAGID(optional)                  +
     |                                                               |
     +                                                               +
     |                                                               |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |   Option(s)...
     +-+-+-+-+-+-+-+-+