[Roll] Unassigned bits of the ... are reserved
Rahul Arvind Jadhav <rahul.jadhav@huawei.com> Tue, 30 April 2019 10:01 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 8213E120125 for <roll@ietfa.amsl.com>; Tue, 30 Apr 2019 03:01:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 0VvR4zMcajbt for <roll@ietfa.amsl.com>; Tue, 30 Apr 2019 03:00:58 -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 A305B12029C for <roll@ietf.org>; Tue, 30 Apr 2019 03:00:58 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id D52399E931EC7F4CA9A9 for <roll@ietf.org>; Tue, 30 Apr 2019 11:00:56 +0100 (IST)
Received: from BLREML703-CAH.china.huawei.com (10.20.4.172) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 30 Apr 2019 11:00:56 +0100
Received: from BLREML503-MBX.china.huawei.com ([169.254.9.86]) by blreml703-cah.china.huawei.com ([::1]) with mapi id 14.03.0439.000; Tue, 30 Apr 2019 15:30:43 +0530
From: Rahul Arvind Jadhav <rahul.jadhav@huawei.com>
To: roll <roll@ietf.org>
Thread-Topic: Unassigned bits of the ... are reserved
Thread-Index: AdT/OaA2dn6+1tMPS1mhUStT51rH4A==
Date: Tue, 30 Apr 2019 10:00:43 +0000
Message-ID: <982B626E107E334DBE601D979F31785C5DE82645@BLREML503-MBX.china.huawei.com>
Accept-Language: en-IN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.18.157.44]
Content-Type: multipart/alternative; boundary="_000_982B626E107E334DBE601D979F31785C5DE82645BLREML503MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/KLIxkhH3SB4sOc0jrwpcvx_94go>
Subject: [Roll] Unassigned bits of the ... are reserved
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: Tue, 30 Apr 2019 10:01:00 -0000
Hello ROLL, RPL (RFC6550) base objects and options have a couple of sentences in the context saying, "Unassigned bits of the [MSG] are reserved. They MUST be set to zero on transmission and MUST be ignored on reception." This text is present for all base objects including, DIO/DAO/DAO-ACK/CC. Also it is present for following options, RIO/PIO/Transit Information Option/Solicited Information But it is not present for following options, DODAG Configuration/DAG Metric Container/Pad1/PadN/RPL Target. Want to understand which bits are referenced by this statement and why for certain options it is not mentioned? <This point was commented upon by Alvaro during review of draft-ietf-roll-efficient-npdao-09> Regards, Rahul
- [Roll] Unassigned bits of the ... are reserved Rahul Arvind Jadhav
- Re: [Roll] Unassigned bits of the ... are reserved Pascal Thubert (pthubert)
- Re: [Roll] Unassigned bits of the ... are reserved Michael Richardson