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

Document Type Active Internet-Draft (ospf WG)
Last updated 2018-01-03
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document (wg milestone: Jun 2016 - Standardize OSPF Ent... )
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
OSPF Working Group                                                 X. Xu
Internet-Draft                                                    Huawei
Intended status: Standards Track                                 S. Kini
Expires: July 7, 2018
                                                            S. Sivabalan
                                                             C. Filsfils
                                                                   Cisco
                                                            S. Litkowski
                                                                  Orange
                                                         January 3, 2018

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

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.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute

Xu, et al.                Expires July 7, 2018                  [Page 1]
Internet-Draft      Signalling ELC and RLD using OSPF       January 2018

   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 7, 2018.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Non-OSPF Functional Capabilities TLV  . . . . . . . . . . . .   3
   4.  Advertising ELC Using OSPF  . . . . . . . . . . . . . . . . .   4
   5.  Advertising RLD Using OSPF  . . . . . . . . . . . . . . . . .   4
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   [RFC6790] describes a method to load balance Multiprotocol Label
   Switching (MPLS) traffic flows using Entropy Labels (EL).  [RFC6790]
   introduces the concept of Entropy Label Capability (ELC) and defines
   the signalings of this capability via MPLS signaling protocols.
   Recently, mechanisms are being defined to signal labels via link-
   state Interior Gateway Protocols (IGP) such as OSPF
Show full document text