Re: [Roll] I-D Action: draft-ietf-roll-enrollment-priority-09.txt Thu, 21 September 2023 11:05 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7C672C151088 for <>; Thu, 21 Sep 2023 04:05:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Status: No, score=-2.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 36YbrbdfLsNH for <>; Thu, 21 Sep 2023 04:05:16 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E9837C14EB19 for <>; Thu, 21 Sep 2023 04:05:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;;; q=dns/txt; s=orange002; t=1695294316; x=1726830316; h=to:subject:date:message-id:references:in-reply-to: mime-version:content-transfer-encoding:from; bh=tdL2+BdJ6vkKBpd0MB2tkJF58oykxmPvelCiNtm1W5E=; b=PKV3UaB45hTxUFbSYSsFkQ64symj1cmJXElYSz8tMZSvC7+31gwvDlP3 nciMzW9qw4vEI6hITRX6zhpWNVcOVOM5q0MyAcTLRYVDX+gR1C/t3s2PJ lrbECSJ99nkoocG8OpDKAagxZxRTysyMctjSwDcHVFo4AZvLP7jTOaD4F JCz15bNO1QWKCVa0P3cp2D5D5UKWxaQgsooK5YVbJwaL/VoYnuRXiZtmp 5Y5b6ECSlU20Qdm3SEgiJ+kzfUtEaTBwex8XUPNyniNpkliFHsulnmqGu RMAqtQOFGC9NyxTI0X0H/Ac0Xvwd/5weEzfNDkqwIf2agilNDY9EbjPgy w==;
Received: from unknown (HELO ([x.x.x.x]) by with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Sep 2023 13:05:13 +0200
Received: from unknown (HELO OPE16NORMBX405.corporate.adroot.infra.ftgroup) ([x.x.x.x]) by with ESMTP/TLS/ECDHE-RSA-AES128-GCM-SHA256; 21 Sep 2023 13:05:14 +0200
Received: from OPE16NORMBX408.corporate.adroot.infra.ftgroup [x.x.x.x] by OPE16NORMBX405.corporate.adroot.infra.ftgroup [x.x.x.x] with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.32; Thu, 21 Sep 2023 13:05:13 +0200
Received: from OPE16NORMBX408.corporate.adroot.infra.ftgroup ([x.x.x.x]) by OPE16NORMBX408.corporate.adroot.infra.ftgroup ([x.x.x.x]) with mapi id 15.01.2507.032; Thu, 21 Sep 2023 13:05:13 +0200
X-IronPort-AV: E=Sophos;i="6.03,165,1694728800"; d="scan'208";a="42720290"
To: Routing Over Low power and Lossy networks <>, Michael Richardson <>
Thread-Topic: [Roll] I-D Action: draft-ietf-roll-enrollment-priority-09.txt
Thread-Index: AQHZiD44kgOt0R5G60++l5Wi1hxjwa9dajqAgAJE1QCAAIUJgIAA8egAgAhi7gCAAEwCAIC8DUtQ
Date: Thu, 21 Sep 2023 11:05:13 +0000
Message-ID: <>
References: <> <4198.1684279709@localhost> <> <26567.1684433011@localhost> <> <2927978.1684946010@dyas> <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Archived-At: <>
Subject: Re: [Roll] I-D Action: draft-ietf-roll-enrollment-priority-09.txt
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Routing Over Low power and Lossy networks <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 21 Sep 2023 11:05:20 -0000

Hello Michael, all,

I just reviewed the draft (as it appears on GitHub today) and have three comments:
- size of the field DODAG_Size: it is specified to be 12 bits, but then there is a full paragraph which explains why DODAG_Size can only be a rough approximation. Would 4 bits for DODAG_Size be enough (accuracy to 8-12%)? That would save a full byte in the option. At a time when we try to compress IoT traffic, pretending the apparent entropy is those extra 8 bits is information sounds suboptimal
- Section 3.2 "Option Processing": the discussion about what a 6LR should do when it receives a DIO with the new option seems to pertain to DIOs received from a DODAG the 6LR is already part of. Should we say something about receiving DIOs from DODAGs the 6LR is currently not part of? Could the option be a reason to switch to another DODAG? In that case, should a 6LR maintain vl's for DODAGs it is currently not part of?
- the new option does not have a name. It is referred to as "the option", "this option" in the draft. I think it should be called something, and this something should be written in this draft. What could this something be? Min_Enrollment_Priority comes to mind, but there is also the DODAG size information. Any ideas?

Best regards


-----Original Message-----
From: Roll [] On Behalf Of Konrad Iwanicki
Sent: 24 May 2023 23:06
To: Michael Richardson <>
Cc:; Huimin She <>
Subject: Re: [Roll] I-D Action: draft-ietf-roll-enrollment-priority-09.txt

Great. Good job! I have just corrected a few typos I noticed. You may want to double-check.

- Konrad Iwanicki.

On 24/05/2023 18:33, Michael Richardson wrote:
> Konrad Iwanicki <> wrote:
>      > On 18/05/2023 20:03, Michael Richardson wrote:
>      >> Konrad Iwanicki <> wrote: > Should I go once more
>      >> over the draft?
>      >>
>      >> Sure, I need to do a top-to-bottom read-through myself.
>      > I went through the entire draft a few times. It is definitely much
>      > clearer now. I did some more editing, though (mostly
>      > clarifications/reordering and minor copy-editing):
>      > 
> okay, merged, and I cleared/checked the other edits/pull requests.
> I will post a new version on Monday.
> --
> Michael Richardson <>, Sandelman Software Works
>   -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*

Roll mailing list
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.