[Docs] [txt|pdf] [Tracker] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 02

Network Working Group                                            M. Chen
Internet-Draft                                                  L. Zheng
Intended status: Standards Track                Huawei Technologies Ltd.
Expires: February 13, 2013                               August 12, 2012


         ICC_Operator_ID Attachment Individual Identifier (AII)
                   draft-chen-pwe3-mpls-tp-aii-icc-02

Abstract

   This document defines a new Attachment Individual Identifier (AII)
   type which could be used to identify the pseudowire endpoint when
   ICC_Operator_ID is used to uniquely identify an operator in MPLS-TP
   networks.  The new AII (ICC_Operator_ID AII) consists a
   ICC_Operator_ID, a prefix and a AC ID field.

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 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 13, 2013.

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



Chen & Zheng            Expires February 13, 2013               [Page 1]


Internet-Draft                   ICC AII                     August 2012


   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.  ICC_Operator_ID AII . . . . . . . . . . . . . . . . . . . . . . 3
     2.1.  Procedures  . . . . . . . . . . . . . . . . . . . . . . . . 4
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
   4.  Security Considerations . . . . . . . . . . . . . . . . . . . . 5
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 5
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 5
     6.1.  Normative References  . . . . . . . . . . . . . . . . . . . 5
     6.2.  Informative References  . . . . . . . . . . . . . . . . . . 5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 5































Chen & Zheng            Expires February 13, 2013               [Page 2]


Internet-Draft                   ICC AII                     August 2012


1.  Introduction

   RFC6370 [RFC6370] specifies an initial set of identifiers to be used
   in the Multiprotocol Label Switching Transport Profile (MPLS-TP).
   The Global_ID is defined in RFC6370 [RFC6370] to uniquely identify an
   operator.  [I.D.draft-ietf-mpls-tp-itu-t-identifiers]
   [I-D.ietf-mpls-tp-itu-t-identifiers] specifies the ICC_Operator_ID,
   an alternative way to uniquely identify an operator based on ITU-T
   conventions.  We call both Global_ID and ICC_Operator_ID as Operator
   ID in this document.

   RFC4447 [RFC4447] defines the signaling mechanisms for establishing
   point- to-point pseudowires (PWs) between two provider edge (PE)
   nodes.  It defines the PWid FEC element and Generalized ID (GID) FEC
   element.  In GID FEC element, the attachment individual identifiers
   (AIIs) in conjunction with an attachment group identifier (AGI),
   serve as PW endpoint identifiers.

   Six types of Attachment Individual Identifier (AII) have been
   defined.  AII Type 1 defined in RFC6074[RFC6074] has a fixed-length
   32-bit value that is unique within the scope of the local Provider
   Edge (PE).  AII Type 2 defined in RFC5003 [RFC5003] consists a
   4-octet length Global ID, a 32-bit prefix field and a 4-octet
   attachment circuit identifier (AC ID) field.  AII type 3-6 has been
   defined by MFA Forum.  Existing AIIs do not support ICC based
   identifier.

   This document defines a new AII type (ICC_Operator_ID AII).  It use a
   combination of a 8-octet length ICC_Operator_ID, a 4-octet length
   prefix and a 4-octet length AC ID to create globally unique AII
   values.  The ICC_Operator_ID AII could be used to identify the
   pseudowire endpoint when ICC_Operator_ID is used to uniquely identify
   an operator in MPLS-TP networks.  A typical use for this AII in
   MPLS-TP enviroment is in Pseudowire Path Identifier.


2.  ICC_Operator_ID AII

   ICC_Operator_ID AII has the consistent structure with AII Type 2,
   which permits varying levels of AII summarization to take place, thus
   reducing the scaling burden on the AII distribution mechanisms and PE
   memory as described in RFC5003[RFC5003].  ICC_Operator_ID AII use a
   combination of a 8-octet length ICC_Operator_ID, a 4-octet length
   prefix and a 4-octet length AC ID to create globally unique AII
   values.  The encoding of ICC_Operator_ID AII is as follows:






Chen & Zheng            Expires February 13, 2013               [Page 3]


Internet-Draft                   ICC AII                     August 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
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |   AII Type    |    Length     |        ICC_Operator_ID        |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                     ICC_Operator_ID(contd.)                   |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |    ICC_Operator_ID(contd.)    |             Prefix            |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |         Prefix(contd.)        |             AC ID             |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |          AC ID(contd.)        |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                             Figure 1. ICC_Operator_ID AII

   AII Type: To be allocated by IANA.

   Length: 1 octet in length, specifies the length of the value field in
   octets.  The length is set to 14.

   ICC_Operator_ID: ICC_Operator_ID of the sender node.  As defined in
   [I-D.ietf-mpls-tp-itu-t-identifiers], the ICC_Operator_ID is formed
   by Country Code (CC) and ICC(ITU Carrier Code ) as CC::ICC.  The ICC
   itself is a string of one to six characters, global uniqueness is
   assured by concatenating the ICC with a CC.  The Country Code
   (alpha-2) is a string of two alphabetic characters represented with
   upper case letters (i.e., A-Z).  When the length of a ICC_Operator_ID
   string is less than 8 octets, the higher-order unused octets of the
   ICC_Operator_ID field MUST be set to zero.

   Prefix: Same as [RFC5003].

   AC ID field: Same as [RFC5003].

2.1.  Procedures

   Since the Operator ID MAY be either the Global_ID or ICC_Operator_ID,
   the two ends of a PW may use the different AII type.  During the
   Label Mapping procedure, one end may not map the TAI to one of its
   Forwarders.  In this case, it MUST send a Label Release message to
   the other end, with a Status Code of "Unassigned/Unrecognized TAI",
   and the processing of the Label Mapping message is complete.


3.  IANA Considerations

   The IANA is requested to as assign a new AII type from the
   "Attachment Individual Identifier (AII) Type" registry.



Chen & Zheng            Expires February 13, 2013               [Page 4]


Internet-Draft                   ICC AII                     August 2012


   Value   Meaning                       Reference
   -----   --------------------------    ----------------------
   TBD     ICC_Operator_ID identifier    this document (sect 2)


4.  Security Considerations

   This draft does not introduce any new security issues, the security
   mechanisms defined in [RFC5003] apply here.


5.  Acknowledgements


6.  References

6.1.  Normative References

   [I-D.ietf-mpls-tp-itu-t-identifiers]
              Winter, R., Gray, E., Helvoort, H., and M. Betts, "MPLS-TP
              Identifiers Following ITU-T Conventions",
              draft-ietf-mpls-tp-itu-t-identifiers-03 (work in
              progress), March 2012.

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

   [RFC6370]  Bocci, M., Swallow, G., and E. Gray, "MPLS Transport
              Profile (MPLS-TP) Identifiers", RFC 6370, September 2011.

6.2.  Informative References

   [RFC4447]  Martini, L., Rosen, E., El-Aawar, N., Smith, T., and G.
              Heron, "Pseudowire Setup and Maintenance Using the Label
              Distribution Protocol (LDP)", RFC 4447, April 2006.

   [RFC5003]  Metz, C., Martini, L., Balus, F., and J. Sugimoto,
              "Attachment Individual Identifier (AII) Types for
              Aggregation", RFC 5003, September 2007.

   [RFC6074]  Rosen, E., Davie, B., Radoaca, V., and W. Luo,
              "Provisioning, Auto-Discovery, and Signaling in Layer 2
              Virtual Private Networks (L2VPNs)", RFC 6074,
              January 2011.







Chen & Zheng            Expires February 13, 2013               [Page 5]


Internet-Draft                   ICC AII                     August 2012


Authors' Addresses

   Mach Chen
   Huawei Technologies Ltd.
   China

   Email: mach.chen@huawei.com


   Lianshu Zheng
   Huawei Technologies Ltd.
   China

   Email: vero.zheng@huawei.com





































Chen & Zheng            Expires February 13, 2013               [Page 6]


Html markup produced by rfcmarkup 1.129d, available from https://tools.ietf.org/tools/rfcmarkup/