Signaling Entropy Label Capability Using OSPF
draft-ietf-ospf-mpls-elc-01

The information below is for an old version of the document
Document Type Active Internet-Draft (ospf WG)
Last updated 2015-11-10
Stream IETF
Intended RFC status (None)
Formats 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 I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                              X. Xu
Internet-Draft                                                    Huawei
Intended status: Standards Track                                 S. Kini
Expires: May 12, 2016                                           Ericsson
                                                            S. Sivabalan
                                                             C. Filsfils
                                                                   Cisco
                                                            S. Litkowski
                                                                  Orange
                                                        November 9, 2015

             Signaling Entropy Label Capability Using OSPF
                      draft-ietf-ospf-mpls-elc-01

Abstract

   Multi Protocol Label Switching (MPLS) has defined a mechanism to load
   balance traffic flows using Entropy Labels (EL).  An ingress LSR
   cannot insert ELs for packets going into a given tunnel unless an
   egress LSR has indicated via signaling that it can process ELs on
   that tunnel.  This draft defines a mechanism to signal that
   capability using OSPF.  This mechanism is useful when the label
   advertisement is also done via OSPF.

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
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://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 May 12, 2016.

Copyright Notice

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

Xu, et al.                Expires May 12, 2016                  [Page 1]
Internet-Draft          Signallng ELC Using OSPF           November 2015

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://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
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Advertising ELC Using OSPF  . . . . . . . . . . . . . . . . .   3
   4.  Advertising RLDC Using OSPF . . . . . . . . . . . . . . . . .   3
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   3
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   Multi Protocol Label Switching (MPLS) has defined a method in
   [RFC6790] to load balance traffic flows using Entropy Labels (EL).
   An ingress LSR cannot insert ELs for packets going into a given
   tunnel unless an egress LSR has indicated that it can process ELs on
   that tunnel.  [RFC6790] defines the signaling of this capability
   (a.k.a Entropy Label Capability - ELC) via signaling protocols.
   Recently, mechanisms are being defined to signal labels via link
   state Interior Gateway Protocols (IGP) such as OSPF
   [I-D.ietf-ospf-segment-routing-extensions] . In such scenario the
   signaling mechanisms defined in [RFC6790] are inadequate.  This draft
   defines a mechanism to signal the ELC using OSPF.  This mechanism is
   useful when the label advertisement is also done via OSPF.  In
   addition, in the cases where stacked LSPs are used for whatever
   reasons (e.g., SPRING-MPLS [I-D.ietf-spring-segment-routing-mpls]),
   it would be useful for ingress LSRs to know each LSR's capability of
   reading the maximum label stack deepth.  This capability, referred to
   as Readable Label Deepth Capability (RLDC) can be used by ingress
   LSRs to determine whether it's necessary to insert an EL for a given
Show full document text