%% You should probably cite rfc9089 instead of this I-D. @techreport{ietf-ospf-mpls-elc-09, number = {draft-ietf-ospf-mpls-elc-09}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-ospf-mpls-elc/09/}, author = {Xiaohu Xu and Sriganesh Kini and Peter Psenak and Clarence Filsfils and Stephane Litkowski}, title = {{Signaling Entropy Label Capability and Entropy Readable Label-stack Depth Using OSPF}}, pagetotal = 7, year = 2019, month = sep, day = 3, abstract = {Multiprotocol Label Switching (MPLS) has defined a mechanism to load- balance traffic flows using Entropy Labels (EL). An ingress Label Switching Router (LSR) cannot insert ELs for packets going into a given tunnel unless an egress LSR has indicated via signaling that it has the capability to process ELs, referred to as Entropy Label Capability (ELC), on that tunnel. In addition, it would be useful for ingress LSRs to know each LSR's capability of reading the maximum label stack depth and performing EL-based load-balancing, referred to as Entropy Readable Label Depth (ERLD). This document defines a mechanism to signal these two capabilities using OSPF and OSPFv3. These mechanism is particularly useful in the environment where Segment Routing (SR) is used, where label advertisements are done via protocols like OSPF and OSPFv3.}, }