Re: [Lsr] draft-ietf-isis-mpls-elc-07

<> Wed, 04 September 2019 23:15 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D35EF120143 for <>; Wed, 4 Sep 2019 16:15:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id kfrR-mvPk8r1 for <>; Wed, 4 Sep 2019 16:15:00 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0620612007A for <>; Wed, 4 Sep 2019 16:15:00 -0700 (PDT)
Received: from (unknown [xx.xx.xx.11]) by (ESMTP service) with ESMTP id 46P05t2kdmz8tK8; Thu, 5 Sep 2019 01:14:58 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.38]) by (ESMTP service) with ESMTP id 46P05t1rjvzCqkN; Thu, 5 Sep 2019 01:14:58 +0200 (CEST)
Received: from OPEXCAUBMA3.corporate.adroot.infra.ftgroup ([fe80::90fe:7dc1:fb15:a02b]) by OPEXCAUBM5C.corporate.adroot.infra.ftgroup ([fe80::393d:418c:3f1d:991d%21]) with mapi id 14.03.0468.000; Thu, 5 Sep 2019 01:14:58 +0200
From: <>
To: Uma Chunduri <>, "" <>
Thread-Topic: draft-ietf-isis-mpls-elc-07
Thread-Index: AdVdzjaWAHP07ic1Rraz/826XoSTqQFpj7Tw
Date: Wed, 4 Sep 2019 23:14:57 +0000
Message-ID: <4460_1567638898_5D704572_4460_60_1_9E32478DFA9976438E7A22F69B08FF924D9FAFDB@OPEXCAUBMA3.corporate.adroot.infra.ftgroup>
References: <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_9E32478DFA9976438E7A22F69B08FF924D9FAFDBOPEXCAUBMA3corp_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [Lsr] draft-ietf-isis-mpls-elc-07
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 04 Sep 2019 23:15:03 -0000

Hi Uma,

There was a discussion on this topic. I think this was agreed during Chicago's IETF if I remember correctly.
The outcome of the discussion was that if an implementation is able to read N labels, this does not mean that it is actually able to hash based on these N labels. So we needed something which combines the ability of reading + doing an action. That's why the ERLD has been defined instead of the base RLD which was foreseen at first stages of the draft.
This implies that there is a possibility to create additional RLDs that may have other applications than entropy.


From: Lsr [] On Behalf Of Uma Chunduri
Sent: Wednesday, August 28, 2019 20:38
Subject: [Lsr] draft-ietf-isis-mpls-elc-07

Can anybody tell what was the conclusion (if any) in previous discussions in various WGs on why the readable label depth in an LSR has to be entropy label specific ?

IOW can we just modify this as "readable label depth" as opposed to "entropy readable label depth" ?
This would allow any other special purpose label inserted in the stack and would be at par with current MSD type "Base MPLS Imposition MSD" ( ).

Uma C.


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.