idnits 2.17.1 draft-ietf-ccamp-otn-signal-type-subregistry-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- -- The draft header indicates that this document updates RFC7139, but the abstract doesn't seem to directly say this. It does mention RFC7139 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (March 17, 2016) is 2961 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 CCAMP Working Group Zafar Ali 2 Internet Draft Antonello Bonfanti 3 Updates: 7139 Matt Hartley 4 Intended status: Standards Track Cisco Systems 5 F. Zhang 6 Huawei Technologies 7 Expires: September 17, 2016 March 17, 2016 9 IANA Allocation Procedures for OTN Signal Type Subregistry of 10 the GMPLS Signaling Parameters Registry 11 draft-ietf-ccamp-otn-signal-type-subregistry-05.txt 13 Status of this Memo 15 This Internet-Draft is submitted in full conformance with the 16 provisions of BCP 78 and BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF). Note that other groups may also distribute 20 working documents as Internet-Drafts. The list of current Internet- 21 Drafts is at http://datatracker.ietf.org/drafts/current/. 23 Internet-Drafts are draft documents valid for a maximum of six 24 months and may be updated, replaced, or obsoleted by other 25 documents at any time. It is inappropriate to use Internet-Drafts 26 as reference material or to cite them other than as "work in 27 progress." 29 This Internet-Draft will expire on September 17, 2016. 31 Copyright Notice 33 Copyright (c) 2016 IETF Trust and the persons identified as the 34 document authors. All rights reserved. 36 This document is subject to BCP 78 and the IETF Trust's Legal 37 Provisions Relating to IETF Documents 38 (http://trustee.ietf.org/license-info) in effect on the date of 39 publication of this document. Please review these documents 40 carefully, as they describe your rights and restrictions with 41 respect to this document. Code Components extracted from this 42 document must include Simplified BSD License text as described in 43 Section 4.e of the Trust Legal Provisions and are provided without 44 warranty as described in the Simplified BSD License. 46 This document may contain material from IETF Documents or IETF 47 Contributions published or made publicly available before November 48 10, 2008. The person(s) controlling the copyright in some of this 49 material may not have granted the IETF Trust the right to allow 50 modifications of such material outside the IETF Standards Process. 51 Without obtaining an adequate license from the person(s) 52 controlling the copyright in such materials, this document may not 53 be modified outside the IETF Standards Process, and derivative 54 works of it may not be created outside the IETF Standards Process, 55 except to format it for publication as an RFC or to translate it 56 into languages other than English. 58 Abstract 60 IANA has defined an "OTN Signal Type" subregistry of the 61 "Generalized Multi-Protocol Label Switching (GMPLS) Signaling 62 Parameters" registry. This document updates the OTN Signal Type 63 subregistry specified in RFC 7139 to allow Specification Required 64 policies, as defined in RFC 5226. 66 Table of Contents 68 1. Introduction...................................................2 69 2. Security Considerations........................................2 70 3. IANA Considerations............................................2 71 4. Acknowledgments................................................3 72 5. References.....................................................3 73 5.1. Normative References.......................................3 74 5.2. Informative References.....................................3 76 1. Introduction 78 IANA maintains "OTN Signal Type" subregistry of the "Generalized 79 Multi-Protocol Label Switching (GMPLS) Signaling Parameters" 80 registry for the OTN signal defined in [RFC4328] and updated by 81 [RFC7139]. This subregistry is defined to use only the Standards 82 Action registration policy as defined by [RFC5226]. This 83 document updates [RFC7139] to allow the "OTN Signal Type" 84 subregistry to also support Specification Required policies, as 85 defined in [RFC5226]. 87 2. Security Considerations 89 This document does not introduce any new security considerations 90 to the existing GMPLS signaling protocols. Refer to [RFC7139] 91 for further details of the specific security measures. 92 Additionally, [RFC5920] provides an overview of security 93 vulnerabilities and protection mechanisms for the GMPLS control 94 plane. 96 3. IANA Considerations 98 IANA maintains the "OTN Signal Type" subregistry of the 99 "Generalized Multi-Protocol Label Switching (GMPLS) Signaling 100 Parameters" registry. The registry currently is defined to use 101 the Standards Action registration policy as defined by 102 [RFC5226]. 104 This document requests that the "OTN Signal Type" subregistry of 105 the "Generalized Multi-Protocol Label Switching (GMPLS) 106 Signaling Parameters" registry be updated with registration 107 policies of "Standards Action" for Standards Track documents, 108 and "Specification Required" for other documents. 110 When needed, the Designated Expert shall be any current CCAMP WG 111 chair or, in the case the group is no longer active, designated 112 by the IESG. 114 4. Acknowledgments 116 The authors would like to thank Lou Berger, Deborah Brungard, 117 Daniele Ceccarelli, Adrian Farrel, Vijay Gurbani, Huub van 118 Helvoort, Barry Lieba and Robert Sparks for comments. 120 5. References 122 5.1. Normative References 124 [RFC4328] Papadimitriou, D., Ed., "Generalized Multi-Protocol 125 Label Switching (GMPLS) Signaling Extensions for G.709 126 Optical Transport Networks Control", RFC 4328, January 127 2006. 129 [RFC7139] Zhang, F., Ed., Zhang, G., Belotti, S., Ceccarelli, 130 D., and K. Pithewan, "GMPLS Signaling Extensions for 131 Control of Evolving G.709 Optical Transport Networks", 132 RFC 7139, March 2014. 134 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing 135 an IANA Considerations Section in RFCs", BCP 26, RFC 136 5226, May 2008. 138 5.2. Informative References 140 [RFC5920] Fang, L., Ed., "Security Framework for MPLS and GMPLS 141 Networks", RFC 5920, July 2010. 143 Authors' Addresses 145 Zafar Ali 146 Cisco Systems 147 Email: zali@cisco.com 149 Antonello Bonfanti 150 Cisco Systems 151 abonfant@cisco.com 153 Matt Hartley 154 Cisco Systems 155 mhartley@cisco.com 157 Fatai Zhang 158 Huawei Technologies 159 Email: zhangfatai@huawei.com