--- 1/draft-ietf-ccamp-otn-signal-type-subregistry-00.txt 2015-03-09 12:14:47.925236139 -0700 +++ 2/draft-ietf-ccamp-otn-signal-type-subregistry-01.txt 2015-03-09 12:14:47.937236428 -0700 @@ -1,43 +1,43 @@ - CCAMP Working Group Zafar Ali Internet Draft Antonello Bonfanti - Intended status: Standards Track Cisco Systems +Intended status: Standards Track Matt Hartley + Cisco Systems F. Zhang Huawei Technologies - Expires: May 12, 2015 November 13, 2014 +Expires: September 9, 2015 March 6, 2015 IANA Allocation Procedures for OTN Signal Type Subregistry to the GMPLS Signaling Parameters Registry - draft-ietf-ccamp-otn-signal-type-subregistry-00.txt + draft-ietf-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 May 12, 2015. +This Internet-Draft will expire on September 9, 2015. Copyright Notice - Copyright (c) 2013 IETF Trust and the persons identified as the +Copyright (c) 2015 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 @@ -52,38 +52,38 @@ 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 draft proposes changes to OTN Signal +Parameters" registry. This draft proposes changes to the OTN Signal Type subregistry to include Specification Required policies, as defined in [RFC5226]. 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 .............................. 3 + 1. Introduction 2 + 2. IANA Considerations 3 + 3. References 3 + 3.1. Normative References 3 + 3.2. Informative References 3 1. Introduction [RFC4328] and [RFC7139] provide the extensions to the Generalized Multi-Protocol Label Switching (GMPLS) signaling to control the full set of OTN features including ODU0, ODU1, ODU2, ODU3, ODU4, ODU2e and ODUflex. However, it does not cover additional signal types mentioned in [G.Sup43] (ODU1e, ODU3e1, and ODU3e2). As ODU1e, ODU3e1, and ODU3e2 signal types are only defined in an ITU-T supplementary document, IANA cannot allocate @@ -99,24 +99,24 @@ support Specification Required policies, as defined in [RFC5226]. 2. IANA Considerations IANA maintains the an "OTN Signal Type" subregistry to the "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Parameters" registry. The registry currently is defined to use the Standards Action registration policy as defined by [RFC5226]. This document directs that both Standards Action and - Specification Required policies, as defined in [RFC5226], be - applied to this subregistry. When needed, the Designated Expert - shall be identified by a CCAMP WG chair or, in the case the - group is no longer active, by the IESG. + IETF Review policies, as defined in [RFC5226], be applied to + this subregistry. When needed, the Designated Expert shall be + identified by a CCAMP WG chair or, in the case the group is no + longer active, by the IESG. 3. Acknowledgments The authors would like to thank Lou Berger and Adrian Farrel for comments. 4. References 4.1. Normative References @@ -136,21 +136,26 @@ [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008. 4.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 + Matt Hartley + Cisco Systems + mhartley@cisco.com + Fatai Zhang Huawei Technologies Email: zhangfatai@huawei.com