RSVP-TE Extensions to Exchange MPLS-TP LSP Tunnel Numbers
draft-zhang-ccamp-mpls-tp-rsvpte-ext-tunnel-num-04

The information below is for an old version of the document
Document Type Active Internet-Draft (candidate for ccamp WG)
Last updated 2012-08-15
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state Call For Adoption By WG Issued
Other - see Comment Log
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
CCAMP Working Group                                             F. Zhang
Internet-Draft                                           ZTE Corporation
Intended status: Standards Track                           M. Venkatesan
Expires: February 17, 2013                                     Dell Inc.
                                                                   Y. Xu
                                                                    CATR
                                                               R. Gandhi
                                                           Cisco Systems
                                                         August 16, 2012

       RSVP-TE Extensions to Exchange MPLS-TP LSP Tunnel Numbers
           draft-zhang-ccamp-mpls-tp-rsvpte-ext-tunnel-num-04

Abstract

   The MPLS Transport Profile (MPLS-TP) identifiers document [RFC6370]
   specifies an initial set of identifiers, including the local assigned
   Z9-Tunnel_Num, 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)
   [RFC6428], 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 mis-connectivity defect [RFC6371], which
   means that the two MEP nodes need to pre-store each other's MEP_IDs.

   This document defines the signaling extensions to communicate the
   local assigned Z9-Tunnel_Num to the ingress LSR (Label Switching
   Router) of a co-routed bidirectional LSP.

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 February 17, 2013.

Copyright Notice
 

Zhang, et al.          Expires February 17, 2013                [Page 1]
Internet-Draft     RSVP-TE Extensions for Tunnel Num     August 16, 2012

   Copyright (c) 2012 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
   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  . . . . . . . . . . . . . .  3
   3.  Operation  . . . . . . . . . . . . . . . . . . . . . . . . . .  3
   4.  RSVP-TE Extensions . . . . . . . . . . . . . . . . . . . . . .  3
     4.1.  Association Type . . . . . . . . . . . . . . . . . . . . .  3
     4.2.  Signaling Procedure  . . . . . . . . . . . . . . . . . . .  4
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  5
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . .  5
   7.  Acknowledgement  . . . . . . . . . . . . . . . . . . . . . . .  5
   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     8.1.  Normative references . . . . . . . . . . . . . . . . . . .  5
     8.2.  Informative References . . . . . . . . . . . . . . . . . .  6
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .  7

1.  Introduction

   The MPLS Transport Profile (MPLS-TP) identifiers document [RFC6370]
   specifies a initial set of identifiers, including the local assigned
   Z9-Tunnel_Num, 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) [RFC6428], 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
   mis-connectivity defect [RFC6371].  Hence, the two MEP nodes must
Show full document text