draft-ietf-ccamp-otn-signal-type-subregistry-02.txt   draft-ietf-ccamp-otn-signal-type-subregistry-03.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 Intended status: Standards Track Matt Hartley
Cisco Systems Cisco Systems
F. Zhang F. Zhang
Huawei Technologies Huawei Technologies
Expires: March 10, 2016 September 10, 2015 Expires: August 2, 2016 February 2, 2016
IANA Allocation Procedures for OTN Signal Type Subregistry to 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-02.txt draft-ietf-ccamp-otn-signal-type-subregistry-03.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/.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet-Drafts documents at any time. It is inappropriate to use Internet-Drafts
as reference material or to cite them other than as "work in as reference material or to cite them other than as "work in
progress." progress."
This Internet-Draft will expire on March 10, 2015. This Internet-Draft will expire on August 2, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without Section 4.e of the Trust Legal Provisions and are provided without
skipping to change at page 2, line 16 skipping to change at page 2, line 16
modifications of such material outside the IETF Standards Process. modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) Without obtaining an adequate license from the person(s)
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 to 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 proposes changes to the OTN Signal Parameters" registry. This draft updates the OTN Signal Type
Type subregistry to include Specification Required policies, as subregistry to allow Specification Required policies, as defined in
defined in [RFC5226]. RFC 5226.
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
this document are to be interpreted as described in RFC 2119 this document are to be interpreted as described in RFC 2119
[RFC2119]. [RFC2119].
Table of Contents Table of Contents
1. Introduction 2 1. Introduction...................................................2
2. IANA Considerations 3 2. IANA Considerations............................................2
3. References 3 3. Acknowledgments................................................3
3.1. Normative References 3 4. References.....................................................3
3.2. Informative References 3 4.1. Normative References.......................................3
1. Introduction 1. Introduction
[RFC4328] and [RFC7139] provide the extensions to the IANA maintains "OTN Signal Type" subregistry of the "Generalized
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
values from the Standards Action registration policy defined in
[RFC5226].
IANA maintains "OTN Signal Type" subregistry to 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 [RFC7139]. registry for the OTN signal defined in [RFC4328] and updated by
However, this subregistry currently is defined to only use the [RFC7139]. This subregistry is defined to use only the Standards
Standards Action registration policy as defined by [RFC5226]. Action registration policy as defined by [RFC5226]. This
This document extends "OTN Signal Type" subregistry to also document updates [RFC7139] to allow the "OTN Signal Type"
support Specification Required policies, as defined in subregistry to also support Specification Required policies, as
[RFC5226]. defined in [RFC5226].
2. IANA Considerations 2. IANA Considerations
IANA maintains the an "OTN Signal Type" subregistry to 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]. This document directs that both Standards Action and [RFC5226].
IETF Review policies, as defined in [RFC5226], be applied to
this subregistry. When needed, the Designated Expert shall be This document requests that the "OTN Signal Type" subregistry of
identified by a CCAMP WG chair or, in the case the group is no the "Generalized Multi-Protocol Label Switching (GMPLS)
longer active, by the IESG. Signaling Parameters" registry be updated with the following
registration policies: "Standards Action" and "Specification
Required" as defined in [RFC5226].
When needed, the Designated Expert shall be any current CCAMP WG
chair or, in the case the group is no longer active, designated
by the IESG.
3. Acknowledgments 3. Acknowledgments
The authors would like to thank Lou Berger and Adrian Farrel for The authors would like to thank Lou Berger, Deborah Brungard,
Daniele Ceccarelli, Adrian Farrel and Huub van Helvoort for
comments. comments.
4. References 4. References
4.1. Normative References 4.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4328] Papadimitriou, D., Ed., "Generalized Multi-Protocol [RFC4328] Papadimitriou, D., Ed., "Generalized Multi-Protocol
skipping to change at page 3, line 45 skipping to change at page 3, line 45
[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.
4.2. Informative References
[GSUP.43] ITU-T, "Proposed revision of G.sup43 (for agreement)",
February, 2011.
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 abonfant@cisco.com
 End of changes. 14 change blocks. 
43 lines changed or deleted 35 lines changed or added

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