[Roll] New column in ND status?

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Tue, 15 December 2020 06:58 UTC

IronPort-PHdr: 9a23:Tgf8VBzqCu/qbtXXCy+N+z0EezQntrPoPwUc9psgjfdUf7+++4j5ZRWDt/pohV7NG47c7qEMh+nXtvXmXmoNqdaEvWsZeZNBHxkClY0NngMmDcLEbC+zLPPjYyEgWsgXUlhj8iK0NEFUHID1YFiB6nG35CQZTxP4Mwc9L+/pG4nU2sKw0e36+5DabwhSwjSnZrYnJxStpgKXvc4T0oY=
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Alvaro Retana <aretana.ietf@gmail.com>, Elwyn Davies <elwynd@dial.pipex.com>
CC: "roll@ietf.org" <roll@ietf.org>
Thread-Topic: New column in ND status?
Thread-Index: AdbSr1UnlvUuSAbpSuOVrAsLk8a2tg==
Date: Tue, 15 Dec 2020 06:57:08 +0000
Deferred-Delivery: Tue, 15 Dec 2020 06:56:54 +0000
Message-ID: <CO1PR11MB48814C6A0407AD9754CFE0DCD8C60@CO1PR11MB4881.namprd11.prod.outlook.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 0953a11d-9a0e-4e12-a48e-08d8a0c6b26c
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Dec 2020 06:57:32.9024 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 0gOyuvzIXfLY78r2ZPb+3AdqO4c/dnVPITgeA7qpwMmIRzVb/LEj92tj3icVsxKhyqu/hbJvqSBL8z9cjS45EA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR1101MB2367
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.13, xch-rcd-003.cisco.com
X-Outbound-Node: alln-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/Rc-f-asgdPvXhprbEI5TryptyiI>
Subject: [Roll] New column in ND status?
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, 15 Dec 2020 06:58:54 -0000

Hello Alvaro

Elwyn has a suggestion that I wanted to run by you:

>> s6.3, next to last para. s8 and s 12.2:  In view of the statement in s6.3:
>> The RPL Root MUST set the 'E' flag to 1 for all rejection and unknown status
>> codes. The status codes in the 1-10 range [RFC8505] are all considered
>> rejections. I think that IANA should be requested to add a column to the EARO
>> status codes registry being modified by s12.2 to add a column that identifies a
>> status code as a rejection or otherwise.   Some words in s8 may be appropriate.

> Well that would require normative text on the 6LoWPAN part.
> I guess we can do that at the next iteration of a 6LoWPAN ND specification.
> For now what we specify is that from the RPL perspective the listed codes denote
> a failure such that the RPL operation that wraps it cannot happen and that's enough for us.

ED>  While I understand that it would be polite to involve 6LoWPAN, WGs don't 'own' RFCs and their associated IANA registries.  Since this draft 'needs' the extra information I personally wouldn't see a problem in asking for the extra column. It doesn't break anythng 6LoWPAN are doing AFAICS. Anyway that's not my call...  ask your AD.

What do you think?


Pascal

[Roll] New column in ND status? Pascal Thubert (pthubert)
Re: [Roll] New column in ND status? Alvaro Retana