draft-ietf-ccamp-otn-signal-type-subregistry-03.txt   draft-ietf-ccamp-otn-signal-type-subregistry-04.txt 
CCAMP Working Group Zafar Ali CCAMP Working Group Zafar Ali
Internet Draft Antonello Bonfanti Internet Draft Antonello Bonfanti
Intended status: Standards Track Matt Hartley Updates: 7139 Matt Hartley
Cisco Systems Intended status: Standards Track Cisco Systems
F. Zhang F. Zhang
Huawei Technologies Huawei Technologies
Expires: August 2, 2016 February 2, 2016 Expires: September 10, 2016 March 10, 2016
IANA Allocation Procedures for OTN Signal Type Subregistry of IANA Allocation Procedures for OTN Signal Type Subregistry of
the GMPLS Signaling Parameters Registry the GMPLS Signaling Parameters Registry
draft-ietf-ccamp-otn-signal-type-subregistry-03.txt draft-ietf-ccamp-otn-signal-type-subregistry-04.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
skipping to change at page 2, line 18 skipping to change at page 2, line 18
controlling the copyright in such materials, this document may not controlling the copyright in such materials, this document may not
be modified outside the IETF Standards Process, and derivative be modified outside the IETF Standards Process, and derivative
works of it may not be created outside the IETF Standards Process, 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 except to format it for publication as an RFC or to translate it
into languages other than English. into languages other than English.
Abstract Abstract
IANA has defined an "OTN Signal Type" subregistry of the IANA has defined an "OTN Signal Type" subregistry of the
"Generalized Multi-Protocol Label Switching (GMPLS) Signaling "Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Parameters" registry. This draft updates the OTN Signal Type Parameters" registry. This document updates the OTN Signal Type
subregistry to allow Specification Required policies, as defined in subregistry specified in RFC 7139 to allow Specification Required
RFC 5226. policies, as defined in RFC 5226.
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 Table of Contents
1. Introduction...................................................2 1. Introduction...................................................2
2. IANA Considerations............................................2 2. Security Considerations........................................2
3. Acknowledgments................................................3 3. IANA Considerations............................................2
4. References.....................................................3 4. Acknowledgments................................................3
4.1. Normative References.......................................3 5. References.....................................................3
5.1. Normative References.......................................3
5.2. Informative References.....................................3
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 for the OTN signal defined in [RFC4328] and updated by registry for the OTN signal 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 updates [RFC7139] to allow the "OTN Signal Type" document updates [RFC7139] to allow the "OTN Signal Type"
subregistry to also support Specification Required policies, as subregistry to also support Specification Required policies, as
defined in [RFC5226]. defined in [RFC5226].
2. IANA Considerations 2. Security Considerations
This document introduces no 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.
3. IANA Considerations
IANA maintains the "OTN Signal Type" subregistry of the IANA maintains the "OTN Signal Type" subregistry of the
"Generalized Multi-Protocol Label Switching (GMPLS) Signaling "Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Parameters" registry. The registry currently is defined to use Parameters" registry. The registry currently is defined to use
the Standards Action registration policy as defined by the Standards Action registration policy as defined by
[RFC5226]. [RFC5226].
This document requests that the "OTN Signal Type" subregistry of This document requests that the "OTN Signal Type" subregistry of
the "Generalized Multi-Protocol Label Switching (GMPLS) the "Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Parameters" registry be updated with the following Signaling Parameters" registry be updated with the following
registration policies: "Standards Action" and "Specification registration policies: "Standards Action" and "Specification
Required" as defined in [RFC5226]. Required" as defined in [RFC5226].
When needed, the Designated Expert shall be any current CCAMP WG When needed, the Designated Expert shall be any current CCAMP WG
chair or, in the case the group is no longer active, designated chair or, in the case the group is no longer active, designated
by the IESG. by the IESG.
3. Acknowledgments 4. Acknowledgments
The authors would like to thank Lou Berger, Deborah Brungard, The authors would like to thank Lou Berger, Deborah Brungard,
Daniele Ceccarelli, Adrian Farrel and Huub van Helvoort for Daniele Ceccarelli, Adrian Farrel, Huub van Helvoort and Robert
comments. Sparks for comments.
4. References
4.1. Normative References 5. References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 5.1. Normative References
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4328] Papadimitriou, D., Ed., "Generalized Multi-Protocol [RFC4328] Papadimitriou, D., Ed., "Generalized Multi-Protocol
Label Switching (GMPLS) Signaling Extensions for G.709 Label Switching (GMPLS) Signaling Extensions for G.709
Optical Transport Networks Control", RFC 4328, January Optical Transport Networks Control", RFC 4328, January
2006. 2006.
[RFC7139] Zhang, F., Ed., Zhang, G., Belotti, S., Ceccarelli, [RFC7139] Zhang, F., Ed., Zhang, G., Belotti, S., Ceccarelli,
D., and K. Pithewan, "GMPLS Signaling Extensions for D., and K. Pithewan, "GMPLS Signaling Extensions for
Control of Evolving G.709 Optical Transport Networks", Control of Evolving G.709 Optical Transport Networks",
RFC 7139, March 2014. RFC 7139, March 2014.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing
an IANA Considerations Section in RFCs", BCP 26, RFC an IANA Considerations Section in RFCs", BCP 26, RFC
5226, May 2008. 5226, May 2008.
Authors' Addresses 5.2. Informative References
[RFC5920] Fang, L., Ed., "Security Framework for MPLS and GMPLS
Networks", RFC 5920, July 2010.
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 abonfant@cisco.com
Matt Hartley Matt Hartley
Cisco Systems Cisco Systems
 End of changes. 13 change blocks. 
29 lines changed or deleted 34 lines changed or added

This html diff was produced by rfcdiff 1.44. The latest version is available from http://tools.ietf.org/tools/rfcdiff/