Re: [Lsr] Signalling ERLD (ISIS, OSPF and BGP-LS)

"Van De Velde, Gunter (Nokia - BE/Antwerp)" <> Wed, 13 June 2018 08:24 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6664C130E0E; Wed, 13 Jun 2018 01:24:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Ux_AmkNdv8M6; Wed, 13 Jun 2018 01:24:41 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4116A130E05; Wed, 13 Jun 2018 01:24:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector1-nokia-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=RWSHcVsbfF19wodCWRVq3JbI7J+MFT7bN4ifBAUtjwc=; b=RstFErEA8TQgZUtKpAcDY6Vg9XSEewqJn2Ns/28Qd2f8yxp6hsp2bLhHNcnUiX7tVy/DEGlaVkCHcFULDN7pWhfDImdaYGE+ajOlJYw/0EI9X2PQXXSmWrSVxrAAjxM3lumdcq83e+QK5XDbRkWvlvJhA+Ar1hTvtV+a226l6Ao=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.863.6; Wed, 13 Jun 2018 08:24:38 +0000
Received: from ([fe80::8d31:126e:da20:2edf]) by ([fe80::8d31:126e:da20:2edf%5]) with mapi id 15.20.0863.010; Wed, 13 Jun 2018 08:24:38 +0000
From: "Van De Velde, Gunter (Nokia - BE/Antwerp)" <>
To: "Ketan Talaulikar (ketant)" <>, "" <>, "" <>, "" <>
Thread-Topic: Signalling ERLD (ISIS, OSPF and BGP-LS)
Thread-Index: AdQCVS4zJNJrYGL7RvyJWFnJWJ9mLgAhqsxQAAPpAwA=
Date: Wed, 13 Jun 2018 08:24:38 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: [2a02:1810:4d67:a00:18ba:dbe2:5c03:c618]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM5PR0701MB3011; 7:BW/febFJMNMqaaLsWQpM2m71y8J1TNgRq8zKvjMMuR+iwwcKXS2bkbOUXk8w/GT4TVGEM34ym0tLuqQkkU9XGoo0QYbpm2y3/zGD7ZT36wDh3S1wsiPaRgHymtjJyAf+Obl02gIq+PyW/aUN5lOPuIrY1SbTZ0rAckMXFT6qjn8aZLbRWik80zUZS3tah0Rddkg4ya4p2+9g4WsU5fZVl7o+5sc8StCc5yDstm9MDTDRU1mpT8qJjHWchq3MyllI
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-ht: Tenant
X-MS-Office365-Filtering-Correlation-Id: 02ba9ca0-14f0-48d6-aefc-08d5d1071ab8
x-microsoft-antispam: UriScan:(109105607167333); BCL:0; PCL:0; RULEID:(7020095)(4652020)(8989080)(48565401081)(5600026)(711020)(4534165)(4627221)(201703031133081)(201702281549075)(8990040)(2017052603328)(7193020); SRVR:AM5PR0701MB3011;
x-ms-traffictypediagnostic: AM5PR0701MB3011:
authentication-results: spf=none (sender IP is );
x-microsoft-antispam-prvs: <>
x-exchange-antispam-report-test: UriScan:(120809045254105)(82608151540597)(109105607167333)(95692535739014);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(10201501046)(3231254)(11241501184)(806099)(944501410)(52105095)(3002001)(6055026)(149027)(150027)(6041310)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123560045)(20161123562045)(6072148)(201708071742011)(7699016); SRVR:AM5PR0701MB3011; BCL:0; PCL:0; RULEID:; SRVR:AM5PR0701MB3011;
x-forefront-prvs: 07025866F6
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(346002)(376002)(366004)(39380400002)(39860400002)(189003)(199004)(13464003)(5660300001)(476003)(966005)(14454004)(8936002)(2201001)(3660700001)(486006)(105586002)(74316002)(7736002)(97736004)(106356001)(5250100002)(446003)(478600001)(46003)(305945005)(3280700002)(2906002)(2501003)(9686003)(229853002)(81166006)(186003)(25786009)(33656002)(6116002)(55016002)(6436002)(99286004)(53936002)(2900100001)(11346002)(110136005)(6306002)(76176011)(86362001)(316002)(59450400001)(68736007)(6246003)(8676002)(7696005)(81156014)(6506007)(53546011)(102836004); DIR:OUT; SFP:1102; SCL:1; SRVR:AM5PR0701MB3011;; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None ( does not designate permitted sender hosts)
x-microsoft-antispam-message-info: 9p6MeyomhrKnuvD5UBIlG13RZW/MKx6+nyeC8YUgyR1HHnso1Isdb4usR6ovBUUmpT1CCyp0M2LcPt8b3xmO9a8O1l19HIj8lgLECVOFiEGHtruulHETzfWuuD2mn4v5OWafeihxTg+W9Jam0eWO+qsDUO+QQKYBZbAlVy3MXHYedY4SpEc5lQKzC/jk5Y7JhyMPioJ7CsaIs4RkSydZD1vZzz3FJoM4qj7xhkNKw79gS5B4C8WpRaxq61PN2FSE
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 02ba9ca0-14f0-48d6-aefc-08d5d1071ab8
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Jun 2018 08:24:38.5142 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5PR0701MB3011
Archived-At: <>
Subject: Re: [Lsr] Signalling ERLD (ISIS, OSPF and BGP-LS)
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Link State Routing Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 13 Jun 2018 08:24:47 -0000

Indeed, the debate that made BGP-LS to go down the ERLD path is of pragmatic motivation.

The major Readable Label Depth use-case is entropy. Hence, if the ERLD TLV is available, then ELC can be implicitly assumed. No pragmatic reason to signal separately, as it just make things more complex then should be. 

>From a holistic perspective having something similar, yet different, in both IGP and BGP-LS encoding 
seems to make little sense and only bring confusion (router/controller implementers and network operators). 

The ways to address this in IGP and BGP-LS going forward:
1) do nothing and leave all as it is (it has potential to create massive confusion) 
2) only signal ERLD TLV in IGP and BGP
3) signal ELC TLV and RLD TLV (unclear pragmatic value of explicit signaling of ELC TLV compared to option (2)) 
4) signal ELC TLV, RLD TLV and ERLD TLV (it has all, but is much much more complex as option (2))

I believe that option (2) is the best option:
* it bring the needed readable label depth value to operators 
* most simple solution for implementers (routers and controller)  
* easy to understand with no confusion
* is compliant with draft-ietf-mpls-spring-entropy-label-10


-----Original Message-----
From: Ketan Talaulikar (ketant) [] 
Sent: Wednesday, June 13, 2018 08:05
To: Van De Velde, Gunter (Nokia - BE/Antwerp) <>;;;
Subject: RE: Signalling ERLD (ISIS, OSPF and BGP-LS)

Hi Gunter,

The difference in IGP signalling seems to be because the ELC is a capability which is advertised differently than ERLD which is a limit. Are you saying that ELC does not have value by itself without the ERLD?

IMHO it makes sense to retain ELC as capability of the router (as specified in the IGP specs) and position ERLD as a MSD sub-type for indicating the limit. This way we have the flexibility of signalling ERLD both per node and per ingress link/LC level.


-----Original Message-----
From: Idr <> On Behalf Of Van De Velde, Gunter (Nokia - BE/Antwerp)
Sent: 12 June 2018 19:28
Subject: [Idr] Signalling ERLD (ISIS, OSPF and BGP-LS)

In LSR WG the following drafts document the signaling of ELC and RLD:
* draft-ietf-ospf-mpls-elc
* draft-ietf-isis-mpls-elc

When exporting this information using BGP-LS encoding to a controller, there is need for BGP-LS extension by means of new TLVs.

BGP-LS is signaling ERLD (entropy capable readable label depth) ISIS/OSPF is signaling individually ELC and RLD

I was working upon the IANA section, and discovered some inconsistency that should be addressed:
* Why is IGP signaling individual ELC and RLD? ERLD is what was decided upon (
* What are the plans to request IANA code points for these drafts?
* (E)RLD seems to have meaning only from NODE perspective, (I assume that LINK ERLD is not of any value at all, is that a correct assumption?)


-----Original Message-----
From: Idr [] On Behalf Of
Sent: Tuesday, June 12, 2018 15:25
Subject: [Idr] I-D Action: draft-ietf-idr-bgp-ls-segment-routing-rld-02.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Inter-Domain Routing WG of the IETF.

        Title           : Signalling ERLD using BGP-LS
        Authors         : Gunter Van de Velde
                          Wim Henderickx
                          Matthew Bocci
                          Keyur Patel
	Filename        : draft-ietf-idr-bgp-ls-segment-routing-rld-02.txt
	Pages           : 6
	Date            : 2018-06-12

   This document defines the attribute encoding to use for BGP-LS to
   expose ERLD "Entropy capable Readable Label Depth" from a node to a
   centralised controller (PCE/SDN).

The IETF datatracker status page for this draft is:

There are also htmlized versions available at:

A diff from the previous version is available at:

Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at

Internet-Drafts are also available by anonymous FTP at:

Idr mailing list

Idr mailing list