[Idr] Splitting draft-ietf-idr-entropy-label into two documents to allow progress

John Scudder <jgs@juniper.net> Tue, 14 October 2025 21:53 UTC

From: John Scudder <jgs@juniper.net>
To: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: Splitting draft-ietf-idr-entropy-label into two documents to allow progress
Thread-Index: AQHcPVT2cPxouRwaCUursdpLEORWaQ==
Date: Tue, 14 Oct 2025 21:53:23 +0000
Message-ID: <9765B574-6FB9-4DDB-A8AE-632046368A5B@juniper.net>
References: <176047720841.947400.3162905508314535598@dt-datatracker-84f8f646b-tg6mn>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: cccVsPSxNmwXr86nZKzj7LYpHYHcQFI5NPFXs9IU62gGZJjuWBr0H58ouUkde8Soj62MHyxGUrb+0iAQs29lz7N1Rt4qASkvXa7i/Cg15uVBE46zQmew20VTuG0jbLZ2K3YV3ZV225JuC88rm4+amDL6euB0SYwX655n2aA7y1HIvy3OW9Lhj5WDgbyzl6ByKhkzHe6+S+A1ue0c2vIc8f6R/+pttvtj8BIIB+IsVuPQJ2oQGcaWSPR5ljRG37GeJYoUkIoQA1UUkowkEvU+Kyot6Dib3s4ufXKUmUBnWn2jyMXTjN8C5vHUhtxhNLdyhOFMQMuj8n7crCuc+jzhwNDyZns2cowvXm+dTnuhbuArRIi3ZyYl8ekoF0qKvrRP26Pn2eCgoNLisGO7D+RIhES//lPnqyecDzrYgeUFL2HMPHhxTRc6GiK9lgD1Z4G/Wvf+QQHgPVjxxj8TDcJ4A/3hoh+8L2zbI/5yYi9x5gqXyQ3JdH6Dpy3NWF6sw8y9CwOO6ief+XGa5Z05Qr0fzMrQZBhzcydAPicRAIISGwDNxMIEvCKRU54qa1vKxbq5oPIHwkBBU1hQDSSzQnX4onwfPnvd7WG5AtBYYtlrPdsoMmLWJj/heAqsLAwFE7Y8Ifxyxp8NwWyoWuKr7lqb+YzO/uoSvnjaHQzrZYz8cPb9BbKvYiMvl5OqTafb0+aEgUuyyQ3yYfu3flDp9Cz7ZS2EmaTwqXKMbxTmPE+ATfFGJn7zXDaqzXnfjsKo11WzJ1MvjjmxA8qENQs7lrdUoEc+Y+cCwW4elO8bu64pouqrqTd0F9d3Od9IAmOiYcez364i4yyOr9xO0UZROoCNY3reXmxo+5Wm9cCmFGPa4w3RMFyXvNYvwR/ptr4xKfEGd6tguvLuHKIp7n+M/+bBd1/N3DPa2YdlcAJSapaNzhPaglBSdH0T7+sn0VcxTGVfrDCQhAUocSvsVeLBaCqSWtX3XD0LIExJjSRYpmyoldcCxx8ktNb7HLEpgeFpSv/su91kxVZaHQDPBkzm2booUYfBe3l9pCJ94OO3i5k+QFZPQ5Hk1WdDy6iVOXVERWmaU81srjolr7JrbWb9GkxwqH4Kc9hQ/syXPc8f52t+irzt/dD+ynfveVClbCB5ACCvMWbnOVHTYlMW84Vrqq7yggOiWMnYMUC4K8PlReHlsHEOdv5vj/wm5474BhxD92+/Nc5NYLN71tEOT5cc7dTJ7s+NjQUBGpwazhd1SbAtWk7Y2wH9JgOofEkMjR/dPcLRrQXyBU6w3UC+s+Fwz1P3PpEL2s8mvyfFXyPJYdq3/LJKfk8ceZXB1i2mSxmezm+kNLoHooEHN6Fcp4diTI2kzxYw77BJWhv4b3kYnxbjmlBuU/qgMs+HYY5Qwa1Jmnx19HfZpRaQ7LGOH1QmiwOqvH+rNJ2mC9OFpIw39eReNeSWWSTdU5gHRnu+8J1WZLVhCM7Shsub5RLYDeRErGellQZqS/ZrV52J51XCEoO4ktRdYQe/41R3xFMwYvaTT7zHnZjSuakYYXrfrBORYfMxvbaaNiv2yCVPG36wIhAGQvuPoLNL4ZcW4R3dtEE71VOu
Content-Type: text/plain; charset="utf-8"
Content-ID: <1B23CCD979613A4190AAFA05E1487D86@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: LV8PR05MB10374.namprd05.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 07d063cc-bd09-455e-5f2e-08de0b6c1901
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Oct 2025 21:53:23.6533 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Oc6zwj2Ci7oZHDsM+Te0kY8favRB3QPfd9n1eC9R5BOtAAgzGNizWF85fLhpdFUk
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PH0PR05MB8670
X-Proofpoint-Spam-Details-Enc: AW1haW4tMjUxMDE0MDEwNiBTYWx0ZWRfX31Ao0VUAa6SZ Z4To4w7jA/1WSPoZuuBSuwzTRhIopmYrlwOgRLGkjy20K5yEqD0hlaAhD0KjQa4vlXt7JrvQI1V kvktDUzJJ5MDp/Nqni34knEzGA1r1o2nR5qBB8hq2lWArlqZSCKqGcmfpWih86WG1crvdpVRhNm 0cERa8VINV4EUmhVcZPbBRkf/Yvw+/n+2ZWIY5UxWs6C137iu/P/GI+Cusr/Tq2w4UYf7Tu9q5C cunJ5ukFqWJK/bDrS6ZC7oTmbq4N0SXiDk5QmiotpxWZZbi2ULIughVjsKXW2wjKgfaUYYPGHAE lDuUqOItaKjPFJwj86mat2adw9sUzn4O996gunKwMrehbiiapOYiuA+pwCKWC4K9tVhGcjNREhG q6Gunl0m2x4iWf3gT2QLaVESiT/8Hw==
X-Proofpoint-GUID: 6lE9R6UeiyhSXhVuyQL39pEeDjnoNm7G
X-Proofpoint-ORIG-GUID: 6lE9R6UeiyhSXhVuyQL39pEeDjnoNm7G
X-Authority-Analysis: v=2.4 cv=YNOSCBGx c=1 sm=1 tr=0 ts=68eec656 cx=c_pps a=FLJGh2IUmjoo+n/grE3sag==:117 a=z/mQ4Ysz8XfWz/Q5cLBRGdckG28=:19 a=lCpzRmAYbLLaTzLvsPZ7Mbvzbb8=:19 a=xqWC_Br6kY4A:10 a=IkcTkHD0fZMA:10 a=x6icFKpwvdMA:10 a=rhJc5-LppCAA:10 a=VkNPw1HP01LnGYTKEx00:22 a=48vgC7mUAAAA:8 a=FPZk6_SxjFhoHheoND4A:9 a=QEXdDO2ut3YA:10
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1121,Hydra:6.1.9,FMLib:17.12.80.40 definitions=2025-10-14_04,2025-10-13_01,2025-03-28_01
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 bulkscore=0 malwarescore=0 phishscore=0 impostorscore=0 adultscore=0 priorityscore=1501 spamscore=0 clxscore=1015 lowpriorityscore=0 suspectscore=0 classifier=typeunknown authscore=0 authtc= authcc= route=outbound adjust=0 reason=mlx scancount=1 engine=8.19.0-2510020000 definitions=main-2510140106
Message-ID-Hash: 525CZM33LCRFNL5GQ2VCVRCB5JW7P7DL
X-Message-ID-Hash: 525CZM33LCRFNL5GQ2VCVRCB5JW7P7DL
X-MailFrom: jgs@juniper.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-idr.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Idr] Splitting draft-ietf-idr-entropy-label into two documents to allow progress
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/J-yAgMbXWC9CsUDeqWQRT1pqC_g>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Owner: <mailto:idr-owner@ietf.org>
List-Post: <mailto:idr@ietf.org>
List-Subscribe: <mailto:idr-join@ietf.org>
List-Unsubscribe: <mailto:idr-leave@ietf.org>

Hi All,

I’ve just posted draft-scudder-idr-nhc-00, which documents the core mechanism from draft-ietf-idr-entropy-label (the "Next Hop Dependent Characteristics Attribute” or NHC). I’ve also uploaded draft-scudder-idr-elc-00, which contains the entropy label characteristic definition, an application on top of NHC; together, the two new drafts represent a split of the original draft-ietf-idr-entropy-label. As you can see from the diffs (links below) the split worked out cleanly; the intent is that if you take them together, nothing was added or subtracted (I did make some minor proofreading fixes).

The purpose of doing this split is to allow NHC to make forward progress on its standardization journey. It completed WGLC and has been parked in “waiting for implementation” status since late 2023. Since then, there have been several new applications for it. At least one of them has two implementations. So, it’s becoming problematic that the underlying spec isn’t yet a standard (for one thing, we need a registry, and can’t get it until we get an RFC number).

I suggest we make the replacements working group drafts, and place them in post-WGLC status, just like draft-ietf-idr-entropy-label. They would replace the older draft, which would then expire. In the case of NHC, we would promptly update the implementation report, after which I suggest we send it to the IESG without further ado. In the case of ELC, we’ll remain parked in “waiting for implementation” unless someone announces a second implementation, but that’s less of a problem since it’s not holding up progress for other drafts.

A URL for the NHC datatracker page is:

https://datatracker.ietf.org/doc/draft-scudder-idr-nhc/

Diff of NHC vs. draft-ietf-idr-entropy-label:

https://author-tools.ietf.org/diff?doc_1=draft-ietf-idr-entropy-label&doc_2=draft-scudder-idr-nhc

ELC datatracker page:

https://www.ietf.org/archive/id/draft-scudder-idr-elc-00.txt

Diff of ELC vs. draft-ietf-idr-entropy-label:

https://author-tools.ietf.org/diff?doc_1=draft-ietf-idr-entropy-label&doc_2=draft-scudder-idr-elc

Thanks,

—John

[Idr] Splitting draft-ietf-idr-entropy-label into… John Scudder
[Idr] Consensus call for splitting draft-ietf-idr… Susan Hares
[Idr] Re: Consensus call for splitting draft-ietf… Susan Hares