draft-ietf-ccamp-gmpls-otn-b100g-applicability-03.txt   draft-ietf-ccamp-gmpls-otn-b100g-applicability-04.txt 
Internet Engineering Task Force Q. Wang, Ed. Internet Engineering Task Force Q. Wang, Ed.
Internet-Draft ZTE Corporation Internet-Draft ZTE Corporation
Intended status: Informational R. Valiveti, Ed. Intended status: Informational R. Valiveti, Ed.
Expires: May 5, 2021 Infinera Corp Expires: May 23, 2021 Infinera Corp
H. Zheng, Ed. H. Zheng, Ed.
Huawei Huawei
H. Helvoort H. Helvoort
Hai Gaoming B.V Hai Gaoming B.V
S. Belotti S. Belotti
Nokia Nokia
November 1, 2020 November 19, 2020
Applicability of GMPLS for B100G Optical Transport Network Applicability of GMPLS for B100G Optical Transport Network
draft-ietf-ccamp-gmpls-otn-b100g-applicability-03 draft-ietf-ccamp-gmpls-otn-b100g-applicability-04
Abstract Abstract
This document examines the applicability of using current existing This document examines the applicability of using existing GMPLS
GMPLS routing and signalling mechanisms to set up ODUk (e.g., routing and signalling mechanisms to set up ODUk (e.g., ODUflex) LSP
ODUflex) LSP over ODUCn links, as defined in the 2016 version of over ODUCn links, as defined in the 2016 version of G.709.
G.709.
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 5, 2021. This Internet-Draft will expire on May 23, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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
skipping to change at page 2, line 18 skipping to change at page 2, line 17
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. OTN terminology used in this document . . . . . . . . . . . . 3 2. OTN terminology used in this document . . . . . . . . . . . . 3
3. Overview of the OTUCn/ODUCn in G.709 . . . . . . . . . . . . 3 3. Overview of the OTUCn/ODUCn in G.709 . . . . . . . . . . . . 3
3.1. OTUCn . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.1. OTUCn . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1.1. OTUCn-M . . . . . . . . . . . . . . . . . . . . . . . 5 3.1.1. OTUCn-M . . . . . . . . . . . . . . . . . . . . . . . 5
3.2. ODUCn . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.2. ODUCn . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.3. Time Slot Granularity . . . . . . . . . . . . . . . . . . 7 3.3. Time Slot Granularity . . . . . . . . . . . . . . . . . . 7
3.4. Structure of OPUCn MSI with Payload type 0x22 . . . . . . 7 3.4. Structure of OPUCn MSI with Payload type 0x22 . . . . . . 7
3.5. Client Signal Mappings . . . . . . . . . . . . . . . . . 8 3.5. Client Signal Mappings . . . . . . . . . . . . . . . . . 8
4. GMPLS Implications and Applicability . . . . . . . . . . . . 9 4. GMPLS Implications and Applicability . . . . . . . . . . . . 9
4.1. TE-Link Representation . . . . . . . . . . . . . . . . . 9 4.1. TE-Link Representation . . . . . . . . . . . . . . . . . 9
4.2. Implications and Applicability for GMPLS Signalling . . . 10 4.2. Implications and Applicability for GMPLS Signalling . . . 10
4.3. Implications and Applicability for GMPLS Routing . . . . 11 4.3. Implications and Applicability for GMPLS Routing . . . . 11
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12
6. Authors (Full List) . . . . . . . . . . . . . . . . . . . . . 12 6. Authors (Full List) . . . . . . . . . . . . . . . . . . . . . 12
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 13 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 13
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
9. Security Considerations . . . . . . . . . . . . . . . . . . . 14 9. Security Considerations . . . . . . . . . . . . . . . . . . . 14
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
10.1. Normative References . . . . . . . . . . . . . . . . . . 14 10.1. Normative References . . . . . . . . . . . . . . . . . . 14
10.2. Informative References . . . . . . . . . . . . . . . . . 14 10.2. Informative References . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
The current GMPLS routing [RFC7138] and signalling [RFC7139] The current GMPLS routing [RFC7138] and signalling [RFC7139]
extensions support the control of OTN signals and capabilities that extensions support the control of OTN signals and capabilities that
were defined in the 2012 version of G.709 [ITU-T_G709_2012]. were defined in the 2012 version of G.709 [ITU-T_G709_2012].
In 2016 a new version of G.709 was published: [ITU-T_G709_2016]. In 2016 a new version of G.709 was published: [ITU-T_G709_2016].
This version introduces new higher rate OTU and ODU signals, termed This version introduces new higher rate OTU and ODU signals, termed
OTUCn and ODUCn respectively, which have a nominal rate of n x 100 OTUCn and ODUCn respectively, which have a nominal rate of n x 100
Gbit/s. According to the definition in G.709 [ITU-T_G709_2016], Gbit/s. According to the definition in [ITU-T_G709_2016], OTUCn and
OTUCn and ODUCn perform only section layer role and ODUCn supports ODUCn perform only section layer role and ODUCn supports only ODUk
only ODUk clients. This document focuses on the use of existing clients. This document focuses on the use of existing GMPLS
GMPLS mechanisms to set up ODUk (e.g., ODUflex) LSP over ODUCn links, mechanisms to set up ODUk (e.g., ODUflex) LSP over ODUCn links,
independently from how these links have been set up independently from how these links have been set up
This document presents an overview of the OTUCn and ODUCn signals This document presents an overview of the OTUCn and ODUCn signals
introduced in [ITU-T_G709_2016] and analyses how the current GMPLS introduced in [ITU-T_G709_2016] and analyses how the current GMPLS
routing and signalling mechanisms can be utilized to setup ODUk routing and signalling mechanisms can be utilized to setup ODUk
(e.g., ODUflex) LSPs over ODUCn links. (e.g., ODUflex) LSPs over ODUCn links.
Note: after discussion, the authors did not see any impact of 2020 Note: after discussion, the authors did not see any impact of 2020
version of G.709 on this draft. version of [ITU-T_G709_2020] on this draft.
2. OTN terminology used in this document 2. OTN terminology used in this document
a. OPUCn: Optical Payload Unit - Cn. Where Cn = number of n-bit a. OPUCn: Optical Payload Unit - Cn. Where Cn indicates that the
client data entities. bit rate is approximately n*100G.
b. ODUCn: Optical Data Unit - Cn. b. ODUCn: Optical Data Unit - Cn.
c. OTUCn: Fully standardized Optical Transport Unit - Cn. c. OTUCn: Fully standardized Optical Transport Unit - Cn.
d. OTUCn-M: This signal is an extension of the OTUCn signal d. OTUCn-M: This signal is an extension of the OTUCn signal
introduced above. This signal contains the same amount of introduced above. This signal contains the same amount of
overhead as the OTUCn signal, but contains a reduced amount of overhead as the OTUCn signal, but contains a reduced amount of
payload area. Specifically, the payload area consists of M 5G payload area. Specifically, the payload area consists of M 5G
tributary slots (where M is strictly less than 20*n). tributary slots (where M is strictly less than 20*n).
skipping to change at page 11, line 5 skipping to change at page 11, line 5
ODUCn link. In [RFC7139], the OTN-TDM GENERALIZED_LABEL object is ODUCn link. In [RFC7139], the OTN-TDM GENERALIZED_LABEL object is
used to indicate how the LO ODUj signal is multiplexed into the HO used to indicate how the LO ODUj signal is multiplexed into the HO
ODUk link. In a similar manner, the OTN-TDM GENERALIZED_LABEL object ODUk link. In a similar manner, the OTN-TDM GENERALIZED_LABEL object
is used to indicate how the ODUk signal is multiplexed into the ODUCn is used to indicate how the ODUk signal is multiplexed into the ODUCn
link. The ODUk Signal Type is indicated by Traffic Parameters. The link. The ODUk Signal Type is indicated by Traffic Parameters. The
IF_ID RSVP_HOP object provides a pointer to the interface associated IF_ID RSVP_HOP object provides a pointer to the interface associated
with TE-Link and therefore the two nodes terminating the TE-link know with TE-Link and therefore the two nodes terminating the TE-link know
(by internal/local configuration) the attributes of the ODUCn TE (by internal/local configuration) the attributes of the ODUCn TE
Link. Link.
One thing should be note is the TPN used in RFC7139 and defined in Since the TPN currently defined in G.709 for ODUCn link has 14 bits,
G.709-2016 for ODUCn link. Since the TPN currently defined in G.709 while this field in RFC7139 only has 12 bits, some extension work is
for ODUCn link has 14 bits, while this field in RFC7139 only has 12 needed. Given that a 12-bit TPN field can support ODUCn links with
bits, some extension work is needed, but this is not so urgent since up to n=400 (i.e. 40Tbit/s links), this extension is not urgently
for today networks scenarios 12 bits are enough, as it can support a needed.
single ODUCn link up to n=400, namely 40 Tbit/s.
An example is given below to illustrate the label format defined in An example is given below to illustrate the label format defined in
RFC7139 for multiplexing ODU4 onto ODUC10. One ODUC10 has 200 5G RFC7139 for multiplexing ODU4 onto ODUC10. One ODUC10 has 200 5G
slots, and twenty of them are allocated to the ODU4. Along with the slots, and twenty of them are allocated to the ODU4. Along with the
increase of "n", the label may become lengthy, an optimized label increase of "n", the label may become lengthy, an optimized label
format may be needed. format may be needed.
================================================================== ==================================================================
0 1 2 3 0 1 2 3
skipping to change at page 11, line 50 skipping to change at page 11, line 49
================================================================== ==================================================================
Figure 5: Label format Figure 5: Label format
4.3. Implications and Applicability for GMPLS Routing 4.3. Implications and Applicability for GMPLS Routing
For routing, it is deemed that no extension to current mechanisms For routing, it is deemed that no extension to current mechanisms
defined in RFC7138 are needed. Because, once an ODUCn link is up, defined in RFC7138 are needed. Because, once an ODUCn link is up,
the resources that need to be advertised are the resources that the resources that need to be advertised are the resources that
exposed by this ODUCn link and the multiplexing hierarchy on this exposed by this ODUCn link and the multiplexing hierarchy on this
link. Since the ODUCn link is the ultimate hierarchy of the ODU link. Since the ODUCn link is the lowest layer of the ODU
multiplexing, there is no need to explicitly define a new value to multiplexing hierarchy, there is no need to explicitly define a new
represent the ODUCn signal type in the OSPF-TE routing protocol. value to represent the ODUCn signal type in the OSPF-TE routing
protocol.
The OSPF-TE extension defined in section 4 of RFC7138 can be reused The OSPF-TE extension defined in section 4 of RFC7138 can be reused
to advertise the resource information on the ODUCn link to help to advertise the resource information on the ODUCn link to help
finish the setup of ODUk/ODUflex. finish the setup of ODUk/ODUflex.
5. Acknowledgements 5. Acknowledgements
6. Authors (Full List) 6. Authors (Full List)
Qilei Wang (editor) Qilei Wang (editor)
skipping to change at page 14, line 27 skipping to change at page 14, line 27
[ITU-T_G709_2012] [ITU-T_G709_2012]
ITU-T, "ITU-T G.709: Optical Transport Network Interfaces; ITU-T, "ITU-T G.709: Optical Transport Network Interfaces;
02/2012", http://www.itu.int/rec/T-REC- 02/2012", http://www.itu.int/rec/T-REC-
G..709-201202-S/en, February 2012. G..709-201202-S/en, February 2012.
[ITU-T_G709_2016] [ITU-T_G709_2016]
ITU-T, "ITU-T G.709: Optical Transport Network Interfaces; ITU-T, "ITU-T G.709: Optical Transport Network Interfaces;
07/2016", http://www.itu.int/rec/T-REC- 07/2016", http://www.itu.int/rec/T-REC-
G..709-201606-P/en, July 2016. G..709-201606-P/en, July 2016.
[ITU-T_G709_2020]
ITU-T, "ITU-T G.709: Optical Transport Network Interfaces;
06/2020", https://www.itu.int/rec/T-REC-
G.709-202006-I/en, June 2020.
[RFC7138] Ceccarelli, D., Ed., Zhang, F., Belotti, S., Rao, R., and [RFC7138] Ceccarelli, D., Ed., Zhang, F., Belotti, S., Rao, R., and
J. Drake, "Traffic Engineering Extensions to OSPF for J. Drake, "Traffic Engineering Extensions to OSPF for
GMPLS Control of Evolving G.709 Optical Transport GMPLS Control of Evolving G.709 Optical Transport
Networks", RFC 7138, DOI 10.17487/RFC7138, March 2014, Networks", RFC 7138, DOI 10.17487/RFC7138, March 2014,
<https://www.rfc-editor.org/info/rfc7138>. <https://www.rfc-editor.org/info/rfc7138>.
[RFC7139] Zhang, F., Ed., Zhang, G., Belotti, S., Ceccarelli, D., [RFC7139] Zhang, F., Ed., Zhang, G., Belotti, S., Ceccarelli, D.,
and K. Pithewan, "GMPLS Signaling Extensions for Control and K. Pithewan, "GMPLS Signaling Extensions for Control
of Evolving G.709 Optical Transport Networks", RFC 7139, of Evolving G.709 Optical Transport Networks", RFC 7139,
DOI 10.17487/RFC7139, March 2014, DOI 10.17487/RFC7139, March 2014,
 End of changes. 14 change blocks. 
26 lines changed or deleted 31 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/