Internet DRAFT - draft-cui-mpls-tp-cc-cv-rdi-id

draft-cui-mpls-tp-cc-cv-rdi-id






Network Working Group                                             Z. Cui
Internet-Draft                                                 R. Winter
Intended status: Standards Track                                     NEC
Expires: September 6, 2012                                 March 5, 2012


 Using ITU-T-based IDs for MPLS-TP Proactive Connectivity Verification
                   draft-cui-mpls-tp-cc-cv-rdi-id-00

Abstract

   This document defines how to use ICC-based Multiprotocol Label
   Switching Transport Profil(MPLS-TP) identifiers for proactive
   connectivity verification (CV) analogous to RFC 6428.  New TLVs are
   defined to support proactive CV based on identifiers following ITU-T
   conventions.

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 September 6, 2012.

Copyright Notice

   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.



Cui & Winter            Expires September 6, 2012               [Page 1]

Internet-Draft           Proactive-CV ITU-T IDs               March 2012


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Requirements notation . . . . . . . . . . . . . . . . . . . . . 3
   3.  ICC_Operator_ID-based Source MEP-ID TLV Definitions . . . . . . 3
   4.  Security Considerations . . . . . . . . . . . . . . . . . . . . 4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
   6.  Normative References  . . . . . . . . . . . . . . . . . . . . . 4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 5










































Cui & Winter            Expires September 6, 2012               [Page 2]

Internet-Draft           Proactive-CV ITU-T IDs               March 2012


1.  Introduction

   Proactive Connectivity Verification, Continuity Check, and Remote
   Defect Indication (CV, CC and RDI) [RFC6428] is a proactive
   Operations, Administration, and Maintenance (OAM) mechanism for the
   MPLS Transport Profile (MPLS-TP).  [RFC6428], defines CV message
   which carry a Global_ID-based Source MEP-ID TLV to permit mis-
   connectivity detection to be performed by sink MEPs.  In transport
   networks however, the ITU Carrier Code (ICC) is traditionally used to
   identify a carrier/service provider.  Instead of using the Global_ID,
   which is derived from the AS number of the service provider, this
   document defines a set of Source MEP-ID TLVs based on the
   ICC_Operator_ID for sections, LSPs and PWs as specified in
   [I-D.ietf-mpls-tp-itu-t-identifiers] for use in CV.


2.  Requirements notation

   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.  ICC_Operator_ID-based Source MEP-ID TLV Definitions

   An MPLS-TP CV message [RFC6428] consists of a BFD control packet pre-
   pended by the Associated Channel Header (ACH) and appended by a
   Source MEP-ID TLV.  This section defines an ICC_Operator_ID-based
   Source MEP-ID TLV object.  It is used as a replacement for the
   Global_ID-based Source MEP-ID TLV as specified in [RFC6428].

   The format of ICC_Operator_ID-based Source MEP-ID TLV is shown below.



















Cui & Winter            Expires September 6, 2012               [Page 3]

Internet-Draft           Proactive-CV ITU-T IDs               March 2012


    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |           Type = X            |          Length = 20          |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                                                               |
    +                                                               +
    |                 ICC_Operator_ID-based MEG-ID                  |
    +                          (15 Characters)                      +
    |                                                               |
    +                                               +-+-+-+-+-+-+-+-+
    |                                               | Must be Zero  |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |       MEP_Index (2 Octets)    |        Must be Zero           |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

         Figure 1: ICC_Operator_ID-based Source MEP-ID TLV Format

   An ICC_Operator_ID-based Source MEP-ID TLV is encoded as a 2-octet
   field that specifies a type, followed by a 2-octet length field,
   followed by a value field.

   The value field is encoded by appending a 16-bit MEP index to the 15
   character long MEG_ID as defined in
   [I-D.ietf-mpls-tp-itu-t-identifiers].  Padding is used to align the
   field with a 4 octet boundary.  The length of the padding MUST be
   included in the length field.  The type will be 'X', with no
   distinction between sections, LSPs and Pseudowires [type value to be
   assigned by IANA].


4.  Security Considerations

   The security concerns expressed in the security considerations
   section of [RFC6428] apply.  No additional concerns stem from the use
   of the TLV defined in this document.


5.  IANA Considerations

   TBD


6.  Normative References

   [I-D.ietf-mpls-tp-itu-t-identifiers]
              Gray, E., Helvoort, H., Betts, M., and R. Winter, "MPLS-TP
              Identifiers Following ITU-T Conventions",



Cui & Winter            Expires September 6, 2012               [Page 4]

Internet-Draft           Proactive-CV ITU-T IDs               March 2012


              draft-ietf-mpls-tp-itu-t-identifiers-02 (work in
              progress), October 2011.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC6428]  Allan, D., Swallow Ed. , G., and J. Drake Ed. , "Proactive
              Connectivity Verification, Continuity Check, and Remote
              Defect Indication for the MPLS Transport Profile",
              RFC 6428, November 2011.


Authors' Addresses

   Zhenlong Cui
   NEC

   Email: c-sai@bx.jp.nec.com


   Rolf Winter
   NEC

   Email: Rolf.Winter@neclab.eu



























Cui & Winter            Expires September 6, 2012               [Page 5]