CCAMP Working Group Zafar AliInternetDraftEngineering Task Force (IETF) Z. Ali Request for Comments: 7963 Antonello BonfantiMatt Hartley Intended status:Category: Informational M. Hartley ISSN: 2070-1721 Cisco Systems F. Zhang Huawei TechnologiesExpires: November 25, 2016 May 25,August 2016Resource ReserVation Protocol-Traffic Engineering (RSVP-TE)RSVP-TE Extension for Additional Signal Types in G.709OTN draft-ietf-ccamp-additional-signal-type-g709v3-04.txtOptical Transport Networks (OTNs) Abstract RFCs 4328 and 7139 provide signaling extensions in Resource ReserVation Protocol - Traffic Engineering (RSVP-TE) to control the full set of Optical Transport Network (OTN) features. However, these specifications do not cover the additional Optical channel Data Unit (ODU) containers defined in G.Sup43 (ODU1e, ODU3e1, and ODU3e2). This document defines new Signal Types for these additional containers. Status ofthisThis Memo ThisInternet-Draftdocument issubmitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documentsnot an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Internet Engineering Task Force (IETF).Note that other groups may also distribute working documents as Internet-Drafts. The listIt represents the consensus ofcurrent Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents validthe 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 amaximumcandidate for any level of Internet Standard; see Section 2 of RFC 7841. Information about the current status ofsix monthsthis document, any errata, and how to provide feedback on it may beupdated, replaced, or obsoleted by other documentsobtained atany 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 November 25, 2016.http://www.rfc-editor.org/info/rfc7963. Copyright Notice Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved. 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. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before NovemberInternet-Draft draft-ietf-ccamp-additional-signal-type-g709v3- 04.txt10, 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 RFC 4328 and RFC 7139 provide Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) signaling extensions to control the full set of Optical Transport Network (OTN) features. However, these specifications do not cover the additional Optical channel Data Unit (ODU) containers defined in G.Sup43 (ODU1e, ODU3e1 and ODU3e2). This document defines new signal types for these additional containers.Table of Contents 1.Introduction...................................................2Introduction ................................................... 3 2. RSVP-TEextensionExtension for Additional SignalTypes..................3Types .................. 3 3. SecurityConsiderations........................................3Considerations ........................................ 3 4. IANAConsiderations............................................3Considerations ............................................ 3 5.Acknowledgments................................................3 6. References.....................................................3 6.1.References ..................................................... 4 5.1. NormativeReferences.......................................4 6.2.References ....................................... 4 5.2. InformativeReferences.....................................4References ..................................... 4 Acknowledgments ................................................... 4 Authors' Addresses ................................................ 5 1. Introduction [RFC7139] updates the portions of text related to the Optical channel Data Unit(ODU)-related portions of(ODU) described in [RFC4328] to provide extensions to Resource ReserVationProtocol-Protocol - Traffic Engineering (RSVP-TE)extensionsto support control for [G.709-v3] in the OTN-TDM SENDER_TSPEC andOTN-TDMOTN- TDM FLOWSPEC objects. However, it does not specifysignal typesSignal Types for the ODU1e, ODU3e1, and ODU3e2 containers defined in[G.Sup43] (ODU1e, ODU3e1, and ODU3e2).[G.Sup43]. This document provides RSVP-TE signaling extensions to support these additionalsignal types.Signal Types. These containers are non-standarddata planedata-plane frame formats (not defined in ITU-T Recommendations). They are among some of theintra-domainintra- domain approaches used in networksforto transportof10GBASE-R signals in optical transport networks. As aSupplement, [G.Sup43],supplement, [G.Sup43] does not guarantee interoperability in the data plane for these containers.Internet-Draft draft-ietf-ccamp-additional-signal-type-g709v3- 04.txt2. RSVP-TEextensionExtension for Additional Signal Types [RFC7139] defines the format of Traffic Parameters in OTN-TDM SENDER_TSPEC and OTN-TDM FLOWSPEC objects. These traffic parameters have asignal typeSignal Type field. This document defines thesignal typeSignal Types for ODU1e,ODU3e1ODU3e1, andODU3e2ODU3e2, as defined in the IANAconsiderationsConsiderations section. They are allocatedfromvia the Specification Required policy added to the subregistry by [RFC7892]. 3. Security Considerations This document does not introduce any additional security issuesabovebeyond those identified in [RFC7139]. 4. IANA Considerations IANA maintainsa registry calledthe "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Parameters"with a subregistry calledregistry that contains the "OTN SignalType".Type" subregistry. IANAis requested to makehas added the following threefurtherallocationsfrom this registry under the Specification Required policyfor ODU1e,ODU3e1ODU3e1, and ODU3e2as follows:in the subregistry via the Specification Required policy [RFC5226]: Value Type ----- ----TBD (IANA is requested23 ODU1e (10Gbps Ethernet [G.Sup43])to assign the value 23) TBD (IANA is requested26 ODU3e1 (40Gbps Ethernet [G.Sup43])to assign the value 26) TBD (IANA is requested27 ODU3e2 (40Gbps Ethernet [G.Sup43])to assign the value 27)Thesesignaled typesSignal Types are carried in the Traffic Parameters inOTN- TDMOTN-TDM SENDER_TSPEC and OTN-TDM FLOWSPEC objects [RFC7139]. 5.Acknowledgments The authors would like to thank Dieter Beller, Lou Berger, Deborah Brungard, Daniele Ceccarelli, Adrian Farrel and Sudip Shukla for comments. 6.ReferencesInternet-Draft draft-ietf-ccamp-additional-signal-type-g709v3- 04.txt 6.1.5.1. Normative 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, January2006.2006, <http://www.rfc-editor.org/info/rfc4328>. [RFC7139]F.Zhang, F., Ed.,G.Zhang,S.G., Belotti,D.S., Ceccarelli, D., and K. Pithewan, "GMPLS Signaling Extensions for Control of Evolving G.709 Optical Transport Networks", RFC 7139, DOI 10.17487/RFC7139, March2014.2014, <http://www.rfc-editor.org/info/rfc7139>. [RFC7892]Z.Ali,A.Z., Bonfanti,M.A., Hartley, M., and F. Zhang, "IANA Allocation Procedures for the GMPLS OTN Signal Type Registry", RFC 7892, DOI 10.17487/RFC7892, May2016. 6.2.2016, <http://www.rfc-editor.org/info/rfc7892>. 5.2. Informative References [G.709-v3] ITU-T,"Interface"Interfaces for theOptical Transport Network (OTN)",optical transport network", Recommendation G.709/Y.1331 Recommendation,February, 2012.June 2016. [G.Sup43] ITU-T, "Transport of IEEE 10GBASE-R in optical transport networks (OTN)", Recommendation G.Sup43, February, 2011. [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, DOI 10.17487/RFC5226, May 2008, <http://www.rfc-editor.org/info/rfc5226>. Acknowledgments The authors would like to thank Dieter Beller, Lou Berger, Deborah Brungard, Daniele Ceccarelli, Adrian Farrel, and Sudip Shukla for their comments. Authors' Addresses Zafar Ali Cisco Systems Email: zali@cisco.com Antonello Bonfanti Cisco Systems Email: abonfant@cisco.com Matt Hartley Cisco Systems Email: mhartley@cisco.com Fatai Zhang Huawei Technologies Email: zhangfatai@huawei.comExpires November 2016 [Page 4]