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

Versions: 00 01 02

Network Working Group                                            M. Chen
Internet-Draft                                                  L. Zheng
Intended status: Standards Track            Huawei Technologies Co., Ltd
Expires: November 13, 2011                                  May 12, 2011


     ITU Carrier Code (ICC) Attachment Individual Identifier (AII)
                 draft-chen-pwe3-mpls-tp-aii-icc-00.txt

Abstract

   This document defines a new Attachment Individual Identifier (AII)
   type which could be used when ITU Carrier Code (ICC) is used as the
   provider's globally unique identifier (Opr_ID).  The new AII (ICC
   AII) consists a ICC, 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 November 13, 2011.

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
   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



Chen & Zheng            Expires November 13, 2011               [Page 1]


Internet-Draft                   ICC AII                        May 2011


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
































Chen & Zheng            Expires November 13, 2011               [Page 2]


Internet-Draft                   ICC AII                        May 2011


1.  Introduction

   [I-D.ietf-mpls-tp-identifiers] specifies two formats of Operator
   Identifier (Opr_ID), uniquely identifying an operator in Multi-
   Protocol Label Switching Transport Profile (MPLS-TP) networks.  One
   format is compatible with IP operational practice called a Global_ID
   and anothor format compatible with ITU practice, the ITU Carrier Code
   (ICC).  The Opr_ID MAY use either the Global_ID or ICC format.

   [RFC4447] defines the signaling mechanisms for establishing point-to-
   point pseudowires (PWs) between two provider edge (PE) nodes.  It
   defines the format of the Generalized PWid FEC (FEC 129) and the use
   and semantics of the Attachment Group Identifier (AGI) and Attachment
   Individual Identifier (AII).  Two types of AII have been defined.
   AII Type 1 defined in [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] consists a 4-octct length Global ID, a 32-bit
   prefix field and a 4-octet attachment circuit identifier (AC ID)
   field.  Existing AIIs do not support ICC based identifier.

   This document defines a new AII type (ICC AII).  It use a combination
   of a 6-octet length ICC, a 4-octet length prefix and a 4-octet length
   AC ID to create globally unique AII values.


2.  ICC AII

   ICC 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
   decribed in RFC5003 [RFC5003].  The encoding of ICC AII is as
   follows:


       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=03  |    Length     |             ICC               |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                             ICC (contd.)                      |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                             Prefix                            |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                             AC ID                             |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                             Figure 1. ICC AII

   AII Type: To be allocated by IANA (0x03 is recommended).



Chen & Zheng            Expires November 13, 2011               [Page 3]


Internet-Draft                   ICC AII                        May 2011


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

   ICC: 6 octets in length.  As defined in M.1400, ICC is a string of
   one to six characters.  When the length of a ICC string is less than
   6, the higher-order unused octets of the ICC field MUST be set to
   zero.

   Prefix: Same as [RFC5003].

   AC ID field: Same as [RFC5003].

2.1.  Procedures

   Since the Opr_ID MAY use either the Global_ID or ICC format, the two
   ends of a PW may use the diffrent AII type.  During the Lable Mapping
   procedure, one end may not map the Target Attachment Identifier (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.  In addition, for a specific PW, relevant PEs MUST use the
   same type of identifiers.


3.  IANA Considerations

   IANA maintains a registry of "Attachment Individual Identifier (AII)
   Type".  This document request IANA to assign a new AII Type as
   follows:

   ICC AII: 0x03(TBD)


4.  Security Considerations

   This draft does not intrduce 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-identifiers]
              Bocci, M., Swallow, G., and E. Gray, "MPLS-TP



Chen & Zheng            Expires November 13, 2011               [Page 4]


Internet-Draft                   ICC AII                        May 2011


              Identifiers", draft-ietf-mpls-tp-identifiers-04 (work in
              progress), March 2011.

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

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

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.

   [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.


Authors' Addresses

   Mach(Guoyi) Chen
   Huawei Technologies Co., Ltd
   No. 3 Xinxi Road, Shang-di, Hai-dian District
   Beijing  100085
   China

   Email: mach@huawei.com


   Lianshu Zheng
   Huawei Technologies Co., Ltd
   No. 3 Xinxi Road, Shang-di, Hai-dian District
   Beijing  100085
   China

   Email: verozheng@huawei.com











Chen & Zheng            Expires November 13, 2011               [Page 5]


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