[Docs] [txt|pdf] [Tracker] [Email] [Nits]

Versions: 00

     CCAMP Working Group                                       Zafar Ali
     Internet Draft                                          Manoj Kumar
     Intended status: Experimental                    Antonello Bonfanti
                                                       Akshaya Nadahalli
                                                           Cisco Systems
                                                             Fatai Zhang
                                                     Huawei Technologies
     
     Expires: April 30, 2017                            October 31, 2016
     
     
               RSVP-TE Extension for Beyond 100G Signal Types in
                    G.709 Optical Transport Networks (OTNs)
                   draft-ali-ccamp-oducn-signal-type-00.txt
     
     Status of this Memo
     
     This Internet-Draft is submitted in full conformance with the
     provisions of BCP 78 and BCP 79.
     
     Internet-Drafts are working documents of the Internet Engineering
     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
     months and may be updated, replaced, or obsoleted by other
     documents 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 April 30, 2017.
     
     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.
     
     
     
     
     
     Expires April 2017                                    [Page 1]


     Internet-Draft draft-ali-ccamp-ODUCn-signal-type-00.txt
     
     This document may contain material from IETF Documents or IETF
     Contributions published or made publicly available before November
     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.
     
     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.709/Y.1331 for ODUC1,
     ODUC2, ODUC3, ODUC4, ODUC5, ODUC6, ODUC7, ODUC8 and ODUC9. This
     document defines new Signal Types for these additional containers.
     
     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
     
        1. Introduction ................................................. 2
        2. RSVP-TE extension for Beyond 100G Signal Types ............... 3
        3. Security Considerations .......................................3
        4. IANA Considerations ...........................................3
        5. References ....................................................3
          5.1. Normative References ......................................3
          5.2. Informative References ....................................4
     
     1. Introduction
     
        [RFC7139] updates the portions of text related to the Optical
        channel Data Unit (ODU) described in [RFC4328] to provide
        extensions to Resource ReserVation Protocol - Traffic
        Engineering (RSVP-TE) 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 beyond 100G ODUCn
        containers defined in [G.709/Y.1331]. This document provides
        RSVP-TE signaling extensions to support ODUC1, ODUC2, ODUC3,
        ODUC4, ODUC5, ODUC6, ODUC7, ODUC8 and ODUC9 Signal Types.
     
     
                          Expires April 2017               [Page 2]


     Internet-Draft draft-ali-ccamp-ODUCn-signal-type-00.txt
     
     2. RSVP-TE extension for Beyond 100G 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 field.  This document defines the
        Signal Types for ODUC1, ODUC2, ODUC3, ODUC4, ODUC5, ODUC6,
        ODUC7, ODUC8 and ODUC9, as defined in the IANA Considerations
        section.  They are allocated via the Specification Required
        policy added to the subregistry by [RFC7892].
     
     
     3. Security Considerations
     
        This document does not introduce any additional security issues
        beyond those identified in [RFC7139].
     
     4. IANA Considerations
     
        IANA maintains the "Generalized Multi-Protocol Label Switching
        (GMPLS) Signaling Parameters" registry that contains the "OTN
        Signal Type" subregistry.
     
     This document request IANA to add the following signal types in the
     subregistry via the Specification Required policy [RFC5226]:
     
     
           Value            Type
           -----            ----
           TBA1             ODUC1  (100Gbps OTN [G.709/Y.1331])
           TBA2             ODUC2  (200Gbps OTN [G.709/Y.1331])
           TBA3             ODUC3  (300Gbps OTN [G.709/Y.1331])
           TBA4             ODUC4  (400Gbps OTN [G.709/Y.1331])
           TBA5             ODUC5  (500Gbps OTN [G.709/Y.1331])
           TBA6             ODUC6  (600Gbps OTN [G.709/Y.1331])
           TBA7             ODUC7  (700Gbps OTN [G.709/Y.1331])
           TBA8             ODUC8  (800Gbps OTN [G.709/Y.1331])
           TBA9             ODUC9  (900Gbps OTN [G.709/Y.1331])
     
     These Signal Types are carried in the Traffic Parameters in OTN-TDM
     SENDER_TSPEC and OTN-TDM FLOWSPEC objects [RFC7139].
     
     5. References
     
     
     5.1. Normative References
     
     
     
     
     
     
                          Expires April 2017               [Page 3]


     Internet-Draft draft-ali-ccamp-ODUCn-signal-type-00.txt
     
        [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, <http://www.rfc-
                  editor.org/info/rfc4328>.
     
        [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>. [RFC2119]
                  Bradner, S., "Key words for use in RFCs to Indicate
                  Requirement Levels", BCP 14, RFC 2119, March 1997.
     
        [RFC7892]  Ali, Z., Bonfanti, A., Hartley, M., and F. Zhang,
                  "IANA Allocation Procedures for the GMPLS OTN Signal
                  Type Registry", RFC 7892, DOI 10.17487/RFC7892, May
                  2016, <http://www.rfc-editor.org/info/rfc7892>.
     
     5.2. Informative References
     
        [G.709-v3] ITU-T, "Interfaces for the optical transport
                  network", Recommendation G.709/Y.1331, June 2016.
     
        [G.709/Y.1331] ITU-T, " Interfaces for the optical transport
                  network", G.709/Y.1331 (06/16).
     
        [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>. [G.709-v3] ITU-T, "Interface
                  for the Optical Transport Network (OTN)", G.709/Y.1331
                  Recommendation, February, 2012.
     
     Authors' Addresses
     
     
        Zafar Ali
        Cisco Systems
        Email: zali@cisco.com
     
        Manoj Kumar
        Cisco System
        Email: manojk2@cisco.com
     
        Akshaya Nadahalli
        Cisco Systems
        anadahal@cisco.com
     
        Antonello Bonfanti
        Cisco Systems
        abonfant@cisco.com
                          Expires April 2017               [Page 4]


     Internet-Draft draft-ali-ccamp-ODUCn-signal-type-00.txt
     
     
        Fatai Zhang
        Huawei Technologies
        Email: zhangfatai@huawei.com
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     
                          Expires April 2017               [Page 5]
     

Html markup produced by rfcmarkup 1.123, available from https://tools.ietf.org/tools/rfcmarkup/