CCAMP Working Group                                       Zafar Ali
Internet Draft Engineering Task Force (IETF)                            Z. Ali
Request for Comments: 7963                            Antonello Bonfanti
                                                       Matt Hartley
Intended status:
Category: Informational                                       M. Hartley
ISSN: 2070-1721                                            Cisco Systems
                                                                F. Zhang
                                                     Huawei Technologies
Expires: November 25, 2016                             May 25,
                                                             August 2016

     Resource ReserVation Protocol-Traffic Engineering (RSVP-TE)

            RSVP-TE Extension for Additional Signal Types in
                G.709 OTN
        draft-ietf-ccamp-additional-signal-type-g709v3-04.txt Optical Transport Networks (OTNs)

Abstract

RFC

   RFCs 4328 and RFC 7139 provide signaling extensions in Resource
   ReserVation Protocol-Traffic 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 ODU3e1, and ODU3e2).
   This document defines new signal types Signal Types for these additional
   containers.

Status of this This Memo

   This Internet-Draft document is submitted in full conformance with the
provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents not 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 list  It represents the consensus of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid 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 maximum candidate for any level of Internet
   Standard; see Section 2 of six
months RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be updated, replaced, or obsoleted by other
documents obtained 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 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 November

Internet-Draft draft-ietf-ccamp-additional-signal-type-g709v3-
04.txt
   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.

Table of Contents

   1. Introduction...................................................2 Introduction ................................................... 3
   2. RSVP-TE extension Extension for Additional Signal Types..................3 Types .................. 3
   3. Security Considerations........................................3 Considerations ........................................ 3
   4. IANA Considerations............................................3 Considerations ............................................ 3
   5. Acknowledgments................................................3
   6. References.....................................................3
     6.1. References ..................................................... 4
     5.1. Normative References.......................................4
     6.2. References ....................................... 4
     5.2. Informative References.....................................4 References ..................................... 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 ReserVation Protocol- Protocol - Traffic Engineering (RSVP-TE) extensions to
   support control for [G.709-v3] in the OTN-TDM SENDER_TSPEC and OTN-TDM OTN-
   TDM FLOWSPEC objects.  However, it does not specify signal types Signal 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
   additional signal types. Signal Types.

   These containers are non-standard data plane data-plane frame formats (not
   defined in ITU-T Recommendations).  They are among some of the
   intra-domain intra-
   domain approaches used in networks for to transport of 10GBASE-R signals in
   optical transport networks.  As a
   Supplement, [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.txt

2.  RSVP-TE extension Extension 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 a signal type Signal Type field.  This document defines the
   signal type Signal Types for
   ODU1e, ODU3e1 ODU3e1, and ODU3e2 ODU3e2, as defined in the IANA
   considerations Considerations
   section.  They are allocated from via the Specification Required policy
   added to the subregistry by [RFC7892].

3.  Security Considerations

   This document does not introduce any additional security issues
   above
   beyond those identified in [RFC7139].

4.  IANA Considerations

   IANA maintains a registry called the "Generalized Multi-Protocol Label Switching
   (GMPLS) Signaling Parameters" with a subregistry
   called registry that contains the "OTN Signal Type".
   Type" subregistry.  IANA is requested to make has added the following three
   further allocations from this registry under the Specification
   Required policy
   for ODU1e, ODU3e1 ODU3e1, and ODU3e2 as follows: in the subregistry via the
   Specification Required policy [RFC5226]:

   Value            Type
   -----            ----
   TBD (IANA is requested
   23               ODU1e  (10Gbps Ethernet [G.Sup43])
     to assign the value 23)
   TBD (IANA is requested
   26               ODU3e1 (40Gbps Ethernet [G.Sup43])
     to assign the value 26)
   TBD (IANA is requested
   27               ODU3e2 (40Gbps Ethernet [G.Sup43])
     to assign the value 27)

   These signaled types Signal Types are carried in the Traffic Parameters in OTN-
   TDM OTN-TDM
   SENDER_TSPEC and OTN-TDM FLOWSPEC objects [RFC7139].

6.

5.  References

Internet-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, January
             2006. 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, March 2014. 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, May 2016.

6.2. 2016,
              <http://www.rfc-editor.org/info/rfc7892>.

5.2.  Informative References

   [G.709-v3] ITU-T, "Interface "Interfaces for the Optical 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.

5.

   [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 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.com

                     Expires November 2016               [Page 4]