draft-ietf-ccamp-gmpls-signaling-g709v3-09.txt   draft-ietf-ccamp-gmpls-signaling-g709v3-10.txt 
Network Working Group Fatai Zhang, Ed. Network Working Group Fatai Zhang, Ed.
Internet Draft Huawei Internet Draft Huawei
Updates: 4328 Guoying Zhang Updates: 4328 Guoying Zhang
Category: Standards Track CATR Category: Standards Track CATR
Sergio Belotti Sergio Belotti
Alcatel-Lucent Alcatel-Lucent
D. Ceccarelli D. Ceccarelli
Ericsson Ericsson
Khuzema Pithewan Khuzema Pithewan
Infinera Infinera
Expires: November 31, 2013 May 31, 2013 Expires: December 18, 2013 June 18, 2013
Generalized Multi-Protocol Label Switching (GMPLS) Signaling Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Extensions for the evolving G.709 Optical Transport Networks Control Extensions for the evolving G.709 Optical Transport Networks Control
draft-ietf-ccamp-gmpls-signaling-g709v3-09.txt draft-ietf-ccamp-gmpls-signaling-g709v3-10.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with This Internet-Draft is submitted to IETF in full conformance with
the provisions of BCP 78 and BCP 79. the 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), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on November 31, 2013. This Internet-Draft will expire on December 18, 2013.
Abstract Abstract
ITU-T Recommendation G.709 [G709-2012] has introduced new Optical ITU-T Recommendation G.709 [G709-2012] has introduced new Optical
channel Data Unit (ODU) containers (ODU0, ODU4, ODU2e and ODUflex) channel Data Unit (ODU) containers (ODU0, ODU4, ODU2e and ODUflex)
and enhanced Optical Transport Networking (OTN) flexibility. and enhanced Optical Transport Networking (OTN) flexibility.
This document updates RFC4328 to provide the extensions to the This document provides an alternative to RFC4328 to provide the
Generalized Multi-Protocol Label Switching (GMPLS) signaling to extensions to the Generalized Multi-Protocol Label Switching (GMPLS)
control the evolving OTN addressing ODUk multiplexing and new signaling to control the full set of OTN features including ODU0,
features including ODU0, ODU4, ODU2e and ODUflex. ODU4, ODU2e and ODUflex.
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
Table of Contents Table of Contents
1. Introduction .................................................. 3 1. Introduction .................................................. 3
2. Terminology ................................................... 3 2. Terminology ................................................... 3
3. GMPLS Extensions for the Evolving G.709 - Overview ............ 3 3. GMPLS Extensions for the Evolving G.709 - Overview ............ 3
4. Generalized Label Request ..................................... 4 4. Generalized Label Request ..................................... 4
5. Extensions for Traffic Parameters for the Evolving G.709 ...... 6 5. Extensions for Traffic Parameters for the Evolving G.709 ...... 7
5.1. Usage of ODUflex(CBR) Traffic Parameters ................. 8 5.1. Usage of ODUflex(CBR) Traffic Parameters ................. 8
5.2. Usage of ODUflex(GFP) Traffic Parameters ................ 10 5.2. Usage of ODUflex(GFP) Traffic Parameters ................ 10
5.3. Notification on Errors of OTN-TDM Traffic Parameters .... 10 5.3. Notification on Errors of OTN-TDM Traffic Parameters .... 11
6. Generalized Label ............................................ 11 6. Generalized Label ............................................ 11
6.1. OTN-TDM Switching Type Generalized Label ................ 11 6.1. OTN-TDM Switching Type Generalized Label ................ 11
6.2. Procedures .............................................. 14 6.2. Procedures .............................................. 14
6.2.1. Notification on Label Error ........................ 15 6.2.1. Notification on Label Error ........................ 15
6.3. Supporting Virtual Concatenation and Multiplication ..... 16 6.3. Supporting Virtual Concatenation and Multiplication ..... 16
6.4. Examples ................................................ 17 6.4. Examples ................................................ 17
7. Supporting Hitless Adjustment of ODUflex (GFP) ............... 18 7. Supporting Hitless Adjustment of ODUflex (GFP) ............... 18
8. Control Plane Backward Compatibility Considerations........... 19 8. Control Plane Backward Compatibility Considerations........... 19
9. Security Considerations ...................................... 20 9. Security Considerations ...................................... 20
10. IANA Considerations.......................................... 20 10. IANA Considerations.......................................... 20
11. References .................................................. 22 11. References .................................................. 22
11.1. Normative References ................................... 22 11.1. Normative References ................................... 22
11.2. Informative References ................................. 23 11.2. Informative References ................................. 23
12. Contributors ................................................ 23 12. Contributors ................................................ 24
13. Authors' Addresses .......................................... 24 13. Authors' Addresses .......................................... 24
14. Acknowledgment .............................................. 26 14. Acknowledgment .............................................. 26
1. Introduction 1. Introduction
With the evolution and deployment of OTN technology, it is necessary With the evolution and deployment of OTN technology, it is necessary
that appropriate enhanced control technology support be provided for that appropriate enhanced control technology support be provided for
[G709-2012]. [G709-2012].
[OTN-FWK] provides a framework to allow the development of protocol [OTN-FWK] provides a framework to allow the development of protocol
extensions to support GMPLS and Path Computation Element (PCE) extensions to support GMPLS and Path Computation Element (PCE)
control of OTN as specified in [G709-2012]. Based on this framework, control of OTN as specified in [G709-2012]. Based on this framework,
[OTN-INFO] evaluates the information needed by the routing and [OTN-INFO] evaluates the information needed by the routing and
signaling process in OTNs to support GMPLS control of OTN. signaling process in OTNs to support GMPLS control of OTN.
[RFC4328] describes the control technology details that are specific [RFC4328] describes the control technology details that are specific
to the 2001 revision of the G.709 specification. This document to the 2001 revision of the G.709 specification. This document
updates [RFC4328] to provide Resource ReserVation Protocol-Traffic provides an alternative to [RFC4328] to provide Resource ReserVation
Engineering (RSVP-TE) extensions to support of control for [G709- Protocol-Traffic Engineering (RSVP-TE) extensions to support of
2012]. control for [G709-2012].
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
3. GMPLS Extensions for the Evolving G.709 - Overview 3. GMPLS Extensions for the Evolving G.709 - Overview
New features for the evolving OTN, for example, new ODU0, ODU2e, ODU4 New features for the evolving OTN, for example, new ODU0, ODU2e, ODU4
skipping to change at page 3, line 44 skipping to change at page 3, line 44
- Optical Channel Transport Unit (OTUk): - Optical Channel Transport Unit (OTUk):
. OTU4 . OTU4
- Optical Channel Data Unit (ODUk): - Optical Channel Data Unit (ODUk):
. ODU0 . ODU0
. ODU2e . ODU2e
. ODU4 . ODU4
. ODUflex . ODUflex
A new Tributary Slot Granularity (TS Granularity, TSG) (i.e., 1.25 A new Tributary Slot granularity (i.e., 1.25Gbps) is also described
Gbps) is also described in [G709-2012]. Thus, there are now two TS in [G709-2012]. Thus, there are now two TS granularities for the
granularities for the foundation OTN ODU1, ODU2 and ODU3 containers. foundation OTN ODU1, ODU2 and ODU3 containers. The TS granularity at
2.5Gbps is used on legacy interfaces while the new 1.25Gbps is used
The TS granularity at 2.5 Gbps is used on legacy interfaces while the on the new interfaces.
new 1.25 Gbps is used on the new interfaces.
In addition to the support of ODUk mapping into OTUk (k = 1, 2, 3, In addition to the support of ODUk mapping into OTUk (k = 1, 2, 3,
4), the evolving OTN [G.709-V3] encompasses the multiplexing of ODUj 4), [G709-2012] encompasses the multiplexing of ODUj (j = 0, 1, 2,
(j = 0, 1, 2, 2e, 3, flex) into an ODUk (k > j), as described in 2e, 3, flex) into an ODUk (k > j), as described in Section 3.1.2 of
Section 3.1.2 of [OTN-FWK]. [OTN-FWK].
Virtual Concatenation (VCAT) of Optical channel Payload Unit-k (OPUk) Virtual Concatenation (VCAT) of Optical channel Payload Unit-k (OPUk)
(OPUk-Xv, k = 1/2/3, X = 1...256) is also supported by [G709-2012]. (OPUk-Xv, k = 1/2/3, X = 1...256) is also supported by [G709-2012].
Note that VCAT of OPU0 / OPU2e / OPU4 / OPUflex is not supported per Note that VCAT of OPU0 / OPU2e / OPU4 / OPUflex is not supported per
[G709-2012]. [G709-2012].
[RFC4328] describes GMPLS signaling extensions to support the control [RFC4328] describes GMPLS signaling extensions to support the control
for the 2001 revision of the G.709 specification. However, [RFC4328] for the 2001 revision of the G.709 specification. However, [RFC4328]
needs to be updated because it does not provide the means to signal does not provide the means to signal all the new Signal Types and
all the new Signal Types and related mapping and multiplexing related mapping and multiplexing functionalities. Moreover, it
functionalities. Moreover, it supports only the deprecated auto- supports only the deprecated auto- Multiframe Structure Identifier
Multiframe Structure Identifier (MSI) mode which assumes that the (MSI) mode which assumes that the Tributary Port Number (TPN) is
Tributary Port Number (TPN) is automatically assigned in the transmit automatically assigned in the transmit direction and not checked in
direction and not checked in the receive direction. the receive direction.
This document extends the G.709 Traffic Parameters described in This document extends the G.709 Traffic Parameters described in
[RFC4328] and presents a new flexible and scalable OTN label format. [RFC4328] and presents a new flexible and scalable OTN-TDM
Additionally, procedures about Tributary Port Number assignment Generalized Label format. Additionally, procedures about Tributary
through control plane are also provided in this document. Port Number assignment through control plane are also provided in
this document.
4. Generalized Label Request 4. Generalized Label Request
The Generalized Label Request, as described in [RFC3471], carries the The GENERALIZED_LABEL_REQUEST object, as described in [RFC3471],
Label Switched Path (LSP) Encoding Type, the Switching Type and the carries the Label Switched Path (LSP) Encoding Type, the Switching
Generalized Protocol Identifier (G-PID). Type and the Generalized Protocol Identifier (G-PID).
[RFC4328] extends the Generalized Label Request, introducing two new [RFC4328] extends the GENERALIZED_LABEL_REQUEST object, introducing
code-points for the LSP Encoding Type (i.e., G.709 ODUk (Digital two new code-points for the LSP Encoding Type (i.e., G.709 ODUk
Path) and G.709 Optical Channel) and adding a list of G-PID values in (Digital Path) and G.709 Optical Channel) and adding a list of G-PID
order to accommodate the 2001 revision of the G.709 specification. values in order to accommodate the 2001 revision of the G.709
specification.
This document follows these extensions and a new Switching Type is This document follows these extensions and a new Switching Type is
introduced to indicate the ODUk switching capability [G709-2012] in introduced to indicate the ODUk switching capability [G709-2012] in
order to support backward compatibility with [RFC4328], as described order to support backward compatibility with [RFC4328], as described
in [OTN-FWK]. The new Switching Type (OTN-TDM Switching Type) is in [OTN-FWK]. The new Switching Type (OTN-TDM Switching Type) is
defined in [OTN-OSPF]. defined in [OTN-OSPF].
This document also updates the G-PID values defined in [RFC4328]: This document also updates the G-PID values defined in [RFC4328]:
Value G-PID Type Value G-PID Type
----- ---------- ----- ----------
47 Type field updated from "G.709 ODUj" to "ODU-2.5G" to 47 Type field updated from "G.709 ODUj" to "ODU-2.5G" to
indicates transport of Digital Paths (e.g., at 2.5, 10 and indicate transport of Digital Paths (e.g., at 2.5, 10 and
40 Gbps) via 2.5Gbps TSG 40Gbps) via 2.5Gbps TS granularity.
56 Type field updated from "ESCON" to "SBCON/ESCON" to align 56 Type field updated from "ESCON" to "SBCON/ESCON" to align
with [G709-2012] payload type 0x1A. with [G709-2012] payload type 0x1A.
Note: Value 47 includes mapping of Synchronous Digital Hierarchy Note: Value 47 includes mapping of Synchronous Digital Hierarchy
(SDH). (SDH).
In the case of ODU multiplexing, the Lower Order ODU (LO ODU) (i.e., In the case of ODU multiplexing, the Lower Order ODU (LO ODU) (i.e.,
the client signal) may be multiplexed into Higher Order ODU (HO ODU) the client signal) may be multiplexed into Higher Order ODU (HO ODU)
via 1.25G TSG, 2.5G TSG or any one of them (i.e., TSG via 1.25G TS granularity, 2.5G TS granularity or any one of them
Auto_Negotiation is enabled). Since the G-PID type "ODUk" defined in (i.e., TS granularity Auto_Negotiation is enabled). Since the G-PID
[RFC4328] is only used for 2.5Gbps TSG, two new G-PID types are type "ODUk" defined in [RFC4328] is only used for 2.5Gbps TS
defined as follows: granularity, two new G-PID types are defined as follows:
- ODU-1.25G: Transport of Digital Paths at 1.25, 2.5, 10, 40 and 100 - ODU-1.25G: Transport of Digital Paths at 1.25, 2.5, 10, 40 and 100
Gbps via 1.25Gbps TSG Gbps via 1.25Gbps TS granularity.
- ODU-any: Transport of Digital Paths at 1.25, 2.5, 10, 40 and 100 - ODU-any: Transport of Digital Paths at 1.25, 2.5, 10, 40 and 100
Gbps via 1.25 or 2.5Gbps TSG (i.e., the fallback Gbps via 1.25 or 2.5Gbps TS granularity (i.e., the
procedure is enabled and the default value of 1.25Gbps fallback procedure is enabled and the default value of
TSG can be fallen back to 2.5Gbps if needed) 1.25Gbps TS granularity can be fallen back to 2.5Gbps
if needed).
The full list of payload types defined in [G709-2012] and their The full list of payload types defined in [G709-2012] and their
mapping to existing and new G-PID types are as follows: mapping to existing and new G-PID types are as follows:
G.709 G.709
Payload Payload
Type G-PID Type/Comment LSP Encoding Type G-PID Type/Comment LSP Encoding
==== ===== ===================== =================== ==== ===== ===================== ===================
0x01 No standard value 0x01 No standard value
0x02 49 CBRa G.709 ODUk 0x02 49 CBRa G.709 ODUk
skipping to change at page 7, line 4 skipping to change at page 7, line 8
Note that the mapping types for ODUj into OPUk are unambiguously per Note that the mapping types for ODUj into OPUk are unambiguously per
Table 7-10 of [G709-2012], so it does not need to carry mapping type Table 7-10 of [G709-2012], so it does not need to carry mapping type
information in the signaling. information in the signaling.
Note also that additional information on G.709 client mapping can be Note also that additional information on G.709 client mapping can be
found in [G7041]. found in [G7041].
5. Extensions for Traffic Parameters for the Evolving G.709 5. Extensions for Traffic Parameters for the Evolving G.709
The Traffic Parameters for OTN-TDM capable Switching Type are carried The Traffic Parameters for OTN-TDM capable Switching Type are carried
in the OTN-TDM SENDER_TSPEC and FLOWSPEC objects. The objects have in the OTN-TDM SENDER_TSPEC and OTN-TDM FLOWSPEC objects. The objects
the following class and type: have the following class and type:
- OTN-TDM SENDER_TSPEC Object: Class = 12, C-Type = 7 (TBA) - OTN-TDM SENDER_TSPEC object: Class = 12, C-Type = 7 (TBA)
- OTN-TDM FLOWSPEC Object: Class = 9, C-Type = 7 (TBA) - OTN-TDM FLOWSPEC object: Class = 9, C-Type = 7 (TBA)
The format of Traffic Parameters in these two objects is defined as The format of Traffic Parameters in these two objects is defined as
follows: follows:
0 1 2 3 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 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 | Reserved | | Signal Type | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NVC | Multiplier (MT) | | NVC | Multiplier (MT) |
skipping to change at page 7, line 30 skipping to change at page 7, line 34
| Bit_Rate | | Bit_Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Signal Type: 8 bits Signal Type: 8 bits
As defined in [RFC4328] Section 3.2.1, with the following As defined in [RFC4328] Section 3.2.1, with the following
additional values: additional values:
Value Type Value Type
----- ---- ----- ----
4 ODU4 (i.e., 100 Gbps) 4 ODU4 (i.e., 100Gbps)
9 OCh at 100 Gbps 9 OCh at 100Gbps
10 ODU0 (i.e., 1.25 Gbps) 10 ODU0 (i.e., 1.25Gbps)
11 ODU2e (i.e., 10Gbps for FC1200 and GE LAN) 11 ODU2e (i.e., 10Gbps for FC1200 and GE LAN)
12~19 Reserved (for future use) 12~19 Reserved (for future use)
20 ODUflex(CBR) (i.e., 1.25*N Gbps) 20 ODUflex(CBR) (i.e., 1.25*N Gbps)
21 ODUflex(Generic Framing Procedure-Framed (GFP-F)), 21 ODUflex(Generic Framing Procedure-Framed (GFP-F)),
resizable (i.e., 1.25*N Gbps) resizable (i.e., 1.25*N Gbps)
22 ODUflex(GFP-F), non resizable (i.e., 1.25*N Gbps) 22 ODUflex(GFP-F), non resizable (i.e., 1.25*N Gbps)
23~255 Reserved (for future use) 23~255 Reserved (for future use)
NVC: 16 bits NVC: 16 bits
skipping to change at page 8, line 23 skipping to change at page 8, line 26
[IEEE]). For other Signal Types, this field MUST be set to zero [IEEE]). For other Signal Types, this field MUST be set to zero
on transmission and MUST be ignored on receipt and SHOULD be on transmission and MUST be ignored on receipt and SHOULD be
passed unmodified by transit nodes. passed unmodified by transit nodes.
5.1. Usage of ODUflex(CBR) Traffic Parameters 5.1. Usage of ODUflex(CBR) Traffic Parameters
In case of ODUflex(CBR), the information of Bit_Rate carried in the In case of ODUflex(CBR), the information of Bit_Rate carried in the
ODUflex Traffic Parameters MUST be used to determine the actual ODUflex Traffic Parameters MUST be used to determine the actual
bandwidth of ODUflex(CBR) (i.e., Bit_Rate * (1 +/- Tolerance)). bandwidth of ODUflex(CBR) (i.e., Bit_Rate * (1 +/- Tolerance)).
Therefore the total number of tributary slots N in the HO ODUk link Therefore the total number of tributary slots N in the HO ODUk link
can be reserved correctly. Here: can be reserved correctly. Where:
N = Ceiling of N = Ceiling of
ODUflex(CBR) nominal bit rate * (1 + ODUflex(CBR) bit rate tolerance) ODUflex(CBR) nominal bit rate * (1 + ODUflex(CBR) bit rate tolerance)
--------------------------------------------------------------------- ---------------------------------------------------------------------
ODTUk.ts nominal bit rate * (1 - HO OPUk bit rate tolerance) ODTUk.ts nominal bit rate * (1 - HO OPUk bit rate tolerance)
In this formula, the ODUflex(CBR) nominal bit rate is the bit rate of In this formula, the ODUflex(CBR) nominal bit rate is the bit rate of
the ODUflex(CBR) on the line side, i.e., the client signal bit rate the ODUflex(CBR) on the line side, i.e., the client signal bit rate
after applying the 239/238 factor (according to Clause 7.3, Table 7-2 after applying the 239/238 factor (according to Clause 7.3, Table 7-2
skipping to change at page 9, line 13 skipping to change at page 9, line 15
ODU4.ts 1,301,683.217 1,301,709.251 1,301,735.285 ODU4.ts 1,301,683.217 1,301,709.251 1,301,735.285
Note that: Note that:
Minimum bit rate of ODUTk.ts = Minimum bit rate of ODUTk.ts =
ODTUk.ts nominal bit rate * (1 - HO OPUk bit rate tolerance) ODTUk.ts nominal bit rate * (1 - HO OPUk bit rate tolerance)
Maximum bit rate of ODTUk.ts = Maximum bit rate of ODTUk.ts =
ODTUk.ts nominal bit rate * (1 + HO OPUk bit rate tolerance) ODTUk.ts nominal bit rate * (1 + HO OPUk bit rate tolerance)
Where: HO OPUk bit rate tolerance = 20ppm Where: HO OPUk bit rate tolerance = 20ppm (parts per million)
Note that the bit rate tolerance is implicit in Signal Type and the Note that the bit rate tolerance is implicit in Signal Type and the
ODUflex(CBR) bit rate tolerance is fixed and it is equal to 100ppm as ODUflex(CBR) bit rate tolerance is fixed and it is equal to 100ppm as
described in Table 7-2 of [G709-2012]. described in Table 7-2 of [G709-2012].
Therefore, a node receiving a PATH message containing ODUflex(CBR) Therefore, a node receiving a Path message containing ODUflex(CBR)
nominal bit rate can allocate precise number of tributary slots and nominal bit rate can allocate precise number of tributary slots and
set up the cross-connection for the ODUflex service. set up the cross-connection for the ODUflex service.
Note that for different ODUk, the bit rates of the tributary slots Note that for different ODUk, the bit rates of the tributary slots
are different, and so the total number of tributary slots to be are different, and so the total number of tributary slots to be
reserved for the ODUflex(CBR) MAY not be the same on different HO reserved for the ODUflex(CBR) may not be the same on different HO
ODUk links. ODUk links.
An example is given below to illustrate the usage of ODUflex(CBR) An example is given below to illustrate the usage of ODUflex(CBR)
Traffic Parameters. Traffic Parameters.
As shown in Figure 1, assume there is an ODUflex(CBR) service
requesting a bandwidth of (2.5Gbps, +/-100ppm) from node A to node C.
In other words, the ODUflex Traffic Parameters indicate that Signal
Type is 20 (ODUflex(CBR)), Bit_Rate is 2.5Gbps and Tolerance is
100ppm.
+-----+ +---------+ +-----+ +-----+ +---------+ +-----+
| +-------------+ +-----+ +-------------+ | | +-------------+ +-----+ +-------------+ |
| +=============+\| ODU |/+=============+ | | +=============+\| ODU |/+=============+ |
| +=============+/| flex+-+=============+ | | +=============+/| flex+-+=============+ |
| +-------------+ | |\+=============+ | | +-------------+ | |\+=============+ |
| +-------------+ +-----+ +-------------+ | | +-------------+ +-----+ +-------------+ |
| | | | | | | | | | | |
| | ....... | | ....... | | | | ....... | | ....... | |
| A +-------------+ B +-------------+ C | | A +-------------+ B +-------------+ C |
+-----+ HO ODU4 +---------+ HO ODU2 +-----+ +-----+ HO ODU4 +---------+ HO ODU2 +-----+
=========: TS occupied by ODUflex =========: TSs occupied by ODUflex
---------: free TS ---------: available TSs
Figure 1 - Example of ODUflex(CBR) Traffic Parameters Figure 1 - Example of ODUflex(CBR) Traffic Parameters
As shown in Figure 1, assume there is an ODUflex(CBR) service
requesting a bandwidth of (2.5Gbps, +/-100ppm) from node A to node C.
In other words, the ODUflex Traffic Parameters indicate that Signal
Type is 20 (ODUflex(CBR)), Bit_Rate is 2.5Gbps (Note that the
tolerance is no longer signaled as explained above).
- On the HO ODU4 link between node A and B: - On the HO ODU4 link between node A and B:
The maximum bit rate of the ODUflex(CBR) equals 2.5Gbps * (1 + The maximum bit rate of the ODUflex(CBR) equals 2.5Gbps * (1 +
100ppm), and the minimum bit rate of the tributary slot of ODU4 100ppm), and the minimum bit rate of the tributary slot of ODU4
equals 1,301,683.217 Kbps, so the total number of tributary slots equals 1,301,683.217 Kbps, so the total number of tributary slots
N1 to be reserved on this link is: N1 to be reserved on this link is:
N1 = ceiling (2.5Gbps * (1 + 100ppm) / 1,301,683.217 Kbps) = 2 N1 = ceiling (2.5Gbps * (1 + 100ppm) / 1,301,683.217 Kbps) = 2
- On the HO ODU2 link between node B and C: - On the HO ODU2 link between node B and C:
skipping to change at page 10, line 33 skipping to change at page 10, line 37
5.2. Usage of ODUflex(GFP) Traffic Parameters 5.2. Usage of ODUflex(GFP) Traffic Parameters
[G709-2012] recommends that the ODUflex(GFP) will fill an integral [G709-2012] recommends that the ODUflex(GFP) will fill an integral
number of tributary slots of the smallest HO ODUk path over which the number of tributary slots of the smallest HO ODUk path over which the
ODUflex(GFP) may be carried, as shown in Table 2. ODUflex(GFP) may be carried, as shown in Table 2.
Table 2 - Recommended ODUflex(GFP) bit rates and tolerance Table 2 - Recommended ODUflex(GFP) bit rates and tolerance
ODU type | Nominal bit-rate | Tolerance ODU type | Nominal bit-rate | Tolerance
--------------------------------+------------------+----------- --------------------------------+------------------+-----------
ODUflex(GFP) of n TS, 1<=n<=8 | n * ODU2.ts | +/-100 ppm ODUflex(GFP) of n TSs, 1<=n<=8 | n * ODU2.ts | +/-100 ppm
ODUflex(GFP) of n TS, 9<=n<=32 | n * ODU3.ts | +/-100 ppm ODUflex(GFP) of n TSs, 9<=n<=32 | n * ODU3.ts | +/-100 ppm
ODUflex(GFP) of n TS, 33<=n<=80 | n * ODU4.ts | +/-100 ppm ODUflex(GFP) of n TSs, 33<=n<=80 | n * ODU4.ts | +/-100 ppm
According to this table, the Bit_Rate field for ODUflex(GFP) MUST According to this table, the Bit_Rate field for ODUflex(GFP) MUST
equal to one of the 80 values listed below: equal to one of the 80 values listed below:
1 * ODU2.ts; 2 * ODU2.ts; ...; 8 * ODU2.ts; 1 * ODU2.ts; 2 * ODU2.ts; ...; 8 * ODU2.ts;
9 * ODU3.ts; 10 * ODU3.ts, ...; 32 * ODU3.ts; 9 * ODU3.ts; 10 * ODU3.ts, ...; 32 * ODU3.ts;
33 * ODU4.ts; 34 * ODU4.ts; ...; 80 * ODU4.ts. 33 * ODU4.ts; 34 * ODU4.ts; ...; 80 * ODU4.ts.
In this way, the number of required tributary slots for the In this way, the number of required tributary slots for the
ODUflex(GFP) (i.e., the value of "n" in Table 2) can be deduced from ODUflex(GFP) (i.e., the value of "n" in Table 2) can be deduced from
the Bit_Rate field. the Bit_Rate field.
5.3. Notification on Errors of OTN-TDM Traffic Parameters 5.3. Notification on Errors of OTN-TDM Traffic Parameters
There is no Adspec associated with the OTN-TDM SENDER_TSPEC. Either There is no Adspec associated with the OTN-TDM SENDER_TSPEC object.
the Adspec is omitted or an Int-serv Adspec with the Default General Either the Adspec is omitted or an Int-serv Adspec with the Default
Characterization Parameters and Guaranteed Service fragment is used, General Characterization Parameters and Guaranteed Service fragment
see [RFC2210]. is used, see [RFC2210].
For a particular sender in a session, the contents of the FLOWSPEC For a particular sender in a session, the contents of the OTN-TDM
object received in a Resv message SHOULD be identical to the contents FLOWSPEC object received in a Resv message SHOULD be identical to the
of the SENDER_TSPEC object received in the corresponding Path contents of the OTN-TDM SENDER_TSPEC object received in the
message. If the objects do not match, a ResvErr message with a corresponding Path message. If the objects do not match, a ResvErr
"Traffic Control Error/Bad Flowspec value" error MUST be generated. message with a "Traffic Control Error/Bad Flowspec value" error MUST
be generated.
Intermediate and egress nodes MUST verify that the node itself, and Intermediate and egress nodes MUST verify that the node itself, and
the interfaces on which the LSP will be established, can support the the interfaces on which the LSP will be established, can support the
requested Signal Type, NVC and Bit_Rate values. If the requested requested Signal Type, NVC and Bit_Rate values. If the requested
value(s) cannot be supported, the receiver node MUST generate a value(s) cannot be supported, the receiver node MUST generate a
PathErr message with a "Traffic Control Error/Service unsupported" PathErr message with a "Traffic Control Error/Service unsupported"
indication (see [RFC2205]). indication (see [RFC2205]).
In addition, if the MT field is received with a zero value, the node In addition, if the MT field is received with a zero value, the node
MUST generate a PathErr message with a "Traffic Control Error/Bad MUST generate a PathErr message with a "Traffic Control Error/Bad
skipping to change at page 11, line 34 skipping to change at page 11, line 40
Further, if the Signal Type is not ODU1, ODU2 or ODU3, and the NVC Further, if the Signal Type is not ODU1, ODU2 or ODU3, and the NVC
field is not 0, the node MUST generate a PathErr message with a field is not 0, the node MUST generate a PathErr message with a
"Traffic Control Error/Bad Tspec value" indication (see [RFC2205]). "Traffic Control Error/Bad Tspec value" indication (see [RFC2205]).
6. Generalized Label 6. Generalized Label
This section defines the format of the OTN-TDM Generalized Label. This section defines the format of the OTN-TDM Generalized Label.
6.1. OTN-TDM Switching Type Generalized Label 6.1. OTN-TDM Switching Type Generalized Label
The following is the Generalized Label format for that MUST be used The following is the GENERALIZED_LABEL object format for that MUST be
with the OTN-TDM Switching Type: used with the OTN-TDM Switching Type:
0 1 2 3 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 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 | | TPN | Reserved | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Bit Map ...... ~ ~ Bit Map ...... ~
~ ...... | Padding Bits ~ ~ ...... | Padding Bits ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The OTN-TDM GENERALIZED_LABEL object is used to indicate how the LO
The OTN-TDM Generalized Label is used to indicate how the LO ODUj ODUj signal is multiplexed into the HO ODUk link. Note that the LO
signal is multiplexed into the HO ODUk link. Note that the LO OUDj OUDj signal type is indicated by Traffic Parameters, while the type
signal type is indicated by Traffic Parameters, while the type of HO of HO ODUk link is identified by the selected interface carried in
ODUk link is identified by the selected interface carried in the the IF_ID RSVP_HOP object.
IF_ID RSVP_HOP Object.
TPN (12 bits): indicates the TPN for the assigned Tributary Slot(s). TPN (12 bits): indicates the TPN for the assigned Tributary Slot(s).
- In case of LO ODUj multiplexed into HO ODU1/ODU2/ODU3, only the - In case of LO ODUj multiplexed into HO ODU1/ODU2/ODU3, only the
lower 6 bits of TPN field are significant and the other bits of lower 6 bits of TPN field are significant and the other bits of
TPN MUST be set to 0. TPN MUST be set to 0.
- In case of LO ODUj multiplexed into HO ODU4, only the lower 7 - In case of LO ODUj multiplexed into HO ODU4, only the lower 7
bits of TPN field are significant and the other bits of TPN bits of TPN field are significant and the other bits of TPN
MUST be set to 0. MUST be set to 0.
skipping to change at page 13, line 33 skipping to change at page 13, line 33
| ODU4 |Any ODU|1~80|Flexible, != ANY other existing LO ODUs' TPNs | | ODU4 |Any ODU|1~80|Flexible, != ANY other existing LO ODUs' TPNs |
+-------+-------+----+----------------------------------------------+ +-------+-------+----+----------------------------------------------+
Note that in the case of "Flexible", the value of TPN MAY not be Note that in the case of "Flexible", the value of TPN MAY not be
corresponding to the TS number as per [G709-2012]. corresponding to the TS number as per [G709-2012].
Length (12 bits): indicates the number of bits of the Bit Map field, Length (12 bits): indicates the number of bits of the Bit Map field,
i.e., the total number of TS in the HO ODUk link. The TS granularity, i.e., the total number of TS in the HO ODUk link. The TS granularity,
1.25Gbps or 2.5Gbps, may be derived by dividing the HO ODUk link's 1.25Gbps or 2.5Gbps, may be derived by dividing the HO ODUk link's
rate by the value of the Length field. In the context of [G709-2012], rate by the value of the Length field. In the context of [G709-2012],
the values of 4 and 16 indicate a TS granularity of 2.5Gps, and the the values of 4 and 16 indicate a TS granularity of 2.5Gbps, and the
values 2, 8, 32 and 80 indicate a TS granularity of 1.25Gps. values 2, 8, 32 and 80 indicate a TS granularity of 1.25Gbps.
In case of an ODUk mapped into OTUk, there is no need to indicate In case of an ODUk mapped into OTUk, there is no need to indicate
which tributary slots will be used, so the length field MUST be set which tributary slots will be used, so the length field MUST be set
to 0. to 0.
Bit Map (variable): indicates which tributary slots in HO ODUk that Bit Map (variable): indicates which tributary slots in HO ODUk that
the LO ODUj will be multiplexed into. The sequence of the Bit Map is the LO ODUj will be multiplexed into. The sequence of the Bit Map is
consistent with the sequence of the tributary slots in HO ODUk. Each consistent with the sequence of the tributary slots in HO ODUk. Each
bit in the bit map represents the corresponding tributary slot in HO bit in the bit map represents the corresponding tributary slot in HO
ODUk with a value of 1 or 0 indicating whether the tributary slot ODUk with a value of 1 or 0 indicating whether the tributary slot
will be used by LO ODUj or not. will be used by LO ODUj or not.
Padding bits are added after the Bit Map to make the whole label a Padding bits are added after the Bit Map to make the whole label a
multiple of four bytes if necessary. Padding bits MUST be set to 0 multiple of four bytes if necessary. Padding bits MUST be set to 0
and MUST be ignored. and MUST be ignored on receipt.
6.2. Procedures 6.2. Procedures
The ingress node MUST generate a Path message and specify the OTN-TDM The ingress node MUST generate a Path message and specify the OTN-TDM
Switching Type and corresponding G-PID in the Generalized Label Switching Type and corresponding G-PID in the
Request object, which MUST be processed as defined in [RFC3473]. GENERALIZED_LABEL_REQUEST object, which MUST be processed as defined
in [RFC3473].
The ingress node of an LSP MAY include label ERO (Explicit Route The ingress node of an LSP MAY include Label ERO (Explicit Route
Object) to indicate the label in each hops along the path. Note that Object) to indicate the label in each hops along the path. Note that
the TPN in the label ERO subobject MAY not be assigned by the ingress the TPN in the Label ERO subobject need not be assigned by the
node. In this case, the node MUST assign a valid TPN value and then ingress node. In this case, the node MUST assign a valid TPN value
put this value into TPN field of the label object when receiving a and then put this value into TPN field of the GENERALIZED_LABEL
Path message. object when receiving a Path message.
In order to create bidirectional LSP, the ingress node and upstream In order to create bidirectional LSP, the ingress node and upstream
node MUST generate an Upstream Label on the out outgoing interface to node MUST generate an UPSTREAM_LABEL object on the out outgoing
indicate the reserved TSs of ODUk and the assigned TPN value in the interface to indicate the reserved TSs of ODUk and the assigned TPN
upstream direction. This Upstream Label is sent to the downstream value in the upstream direction. This UPSTREAM_LABEL object is sent
node via Path massage for upstream resource reservation. to the downstream node via Path massage for upstream resource
reservation.
The ingress node or upstream node MAY generate Label Set to indicate The ingress node or upstream node MAY generate LABEL_SET object to
which labels on the outgoing interface in the downstream direction indicate which labels on the outgoing interface in the downstream
are acceptable. The downstream node will restrict its choice of direction are acceptable. The downstream node will restrict its
labels, i.e., TS resource and TPN value, to one which is in the Label choice of labels, i.e., TS resource and TPN value, to one which is in
Set. the LABEL_SET object.
The ingress node or upstream node MAY also generate Suggested Label The ingress node or upstream node MAY also generate SUGGESTED_LABEL
to indicate the preference of TS resource and TPN value on the object to indicate the preference of TS resource and TPN value on the
outgoing interface in the downstream direction. The downstream node outgoing interface in the downstream direction. The downstream node
is not REQUIRED to use the Suggested Label and MAY use another label is not required to use the suggested labels and may use another label
based on local decision and send it to the upstream node, as based on local decision and send it to the upstream node, as
described in [RFC3473]. described in [RFC3473].
When an upstream node receives a Resv message containing an LABEL When an upstream node receives a Resv message containing a
object with an OTN-TDM label, it MUST firstly identify which ODU GENERALIZED_LABEL object with an OTN-TDM label, it MUST firstly
Signal Type is multiplexed or mapped into which ODU Signal Type identify which ODU Signal Type is multiplexed or mapped into which
accordingly to the Traffic Parameters and the IF_ID RSVP_HOP Object ODU Signal Type accordingly to the Traffic Parameters and the IF_ID
in the received message. RSVP_HOP object in the received message.
- In case of ODUj to ODUk multiplexing, the node MUST retrieve the - In case of ODUj to ODUk multiplexing, the node MUST retrieve the
reserved tributary slots in the ODUk by its downstream neighbor reserved tributary slots in the ODUk by its downstream neighbor
node according to the position of the bits that are set to 1 in node according to the position of the bits that are set to 1 in
the Bit Map field. The node determines the TS type (according to the Bit Map field. The node determines the TS granularity
the total TS number of the ODUk, or pre-configured TS type), so (according to the total TS number of the ODUk, or pre-configured
that the node can multiplex the ODUj into the ODUk based on the TS TS granularity), so that the node can multiplex the ODUj into the
type. The node MUST also retrieve the TPN value assigned by its ODUk based on the TS granularity. The node MUST also retrieve the
downstream neighbor node from the label, and fill the TPN into the TPN value assigned by its downstream neighbor node from the label,
related MSI byte(s) in the OPUk overhead in the data plane, so and fill the TPN into the related MSI byte(s) in the OPUk overhead
that the downstream neighbor node can check whether the TPN in the data plane, so that the downstream neighbor node can check
received from the data plane is consistent with the ExMSI and whether the TPN received from the data plane is consistent with
determine whether there is any mismatch defect. the ExMSI and determine whether there is any mismatch defect.
- In case of ODUk to OTUk mapping, the size of Bit Map field MUST be - In case of ODUk to OTUk mapping, the size of Bit Map field MUST be
0 and no additional procedure is needed. 0 and no additional procedure is needed.
When a downstream node or egress node receives a Path message When a downstream node or egress node receives a Path message
containing Generalized Label Request object for setting up an ODUj containing GENERALIZED_LABEL_REQUEST object for setting up an ODUj
LSP from its upstream neighbor node, the node MUST generate an OTN- LSP from its upstream neighbor node, the node MUST generate an OTN-
TDM label according to the Signal Type of the requested LSP and the TDM label according to the Signal Type of the requested LSP and the
free resources (i.e., free tributary slots of ODUk) that will be available resources (i.e., available tributary slots of ODUk) that
reserved for the LSP, and send the label to its upstream neighbor will be reserved for the LSP, and send the label to its upstream
node. neighbor node.
- In case of ODUj to ODUk multiplexing, the node MUST firstly - In case of ODUj to ODUk multiplexing, the node MUST firstly
determine the size of the Bit Map field according to the Signal determine the size of the Bit Map field according to the Signal
Type and the tributary slot type of ODUk, and then set the bits to Type and the tributary slot type of ODUk, and then set the bits to
1 in the Bit Map field corresponding to the reserved tributary 1 in the Bit Map field corresponding to the reserved tributary
slots. The node MUST also assign a valid TPN, which MUST NOT slots. The node MUST also assign a valid TPN, which MUST NOT
collide with other TPN value used by existing LO ODU connections collide with other TPN value used by existing LO ODU connections
in the selected HO ODU link, and configure the Expected MSI in the selected HO ODU link, and configure the Expected MSI
(ExMSI) using this TPN. Then, the assigned TPN MUST be filled into (ExMSI) using this TPN. Then, the assigned TPN MUST be filled into
the label. the label.
- In case of ODUk to OTUk mapping, TPN field MUST be set to 0. Bit - In case of ODUk to OTUk mapping, TPN field MUST be set to 0. Bit
Map information is not REQUIRED and MUST NOT be included, so Map information is not REQUIRED and MUST NOT be included, so
Length field MUST be set to 0 as well. Length field MUST be set to 0 as well.
6.2.1. Notification on Label Error 6.2.1. Notification on Label Error
When an upstream node receives a Resv message containing an LABEL When an upstream node receives a Resv message containing an
object with an OTN-TDM label, the node MUST verify if the label is GENERALIZED_LABEL object with an OTN-TDM label, the node MUST verify
acceptable. If the label is not acceptable, the node MUST generate a if the label is acceptable. If the label is not acceptable, the node
ResvErr message with a "Routing problem/Unacceptable label value" MUST generate a ResvErr message with a "Routing problem/Unacceptable
indication. Per [RFC3473], the generated ResvErr message MAY include label value" indication. Per [RFC3473], the generated ResvErr
an ACCEPTABLE_LABEL_SET object. With the exception of label message MAY include an ACCEPTABLE_LABEL_SET object. With the
semantics, downstream node processing a received ResvErr messages and exception of label semantics, downstream node processing a received
of ACCEPTABLE_LABEL_SET objects is not modified by this document. ResvErr message and of ACCEPTABLE_LABEL_SET object is not modified
by this document.
Similarly, when a downstream node receives a Path message containing Similarly, when a downstream node receives a Path message containing
an UPSTREAM_LABEL object with an OTN-TDM label, the node MUST verify an UPSTREAM_LABEL object with an OTN-TDM label, the node MUST verify
if the label is acceptable. If the label is not acceptable, the node if the label is acceptable. If the label is not acceptable, the node
MUST generate a PathErr message with a "Routing problem/Unacceptable MUST generate a PathErr message with a "Routing problem/Unacceptable
label value" indication. Per [RFC3473], the generated ResvErr message label value" indication. Per [RFC3473], the generated ResvErr message
MAY include an ACCEPTABLE_LABEL_SET object. With the exception of MAY include an ACCEPTABLE_LABEL_SET object. With the exception of
label semantics, downstream node processing received PathErr messages label semantics, downstream node processing received a PathErr message
and of ACCEPTABLE_LABEL_SET objects is not modified by this document. and of ACCEPTABLE_LABEL_SET object is not modified by this document.
A received label SHALL be considered unacceptable when one of the A received label SHALL be considered unacceptable when one of the
following cases occurs: following cases occurs:
- The received label doesn't conform to local policy; - The received label doesn't conform to local policy;
- Invalid value in the length field; - Invalid value in the length field;
- The selected link only supports 2.5Gbps TS granularity while the - The selected link only supports 2.5Gbps TS granularity while the
Length field in the label along with ODUk Signal Type indicates Length field in the label along with ODUk Signal Type indicates
skipping to change at page 17, line 40 skipping to change at page 17, line 40
0 1 2 3 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 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 = 2 | Reserved | Length = 8 | | TPN = 2 | Reserved | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 1 0 0 0 0 0 0| Padding Bits (0) | |0 1 0 0 0 0 0 0| Padding Bits (0) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
This above label indicates an ODU0 multiplexed into the second This above label indicates an ODU0 multiplexed into the second
tributary slot of ODU2, wherein there are 8 TS in ODU2 (i.e., the tributary slot of ODU2, wherein there are 8 TSs in ODU2 (i.e., the
type of the tributary slot is 1.25Gbps), and the TPN value is 2. type of the tributary slot is 1.25Gbps), and the TPN value is 2.
- ODU1 into ODU2 Multiplexing with 1.25Gbps TS granularity: - ODU1 into ODU2 Multiplexing with 1.25Gbps TS granularity:
0 1 2 3 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 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 | Reserved | Length = 8 | | TPN = 1 | Reserved | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 1 0 1 0 0 0 0| Padding Bits (0) | |0 1 0 1 0 0 0 0| Padding Bits (0) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
This above label indicates an ODU1 multiplexed into the 2nd and the This above label indicates an ODU1 multiplexed into the 2nd and the
4th tributary slot of ODU2, wherein there are 8 TS in ODU2 (i.e., the 4th tributary slot of ODU2, wherein there are 8 TSs in ODU2 (i.e.,
type of the tributary slot is 1.25Gbps), and the TPN value is 1. the type of the tributary slot is 1.25Gbps), and the TPN value is 1.
- ODU2 into ODU3 Multiplexing with 2.5Gbps TS granularity: - ODU2 into ODU3 Multiplexing with 2.5Gbps TS granularity:
0 1 2 3 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 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 | Reserved | Length = 16 | | TPN = 1 | Reserved | Length = 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 1 1 0 1 0 1 0 0 0 0 0 0 0 0 0| Padding Bits (0) | |0 1 1 0 1 0 1 0 0 0 0 0 0 0 0 0| Padding Bits (0) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
This above label indicates an ODU2 multiplexed into the 2nd, 3rd, 5th This above label indicates an ODU2 multiplexed into the 2nd, 3rd, 5th
and 7th tributary slot of ODU3, wherein there are 16 TS in ODU3 and 7th tributary slot of ODU3, wherein there are 16 TSs in ODU3
(i.e., the type of the tributary slot is 2.5Gbps), and the TPN value (i.e., the type of the tributary slot is 2.5Gbps), and the TPN value
is 1. is 1.
7. Supporting Hitless Adjustment of ODUflex (GFP) 7. Supporting Hitless Adjustment of ODUflex (GFP)
[G7044] describes the procedure of ODUflex (GFP) hitless resizing [G7044] describes the procedure of ODUflex (GFP) hitless resizing
using Link Connection Resize (LCR) and Bandwidth Resize (BWR) using Link Connection Resize (LCR) and Bandwidth Resize (BWR)
protocols in OTN data plane. protocols in OTN data plane.
For the control plane, signaling messages are REQUIRED to initiate For the control plane, signaling messages are REQUIRED to initiate
skipping to change at page 19, line 11 skipping to change at page 19, line 11
The ingress node will trigger the BWR protocol when successful The ingress node will trigger the BWR protocol when successful
completion of LCR protocols on every hop after Resv message is completion of LCR protocols on every hop after Resv message is
processed. On success of BWR, the ingress node SHOULD send a processed. On success of BWR, the ingress node SHOULD send a
PathTear message to delete the old control state (i.e., the PathTear message to delete the old control state (i.e., the
control state of the ODUflex (GFP) before resizing) on the control state of the ODUflex (GFP) before resizing) on the
control plane. control plane.
A downstream node receiving Path message with SE style compares A downstream node receiving Path message with SE style compares
the old Traffic Parameters (stored locally) with the new one the old Traffic Parameters (stored locally) with the new one
carried in the Path message, to determine the number of TS to be carried in the Path message, to determine the number of TS to be
added. After choosing and reserving new free TS, the downstream added. After choosing and reserving new available TS(s), the
node MUST send back a Resv message carrying both the old and new downstream node MUST send back a Resv message carrying both the
LABEL Objects in the SE flow descriptor. old and new GENERALIZED_LABEL objects in the SE flow descriptor.
An upstream neighbor receiving Resv message with SE flow An upstream neighbor receiving Resv message with SE flow
descriptor MUST determine which TS are added and trigger the LCR descriptor MUST determine which TS(s) is/are added and trigger
protocol between itself and its downstream neighbor node. the LCR protocol between itself and its downstream neighbor node.
- Bandwidth decreasing - Bandwidth decreasing
For the ingress node, a Path message with SE style SHOULD also be For the ingress node, a Path message with SE style SHOULD also be
sent for ODUflex bandwidth decreasing. sent for ODUflex bandwidth decreasing.
The ingress node will trigger the BWR protocol when successful The ingress node will trigger the BWR protocol when successful
completion of LCR handshake on every hop after Resv message is completion of LCR handshake on every hop after Resv message is
processed. On success of BWR, the second step of LCR, i.e., link processed. On success of BWR, the second step of LCR, i.e., link
connection decrease procedure will be started on every hop of the connection decrease procedure will be started on every hop of the
connection. After completion of bandwidth decreasing, the ingress connection. After completion of bandwidth decreasing, the ingress
node SHOULD send a ResvErr message to tear down the old control node SHOULD send a ResvErr message to tear down the old control
state. state.
A downstream node receiving Path message with SE style compares A downstream node receiving Path message with SE style compares
the old Traffic Parameters with the new one carried in the Path the old Traffic Parameters with the new one carried in the Path
message to determine the number of TS to be decreased. After message to determine the number of TS to be decreased. After
choosing TSs to be decreased, the downstream node MUST send back choosing TSs to be decreased, the downstream node MUST send back
a Resv message carrying both the old and new LABEL Objects in the a Resv message carrying both the old and new GENERALIZED_LABEL
SE flow descriptor. objects in the SE flow descriptor.
An upstream neighbor receiving Resv message with SE flow An upstream neighbor receiving Resv message with SE flow
descriptor MUST determine which TS are decreased and trigger the descriptor MUST determine which TS(s) is/are decreased and
first step of LCR protocol (i.e., LCR handshake) between itself trigger the first step of LCR protocol (i.e., LCR handshake)
and its downstream neighbor node. between itself and its downstream neighbor node.
8. Control Plane Backward Compatibility Considerations 8. Control Plane Backward Compatibility Considerations
As described in [OTN-FWK], since the [RFC4328] has been deployed in As described in [OTN-FWK], since the [RFC4328] has been deployed in
the network for the nodes that support the 2001 revision of the G.709 the network for the nodes that support the 2001 revision of the G.709
specification, control plane backward compatibility SHOULD be taken specification, control plane backward compatibility SHOULD be taken
into consideration. More specifically: into consideration. More specifically:
o Nodes supporting this document SHOULD support [OTN-OSPF]. o Nodes supporting this document SHOULD support [OTN-OSPF].
skipping to change at page 20, line 25 skipping to change at page 20, line 25
o Ingress nodes that support both sets of procedures MAY select o Ingress nodes that support both sets of procedures MAY select
which set of procedures to follow based on routing information or which set of procedures to follow based on routing information or
local policy. local policy.
o Per [RFC3473], nodes that do not support this document will o Per [RFC3473], nodes that do not support this document will
generate a PathErr message, with a "Routing problem/Switching generate a PathErr message, with a "Routing problem/Switching
Type" indication. Type" indication.
9. Security Considerations 9. Security Considerations
This document introduces no new security considerations to the This document is a modification to [RFC3473] and [RFC4328], and only
existing GMPLS signaling protocols. Referring to [RFC3473] and differs in specific information communicated. As such, this document
[RFC4328], further details of the specific security measures are introduces no new security considerations to the existing GMPLS
provided. Additionally, [RFC5920] provides an overview of security signaling protocols. Referring to [RFC3473] and [RFC4328], further
vulnerabilities and protection mechanisms for the GMPLS control details of the specific security measures are provided. Additionally,
plane. [RFC5920] provides an overview of security vulnerabilities and
protection mechanisms for the GMPLS control plane.
10. IANA Considerations 10. IANA Considerations
Two RSVP C-Types are defined for OTN-TDM Traffic Parameters in this Upon approval of this document, IANA will make the following
document: assignments in the "Class Types or C-Types 9 FLOWSPEC" and "Class
http://www.iana.org/assignments/rsvp-parameters Types or C-Types 12 SENDER_TSPEC" section of the "RSVP Parameters"
registry located at http://www.iana.org/assignments/rsvp-
- OTN-TDM SENDER_TSPEC and FLOWSPEC objects: parameters/rsvp-parameters.xml.
o OTN-TDM SENDER_TSPEC Object: Class = 12, C-Type = 7 (see Value Description Reference
Section 5) 7(*) OTN-TDM [This.I-D]
o OTN-TDM FLOWSPEC Object: Class = 9, C-Type = 7 (see Section 5) (*) Suggested value
IANA maintains the "Generalized Multi-Protocol Label Switching IANA maintains the "Generalized Multi-Protocol Label Switching
(GMPLS) Signaling Parameters" registry (see (GMPLS) Signaling Parameters" registry (see
http://www.iana.org/assignments/gmpls-sig-parameters). "Generalized http://www.iana.org/assignments/gmpls-sig-parameters). "Generalized
PIDs (G-PID)" subregistry is included in this registry, which will be PIDs (G-PID)" subregistry is included in this registry, which will be
extended and updated by this document as below: extended and updated by this document as below:
- Generalized PID (G-PID): Value Type Technology Reference
===== ====================== ==========
Name: G-PID 47 G.709 ODU-2.5G G.709 ODUk [RFC4328]
Format: 16-bit number (IANA to update Type field) [This.I-D]
Values: 56 SBCON/ESCON G.709 ODUk, [RFC4328]
(IANA to update Type field) Lambda, Fiber [This.I-D]
59* Framed GFP G.709 ODUk [This.I-D]
60* STM-1 G.709 ODUk [This.I-D]
61* STM-4 G.709 ODUk [This.I-D]
62* InfiniBand G.709 ODUflex [This.I-D]
63* SDI (Serial Digital Interface) G.709 ODUk [This.I-D]
64* SDI/1.001 G.709 ODUk [This.I-D]
65* DVB_ASI G.709 ODUk [This.I-D]
66* G.709 ODU-1.25G G.709 ODUk [This.I-D]
67* G.709 ODU-Any G.709 ODUk [This.I-D]
68* Null Test G.709 ODUk [This.I-D]
69* Random Test G.709 ODUk [This.I-D]
70* 64B/66B GFP-F Ethernet G.709 ODUk [This.I-D]
Value Type/Comment LSP Encoding/Technology (*) Suggested value
======= ====================== =======================
47 G.709 ODU-2.5G G.709 ODUk (k=2,3)
(IANA to update Type field)
56 SBCON/ESCON G.709 ODUk, Lambda, Fiber
(IANA to update Type field)
59(TBA) Framed GFP G.709 ODUk
60(TBA) STM-1 G.709 ODUk (k=0)
61(TBA) STM-4 G.709 ODUk (k=0)
62(TBA) InfiniBand G.709 ODUflex
63(TBA) Serial Digital Interface G.709 ODUk (k=0,1,flex)
64(TBA) Serial Digital Interface/1.001 G.709 ODUk (k=1,flex)
65(TBA) DVB_ASI G.709 ODUk (k=0)
66(TBA) G.709 ODU-1.25G G.709 ODUk
67(TBA) G.709 ODU-Any G.709 ODUk (k=2,3)
68(TBA) Null Test G.709 ODUk
69(TBA) Random Test G.709 ODUk
70(TBA) 64B/66B GFP-F Ethernet G.709 ODUk (k=2)
"Signal Type" subregistry to the "Generalized Multi-Protocol Label Upon approval of this document, IANA will define an "OTN Signal Type"
Switching (GMPLS) Signaling Parameters" will be defined by this subregistry to the "Generalized Multi-Protocol Label Switching
document as below: (GMPLS) Signaling Parameters":
Value Signal Type Reference Value Signal Type Reference
----- ----------- --------- ----- ----------- ---------
0 Not significant [RFC4328] 0 Not significant [RFC4328]
1 ODU1 (i.e., 2.5 Gbps) [RFC4328] 1 ODU1 (i.e., 2.5Gbps) [RFC4328]
2 ODU2 (i.e., 10 Gbps) [RFC4328] 2 ODU2 (i.e., 10Gbps) [RFC4328]
3 ODU3 (i.e., 40 Gbps) [RFC4328] 3 ODU3 (i.e., 40Gbps) [RFC4328]
4 ODU4 (i.e., 100 Gbps) [this document] 4 ODU4 (i.e., 100Gbps) [this document]
5 Reserved (for future use) [RFC4328] 5 Reserved (for future use) [RFC4328]
6 Och at 2.5 Gbps [RFC4328] 6 Och at 2.5Gbps [RFC4328]
7 OCh at 10 Gbps [RFC4328] 7 OCh at 10Gbps [RFC4328]
8 OCh at 40 Gbps [RFC4328] 8 OCh at 40Gbps [RFC4328]
9 OCh at 100 Gbps [this document] 9 OCh at 100Gbps [this document]
10 ODU0 (i.e., 1.25 Gbps) [this document] 10 ODU0 (i.e., 1.25Gbps) [this document]
11 ODU2e (i.e., 10Gbps for FC1200 [this document] 11 ODU2e (i.e., 10Gbps for FC1200 [this document]
and GE LAN) and GE LAN)
12~19 Reserved (for future use) [this document] 12~19 Reserved (for future use) [this document]
20 ODUflex(CBR) (i.e., 1.25*N Gbps) [this document] 20 ODUflex(CBR) (i.e., 1.25*N Gbps) [this document]
21 ODUflex(GFP-F), resizable [this document] 21 ODUflex(GFP-F), resizable [this document]
(i.e., 1.25*N Gbps) (i.e., 1.25*N Gbps)
22 ODUflex(GFP-F), non resizable [this document] 22 ODUflex(GFP-F), non resizable [this document]
(i.e., 1.25*N Gbps) (i.e., 1.25*N Gbps)
23~255 Reserved (for future use) [this document] 23~255 Reserved (for future use) [this document]
New values are to be assigned via Standards Action as defined in
[RFC5226].
11. References 11. References
11.1. Normative References 11.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2205] Braden, R., Zhang, L., Berson, S., Herzog, S., and S. [RFC2205] Braden, R., Zhang, L., Berson, S., Herzog, S., and S.
Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1 Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1
Functional Specification", RFC 2205, September 1997. Functional Specification", RFC 2205, September 1997.
skipping to change at page 23, line 10 skipping to change at page 23, line 10
[RFC4328] D. Papadimitriou, Ed. "Generalized Multi-Protocol Label [RFC4328] D. Papadimitriou, Ed. "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling Extensions for G.709 Optical Switching (GMPLS) Signaling Extensions for G.709 Optical
Transport Networks Control", RFC 4328, Jan 2006. Transport Networks Control", RFC 4328, Jan 2006.
[RFC6344] G. Bernstein et al, "Operating Virtual Concatenation (VCAT) [RFC6344] G. Bernstein et al, "Operating Virtual Concatenation (VCAT)
and the Link Capacity Adjustment Scheme (LCAS) with and the Link Capacity Adjustment Scheme (LCAS) with
Generalized Multi-Protocol Label Switching (GMPLS)", Generalized Multi-Protocol Label Switching (GMPLS)",
RFC6344, August 2011. RFC6344, August 2011.
11.2. Informative References
[OTN-FWK] Fatai Zhang et al, "Framework for GMPLS and PCE Control of
G.709 Optical Transport Networks", Work in Progress: draft-
ietf-ccamp-gmpls-g709-framework, February 2013.
[OTN-INFO] S. Belotti et al, "Information model for G.709 Optical
Transport Networks (OTN)", Work in Progress: draft-ietf-
ccamp-otn-g709-info-model, May 2013.
[OTN-OSPF] D. Ceccarelli et al, "Traffic Engineering Extensions to
OSPF for Generalized MPLS (GMPLS) Control of Evolving G.709
OTN Networks", Work in Progress: draft-ietf-ccamp-gmpls-
ospf-g709v3, April 2013.
[G709-2012] ITU-T, "Interfaces for the Optical Transport Network [G709-2012] ITU-T, "Interfaces for the Optical Transport Network
(OTN)", G.709/Y.1331 Recommendation, February 2012. (OTN)", G.709/Y.1331 Recommendation, February 2012.
[G7044] ITU-T, "Hitless adjustment of ODUflex", G.7044/Y.1347, [G7044] ITU-T, "Hitless adjustment of ODUflex", G.7044/Y.1347,
October 2011. October 2011.
[G7041] ITU-T, "Generic framing procedure", G.7041/Y.1303, April [G7041] ITU-T, "Generic framing procedure", G.7041/Y.1303, April
2011. 2011.
[RFC4506] M. Eisler, Ed., "XDR: External Data Representation [RFC4506] M. Eisler, Ed., "XDR: External Data Representation
Standard", RFC 4506, May 2006. Standard", RFC 4506, May 2006.
[RFC5920] Fang, L., Ed., "Security Framework for MPLS and GMPLS
Networks", RFC5920, July 2010.
[IEEE] "IEEE Standard for Binary Floating-Point Arithmetic", [IEEE] "IEEE Standard for Binary Floating-Point Arithmetic",
ANSI/IEEE Standard 754-1985, Institute of Electrical and ANSI/IEEE Standard 754-1985, Institute of Electrical and
Electronics Engineers, August 1985. Electronics Engineers, August 1985.
11.2. Informative References
[OTN-FWK] Fatai Zhang et al, "Framework for GMPLS and PCE Control of
G.709 Optical Transport Networks", Work in Progress: draft-
ietf-ccamp-gmpls-g709-framework, June 2013.
[OTN-INFO] S. Belotti et al, "Information model for G.709 Optical
Transport Networks (OTN)", Work in Progress: draft-ietf-
ccamp-otn-g709-info-model, June 2013.
[OTN-OSPF] D. Ceccarelli et al, "Traffic Engineering Extensions to
OSPF for Generalized MPLS (GMPLS) Control of Evolving G.709
OTN Networks", Work in Progress: draft-ietf-ccamp-gmpls-
ospf-g709v3, June 2013.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, May
2008.
[RFC5920] Fang, L., Ed., "Security Framework for MPLS and GMPLS
Networks", RFC 5920, July 2010.
12. Contributors 12. Contributors
Jonathan Sadler, Tellabs Jonathan Sadler, Tellabs
Email: jonathan.sadler@tellabs.com Email: jonathan.sadler@tellabs.com
Kam LAM, Alcatel-Lucent Kam LAM, Alcatel-Lucent
Email: kam.lam@alcatel-lucent.com Email: kam.lam@alcatel-lucent.com
Xiaobing Zi, Huawei Technologies Xiaobing Zi, Huawei Technologies
Email: zixiaobing@huawei.com Email: zixiaobing@huawei.com
Francesco Fondelli, Ericsson Francesco Fondelli, Ericsson
Email: francesco.fondelli@ericsson.com Email: francesco.fondelli@ericsson.com
Lyndon Ong, Ciena Lyndon Ong, Ciena
 End of changes. 69 change blocks. 
218 lines changed or deleted 229 lines changed or added

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