draft-ietf-ccamp-otn-signal-type-subregistry-05.txt | rfc7892.txt | |||
---|---|---|---|---|
CCAMP Working Group Zafar Ali | ||||
Internet Draft Antonello Bonfanti | ||||
Updates: 7139 Matt Hartley | ||||
Intended status: Standards Track Cisco Systems | ||||
F. Zhang | ||||
Huawei Technologies | ||||
Expires: September 17, 2016 March 17, 2016 | ||||
IANA Allocation Procedures for OTN Signal Type Subregistry of | Internet Engineering Task Force (IETF) Z. Ali | |||
the GMPLS Signaling Parameters Registry | Request for Comments: 7892 A. Bonfanti | |||
draft-ietf-ccamp-otn-signal-type-subregistry-05.txt | Updates: 7139 M. Hartley | |||
Category: Standards Track Cisco Systems | ||||
ISSN: 2070-1721 F. Zhang | ||||
Huawei Technologies | ||||
May 2016 | ||||
Status of this Memo | IANA Allocation Procedures for the GMPLS OTN Signal Type Registry | |||
This Internet-Draft is submitted in full conformance with the | Abstract | |||
provisions of BCP 78 and BCP 79. | ||||
Internet-Drafts are working documents of the Internet Engineering | IANA defined the "OTN Signal Type" subregistry of the "Generalized | |||
Task Force (IETF). Note that other groups may also distribute | Multi-Protocol Label Switching (GMPLS) Signaling Parameters" registry | |||
working documents as Internet-Drafts. The list of current Internet- | in RFC 7139. This document updates the "OTN Signal Type" subregistry | |||
Drafts is at http://datatracker.ietf.org/drafts/current/. | to allow registration via Specification Required. | |||
Internet-Drafts are draft documents valid for a maximum of six | Status of This Memo | |||
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 September 17, 2016. | This is an Internet Standards Track document. | |||
Copyright Notice | This document is a product of the Internet Engineering Task Force | |||
(IETF). It represents the consensus of the IETF community. It has | ||||
received public review and has been approved for publication by the | ||||
Internet Engineering Steering Group (IESG). Further information on | ||||
Internet Standards is available in Section 2 of RFC 7841. | ||||
Copyright (c) 2016 IETF Trust and the persons identified as the | Information about the current status of this document, any errata, | |||
document authors. All rights reserved. | and how to provide feedback on it may be obtained at | |||
http://www.rfc-editor.org/info/rfc7892. | ||||
This document is subject to BCP 78 and the IETF Trust's Legal | Copyright Notice | |||
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 | Copyright (c) 2016 IETF Trust and the persons identified as the | |||
Contributions published or made publicly available before November | document authors. All rights reserved. | |||
10, 2008. The person(s) controlling the copyright in some of this | ||||
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 | 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. | ||||
IANA has defined an "OTN Signal Type" subregistry of the | This document may contain material from IETF Documents or IETF | |||
"Generalized Multi-Protocol Label Switching (GMPLS) Signaling | Contributions published or made publicly available before November | |||
Parameters" registry. This document updates the OTN Signal Type | 10, 2008. The person(s) controlling the copyright in some of this | |||
subregistry specified in RFC 7139 to allow Specification Required | material may not have granted the IETF Trust the right to allow | |||
policies, as defined in RFC 5226. | 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. | ||||
Table of Contents | Table of Contents | |||
1. Introduction...................................................2 | 1. Introduction ................................................... 2 | |||
2. Security Considerations........................................2 | 2. Security Considerations ........................................ 3 | |||
3. IANA Considerations............................................2 | 3. IANA Considerations ............................................ 3 | |||
4. Acknowledgments................................................3 | 4. References ..................................................... 3 | |||
5. References.....................................................3 | 4.1. Normative References ...................................... 3 | |||
5.1. Normative References.......................................3 | 4.2. Informative References .................................... 3 | |||
5.2. Informative References.....................................3 | Acknowledgments ................................................... 4 | |||
Authors' Addresses ................................................ 4 | ||||
1. Introduction | 1. Introduction | |||
IANA maintains "OTN Signal Type" subregistry of the "Generalized | IANA maintains "OTN Signal Type" subregistry of the "Generalized | |||
Multi-Protocol Label Switching (GMPLS) Signaling Parameters" | Multi-Protocol Label Switching (GMPLS) Signaling Parameters" registry | |||
registry for the OTN signal defined in [RFC4328] and updated by | for OTN signal types (as defined in [RFC4328] and updated by | |||
[RFC7139]. This subregistry is defined to use only the Standards | [RFC7139]). This subregistry is defined to use only the Standards | |||
Action registration policy as defined by [RFC5226]. This | Action registration policy as defined by [RFC5226]. This document | |||
document updates [RFC7139] to allow the "OTN Signal Type" | updates [RFC7139] to allow the "OTN Signal Type" subregistry to also | |||
subregistry to also support Specification Required policies, as | use the Specification Required policy as defined in [RFC5226]. | |||
defined in [RFC5226]. | ||||
2. Security Considerations | ||||
This document does not introduce any new security considerations | 2. Security Considerations | |||
to the existing GMPLS signaling protocols. Refer to [RFC7139] | ||||
for further details of the specific security measures. | ||||
Additionally, [RFC5920] provides an overview of security | ||||
vulnerabilities and protection mechanisms for the GMPLS control | ||||
plane. | ||||
3. IANA Considerations | This document does not introduce any new security considerations to | |||
the existing GMPLS signaling protocols. Refer to [RFC7139] for | ||||
further details of the specific security measures. Additionally, | ||||
[RFC5920] provides an overview of security vulnerabilities and | ||||
protection mechanisms for the GMPLS control plane. | ||||
IANA maintains the "OTN Signal Type" subregistry of the | 3. IANA Considerations | |||
"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 requests that the "OTN Signal Type" subregistry of | IANA maintains the "OTN Signal Type" subregistry of the "Generalized | |||
the "Generalized Multi-Protocol Label Switching (GMPLS) | Multi-Protocol Label Switching (GMPLS) Signaling Parameters" | |||
Signaling Parameters" registry be updated with registration | registry. The registry currently is defined to use the Standards | |||
policies of "Standards Action" for Standards Track documents, | Action registration policy as defined by [RFC5226]. | |||
and "Specification Required" for other documents. | ||||
When needed, the Designated Expert shall be any current CCAMP WG | Per this document, IANA has updated the registration policies for the | |||
chair or, in the case the group is no longer active, designated | "OTN Signal Type" subregistry to be "Standards Action" for Standards | |||
by the IESG. | Track documents and "Specification Required" for other documents. | |||
4. Acknowledgments | 4. References | |||
The authors would like to thank Lou Berger, Deborah Brungard, | 4.1. Normative References | |||
Daniele Ceccarelli, Adrian Farrel, Vijay Gurbani, Huub van | ||||
Helvoort, Barry Lieba and Robert Sparks for comments. | ||||
5. References | [RFC4328] Papadimitriou, D., Ed., "Generalized Multi-Protocol Label | |||
Switching (GMPLS) Signaling Extensions for G.709 Optical | ||||
Transport Networks Control", RFC 4328, | ||||
DOI 10.17487/RFC4328, January 2006, | ||||
<http://www.rfc-editor.org/info/rfc4328>. | ||||
5.1. Normative References | [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, | ||||
DOI 10.17487/RFC7139, March 2014, | ||||
<http://www.rfc-editor.org/info/rfc7139>. | ||||
[RFC4328] Papadimitriou, D., Ed., "Generalized Multi-Protocol | [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an | |||
Label Switching (GMPLS) Signaling Extensions for G.709 | IANA Considerations Section in RFCs", BCP 26, RFC 5226, | |||
Optical Transport Networks Control", RFC 4328, January | DOI 10.17487/RFC5226, May 2008, | |||
2006. | <http://www.rfc-editor.org/info/rfc5226>. | |||
[RFC7139] Zhang, F., Ed., Zhang, G., Belotti, S., Ceccarelli, | 4.2. Informative References | |||
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 | [RFC5920] Fang, L., Ed., "Security Framework for MPLS and GMPLS | |||
an IANA Considerations Section in RFCs", BCP 26, RFC | Networks", RFC 5920, DOI 10.17487/RFC5920, July 2010, | |||
5226, May 2008. | <http://www.rfc-editor.org/info/rfc5920>. | |||
5.2. Informative References | Acknowledgments | |||
[RFC5920] Fang, L., Ed., "Security Framework for MPLS and GMPLS | The authors would like to thank Lou Berger, Deborah Brungard, Daniele | |||
Networks", RFC 5920, July 2010. | Ceccarelli, Adrian Farrel, Vijay Gurbani, Huub van Helvoort, Barry | |||
Leiba, and Robert Sparks for comments. | ||||
Authors' Addresses | Authors' Addresses | |||
Zafar Ali | Zafar Ali | |||
Cisco Systems | Cisco Systems | |||
Email: zali@cisco.com | Email: zali@cisco.com | |||
Antonello Bonfanti | Antonello Bonfanti | |||
Cisco Systems | Cisco Systems | |||
abonfant@cisco.com | ||||
Email: abonfant@cisco.com | ||||
Matt Hartley | Matt Hartley | |||
Cisco Systems | Cisco Systems | |||
mhartley@cisco.com | ||||
Email: mhartley@cisco.com | ||||
Fatai Zhang | Fatai Zhang | |||
Huawei Technologies | Huawei Technologies | |||
Email: zhangfatai@huawei.com | Email: zhangfatai@huawei.com | |||
End of changes. 34 change blocks. | ||||
111 lines changed or deleted | 105 lines changed or added | |||
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |