LDP Extensions for FEC elements sharing label
draft-chenpeng-mpls-ldp-ext-01

Document Type Active Internet-Draft (individual)
Last updated 2017-05-09
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Networking Working Group                                       Ran. Chen
Internet-Draft                                              Shaofu. Peng
Intended status: Standards Track                         ZTE Corporation
Expires: November 10, 2017                                  May 09, 2017

             LDP Extensions for FEC elements sharing label
                     draft-chenpeng-mpls-ldp-ext-01

Abstract

   Label Distribution Protocol (LDP) is defined in [RFC5036] for
   distribution of labels inside one MPLS domain.  It defined how to
   associate a Forwarding Equivalence Class (FEC) with each label it
   distributes.  A FEC is a list of one or more FEC elements, but it
   does not describe operations how to achieve one or more FEC element
   share the same label.

   Currently Label resources are getting more and more nervous, and it
   is necessary to save the label resources.  This document defines
   extensions to the LDP protocol to achieve one or more FEC element
   share the same label.

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 November 10, 2017.

Copyright Notice

   Copyright (c) 2017 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
   (http://trustee.ietf.org/license-info) in effect on the date of

Chen & Peng             Expires November 10, 2017               [Page 1]
Internet-DraftLDP Extensions for FEC elements sharing label     May 2017

   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.  Conventions used in this document . . . . . . . . . . . . . .   2
   3.  LDP Extension . . . . . . . . . . . . . . . . . . . . . . . .   2
     3.1.  Host-parasitism FEC Relationship TLV  . . . . . . . . . .   3
     3.2.  Label Borrowing Message . . . . . . . . . . . . . . . . .   4
   4.  Operations  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Egress Operation  . . . . . . . . . . . . . . . . . . . .   4
     4.2.  Ingress/Transit Operation . . . . . . . . . . . . . . . .   5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   8.  Normative references  . . . . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   Label Distribution Protocol (LDP) is defined in [RFC5036] for
   distribution of labels inside one MPLS domain.  It defined how to
   associate a Forwarding Equivalence Class (FEC) with each label it
   distributes.  A FEC is a list of one or more FEC elements, but it
   does not describe operations how to achieve one or more FEC element
   share the same label.

   Currently Label resources are getting more and more nervous, and it
   is necessary to save the label resources.  This document defines
   extensions to the LDP protocol to achieve one or more FEC element
   share the same label.

2.  Conventions used in this document

   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 RFC2119.

3.  LDP Extension

Chen & Peng             Expires November 10, 2017               [Page 2]
Internet-DraftLDP Extensions for FEC elements sharing label     May 2017

3.1.  Host-parasitism FEC Relationship TLV
Show full document text