RSVP-TE Extensions to Exchange MPLS-TP LSP Identifiers
draft-zhang-ccamp-mpls-tp-rsvpte-ext-tunnel-num-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2011-11-13 (latest revision 2011-09-16)
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)
MPLS Working Group                                              F. Zhang
Internet-Draft                                           ZTE Corporation
Intended status: Standards Track                       November 13, 2011
Expires: May 16, 2012

         RSVP-TE Extensions to Exchange MPLS-TP LSP Identifiers
           draft-zhang-ccamp-mpls-tp-rsvpte-ext-tunnel-num-01

Abstract

   The MPLS Transport Profile (MPLS-TP) identifiers document [RFC6370]
   specifies a initial set of identifiers, such as local assigned tunnel
   number and Global_ID, which can be used to form Maintenance Entity
   Point Identifier (MEP_ID).  As to some Operation, Administration and
   Maintenance (OAM) functions, such as Connectivity Verification (CV)
   [I-D.ietf-mpls-tp-cc-cv-rdi], source MEP_ID must be inserted in the
   OAM packets, so that the peer endpoint can compare the received and
   expected MEP_IDs to judge whether there is a mismatch [RFC6371],
   which means that the two MEP nodes need to pre-store each other's
   MEP_IDs.

   This document defines the signaling extensions to exchange the Label
   Switched Path (LSP) identifiers.

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 16, 2012.

Copyright Notice

   Copyright (c) 2011 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

Zhang                     Expires May 16, 2012                  [Page 1]
Internet-Draft   RSVP-TE Extentions for LSP Identifiers    November 2011

   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  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Conventions used in this document . . . . . . . . . . . . . . . 3
   3.  Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
     3.1.  Co-routed Bidirectional LSP . . . . . . . . . . . . . . . . 3
     3.2.  Associated Bidirectional LSP  . . . . . . . . . . . . . . . 4
   4.  RSVP-TE Extensions  . . . . . . . . . . . . . . . . . . . . . . 5
     4.1.  LSP Attribute Flags . . . . . . . . . . . . . . . . . . . . 5
     4.2.  Connection TLV  . . . . . . . . . . . . . . . . . . . . . . 5
     4.3.  Global_ID TLV . . . . . . . . . . . . . . . . . . . . . . . 6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . . . 7
   7.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . . 7
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 7
     8.1.  Normative references  . . . . . . . . . . . . . . . . . . . 7
     8.2.  Informative References  . . . . . . . . . . . . . . . . . . 8
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . . 8

Zhang                     Expires May 16, 2012                  [Page 2]
Internet-Draft   RSVP-TE Extentions for LSP Identifiers    November 2011

1.  Introduction

   The MPLS Transport Profile (MPLS-TP) identifiers document [RFC6370]
   specifies a initial set of identifiers, such as local assigned tunnel
   number (Tunnel_Num) and Global_ID, which can be used to form
   Maintenance Entity Point Identifier (MEP_ID).  The MPLS-TP LSP_MEP_ID
   is Node_ID::Tunnel_Num::LSP_Num, and in situations where global
   uniqueness is required, this becomes: Global_ID::Node_ID::
   Tunnel_Num::LSP_Num. In order to realize some Operation,
   Administration and Maintenance (OAM) functions, such as Connectivity
   Verification (CV) [I-D.ietf-mpls-tp-cc-cv-rdi], source MEP-ID MUST be
   inserted in the OAM packets, in this way the peer endpoint can
   compare the received and expected MEP-IDs to judge whether there is a
   mismatch [RFC6371].  Hence, the two MEP nodes must pre-store each
   other's MEP-IDs before sending the CV packets.

   Obviously, the exchange of MEP_IDs can be accomplished by the Network
Show full document text