CCAMP Working Group Haomian Zheng
Internet-Draft Italo Busi
Intended status: Standards Track Huawei
Zafar Ali
Cisco
Daniele Ceccarelli
Ericsson
Daniel King
Lancaster University
Expires: September 6, 2017 March 6, 2017
GMPLS Signaling Extension for Optical Transport Networks with Beyond
100G in G.709 Edition 5
draft-zheng-ccamp-gmpls-g709v5-signal-ext-00.txt
Abstract
The International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) has extended its Recommendations
G.709 to edition 5 to support beyond 100G (B100G) features.
Corresponding signaling extensions have been described in this
document.
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with
the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
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."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 6, 2017.
Zheng et al Expires September 2017 [Page 1]
draft-zheng-ccamp-gmpls-g709v5-signal-ext-00.txt March 2017
Copyright Notice
Copyright (c) 2017 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.
Table of Contents
1. Introduction ................................................. 2
2. Terminology .................................................. 3
2.1. Conventions Used in this Document ....................... 3
3. RSVP-TE Extensions to Support Optical Transport Network B100G. 3
3.1. New Signal types in B100G OTN ........................... 3
3.2. New Tributary Slot Definition in B100G OTN .............. 4
3.3. Generalized Label for B100G ............................. 5
3.4. TPN allocation and MSI .................................. 6
3.5. Supporting of OTUCn sub rates (OTUCn-M) ................. 8
3.6. Examples: ............................................... 8
4. Security Considerations ...................................... 9
5. IANA considerations .......................................... 9
6. Contributors' Addresses ..................................... 12
7. References .................................................. 12
7.1. Normative References ................................... 12
7.2. Informative References ................................. 13
Authors' Addresses ............................................. 13
1. Introduction
[ITU-T G.709v5] defines the interfaces to Optical Transport Network.
B100G features was included in the latest version v5. Corresponding
OTN control plane techniques have been considered in [B100G-fwk].
[RFC4328] describes the control technology details that are specific
to the 2001 revision of the G.709 specification. The previous
signaling extension drafts include the [RFC7139] too support ODU4,
ODU2e and ODUflex, and [RFC7963] to support additional ODU1e, ODU3e1
Zheng et al Expires September 2017 [Page 2]
draft-zheng-ccamp-gmpls-g709v5-signal-ext-00.txt March 2017
and ODU3e2. The signaling extension for B100G OTN network is
described in this document.
2. Terminology
2.1. 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].
3. RSVP-TE Extensions to Support Optical Transport Network B100G
3.1. New Signal types in B100G OTN
New features has been defined for B100G OTN. The corresponding new
signal types can be summarized as follow:
- Optical Data Unit - Cn (ODUCn)
n can vary from 1 to 255;
- Optical Transport Unit - Cn (OTUCn)
n can vary from 1 to 255;
[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 a new Signal Type
for ODUCn, where n can vary from 1 to 255.
Value Type
----- ----
TBD(31) ODUCn (i.e., n * 100 Gbps)
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Signal Type | n | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NVC | Multiplier (MT) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Bit_Rate |
Zheng et al Expires September 2017 [Page 3]
draft-zheng-ccamp-gmpls-g709v5-signal-ext-00.txt March 2017
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Signal Type: 8 bits
As defined in Section 3.2.1 of [RFC4328], with the following
additional values:
Value Type
----- ----
4 ODU4 (i.e., 100 Gbps)
9 OCh at 100 Gbps
10 ODU0 (i.e., 1.25 Gbps)
11 ODU2e (i.e., 10 Gbps for FC1200 and GE LAN)
12-19 Reserved (for future use)
20 ODUflex(CBR) (i.e., 1.25*N Gbps)
21 ODUflex(GFP-F), resizable (i.e., 1.25*N Gbps)
22 ODUflex(GFP-F), non-resizable (i.e., 1.25*N Gbps)
23 ODU1e (10Gbps Ethernet [G.Sup43])
26 ODU3e1 (40Gbps Ethernet [G.Sup43])
27 ODU3e2 (40Gbps Ethernet [G.Sup43])
31 ODUCn (B100G OTN [G.709-2016])
32-255 Reserved (for future use)
n : 8 bits
When the signal type is ODUCn, the n is used to specify the ODUCn
granularity, the value of n varies from 1 to 255. When the signal
type is not ODUCn, the n MUST be set to 0 and ignored.
3.2. New Tributary Slot Definition in B100G OTN
A new tributary slot granularity (i.e., 5Gbps) is defined in [G.709-
2016]. This granularity is specially used to support ODUCn in B100G
OTN networks. Legacy OTN interfaces will continue to use
2.5Gbps/1.25Gbps tributary slot granularity.
The OPUCn consists of n OPUC. Each OPUC is divided into 20 tributary
slots (TS) and these tributary slots are 16-byte interleaved within
the OPUC payload area. A tributary slot includes a part of the OPUC
OH area and a part of the OPUC payload area. The bytes of the ODUk
frame are mapped into the ODTUCn payload area and the ODTUCn bytes
are mapped into the OPUCn tributary slot or slots. The bytes of the
ODTUCn justification overhead are mapped into the OPUCn OH area.
Zheng et al Expires September 2017 [Page 4]
draft-zheng-ccamp-gmpls-g709v5-signal-ext-00.txt March 2017
There is only one type of tributary slot: Tributary slot with a
bandwidth of approximately 5 Gbit/s; an OPUCn is divided into 20n
tributary slots, numbered 1.1 to n.20.
To satisfy the new TS granularity, this document also updates the G-
PID values defined in [RFC4328].
Value G-PID Type
----- ----------
TBA(71) OTN B100G control defined in [G.709-2016]
The update of payload types updated in [G709-2016] and their mapping
to existing and new G-PID types are as follows:
G.709
Payload
Type G-PID Type/Comment LSP Encoding
==== ===== ===================== ===================
0x22 TBA(71) G.709 ODU-5G G.709 ODUCn(n=1..255)
3.3. Generalized Label for B100G
[RFC7139] defined the GENERALIZED_LABEL object format that MUST be
used with the OTN-TDM Switching Type, the format is re-drawn as
follow:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TPN | Reserved | Length |
Zheng et al Expires September 2017 [Page 5]
draft-zheng-ccamp-gmpls-g709v5-signal-ext-00.txt March 2017
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Bit Map ...... ~
~ ...... | Padding Bits ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
This object was used to indicate how LO ODUj is multiplexed into HO
ODUk. It can also be used to indicate how ODUk can be multiplexed
into ODUCn.
In the extreme case for B100G, ODU0 need to be multiplexed to
ODUC255. The maximum for TPN number is 20,400, which is beyond the
2^12. In this document this object need to be updated as follow:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TPN | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Bit Map ...... ~
~ ...... | Padding Bits ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
After the extension, the maximum values for TPN and Length are
updated to 65,536, which can cover the extreme case in B100G
multiplexing.
3.4. TPN allocation and MSI
TPN section has been used to indicates the tributary port number for
the assigned tributary slot(s).
- In the case of an ODUk mapped into ODUCn, only the lower 15
bits of the TPN field are significant; the other bits of TPN field
MUST be set to 0;
Per [G709-2016], the TPN is used to allow for correct demultiplexing
in the data plane. When an LO ODUj is multiplexed into an HO ODUk
Zheng et al Expires September 2017 [Page 6]
draft-zheng-ccamp-gmpls-g709v5-signal-ext-00.txt March 2017
occupying one or more TSs, a new TPN value is configured at the two
ends of the HO ODUk link and is put into the related MSI byte(s) in
the OPUk overhead at the (traffic) ingress end of the link, so that
the other end of the link can learn which TS(s) is/are used by the
LO ODUj in the data plane.
According to [G709-2016], the TPN field MUST be set according to the
following tables:
+-------+-------+----+----------------------------------------------+
| ODUk | ODUC1 |TPN | TPN Assignment Rules |
+-------+-------+----+----------------------------------------------+
| ODU0 | ODUC1 |1-20|Flexible, != any other existing LO ODUs'TPNs |
+-------+-------+----+----------------------------------------------+
| ODU1 | ODUC1 |1-20|Flexible, != any other existing LO ODUs' TPNs |
|-------+-------+----+----------------------------------------------+
| ODU2 | ODUC1 |1-10|Flexible, != any other existing LO ODUs' TPNs |
+-------+-------+----+----------------------------------------------+
| ODU3 | ODUC1 |1-2 |Flexible, != any other existing LO ODUs' TPNs |
|-------+-------+----+----------------------------------------------+
| ODU4 | ODUC1 |1-1 |Flexible, != any other existing LO ODUs' TPNs |
+-------+-------+----+----------------------------------------------+
Table X: TPN Assignment Rules from ODUk to ODUC1 (5 Gbps TS Granularity)
Editor's Note: The I-D stills need to consider how to multiplex ODU2e,
ODU1e, and ODUFlex to ODUCn. This is a topic for further discussion.
For ODUCn where n>1, the only changes are the upper bound of TPN. As
ODUCn is composed by n ODUC, the upper bound of TPN is multiplied by
n.
+-------+-------+-----+----------------------------------------------+
| ODUk | ODUCn | TPN | TPN Assignment Rules |
+-------+-------+-----+----------------------------------------------+
| ODU0 | ODUCn |1-20n|Flexible, != any other existing LO ODUs'TPNs |
+-------+-------+----+----------------------------------------------+
| ODU1 | ODUCn |1-20n|Flexible, != any other existing LO ODUs' TPNs |
|-------+-------+-----+----------------------------------------------+
| ODU2 | ODUCn |1-10n|Flexible, != any other existing LO ODUs' TPNs |
+-------+-------+-----+----------------------------------------------+
| ODU3 | ODUCn |1-2n |Flexible, != any other existing LO ODUs' TPNs |
Zheng et al Expires September 2017 [Page 7]
draft-zheng-ccamp-gmpls-g709v5-signal-ext-00.txt March 2017
|-------+-------+-----+----------------------------------------------+
| ODU4 | ODUCn | 1-n |Flexible, != any other existing LO ODUs' TPNs |
+-------+-------+-----+----------------------------------------------+
Table X: TPN Assignment Rules from ODUk to ODUCn (5 Gbps TS Granularity)
3.5. Supporting of OTUCn sub rates (OTUCn-M)
The OTUCn-M frame is a type of OTUCn frame which contains n
instances of OTUC, ODUC and OPUC overhead and M 5 Gbit/s OPUCn
tributary slots. If a particular value of M is not indicated, the
frame contains 20*n tributary slots.
For OTUCn-M, there is totally 20*n+M tributary slots. Accordingly, M
need to be considered as in TPN numbers defined in section 3.4.
3.6. Examples:
Following examples are given to illustrate how to multiplexing ODUk
into ODUCn format.
(1) ODU2 to ODUC1 Multiplexing
In this example, the n value in ODUCn is set to 1, with a signal
type assigned as 31 which means ODUCn.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Signal Type=31| n=1 | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The label format, defined in section 3.3 of this document, is
illustrated as follow.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TPN = 1 | Length = 20 |
Zheng et al Expires September 2017 [Page 8]
draft-zheng-ccamp-gmpls-g709v5-signal-ext-00.txt March 2017
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 1 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 | Padding Bits (0) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The label above indicate that ODU2 (10G) is using the 2nd and 5th
tributary slots of ODUC1. The tributary slot granularity in B100G
MUST be set to 5Gbps.
(2) ODU4 to ODUC1 Multiplexing
This example is special, as both ODU4 and ODUC1 are assumed to be
with a rate of 100Gbps. The signal type of ODUC1 is the same as
previous example.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TPN = 1 | Length = 20 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 | Padding Bits (0) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
In this example, all the 20 tributary slots are occupied in the
multiplexing.
4. Security Considerations
TBD.
5. IANA considerations
IANA maintains the "Generalized Multi-Protocol Label Switching
(GMPLS) Signaling Parameters" registry (see
<http://www.iana.org/assignments/gmpls-sig-parameters>). The
"Generalized PIDs (G-PID)" subregistry is included in this registry,
which is extended and updated by this document as detailed below.
Zheng et al Expires September 2017 [Page 9]
draft-zheng-ccamp-gmpls-g709v5-signal-ext-00.txt March 2017
Value Type Technology Reference
===== ====================== ========== =========
47 G.709 ODU-2.5G G.709 ODUk [RFC4328]
(IANA updated the Type field) [RFC7139]
56 SBCON/ESCON G.709 ODUk, [RFC4328]
(IANA updated the Type field) Lambda, Fiber [RFC7139]
59 Framed GFP G.709 ODUk [RFC7139]
60 STM-1 G.709 ODUk [RFC7139]
61 STM-4 G.709 ODUk [RFC7139]
62 InfiniBand G.709 ODUflex [RFC7139]
63 SDI (Serial Digital Interface) G.709 ODUk [RFC7139]
64 SDI/1.001 G.709 ODUk [RFC7139]
65 DVB_ASI G.709 ODUk [RFC7139]
66 G.709 ODU-1.25G G.709 ODUk [RFC7139]
67 G.709 ODU-any G.709 ODUk [RFC7139]
68 Null Test G.709 ODUk [RFC7139]
69 Random Test G.709 ODUk [RFC7139]
70 64B/66B GFP-F Ethernet G.709 ODUk [RFC7139]
TBD(71)G.709 ODU-5G G.709 ODUCn [This draft]
This document also request IANA to add the following signal types in
the subregistry via the Specification Required policy [RFC5226]:
Zheng et al Expires September 2017 [Page 10]
draft-zheng-ccamp-gmpls-g709v5-signal-ext-00.txt March 2017
Value Signal Type Reference
----- ----------- ---------
0 Not significant [RFC4328]
1 ODU1 (i.e., 2.5 Gbps) [RFC4328]
2 ODU2 (i.e., 10 Gbps) [RFC4328]
3 ODU3 (i.e., 40 Gbps) [RFC4328]
4 ODU4 (i.e., 100 Gbps) [RFC7139]
5 Unassigned [RFC4328]
6 Och at 2.5 Gbps [RFC4328]
7 OCh at 10 Gbps [RFC4328]
8 OCh at 40 Gbps [RFC4328]
9 OCh at 100 Gbps [RFC7139]
10 ODU0 (i.e., 1.25 Gbps) [RFC7139]
11 ODU2e (i.e., 10 Gbps for FC1200 [RFC7139]
and GE LAN)
12-19 Unassigned
20 ODUflex(CBR) (i.e., 1.25*N Gbps) [RFC7139]
21 ODUflex(GFP-F), resizable [RFC7139]
(i.e., 1.25*N Gbps)
22 ODUflex(GFP-F), non-resizable [RFC7139]
(i.e., 1.25*N Gbps)
23 ODU1e (10Gbps Ethernet) [RFC7963]
26 ODU3e1 (40Gbps Ethernet) [RFC7963]
27 ODU3e2 (40Gbps Ethernet) [RFC7963]
Zheng et al Expires September 2017 [Page 11]
draft-zheng-ccamp-gmpls-g709v5-signal-ext-00.txt March 2017
31 ODUCn [This Draft]
23-255 Unassigned
These Signal Types are carried in the Traffic Parameters in OTN-
TDM SENDER_TSPEC and OTN-TDM FLOWSPEC objects.
6. Contributors' Addresses
Xian Zhang
Huawei Technologies
Email: zhang.xian@huawei.com
Antonello Bonfanti
Cisco
Email: abonfant@cisco.com
Sergio Belotti
Nokia
Email: sergio.belotti@nokia.com
Dieter Beller
Nokia
Email: Dieter.Beller@nokia.com
7. References
7.1. Normative References
[RFC2119] S. Bradner, "Key words for use in RFCs to indicate
requirements levels", RFC 2119, March 1997.
[ITU-T G.709v5] ITU-T, "Interface for the Optical Transport Network
(OTN)", G.709/Y.1331 Recommendation, June 2016.
[RFC7062] F. Zhang, D. Li, H. Li, S. Belotti, D. Ceccarelli,
'Framework for GMPLS and PCE Control of G.709 Optical
Transport Networks', RFC 7062, November 2013.
[RFC7138] D. Ceccarelli, F. Zhang, S. Belotti, R. Rao, J. Drake,
'Traffic Engineering Extensions to OSPF for GMPLS Control
of Evolving G.709 Optical Transport Networks', RFC7138,
March 2014.
Zheng et al Expires September 2017 [Page 12]
draft-zheng-ccamp-gmpls-g709v5-signal-ext-00.txt March 2017
[RFC7139] F. Zhang, G. Zhang, S. Belotti, D. Ceccarelli, K. Pithewan,
'GMPLS Signaling Extensions for Control of Evolving G.709
Optical Transport Networks', RFC7139, March 2014.
[RFC7892] Z. Ali, A. Bonfanti, M. Hartley, F. Zhang, 'IANA
Allocation Procedures for the GMPLS OTN Signal Type
Registry', RFC7892, May 2016.
[RFC7963] Z. Ali, A. Bonfanti, M. Hartley, F. Zhang, 'RSVP-TE
Extension for Additional Signal Types in G.709 Optical
Transport Networks (OTNs)', RFC7963, August 2016.
7.2. Informative References
Authors' Addresses
Haomian Zheng
Huawei Technologies
Email: zhenghaomian@huawei.com
Italo Busi
Huawei Technologies
Email: Italo.Busi@huawei.com
Zafar Ali
Cisco
Email: zali@cisco.com
Daniele Ceccarelli
Ericsson
Email: daniele.ceccarelli@ericsson.com
Daniel King
Lancaster University
Email: d.king@lancaster.ac.uk
Zheng et al Expires September 2017 [Page 13]