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

Versions: 00 01 02 draft-ietf-ccamp-otn-signal-type-subregistry

     PCE Working Group                                         Zafar Ali
     Internet Draft                                   Antonello Bonfanti
     Intended status: Standards Track                      Cisco Systems
                                                                F. Zhang
                                                     Huawei Technologies
     Expires: January 25, 2015                             July 26, 2014
     
     
         IANA Allocation Procedures for OTN Signal Type Subregistry to
                    the GMPLS Signaling Parameters Registry
              draft-ali-ccamp-otn-signal-type-subregistry-01.txt
     
     
     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 January 25,2015.
     
     Copyright Notice
     
     Copyright (c) 2013 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.
     
     This document may contain material from IETF Documents or IETF
     Contributions published or made publicly available before November
     10, 2008.  The person(s) controlling the copyright in some of this
     
     
     
     Expires January 2015                                      [Page 1]


        draft-ali-ccamp-otn-signal-type-subregistry-01.txt
     
     material may not have granted the IETF Trust the right to allow
     modifications of such material outside the IETF Standards Process.
     Without obtaining an adequate license from the person(s)
     controlling the copyright in such materials, this document may not
     be modified outside the IETF Standards Process, and derivative
     works of it may not be created outside the IETF Standards Process,
     except to format it for publication as an RFC or to translate it
     into languages other than English.
     
     Abstract
     
     IANA has defined an "OTN Signal Type" subregistry to the
     "Generalized Multi-Protocol Label Switching (GMPLS) Signaling
     Parameters" registry. This subregistry does not specify Expert
     Review or Private ranges. This draft proposes changes to OTN Signal
     Type subregistry to include Expert Review and Private ranges.
     
     Conventions used in this document
     
     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].
     
     Table of Contents
     
        1. Introduction ......................................... 2
        2. IANA Considerations .................................. 3
        3. References ........................................... 3
          3.1. Normative References ............................. 3
          3.2. Informative References ........................... 4
     
     1. Introduction
     
        With the evolution and deployment of Optical Transport Network
        (OTN) technology, it is necessary to support additional signal
        types ODU1e, ODU3e1 and ODU3e2 mentioned in [G.Sup43]. However,
        as these signal types are only defined in an ITU-T supplementary
        document, IANA cannot allocate values from the "Standards
        Action" range [RFC5226].
     
        IANA maintains "OTN Signal Type" subregistry to the "Generalized
        Multi-Protocol Label Switching (GMPLS) Signaling Parameters"
        registry for the OTN signal defined in [RFC4328] and [RFC7139].
        However, this subregistry does not specify Expert Review or
        Private ranges. This draft proposes changes to OTN Signal Type
        subregistry to include Expert Review and Private ranges.
     
     
     
     
     
                          Expires January 2015               [Page 2]


        draft-ali-ccamp-otn-signal-type-subregistry-01.txt
     
     2. IANA Considerations
     
        IANA has defined an "OTN Signal Type" subregistry to the
        "Generalized Multi-Protocol Label Switching (GMPLS) Signaling
        Parameters" registry. This document modifies OTN Signal Type
        subregistry by including the following ranges for Expert Review
        and private use. Both ranges come from the "Unassigned" value
        space in [RFC4328] and [RFC7139].
     
        The registry is modified as follows:
     
              Value    Signal Type                           Reference
     
              -----    -----------                           ---------
     
              23-229   A range assigned under the         [This draft]
                       "Unassigned" policy described
                       in [RFC5226].
              230-234  A range assigned under the         [This draft]
                       "Experimental" policy described
                       in [RFC5226].
              235-239  A range assigned under the         [This draft]
                       "Private Use" policy described
                       in [RFC5226].
              240-255   A range assigned under the         [This draft]
                       "Unassigned" policy described
                       in [RFC5226].
     
     3. References
     
     
     3.1. Normative References
     
        [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
                  Requirement Levels", BCP 14, RFC 2119, March 1997.
     
        [RFC4328] Papadimitriou, D., Ed., "Generalized Multi-Protocol
                  Label Switching (GMPLS) Signaling Extensions for G.709
                  Optical Transport Networks Control", RFC 4328, January
                  2006.
     
        [RFC7139] Zhang, F., Ed., Zhang, G., Belotti, S., Ceccarelli,
                  D., and K. Pithewan, "GMPLS Signaling Extensions for
                  Control of Evolving G.709 Optical Transport Networks",
                  RFC 7139, March 2014.
     
        [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing
                  an IANA Considerations Section in RFCs", BCP 26, RFC
                  5226, May 2008.
     
     
     
                          Expires January 2015               [Page 3]


        draft-ali-ccamp-otn-signal-type-subregistry-01.txt
     
     3.2. Informative References
     
        [GSUP.43] ITU-T, "Proposed revision of G.sup43 (for agreement)",
                  February, 2011.
     
     Authors' Addresses
     
     
        Zafar Ali
        Cisco Systems
        Email: zali@cisco.com
     
        Antonello Bonfanti
        Cisco Systems
        abonfant@cisco.com
     
        Fatai Zhang
        Huawei Technologies
        Email: zhangfatai@huawei.com
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
                          Expires January 2015               [Page 4]
     

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