draft-ietf-ccamp-additional-signal-type-g709v3-02.txt   draft-ietf-ccamp-additional-signal-type-g709v3-03.txt 
CCAMP Working Group Zafar Ali CCAMP Working Group Zafar Ali
Internet Draft Antonello Bonfanti Internet Draft Antonello Bonfanti
Intended status: Informational Matt Hartley Updates: 7139 Matt Hartley
Cisco Systems Intended status: Informational Cisco Systems
F. Zhang F. Zhang
Huawei Technologies Huawei Technologies
Expires: March 10, 2016 September 10, 2015 Expires: August 5, 2016 February 5, 2016
Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Resource ReserVation Protocol-Traffic Engineering (RSVP-TE)
Extension for Additional Signal Types in G.709 OTN Extension for Additional Signal Types in G.709 OTN
draft-ietf-ccamp-additional-signal-type-g709v3-02.txt draft-ietf-ccamp-additional-signal-type-g709v3-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 5, 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
warranty as described in the Simplified BSD License. warranty as described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November Contributions published or made publicly available before November
Internet-Draft draft-ietf-ccamp-additional-signal-type-g709v3- Internet-Draft draft-ietf-ccamp-additional-signal-type-g709v3-
02.txt 03.txt
10, 2008. The person(s) controlling the copyright in some of this 10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow material may not have granted the IETF Trust the right to allow
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
[RFC4328] and [RFC7139] provide the extensions to Generalized RFC 4328 and RFC 7139 provide Resource ReserVation Protocol-Traffic
Multi-Protocol Label Switching (GMPLS) signaling to control the Engineering (RSVP-TE) signaling extensions to control the full set
full set of OTN features including ODU0, ODU1, ODU2, ODU3, ODU4, of Optical Transport Network (OTN) features. However, these
ODU2e and ODUflex. However, these specifications do not cover the specifications do not cover the additional Optical channel Data
additional signal types ODU1e, ODU3e1, and ODU3e2 mentioned in Unit (ODU) containers defined in G.Sup43 (ODU1e, ODU3e1 and
[G.Sup43]. This draft provides GMPLS signaling extensions for these ODU3e2). This document updates RFC 7139 to define new signal types
additional 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 Table of Contents
1. Introduction 2 1. Introduction...................................................2
2. RSVP-TE extension for Additional Signal Types 3 2. RSVP-TE extension for Additional Signal Types..................2
3. Security Considerations 3 3. Security Considerations........................................3
4. IANA Considerations 3 4. IANA Considerations............................................3
5. Acknowledgments 3 5. Acknowledgments................................................3
6. References 3 6. References.....................................................3
6.1. Normative References 3 6.1. Normative References.......................................3
6.2. Informative References 4 6.2. Informative References.....................................4
1. Introduction 1. Introduction
[RFC7139] updates the ODU-related portions of [RFC4328] to [RFC7139] updates the Optical channel Data Unit (ODU)-related
provide Resource ReserVation Protocol-Traffic Engineering (RSVP- portions of [RFC4328] to provide Resource ReserVation Protocol-
TE) extensions to support control for [G.709-v3]. However, it Traffic Engineering (RSVP-TE) extensions to support control for
does not cover additional signal types mentioned in [G.Sup43] [G.709-v3] in the OTN-TDM SENDER_TSPEC and OTN-TDM FLOWSPEC
(ODU1e, ODU3e1, and ODU3e2). This draft provides GMPLS signaling objects. However, it does not specify signal types for the
extension to support these additional signal types mentioned in containers defined in [G.Sup43] (ODU1e, ODU3e1, and ODU3e2).
[G.Sup43]. This document provides RSVP-TE signaling extensions to support
these additional signal types.
Internet-Draft draft-ietf-ccamp-additional-signal-type-g709v3-
02.txt
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 have a signal type field. This document defines the parameters have a signal type field. This document defines the
signal type for ODU1e, ODU3e1 and ODU3e2 as defined in the IANA signal type for ODU1e, ODU3e1 and ODU3e2 as defined in the IANA
considerations section. considerations section. They are allocated from the
Specification Required policy added to the subregistry by
[draft-subreg].
Internet-Draft draft-ietf-ccamp-additional-signal-type-g709v3-
03.txt
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]. above those identified in [RFC7139].
4. IANA Considerations 4. IANA Considerations
This document defines signal type for ODU1e, ODU3e1 and ODU3e2, IANA maintains a registry called "Generalized Multi-Protocol
as follows: Label Switching (GMPLS) Signaling Parameters" with a subregistry
Value Type called "OTN Signal Type". IANA is requested to make three
----- ---- further allocations from this registry under the Specification
TBD ODU1e (10Gbps Ethernet [GSUP.43]) Required policy for ODU1e, ODU3e1 and ODU3e2 as follows:
TBD ODU3e1 (40Gbps Ethernet [GSUP.43])
TBD ODU3e2 (40Gbps Ethernet [GSUP.43]) Value Type
----- ----
TBD (IANA is requested ODU1e (10Gbps Ethernet [G.Sup43])
to assign the value 23)
TBD (IANA is requested ODU3e1 (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 signaled types are carried in Traffic Parameters in OTN-
TDM SENDER_TSPEC and OTN-TDM FLOWSPEC objects [RFC7139]. TDM SENDER_TSPEC and OTN-TDM FLOWSPEC objects [RFC7139].
5. Acknowledgments 5. Acknowledgments
The authors would like to thank Lou Berger, Adrian Farrel and The authors would like to thank Dieter Beller, Lou Berger,
Sudip Shukla for comments. Deborah Brungard, Daniele Ceccarelli, Adrian Farrel and Sudip
Shukla for comments.
6. References 6. References
6.1. Normative References 6.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC4328] Papadimitriou, D., Ed., "Generalized Multi-Protocol
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4328] Papadimitriou, D., Ed., "Generalized Multi-Protocol
Label Switching (GMPLS) Signaling Extensions for G.709 Label Switching (GMPLS) Signaling Extensions for G.709
Optical Transport Networks Control", RFC 4328, January Optical Transport Networks Control", RFC 4328, January
2006. 2006.
[RFC7139] Zhang, F., Ed., Zhang, G., Belotti, S., Ceccarelli, [RFC7139] F. Zhang, Ed., G. Zhang, S. Belotti, D. Ceccarelli,
D., and K. Pithewan, "GMPLS Signaling Extensions for 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.
Internet-Draft draft-ietf-ccamp-additional-signal-type-g709v3- Internet-Draft draft-ietf-ccamp-additional-signal-type-g709v3-
02.txt 03.txt
[RFC7139] F.Zhang, G.Zhang, S.Belotti, D.Ceccarelli, K.Pithewan, [draft-subreg] Z. Ali, A. Bonfanti, M. Hartley, F. Zhang, "IANA
"Generalized Multi-Protocol Label Switching (GMPLS) Allocation Procedures for OTN Signal Type Subregistry
Signaling Extensions for the evolving G.709 Optical of the GMPLS Signaling Parameters Registry", draft-
Transport Networks Control, draft-ietf-ccamp-gmpls- ietf-ccamp-otn-signal-type-subregistry, work in
signaling-g709v3, work in progress. progress.
6.2. Informative References 6.2. Informative References
[G.709-v3] ITU-T, "Interface for the Optical Transport Network [G.709-v3] ITU-T, "Interface for the Optical Transport Network
(OTN)", G.709/Y.1331 Recommendation, February, 2012. (OTN)", G.709/Y.1331 Recommendation, February, 2012.
[GSUP.43] ITU-T, "Proposed revision of G.sup43 (for agreement)", [G.Sup43] ITU-T, "Transport of IEEE 10GBASE-R in optical
February, 2011. transport networks (OTN)", 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. 17 change blocks. 
63 lines changed or deleted 64 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/