%% You should probably cite rfc9089 instead of this I-D. @techreport{ietf-ospf-mpls-elc-15, number = {draft-ietf-ospf-mpls-elc-15}, 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/15/}, author = {Xiaohu Xu and Sriganesh Kini and Peter Psenak and Clarence Filsfils and Stephane Litkowski and Matthew Bocci}, title = {{Signaling Entropy Label Capability and Entropy Readable Label Depth Using OSPF}}, pagetotal = 8, year = 2020, month = jun, day = 1, 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 Label Switched Path (LSP) unless an egress LSR has indicated via signaling that it has the capability to process ELs, referred to as the Entropy Label Capability (ELC), on that LSP. In addition, it would be useful for ingress LSRs to know each LSR's capability for 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 OSPFv2 and OSPFv3, and Border Gateway Protocol - Link State (BGP-LS).}, }