Signaling Entropy Label Capability and Readable Label-stack Depth Using OSPF
draft-ietf-ospf-mpls-elc-05

Document Type Expired Internet-Draft (lsr WG)
Last updated 2018-07-16 (latest revision 2018-01-03)
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state WG Document (wg milestone: Jun 2016 - Standardize OSPF Ent... )
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-ospf-mpls-elc-05.txt

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, referred to as Readable Label-stack Depth (RLD), 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 Router Non-OSPF Functional Capabilities TLV for advertising OSPF router's actual non-OSPF functional capabilities. ELC is one of such non-OSPF functional capabilities.

Authors

Xiaohu Xu (xuxh.mail@gmail.com)
Sriganesh Kini (sriganeshkini@gmail.com)
Siva Sivabalan (msiva@cisco.com)
Clarence Filsfils (cfilsfil@cisco.com)
Stephane Litkowski (stephane.litkowski@orange.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)