MPLS LDP Identifier Name
draft-abd-mpls-ldp-identifier-name-00

Document Type Active Internet-Draft (individual)
Last updated 2018-09-21
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
Network Working Group                                         Anil Kumar
Internet-Draft                                                  Deepak J
Intended status: Standards Track                              Basil Saji
Expires: March 25, 2019                                    RtBrick India
                                                      September 21, 2018

                        MPLS LDP Identifier Name
                 draft-abd-mpls-ldp-identifier-name-00

Abstract

   This document introduces a new optional LDP Identifier Name TLV that
   allows LDP routers to inform their LDP-Identifier-to-Name mapping in
   LDP Hello messages as part of the LDP Discovery Mechanism.  This
   document describes a mechanism to provide a simple and dynamic
   mechanism for ldp routers to learn about symbolic LDP Identifier
   Names.

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
   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 March 25, 2019.

Copyright Notice

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

Anil Kumar, et al.       Expires March 25, 2019                 [Page 1]
Internet-Draft             LDP Identifier Name            September 2018

   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.  LDP Identifier Name TLV . . . . . . . . . . . . . . . . . . .   3
     2.1.  Optional Parameter for Hello Message  . . . . . . . . . .   3
     2.2.  LDP Identifier Name TLV Encoding  . . . . . . . . . . . .   4
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   The Label Distribution Protocol (LDP) [RFC5036] sets up LDP sessions
   that run between LDP peers.  The peers could either be directly
   connected at the link level or could be multiple hops away.  An LDP
   Label Switching Router (LSR) could either be configured with the
   identity of its peers or could discover them using LDP Hello
   messages.  These messages are sent encapsulated in UDP addressed to
   "all routers on this subnet" or to a specific IP address.  Periodic
   Hello messages are also used to maintain the relationship between LDP
   peers necessary to keep the LDP session active.

   [RFC5036] states that an LDP Identifier is a six octet quantity used
   to identify an LSR label space.  The first four octets identify the
   LSR and must be a globally unique value, such as a 32-bit router Id
   assigned to the LSR.  The last two octets identify a specific label
   space within the LSR.  The last two octets of LDP Identifiers for
   platform-wide label spaces are always both zero.

   An LSR that manages and advertises multiple label spaces uses a
   different LDP Identifier for each such label space.

Anil Kumar, et al.       Expires March 25, 2019                 [Page 2]
Internet-Draft             LDP Identifier Name            September 2018

   [RFC5036] specifies using following representation for LDP
   Identifiers: <LSR Id> : <label space id> e.g., lsr171 : 0 lsr19 : 2

   For management and operational reasons, network operators need to
   check the status of LDP adjacencies, entries in Label Information
Show full document text