%% You should probably cite rfc9089 instead of this I-D. @techreport{ietf-ospf-mpls-elc-06, number = {draft-ietf-ospf-mpls-elc-06}, 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/06/}, author = {Xiaohu Xu and Sriganesh Kini and Siva Sivabalan and Clarence Filsfils and Stephane Litkowski}, title = {{Signaling Entropy Label Capability and Entropy Readable Label-stack Depth Using OSPF}}, pagetotal = 6, year = , month = , day = , 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 of processing 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), in the cases where stacked LSPs are used for whatever reasons. This document defines mechanisms to signal these two capabilities using OSPF. These mechanisms are useful when the label advertisement is also done via OSPF. In addition, this document introduces the Non-IGP Functional Capabilities TLV for advertising OSPF router's actual non-IGP functional capabilities. ELC is one of such non-IGP functional capabilities.}, }