draft-ietf-ccamp-gmpls-otn-b100g-applicability-00.txt   draft-ietf-ccamp-gmpls-otn-b100g-applicability-01.txt 
Internet Engineering Task Force Q. Wang, Ed. Internet Engineering Task Force Q. Wang, Ed.
Internet-Draft ZTE Internet-Draft ZTE
Intended status: Informational R. Valiveti, Ed. Intended status: Informational R. Valiveti, Ed.
Expires: August 31, 2019 Infinera Corp Expires: January 8, 2020 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
February 27, 2019 July 7, 2019
Applicability of GMPLS for B100G Optical Transport Network Applicability of GMPLS for B100G Optical Transport Network
draft-ietf-ccamp-gmpls-otn-b100g-applicability-00 draft-ietf-ccamp-gmpls-otn-b100g-applicability-01
Abstract Abstract
This document examines the applicability of using current existing This document examines the applicability of using current existing
GMPLS routing and signaling to set up ODUk/ODUflex over ODUCn link, GMPLS routing and signaling to set up ODUk/ODUflex over ODUCn link,
as a result of the support of OTU/ODU links with rates larger than as a result of the support of OTU/ODU links with rates larger than
100G in the 2016 version of G.709. 100G in the 2016 version of G.709.
Status of This Memo Status of This Memo
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 August 31, 2019. This Internet-Draft will expire on January 8, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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 29 skipping to change at page 2, line 29
3.1. OTUCn . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.1. OTUCn . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1.1. Carrying OTUCn between 3R points . . . . . . . . . . 5 3.1.1. Carrying OTUCn between 3R points . . . . . . . . . . 5
3.2. ODUCn . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.2. ODUCn . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.3. OTUCn-M . . . . . . . . . . . . . . . . . . . . . . . . . 7 3.3. OTUCn-M . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.4. Time Slot Granularity . . . . . . . . . . . . . . . . . . 8 3.4. Time Slot Granularity . . . . . . . . . . . . . . . . . . 8
3.5. Structure of OPUCn MSI with Payload type 0x22 . . . . . . 8 3.5. Structure of OPUCn MSI with Payload type 0x22 . . . . . . 8
3.6. Client Signal Mappings . . . . . . . . . . . . . . . . . 8 3.6. Client Signal Mappings . . . . . . . . . . . . . . . . . 8
4. Applicability and GMPLS Implications . . . . . . . . . . . . 10 4. Applicability and GMPLS Implications . . . . . . . . . . . . 10
4.1. Applicability and Challenges . . . . . . . . . . . . . . 10 4.1. Applicability and Challenges . . . . . . . . . . . . . . 10
4.2. GMPLS Implications and Applicability . . . . . . . . . . 12 4.2. GMPLS Implications and Applicability . . . . . . . . . . 12
4.2.1. Implications and Applicability for GMPLS Signalling . 12 4.2.1. TE-Link Representation . . . . . . . . . . . . . . . 12
4.2.2. Implications and Applicability for GMPLS Routing . . 13 4.2.2. Implications and Applicability for GMPLS Signalling . 13
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14 4.2.3. Implications and Applicability for GMPLS Routing . . 14
6. Authors (Full List) . . . . . . . . . . . . . . . . . . . . . 14 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 15 6. Authors (Full List) . . . . . . . . . . . . . . . . . . . . . 15
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 16
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
9. Security Considerations . . . . . . . . . . . . . . . . . . . 16 9. Security Considerations . . . . . . . . . . . . . . . . . . . 17
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 16 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
10.1. Normative References . . . . . . . . . . . . . . . . . . 16 10.1. Normative References . . . . . . . . . . . . . . . . . . 17
10.2. Informative References . . . . . . . . . . . . . . . . . 17 10.2. Informative References . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18
1. Introduction 1. Introduction
The current GMPLS routing [RFC7138] and signaling extensions The current GMPLS routing [RFC7138] and signaling extensions
[RFC7139] only includes coverage for the control of all the OTN [RFC7139] only includes coverage for the control of all the OTN
capabilities that were defined in the 2012 version of G.709 capabilities that were defined in the 2012 version of G.709
[ITU-T_G709_2012]. [ITU-T_G709_2012].
While the 2016 version of G.709 [ITU-T_G709_2016] introduces support While the 2016 version of G.709 [ITU-T_G709_2016] introduces support
for new higher rate ODU signals, termed ODUCn (which have a nominal for new higher rate ODU signals, termed ODUCn (which have a nominal
skipping to change at page 7, line 22 skipping to change at page 7, line 22
================================================================== ==================================================================
+--------+ +--------+ +--------+ +--------+ +--------+ +--------+ +--------+ +--------+
| +-----------+ | | +----------+ | | +-----------+ | | +----------+ |
| OTN |-----------| OTN | | OTN |----------| OTN | | OTN |-----------| OTN | | OTN |----------| OTN |
| DXC +-----------+ WXC +----------------+ WXC +----------+ DXC | | DXC +-----------+ WXC +----------------+ WXC +----------+ DXC |
| | | 3R | | 3R | | | | | | 3R | | 3R | | |
+--------+ +--------+ +--------+ +--------+ +--------+ +--------+ +--------+ +--------+
<--------------------------------ODUCn------------------------------> <--------------------------------ODUCn------------------------------>
<------------------> <----------------------> <------------------> <------------------> <-----------------------> <------------------>
OTUCn OTUCn OTUCn OTUCn OTUCn OTUCn
================================================================== ==================================================================
Figure 2: ODUCn signal Figure 2: ODUCn signal
3.3. OTUCn-M 3.3. OTUCn-M
The standard OTUCn signal has the same rate as that of the ODUCn The standard OTUCn signal has the same rate as that of the ODUCn
signal as captured in Table 1. This implies that the OTUCn signal signal as captured in Table 1. This implies that the OTUCn signal
skipping to change at page 12, line 37 skipping to change at page 12, line 37
According to the above description, it can be concluded that some According to the above description, it can be concluded that some
uncertainty about setup of ODUCn link still exist, and this uncertainty about setup of ODUCn link still exist, and this
uncertainty may have relationship with the progress in ITU-T. Based uncertainty may have relationship with the progress in ITU-T. Based
on the analysis, it is suggested that the scope of this draft should on the analysis, it is suggested that the scope of this draft should
mainly focus on how to set up ODUk/ODUflex LSPs over ODUCn links, as mainly focus on how to set up ODUk/ODUflex LSPs over ODUCn links, as
also indicated in the figure above. also indicated in the figure above.
4.2. GMPLS Implications and Applicability 4.2. GMPLS Implications and Applicability
4.2.1. Implications and Applicability for GMPLS Signalling 4.2.1. TE-Link Representation
Section 3 of RFC7138 describes how to represent G.709 OTUk/ODUk with
TE-Links in GMPLS. Similar to that, ODUCn links can also be
represented as TE-Links, which can be seen in the figure below.
==================================================================
3R 3R
+--------+ +--------+ +--------+ +--------+
| | | | | | | |
| node A |<-OTUCn Link->| node B |<-OTUCn Link->| node C |<-OTUCn Link->| node D |
| | | | | | | |
+--------+ +--------+ +--------+ +--------+
|<--------------------------- ODUCn Link -------------------------->|
|<----------------------------- TE-Link --------------------------->|
==================================================================
Figure 6: telink
Two ends of a TE-Link is able to know whether the TE-Link is
supported by an ODUCn or an ODUk or an OTUk, as well as the resource
related information (e.g., slot granularity, number of tributary slot
available).
4.2.2. Implications and Applicability for GMPLS Signalling
Once the ODUCn link is configured, the GMPLS mechanisms defined in Once the ODUCn link is configured, the GMPLS mechanisms defined in
RFC7139 can be reused to set up ODUk/ODUflex LSP with no/few changes. RFC7139 can be reused to set up ODUk/ODUflex LSP with no/few changes.
As the resource on the ODUCn link which can be seen by the client As the resource on the ODUCn link which can be seen by the client
ODUk/ODUflex is a serial of 5G slots, the label defined in RFC7139 is ODUk/ODUflex is a serial of 5G slots, the label defined in RFC7139 is
able to accommodate the requirement of the setup of ODUk/ODUflex over able to accommodate the requirement of the setup of ODUk/ODUflex over
ODUCn link. ODUCn link. The OTN-TDM GENERALIZED_LABEL object is used to indicate
how the LO ODUj signal is multiplexed into the HO ODUk link. The LO
ODUj Signal Type is indicated by Traffic Parameters, while the type
of HO ODUk link is identified by the selected interface carried in
the IF_ID RSVP_HOP object. 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 (by internal/local configuration) the
attributes of ODUCn TE-Link.
One thing should be note is the TPN used in RFC7139 and defined in One thing should be note is the TPN used in RFC7139 and defined in
G.709-2016 for ODUCn link. Since the TPN currently defined in G.709 G.709-2016 for ODUCn link. Since the TPN currently defined in G.709
for ODUCn link has 14 bits, while this field in RFC7139 only has 12 for ODUCn link has 14 bits, while this field in RFC7139 only has 12
bits, some extension work is needed, but this is not so urgent since bits, some extension work is needed, but this is not so urgent since
for today networks scenarios 12 bits are enough, as it can support a for today networks scenarios 12 bits are enough, as it can support a
single ODUCn link up to n=400, namely 40Tbit. single ODUCn link up to n=400, namely 40Tbit.
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
skipping to change at page 13, line 37 skipping to change at page 14, line 31
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 1 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0| |0 0 0 0 0 1 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 1 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0| |0 0 0 0 0 1 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0| Padding Bits(0) | |0 0 0 0 0 0 0 0| Padding Bits(0) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
================================================================== ==================================================================
Figure 6: Label format Figure 7: Label format
4.2.2. Implications and Applicability for GMPLS Routing 4.2.3. Implications and Applicability for GMPLS Routing
For routing, we think that no extension to current mechanisms defined For routing, we think that no extension to current mechanisms defined
in RFC7138 are needed. Because, once one ODUCn link is up, we need in RFC7138 are needed. Because, once one ODUCn link is up, we need
to advertise only the resources that can be used on this ODUCn link to advertise only the resources that can be used on this ODUCn link
and the multiplexing hierarchy on this link. Considering ODUCn link and the multiplexing hierarchy on this link. Considering ODUCn link
is already configured, it's the ultimate hierarchy of this is already configured, it's the ultimate hierarchy of this
multiplexing, there is no need to explicitly extent the ODUCn signal multiplexing, there is no need to explicitly extent the ODUCn signal
type in the routing. type in the routing.
The OSPF-TE extension defined in section 4 of RFC7138 can be used to The OSPF-TE extension defined in section 4 of RFC7138 can be used to
skipping to change at page 15, line 30 skipping to change at page 16, line 26
Email: daniele.ceccarelli@ericsson.com Email: daniele.ceccarelli@ericsson.com
7. Contributors 7. Contributors
Rajan Rao, Infinera Corp, Sunnyvale, USA, rrao@infinera.com Rajan Rao, Infinera Corp, Sunnyvale, USA, rrao@infinera.com
Fatai Zhang, Huawei,zhangfatai@huawei.com Fatai Zhang, Huawei,zhangfatai@huawei.com
Italo Busi, Huawei,italo.busi@huawei.com Italo Busi, Huawei,italo.busi@huawei.com
Zheyu Fan, Huawei, fanzheyu2@huawei.com Zheyu Fan, Individual, zheyu2008@gmail.com
Dieter Beller, Nokia, Dieter.Beller@nokia.com Dieter Beller, Nokia, Dieter.Beller@nokia.com
Yuanbin Zhang, ZTE, Beiing, zhang.yuanbin@zte.com.cn Yuanbin Zhang, ZTE, Beiing, zhang.yuanbin@zte.com.cn
Zafar Ali, Cisco Systems, zali@cisco.com Zafar Ali, Cisco Systems, zali@cisco.com
Daniel King, d.king@lancaster.ac.uk Daniel King, d.king@lancaster.ac.uk
Manoj Kumar, Cisco Systems, manojk2@cisco.com Manoj Kumar, Cisco Systems, manojk2@cisco.com
Antonello Bonfanti, Cisco Systems, abonfant@cisco.com Antonello Bonfanti, Cisco Systems, abonfant@cisco.com
Akshaya Nadahalli, Cisco Systems, anadahal@cisco.com Akshaya Nadahalli, Individual, nadahalli@gmail.com
8. IANA Considerations 8. IANA Considerations
This memo includes no request to IANA. This memo includes no request to IANA.
9. Security Considerations 9. Security Considerations
None. None.
10. References 10. References
 End of changes. 13 change blocks. 
21 lines changed or deleted 55 lines changed or added

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