draft-ietf-ccamp-additional-signal-type-g709v3-04.txt   rfc7963.txt 
CCAMP Working Group Zafar Ali
Internet Draft Antonello Bonfanti
Matt Hartley
Intended status: Informational Cisco Systems
F. Zhang
Huawei Technologies
Expires: November 25, 2016 May 25, 2016
Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Internet Engineering Task Force (IETF) Z. Ali
Extension for Additional Signal Types in G.709 OTN Request for Comments: 7963 A. Bonfanti
draft-ietf-ccamp-additional-signal-type-g709v3-04.txt Category: Informational M. Hartley
ISSN: 2070-1721 Cisco Systems
Status of this Memo F. Zhang
Huawei Technologies
August 2016
This Internet-Draft is submitted in full conformance with the RSVP-TE Extension for Additional Signal Types in
provisions of BCP 78 and BCP 79. G.709 Optical Transport Networks (OTNs)
Internet-Drafts are working documents of the Internet Engineering Abstract
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 RFCs 4328 and 7139 provide signaling extensions in Resource
months and may be updated, replaced, or obsoleted by other ReserVation Protocol - Traffic Engineering (RSVP-TE) to control the
documents at any time. It is inappropriate to use Internet-Drafts full set of Optical Transport Network (OTN) features. However, these
as reference material or to cite them other than as "work in specifications do not cover the additional Optical channel Data Unit
progress." (ODU) containers defined in G.Sup43 (ODU1e, ODU3e1, and ODU3e2).
This document defines new Signal Types for these additional
containers.
This Internet-Draft will expire on November 25, 2016. Status of This Memo
Copyright Notice This document is not an Internet Standards Track specification; it is
published for informational purposes.
Copyright (c) 2016 IETF Trust and the persons identified as the This document is a product of the Internet Engineering Task Force
document authors. All rights reserved. (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). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see Section 2 of RFC 7841.
This document is subject to BCP 78 and the IETF Trust's Legal Information about the current status of this document, any errata,
Provisions Relating to IETF Documents and how to provide feedback on it may be obtained at
(http://trustee.ietf.org/license-info) in effect on the date of http://www.rfc-editor.org/info/rfc7963.
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 Notice
Contributions published or made publicly available before November
Internet-Draft draft-ietf-ccamp-additional-signal-type-g709v3-
04.txt
10, 2008. The person(s) controlling the copyright in some of this Copyright (c) 2016 IETF Trust and the persons identified as the
material may not have granted the IETF Trust the right to allow document authors. All rights reserved.
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.
RFC 4328 and RFC 7139 provide Resource ReserVation Protocol-Traffic This document may contain material from IETF Documents or IETF
Engineering (RSVP-TE) signaling extensions to control the full set Contributions published or made publicly available before November
of Optical Transport Network (OTN) features. However, these 10, 2008. The person(s) controlling the copyright in some of this
specifications do not cover the additional Optical channel Data material may not have granted the IETF Trust the right to allow
Unit (ODU) containers defined in G.Sup43 (ODU1e, ODU3e1 and modifications of such material outside the IETF Standards Process.
ODU3e2). This document defines new signal types for these Without obtaining an adequate license from the person(s) controlling
additional containers. 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 ................................................... 3
2. RSVP-TE extension for Additional Signal Types..................3 2. RSVP-TE Extension for Additional Signal Types .................. 3
3. Security Considerations........................................3 3. Security Considerations ........................................ 3
4. IANA Considerations............................................3 4. IANA Considerations ............................................ 3
5. Acknowledgments................................................3 5. References ..................................................... 4
6. References.....................................................3 5.1. Normative References ....................................... 4
6.1. Normative References.......................................4 5.2. Informative References ..................................... 4
6.2. Informative References.....................................4 Acknowledgments ................................................... 4
Authors' Addresses ................................................ 5
1. Introduction
[RFC7139] updates the Optical channel Data Unit (ODU)-related 1. Introduction
portions of [RFC4328] to provide Resource ReserVation Protocol-
Traffic Engineering (RSVP-TE) extensions to support control for
[G.709-v3] in the OTN-TDM SENDER_TSPEC and OTN-TDM FLOWSPEC
objects. However, it does not specify signal types for the
containers defined in [G.Sup43] (ODU1e, ODU3e1, and ODU3e2).
This document provides RSVP-TE signaling extensions to support
these additional signal types.
These containers are non-standard data plane frame formats (not [RFC7139] updates the portions of text related to the Optical channel
defined in ITU-T Recommendations). They are among some of the Data Unit (ODU) described in [RFC4328] to provide extensions to
intra-domain approaches used in networks for transport of Resource ReserVation Protocol - Traffic Engineering (RSVP-TE) to
10GBASE-R signals in optical transport networks. As a support control for [G.709-v3] in the OTN-TDM SENDER_TSPEC and OTN-
Supplement, [G.Sup43], does not guarantee interoperability in TDM FLOWSPEC objects. However, it does not specify Signal Types for
the data plane for these containers. the ODU1e, ODU3e1, and ODU3e2 containers defined in [G.Sup43]. This
document provides RSVP-TE signaling extensions to support these
additional Signal Types.
Internet-Draft draft-ietf-ccamp-additional-signal-type-g709v3- These containers are non-standard data-plane frame formats (not
04.txt defined in ITU-T Recommendations). They are among some of the intra-
domain approaches used in networks to transport 10GBASE-R signals in
optical transport networks. As a supplement, [G.Sup43] does not
guarantee interoperability in the data plane for these containers.
2. RSVP-TE extension for Additional Signal Types 2. RSVP-TE Extension for Additional Signal Types
[RFC7139] defines the format of Traffic Parameters in OTN-TDM [RFC7139] defines the format of Traffic Parameters in OTN-TDM
SENDER_TSPEC and OTN-TDM FLOWSPEC objects. These traffic SENDER_TSPEC and OTN-TDM FLOWSPEC objects. These traffic parameters
parameters have a signal type field. This document defines the have a Signal Type field. This document defines the Signal Types for
signal type for ODU1e, ODU3e1 and ODU3e2 as defined in the IANA ODU1e, ODU3e1, and ODU3e2, as defined in the IANA Considerations
considerations section. They are allocated from the section. They are allocated via the Specification Required policy
Specification Required policy added to the subregistry by added to the subregistry by [RFC7892].
[RFC7892].
3. Security Considerations 3. Security Considerations
This document does not introduce any additional security issues This document does not introduce any additional security issues
above those identified in [RFC7139]. beyond those identified in [RFC7139].
4. IANA Considerations 4. IANA Considerations
IANA maintains a registry called "Generalized Multi-Protocol IANA maintains the "Generalized Multi-Protocol Label Switching
Label Switching (GMPLS) Signaling Parameters" with a subregistry (GMPLS) Signaling Parameters" registry that contains the "OTN Signal
called "OTN Signal Type". IANA is requested to make three Type" subregistry. IANA has added the following three allocations
further allocations from this registry under the Specification for ODU1e, ODU3e1, and ODU3e2 in the subregistry via the
Required policy for ODU1e, ODU3e1 and ODU3e2 as follows: Specification Required policy [RFC5226]:
Value Type Value Type
----- ---- ----- ----
TBD (IANA is requested ODU1e (10Gbps Ethernet [G.Sup43]) 23 ODU1e (10Gbps Ethernet [G.Sup43])
to assign the value 23) 26 ODU3e1 (40Gbps Ethernet [G.Sup43])
TBD (IANA is requested ODU3e1 (40Gbps Ethernet [G.Sup43]) 27 ODU3e2 (40Gbps Ethernet [G.Sup43])
to assign the value 26)
TBD (IANA is requested ODU3e2 (40Gbps Ethernet [G.Sup43])
to assign the value 27)
These signaled types are carried in Traffic Parameters in OTN- These Signal Types are carried in the Traffic Parameters in OTN-TDM
TDM SENDER_TSPEC and OTN-TDM FLOWSPEC objects [RFC7139]. SENDER_TSPEC and OTN-TDM FLOWSPEC objects [RFC7139].
5. Acknowledgments 5. References
The authors would like to thank Dieter Beller, Lou Berger, 5.1. Normative References
Deborah Brungard, Daniele Ceccarelli, Adrian Farrel and Sudip
Shukla for comments.
6. References [RFC4328] Papadimitriou, D., Ed., "Generalized Multi-Protocol Label
Internet-Draft draft-ietf-ccamp-additional-signal-type-g709v3- Switching (GMPLS) Signaling Extensions for G.709 Optical
04.txt Transport Networks Control", RFC 4328,
DOI 10.17487/RFC4328, January 2006,
<http://www.rfc-editor.org/info/rfc4328>.
6.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 [RFC7892] Ali, Z., Bonfanti, A., Hartley, M., and F. Zhang, "IANA
Label Switching (GMPLS) Signaling Extensions for G.709 Allocation Procedures for the GMPLS OTN Signal Type
Optical Transport Networks Control", RFC 4328, January Registry", RFC 7892, DOI 10.17487/RFC7892, May 2016,
2006. <http://www.rfc-editor.org/info/rfc7892>.
[RFC7139] F. Zhang, Ed., G. Zhang, S. Belotti, D. Ceccarelli, 5.2. Informative References
and K. Pithewan, "GMPLS Signaling Extensions for
Control of Evolving G.709 Optical Transport Networks",
RFC 7139, March 2014.
[RFC7892] Z. Ali, A. Bonfanti, M. Hartley, F. Zhang, "IANA [G.709-v3] ITU-T, "Interfaces for the optical transport network",
Allocation Procedures for the GMPLS OTN Signal Type Recommendation G.709/Y.1331, June 2016.
Registry", May 2016.
6.2. Informative References [G.Sup43] ITU-T, "Transport of IEEE 10GBASE-R in optical transport
networks (OTN)", Recommendation G.Sup43, February 2011.
[G.709-v3] ITU-T, "Interface for the Optical Transport Network [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
(OTN)", G.709/Y.1331 Recommendation, February, 2012. IANA Considerations Section in RFCs", BCP 26, RFC 5226,
DOI 10.17487/RFC5226, May 2008,
<http://www.rfc-editor.org/info/rfc5226>.
[G.Sup43] ITU-T, "Transport of IEEE 10GBASE-R in optical Acknowledgments
transport networks (OTN)", February, 2011.
The authors would like to thank Dieter Beller, Lou Berger, Deborah
Brungard, Daniele Ceccarelli, Adrian Farrel, and Sudip Shukla for
their 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. 39 change blocks. 
134 lines changed or deleted 132 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/