draft-ietf-ccamp-gmpls-signaling-g709v3-05.txt   draft-ietf-ccamp-gmpls-signaling-g709v3-06.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: May 30, 2013 November 30, 2012 Expires: July 24, 2013 January 24, 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-05.txt draft-ietf-ccamp-gmpls-signaling-g709v3-06.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 May 30, 2013. This Internet-Draft will expire on July 24, 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 updates RFC4328 to provide the extensions to the
Generalized Multi-Protocol Label Switching (GMPLS) signaling to Generalized Multi-Protocol Label Switching (GMPLS) signaling to
control the evolving OTN addressing ODUk multiplexing and new control the evolving OTN addressing ODUk multiplexing and new
skipping to change at page 2, line 26 skipping to change at page 2, line 26
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 ...... 6
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
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 .............................................. 13 6.2. Procedures .............................................. 13
6.2.1. Notification on Label Error ........................ 15 6.2.1. Notification on Label Error ........................ 15
6.3. Supporting Virtual Concatenation and Multiplication ..... 15 6.3. Supporting Virtual Concatenation and Multiplication ..... 16
6.4. Examples ................................................ 15 6.4. Examples ................................................ 16
7. Supporting Hitless Adjustment of ODUflex (GFP) ............... 17 7. Supporting Hitless Adjustment of ODUflex (GFP) ............... 18
8. Control Plane Backward Compatibility Considerations........... 18 8. Control Plane Backward Compatibility Considerations........... 19
9. Security Considerations ...................................... 19 9. Security Considerations ...................................... 20
10. IANA Considerations.......................................... 19 10. IANA Considerations.......................................... 20
11. References .................................................. 20 11. References .................................................. 22
11.1. Normative References ................................... 20 11.1. Normative References ................................... 22
11.2. Informative References ................................. 21 11.2. Informative References ................................. 22
12. Contributors ................................................ 21 12. Contributors ................................................ 23
13. Authors' Addresses .......................................... 22 13. Authors' Addresses .......................................... 24
14. Acknowledgment .............................................. 24 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,
skipping to change at page 4, line 27 skipping to change at page 4, line 27
[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 needs to be updated because it does not provide the means to signal
all the new signal types and related mapping and multiplexing all the new signal types and related mapping and multiplexing
functionalities. Moreover, it supports only the deprecated auto- functionalities. Moreover, it supports only the deprecated auto-
Multiframe Structure Identifier (MSI) mode which assumes that the Multiframe Structure Identifier (MSI) mode which assumes that the
Tributary Port Number (TPN) is automatically assigned in the transmit Tributary Port Number (TPN) is automatically assigned in the transmit
direction and not checked in the receive direction. direction and not checked in 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 label format.
Additionally, procedures about Tributary Port Number assignment Additionally, procedures about Tributary Port Number assignment
through control plane are also provided in this document. 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, as described in [RFC3471], carries the
Label Switched Path (LSP) Encoding Type, the Switching Type and the Label Switched Path (LSP) Encoding Type, the Switching Type and the
Generalized Protocol Identifier (G-PID). Generalized Protocol Identifier (G-PID).
[RFC4328] extends the Generalized Label Request, introducing two new [RFC4328] extends the Generalized Label Request, introducing two new
code-points for the LSP Encoding Type (i.e., G.709 ODUk (Digital code-points for the LSP Encoding Type (i.e., G.709 ODUk (Digital
Path) and G.709 Optical Channel) and adding a list of G-PID values in Path) and G.709 Optical Channel) and adding a list of G-PID values in
order to accommodate the 2001 revision of the G.709 specification. 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 (101, TBA by IANA) is defined in in [OTN-FWK]. The new Switching Type (OTN-TDM Switching Type) is
[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 ODU-2.5G: transport of Digital Paths (e.g., at 2.5, 10 and 47 ODU-2.5G: Transport of Digital Paths (e.g., at 2.5, 10 and
40 Gbps) via 2.5Gbps TSG 40 Gbps) via 2.5Gbps TSG
49 CBRa: asynchronous Constant Bit Rate (CBR) (e.g., 49 CBRa: Asynchronous Constant Bit Rate (CBR) (e.g.,
mapping of CBR2G5, CBR10G and CBR40G) mapping of CBR2G5, CBR10G and CBR40G)
50 CBRb: bit synchronous Constant Bit Rate (e.g., mapping 50 CBRb: Bit synchronous Constant Bit Rate (e.g., mapping
of CBR2G5, CBR10G, CBR40G, CBR10G3 and supra- of CBR2G5, CBR10G, CBR40G, CBR10G3 and supra-
2.488 CBR Gbit/s signal (carried by OPUflex)) 2.488 CBR Gbit/s signal (carried by OPUflex))
32 ATM: mapping of Asynchronous Transfer Mode (ATM) cell 32 ATM: Mapping of Asynchronous Transfer Mode (ATM) cell
stream (e.g., at 1.25, 2.5, 10 and 40 Gbps) stream (e.g., at 1.25, 2.5, 10 and 40 Gbps)
51 BSOT: non-specific client Bit Stream with Octet Timing 51 BSOT: Non-specific client Bit Stream with Octet Timing
(e.g., Mapping of 1.25, 2.5, 10, 40 and 100 Gbps (e.g., Mapping of 1.25, 2.5, 10, 40 and 100 Gbps
Bit Stream) Bit Stream)
52 BSNT: non-specific client Bit Stream without Octet 52 BSNT: Non-specific client Bit Stream without Octet
Timing (e.g., Mapping of 1.25, 2.5, 10, 40 and Timing (e.g., Mapping of 1.25, 2.5, 10, 40 and
100 Gbps Bit Stream) 100 Gbps Bit Stream)
Note: Values 32, 47, 49 and 50 include mapping of Synchronous Digital Note: Values 32, 47, 49 and 50 include mapping of Synchronous Digital
Hierarchy (SDH). Hierarchy (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 TSG, 2.5G TSG or any one of them (i.e., TSG
Auto_Negotiation is enabled). Since the G-PID type "ODUk" defined in Auto_Negotiation is enabled). Since the G-PID type "ODUk" defined in
[RFC4328] is only used for 2.5Gbps TSG, two new G-PID types are [RFC4328] is only used for 2.5Gbps TSG, two new G-PID types are
defined as follows: 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 TSG
- 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 TSG (i.e., the fallback
procedure is enabled and the default value of 1.25Gbps procedure is enabled and the default value of 1.25Gbps
TSG can be fallen back to 2.5Gbps if needed) TSG can be fallen back to 2.5Gbps if needed)
In addition, some other new G-PID types are defined to support other In addition, some other new G-PID types are defined to support other
new client signals described in [G709-2012]: new client signals described in [G709-2012]:
- CBRc: Mapping of constant bit-rate signals with justification - CBRc: Mapping of constant bit-rate signals with justification
into OPUk (k = 0, 1, 2, 3, 4) via Generic Mapping into OPUk (k = 0, 1, 2, 3, 4) via Generic Mapping
Procedure (GMP) (i.e., mapping of sub-1.238, supra- Procedure (GMP) (i.e., mapping of sub-1.238, supra-
skipping to change at page 6, line 28 skipping to change at page 6, line 28
59(TBA) G.709 ODU-1.25G G.709 ODUk 59(TBA) G.709 ODU-1.25G G.709 ODUk
60(TBA) G.709 ODU-any G.709 ODUk 60(TBA) G.709 ODU-any G.709 ODUk
61(TBA) CBRc G.709 ODUk 61(TBA) CBRc G.709 ODUk
62(TBA) 1000BASE-X G.709 ODUk (k=0) 62(TBA) 1000BASE-X G.709 ODUk (k=0)
63(TBA) FC-1200 G.709 ODUk (k=2e) 63(TBA) FC-1200 G.709 ODUk (k=2e)
Note: Values 59 and 60 include mapping of SDH. Note: Values 59 and 60 include mapping of SDH.
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 FLOWSPEC objects. The objects have
the following class and type: 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 are 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 | Tolerance | | Signal Type | N | Tolerance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NVC | Multiplier (MT) | | NVC | Multiplier (MT) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Bit_Rate | | Bit_Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The valid Signal Type values defined in [RFC4328] are updated to be: Signal Type: 8 bits
As defined in [RFC4328] Section 3.2.1, with the following
additional values:
Value Type Value Type
----- ---- ----- ----
0 Not significant 4 ODU4 (i.e., 100 Gbps)
1 ODU1 (i.e., 2.5 Gbps) 9 OCh at 100 Gbps
2 ODU2 (i.e., 10 Gbps) 10 ODU0 (i.e., 1.25 Gbps)
3 ODU3 (i.e., 40 Gbps) 11 ODU2e (i.e., 10Gbps for FC1200 and GE LAN)
4 ODU4 (i.e., 100 Gbps) 12~19 Reserved (for future use)
5 Reserved (for future use) 20 ODUflex(CBR) (i.e., 1.25*N Gbps)
6 Optical Channel (Och) at 2.5 Gbps 21 ODUflex(Generic Framing Procedure-Framed (GFP-F)),
7 OCh at 10 Gbps resizable (i.e., 1.25*N Gbps)
8 OCh at 40 Gbps 22 ODUflex(GFP-F), non resizable (i.e., 1.25*N Gbps)
9 OCh at 100 Gbps 23~255 Reserved (for future use)
10 ODU0 (i.e., 1.25 Gbps)
11 ODU2e (i.e., 10Gbps for FC1200 and GE LAN)
12~19 Reserved (for future use)
20 ODUflex(CBR) (i.e., 1.25*N Gbps)
21 ODUflex(Generic Framing Procedure-Framed (GFP-F)),
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)
In case of ODUflex(CBR), the Bit_Rate and Tolerance fields MUST be N: 8 bits
used together to represent the actual bandwidth of ODUflex, where:
- The Bit_Rate field indicates the nominal bit rate of ODUflex(CBR) In case of ODUflex(GFP) signal types (both resizable and non
expressed in bytes per second, encoded as a 32-bit IEEE single- resizable), this field indicates the number of tributary slots
precision floating-point number (referring to [RFC4506] and needed for the requested ODUflex(GFP). For other signal types,
[IEEE]). The value contained in the Bit Rate field has to keep this field is not necessary and MUST be set to 0.
into account both 239/238 factor and the Transcoding factor.
- The Tolerance field indicates the bit rate tolerance (part per NVC: 16 bits
million, ppm) of the ODUflex(CBR) encoded as an unsigned integer,
which MUST be bounded in 0~100ppm.
For example, for an ODUflex(CBR) service with Bit_Rate = 2.5Gbps and As defined in [RFC4328] Section 3.2.3.
Tolerance = 100ppm, the actual bandwidth of the ODUflex is:
2.5Gbps * (1 +/- 100ppm) Multiplier (MT): 16 bits
In case of ODUflex(GFP), the Bit_Rate field is used to indicate the As defined in [RFC4328] Section 3.2.4.
nominal bit rate of the ODUflex(GFP), which implies the number of
tributary slots requested for the ODUflex(GFP). Since the tolerance
of ODUflex(GFP) makes no sense on tributary slot resource
reservation, the Tolerance field for ODUflex(GFP) is not necessary
and MUST be filled with 0.
In case of other ODUk signal types, the Bit_Rate and Tolerance fields Bit_Rate: 32 bits
are not necessary and MUST be set to 0.
The usage of the NVC and Multiplier (MT) fields are the same as In case of ODUflex(CBR) signal type, this field indicates the
[RFC4328]. nominal bit rate of ODUflex(CBR) expressed in bytes per second,
encoded as a 32-bit IEEE single-precision floating-point number
(referring to [RFC4506] and [IEEE]). The value contained in the
Bit Rate field has to keep into account both 239/238 factor and
the Transcoding factor. For other signal types, this field is not
necessary and MUST be set to 0.
Note that the error process on the traffic parameters MUST follow the Tolerance: 16 bits
rules defined in Section 6 of [RFC4328].
In case of ODUflex(CBR) signal type, this field indicates the bit
rate tolerance (part per million, ppm) of the ODUflex(CBR)
encoded as an unsigned integer, which MUST be bounded in
0~100ppm. For other signal types, this field is not necessary and
MUST be set to 0.
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 and Tolerance in In case of ODUflex(CBR), the information of Bit_Rate and Tolerance in
the ODUflex traffic parameters MUST be used to determine the total the ODUflex Traffic Parameters MUST be used to determine the actual
number of tributary slots N in the HO ODUk link to be reserved. Here: bandwidth of ODUflex(CBR) (i.e., Bit_Rate * (1 +/- Tolerance)).
Therefore the total number of tributary slots N in the HO ODUk link
can be reserved correctly. Here:
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 8, line 47 skipping to change at page 8, line 41
The ODTUk.ts (Optical channel Data Tributary Unit k with ts tributary The ODTUk.ts (Optical channel Data Tributary Unit k with ts tributary
slots) nominal bit rate is the nominal bit rate of the tributary slot slots) nominal bit rate is the nominal bit rate of the tributary slot
of ODUk, as shown in Table 1 (referring to Table 7-7 of [G709-2012]). of ODUk, as shown in Table 1 (referring to Table 7-7 of [G709-2012]).
Table 1 - Actual TS bit rate of ODUk (in Kbps) Table 1 - Actual TS bit rate of ODUk (in Kbps)
ODUk.ts Minimum Nominal Maximum ODUk.ts Minimum Nominal Maximum
----------------------------------------------------------- -----------------------------------------------------------
ODU2.ts 1,249,384.632 1,249,409.620 1,249,434.608 ODU2.ts 1,249,384.632 1,249,409.620 1,249,434.608
ODU3.ts 1,254,678.635 1,254,703.729 1,254,728.823 ODU3.ts 1,254,678.635 1,254,703.729 1,254,728.823
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
Therefore, a node receiving a PATH message containing ODUflex(CBR) Therefore, a node receiving a PATH message containing ODUflex(CBR)
nominal bit rate and tolerance can allocate precise number of nominal bit rate and tolerance can allocate precise number of
tributary slots and set up the cross-connection for the ODUflex tributary slots and set up the cross-connection for the ODUflex
service. 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 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. requesting a bandwidth of (2.5Gbps, +/-100ppm) from node A to node C.
In other words, the ODUflex traffic parameters indicate that Signal In other words, the ODUflex Traffic Parameters indicate that Signal
Type is 20 (ODUflex(CBR)), Bit_Rate is 2.5Gbps and Tolerance is Type is 20 (ODUflex(CBR)), Bit_Rate is 2.5Gbps and Tolerance is
100ppm. 100ppm.
+-----+ +---------+ +-----+ +-----+ +---------+ +-----+
| +-------------+ +-----+ +-------------+ | | +-------------+ +-----+ +-------------+ |
| +=============+\| ODU |/+=============+ | | +=============+\| ODU |/+=============+ |
| +=============+/| flex+-+=============+ | | +=============+/| flex+-+=============+ |
| +-------------+ | |\+=============+ | | +-------------+ | |\+=============+ |
| +-------------+ +-----+ +-------------+ | | +-------------+ +-----+ +-------------+ |
| | | | | | | | | | | |
skipping to change at page 10, line 33 skipping to change at page 10, line 22
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 TS, 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 TS, 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 TS, 33<=N<=80 | N * ODU4.ts | +/-100 ppm
According to this table, the Bit_Rate field for ODUflex(GFP) MUST Since each hop on an ODUflex(GFP) LSP requires the same number of
equal to one of the 80 values listed below: tributary slots (i.e., "N" in Table 2), the Traffic Parameters for
ODUflex(GFP) just need to carry "N" value to indicate the number of
TSs rather than carrying the Bit_Rate and Tolorance.
1 * ODU2.ts; 2 * ODU2.ts; ...; 8 * ODU2.ts; 5.3. Notification on Errors of OTN-TDM Traffic Parameters
9 * ODU3.ts; 10 * ODU3.ts, ...; 32 * ODU3.ts;
33 * ODU4.ts; 34 * ODU4.ts; ...; 80 * ODU4.ts.
In this way, the number of required tributary slots for the There is no Adspec associated with the OTN-TDM SENDER_TSPEC. Either
ODUflex(GFP) (i.e., the value of "n" in Table 2) can be deduced from the Adspec is omitted or an Int-serv Adspec with the Default General
the Bit_Rate field. Characterization Parameters and Guaranteed Service fragment is used,
see [RFC2210].
For a particular sender in a session, the contents of the FLOWSPEC
object received in a Resv message SHOULD be identical to the contents
of the SENDER_TSPEC object received in the corresponding Path
message. If the objects do not match, a ResvErr message with a
"Traffic Control Error/Bad Flowspec value" error SHOULD be generated.
Intermediate and egress nodes MUST verify that the node itself, and
the interfaces on which the LSP will be established, can support the
requested Signal Type, NVC, Tolerance and Bit_Rate values. If the
requested value(s) cannot be supported, the receiver node MUST
generate a PathErr message with a "Traffic Control Error/Service
unsupported" indication (see [RFC2205]).
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
Tspec value" indication (see [RFC2205]).
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
"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 format for that MUST be used
with the OTN-TDM Switching Type: with the OTN-TDM Switching Type:
skipping to change at page 11, line 29 skipping to change at page 11, line 33
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 is used to indicate how the LO ODUj The OTN-TDM Generalized Label is used to indicate how the LO ODUj
signal is multiplexed into the HO ODUk link. Note that the LO OUDj signal is multiplexed into the HO ODUk link. Note that the LO OUDj
signal type is indicated by traffic parameters, while the type of HO signal type is indicated by Traffic Parameters, while the type of HO
ODUk link is identified by the selected interface carried in the ODUk link is identified by the selected interface carried in 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
skipping to change at page 13, line 22 skipping to change at page 13, line 26
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.
6.2. Procedures 6.2. Procedures
When a node receives a generalized label request for setting up an The ingress node MUST generate a Path message and specify the OTN-TDM
ODUj LSP from its upstream neighbor node, the node MUST generate an Switching Type and corresponding G-PID in the Generalized Label
OTN-TDM label according to the signal type of the requested LSP and Request object, which MUST be processed as defined in [RFC3473].
the free resources (i.e., free tributary slots of ODUk) that will be
reserved for the LSP, and send the label to its upstream neighbor
node.
In case of ODUj to ODUk multiplexing, the node MUST firstly determine The ingress node of an LSP MAY include label ERO (Explicit Route
the size of the Bit Map field according to the signal type and the Object) to indicate the label in each hops along the path. Note that
tributary slot type of ODUk, and then set the bits to 1 in the Bit the TPN in the label ERO subobject MAY not be assigned by the ingress
Map field corresponding to the reserved tributary slots. The node node. In this case, the node MUST assign a valid TPN value and then
MUST also assign a valid TPN, which MUST NOT collide with other TPN put this value into TPN field of the label object when receiving a
value used by existing LO ODU connections in the selected HO ODU Path message.
link, and configure the Expected MSI (ExMSI) using this TPN. Then,
the assigned TPN MUST be filled into the label.
In case of ODUk to OTUk mapping, TPN field MUST be set to 0. Bit Map In order to create bidirectional LSP, the ingress node and upstream
information is not REQUIRED and MUST NOT be included, so Length field node MUST generate an Upstream Label on the out outgoing interface to
MUST be set to 0 as well. indicate the reserved TSs of ODUk and the assigned TPN value in the
upstream direction. This Upstream Label is sent to the downstream
node via Path massage for upstream resource reservation.
The node receiving a OTN-TDM generalized label MUST firstly identify The ingress node or upstream node MAY generate Label Set to indicate
which ODU signal type is multiplexed or mapped into which ODU signal which labels on the outgoing interface in the downstream direction
type accordingly to the traffic parameters and the IF_ID RSVP_HOP are acceptable. The downstream node will restrict its choice of
Object in the received message. labels, i.e., TS resource and TPN value, to one which is in the Label
Set.
In case of ODUj to ODUk multiplexing, the node MUST retrieve the The ingress node or upstream node MAY also generate Suggested Label
reserved tributary slots in the ODUk by its downstream neighbor node to indicate the preference of TS resource and TPN value on the
according to the position of the bits that are set to 1 in the Bit outgoing interface in the downstream direction. The downstream node
Map field. The node determines the TS type (according to the total TS is not REQUIRED to use the Suggested Label and MAY use another label
number of the ODUk, or pre-configured TS type), so that the node, based on local decision and send it to the upstream node, as
based on the TS type, can multiplex the ODUj into the ODUk. The node described in [RFC3473].
MUST also retrieve the TPN value assigned by its downstream neighbor
node from the label, and fill the TPN into the related MSI byte(s) in
the OPUk overhead in the data plane, so that the downstream neighbor
node can check whether the TPN received from the data plane is
consistent with the ExMSI and determine whether there is any mismatch
defect.
Note that the Length field in the label format MAY be used to When an upstream node receives a Resv message containing an LABEL
indicate the TS type of the HO ODUk (i.e., TS granularity at 1.25Gbps object with an OTN-TDM label, it MUST firstly identify which ODU
or 2.5Gbps) since the HO ODUk type can be known from IF_ID RSVP_HOP signal type is multiplexed or mapped into which ODU signal type
Object. In some cases when there is no Link Management Protocol (LMP) accordingly to the Traffic Parameters and the IF_ID RSVP_HOP Object
or routing to make the two end points of the link to know the TSG, in the received message.
the TSG information used by another end can be deduced from the label
format. For example, for HO ODU2 link, the value of the length filed
will be 4 or 8, which indicates the TS granularity is 2.5Gbps or
1.25Gbps, respectively.
In case of ODUk to OTUk mapping, the size of Bit Map field MUST be 0 - In case of ODUj to ODUk multiplexing, the node MUST retrieve the
and no additional procedure is needed. reserved tributary slots in the ODUk by its downstream neighbor
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 total TS number of the ODUk, or pre-configured TS type), so
that the node can multiplex the ODUj into the ODUk based on the TS
type. The node MUST also retrieve the TPN value assigned by its
downstream neighbor node from the label, and fill the TPN into the
related MSI byte(s) in the OPUk overhead in the data plane, so
that the downstream neighbor node can check whether the TPN
received from the data plane is consistent with the ExMSI and
determine whether there is any mismatch defect. Note that the
Length field in the label format MAY be used to indicate the TS
type of the HO ODUk (i.e., TS granularity at 1.25Gbps or 2.5Gbps)
since the HO ODUk type can be known from IF_ID RSVP_HOP Object. In
some cases when there is no Link Management Protocol (LMP) or
routing to make the two end points of the link to know the TSG,
the TSG information used by another end can be deduced from the
label format. For example, for HO ODU2 link, the value of the
length filed will be 4 or 8, which indicates the TS granularity is
2.5Gbps or 1.25Gbps, respectively.
In order to create bidirectional LSP, an upstream node MUST generate - In case of ODUk to OTUk mapping, the size of Bit Map field MUST be
an Upstream Label on the out outgoing interface to indicate the 0 and no additional procedure is needed.
reserved TSs of ODUk and the assigned TPN value in the upstream
direction. This Upstream Label is sent to the downstream node via
Path massage for upstream resource reservation.
The upstream node MAY generate Label Set to indicate which labels on When a downstream node or egress node receives a Path message
the outgoing interface in the downstream direction are acceptable. containing Generalized Label Request object for setting up an ODUj
The downstream node will restrict its choice of labels, i.e., TS LSP from its upstream neighbor node, the node MUST generate an OTN-
resource and TPN value, to one which is in the Label Set. 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
reserved for the LSP, and send the label to its upstream neighbor
node.
The upstream node MAY also generate Suggested Label to indicate the - In case of ODUj to ODUk multiplexing, the node MUST firstly
preference of TS resource and TPN value on the outgoing interface in determine the size of the Bit Map field according to the signal
the downstream direction. The downstream node is not REQUIRED to use type and the tributary slot type of ODUk, and then set the bits to
the Suggested Label and MAY use another label based on local decision 1 in the Bit Map field corresponding to the reserved tributary
and send it to the upstream node, as described in [RFC3473]. slots. The node MUST also assign a valid TPN, which MUST NOT
collide with other TPN value used by existing LO ODU connections
in the selected HO ODU link, and configure the Expected MSI
(ExMSI) using this TPN. Then, the assigned TPN MUST be filled into
the label.
The ingress node of an LSP MAY include label ERO to indicate the - In case of ODUk to OTUk mapping, TPN field MUST be set to 0. Bit
label in each hops along the path. Note that the TPN in the label ERO Map information is not REQUIRED and MUST NOT be included, so
(Explicit Route Object) subobject MAY not be assigned by the ingress Length field MUST be set to 0 as well.
node. In this case, the node MUST assign a valid TPN value and then
put this value into TPN field of the label object when receiving a
Path message.
6.2.1. Notification on Label Error 6.2.1. Notification on Label Error
When receiving an OTN-TDM label from the neighbor node, the node MUST When an upstream node receives a Resv message containing an LABEL
check whether the label is acceptable. An error message containing an object with an OTN-TDM label, the node MUST verify if the label is
"Unacceptable label value" indication ([RFC3209]) MUST be sent if one acceptable. If the label is not acceptable, the node MUST generate a
of the following cases occurs: ResvErr message with a "Routing problem/Unacceptable label value"
indication. Per [RFC3473], the generated ResvErr message MAY include
an ACCEPTABLE_LABEL_SET object. With the exception of label
semantics, downstream node processing a received ResvErr messages and
of ACCEPTABLE_LABEL_SET objects is not modified by this document.
Similarly, when a downstream node receives a Path message containing
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
MUST generate a PathErr message with a "Routing problem/Unacceptable
label value" indication. Per [RFC3473], the generated ResvErr message
MAY include an ACCEPTABLE_LABEL_SET object. With the exception of
label semantics, downstream node processing received PathErr messages
and of ACCEPTABLE_LABEL_SET objects is not modified by this document.
A received label SHALL be considered unacceptable when one of the
following cases occurs:
- 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
the 1.25Gbps TS granularity; the 1.25Gbps TS granularity;
- The label includes an invalid TPN value that breaks the TPN - The label includes an invalid TPN value that breaks the TPN
assignment rules; assignment rules;
skipping to change at page 15, line 41 skipping to change at page 16, line 22
In case of multiplexed virtually concatenated signals (NVC > 1), the In case of multiplexed virtually concatenated signals (NVC > 1), the
first label MUST indicate the components of the first virtually first label MUST indicate the components of the first virtually
concatenated signal; the second label MUST indicate the components of concatenated signal; the second label MUST indicate the components of
the second virtually concatenated signal; and so on. In case of the second virtually concatenated signal; and so on. In case of
multiplication of multiplexed virtually concatenated signals (MT > multiplication of multiplexed virtually concatenated signals (MT >
1), the first label MUST indicate the components of the first 1), the first label MUST indicate the components of the first
multiplexed virtually concatenated signal; the second label MUST multiplexed virtually concatenated signal; the second label MUST
indicate components of the second multiplexed virtually concatenated indicate components of the second multiplexed virtually concatenated
signal; and so on. signal; and so on.
In case of Multiple LSPs style, multiple control plane LSPs are Support for Virtual Concatenation of ODU1, ODU2 and ODU3 signal
created with a single VCG and the VCAT Call SHOULD be used to types, as defined by [RFC6344], is not modified by this document.
associate the control plane LSPs. The procedures are similar to Virtual Concatenation of other signal types is not supported by
section 6 of [RFC6344]. [G709-2012].
Multiplier (MT) usage is as defined in [RFC6344] and [RFC4328].
6.4. Examples 6.4. Examples
The following examples are given in order to illustrate the label The following examples are given in order to illustrate the label
format described in Section 5.1 of this document. format described in Section 6.1 of this document.
(1) ODUk into OTUk mapping: (1) ODUk into OTUk mapping:
In such conditions, the downstream node along an LSP returns a label In such conditions, the downstream node along an LSP returns a label
indicating that the ODUk (k=1, 2, 3, 4) is directly mapped into the indicating that the ODUk (k=1, 2, 3, 4) is directly mapped into the
corresponding OTUk. The following example label indicates an ODU1 corresponding OTUk. The following example label indicates an ODU1
mapped into OTU1. mapped into OTU1.
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
skipping to change at page 16, line 29 skipping to change at page 17, line 12
into several tributary slots of OPUk and then mapped into OTUk. Some into several tributary slots of OPUk and then mapped into OTUk. Some
instances are shown as follow: instances are shown as follow:
- ODU0 into ODU2 Multiplexing: - ODU0 into ODU2 Multiplexing:
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| Padded 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 TS 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| Padded 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 TS in ODU2 (i.e., the
type of the tributary slot is 1.25Gbps), and the TPN value is 1. 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| Padded 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 TS 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
skipping to change at page 17, line 38 skipping to change at page 18, line 25
which is still applicable for triggering the ODUflex (GFP) adjustment which is still applicable for triggering the ODUflex (GFP) adjustment
procedure in data plane. procedure in data plane.
Note that the SE style MUST be used at the beginning when creating a Note that the SE style MUST be used at the beginning when creating a
resizable ODUflex connection (Signal Type = 21). Otherwise an error resizable ODUflex connection (Signal Type = 21). Otherwise an error
with Error Code "Conflicting reservation style" MUST be generated with Error Code "Conflicting reservation style" MUST be generated
when performing bandwidth adjustment. when performing bandwidth adjustment.
- Bandwidth increasing - Bandwidth increasing
In order to increase the bandwidth of an ODUflex (GFP) For the ingress node, in order to increase the bandwidth of an
connection, a Path message with SE style (keeping Tunnel ID ODUflex (GFP) connection, a Path message with SE style (keeping
unchanged and assigning a new LSP ID) MUST be sent along the Tunnel ID unchanged and assigning a new LSP ID) MUST be sent
path. along the path.
A downstream node compares the old Traffic Parameters (stored
locally) with the new one carried in the Path message, to
determine the number of TS to be added. After choosing and
reserving new free TS, the downstream node MUST send back a Resv
message carrying both the old and new LABEL Objects in the SE
flow descriptor, so that its upstream neighbor can determine
which TS are added. And the LCR protocol between each pair of
neighbor nodes MUST be triggered.
On the source node, the BWR protocol will be triggered by the The ingress node will trigger the BWR protocol when successful
successful completion of LCR protocols on every hop after Resv completion of LCR protocols on every hop after Resv message is
message is processed. On success of BWR, the source node MUST processed. On success of BWR, the ingress node SHOULD send a
send a PathTear message to delete the old control state (i.e., PathTear message to delete the old control state (i.e., the
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
the old Traffic Parameters (stored locally) with the new one
carried in the Path message, to determine the number of TS to be
added. After choosing and reserving new free TS, the downstream
node MUST send back a Resv message carrying both the old and new
LABEL Objects in the SE flow descriptor.
An upstream neighbor receiving Resv message with SE flow
descriptor MUST determine which TS are added and trigger the LCR
protocol between itself and its downstream neighbor node.
- Bandwidth decreasing - Bandwidth decreasing
The SE style SHOULD also be used for ODUflex bandwidth For the ingress node, a Path message with SE style SHOULD also be
decreasing. For each pair of neighbor nodes, the sending and sent for ODUflex bandwidth decreasing.
receiving Resv message with old and new LABEL Objects will
trigger the first step of LCR between them to perform LCR
handshake. On the source node, the BWR protocol will be triggered
by the successful completion of LCR handshake on every hop after
Resv message is 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.
Similarly, after completion of bandwidth decreasing, a ResvErr The ingress node will trigger the BWR protocol when successful
message SHOULD be sent to tear down the old control state. completion of LCR handshake on every hop after Resv message is
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. After completion of bandwidth decreasing, the ingress
node SHOULD send a ResvErr message to tear down the old control
state.
A downstream node receiving Path message with SE style compares
the old Traffic Parameters with the new one carried in the Path
message to determine the number of TS to be decreased. After
choosing TSs to be decreased, the downstream node MUST send back
a Resv message carrying both the old and new LABEL Objects in the
SE flow descriptor.
An upstream neighbor receiving Resv message with SE flow
descriptor MUST determine which TS are decreased and trigger the
first step of LCR protocol (i.e., LCR handshake) 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 19, line 21 skipping to change at page 20, line 17
This document introduces no new security considerations to the This document introduces no new security considerations to the
existing GMPLS signaling protocols. Referring to [RFC3473] and existing GMPLS signaling protocols. Referring to [RFC3473] and
[RFC4328], further details of the specific security measures are [RFC4328], further details of the specific security measures are
provided. Additionally, [RFC5920] provides an overview of security provided. Additionally, [RFC5920] provides an overview of security
vulnerabilities and protection mechanisms for the GMPLS control vulnerabilities and protection mechanisms for the GMPLS control
plane. plane.
10. IANA Considerations 10. IANA Considerations
Three RSVP C-Types are defined for OTN-TDM Traffic Parameters and Three RSVP C-Types are defined for OTN-TDM Traffic Parameters and
OTN-TDM Generalized Label in this document. OTN-TDM Generalized Label in this document:
http://www.iana.org/assignments/rsvp-parameters
- OTN-TDM SENDER_TSPEC and FLOWSPEC objects: - OTN-TDM SENDER_TSPEC and FLOWSPEC objects:
o OTN-TDM SENDER_TSPEC Object: Class = 12, C-Type = 7 (see o OTN-TDM SENDER_TSPEC Object: Class = 12, C-Type = 7 (see
Section 4) Section 5)
o OTN-TDM FLOWSPEC Object: Class = 9, C-Type = 7 (see Section 4) o OTN-TDM FLOWSPEC Object: Class = 9, C-Type = 7 (see Section 5)
- OTN-TDM Generalized Label Object: - OTN-TDM Generalized Label Object:
o OTN-TDM Generalized Label Object: Class = 16, C-Type = 2 (see o OTN-TDM Generalized Label Object: Class = 16, C-Type = 2 (see
Section 5.1) Section 6.1)
IANA will also track the code-point spaces extended and/or updated by IANA maintains the "Generalized Multi-Protocol Label Switching
this document. The Generalized PID has been added in the newly (GMPLS) Signaling Parameters" registry (see
requested registry entry: http://www.iana.org/assignments/gmpls-sig-parameters). "Generalized
PIDs (G-PID)" subregistry is included in this registry, which will be
extended and updated by this document as below:
- Generalized PID (G-PID): - Generalized PID (G-PID):
Name: G-PID Name: G-PID
Format: 16-bit number Format: 16-bit number
Values: Values:
[0..31, 36..46] defined in [RFC3471] [0..31, 36..46] defined in [RFC3471]
[32] defined in [RFC3471] and updated by Section 4
[32] defined in [RFC3471] and updated by Section 3
[33..35] defined in [RFC3471] and updated by [RFC4328] [33..35] defined in [RFC3471] and updated by [RFC4328]
[47, 49..52] defined in [RFC4328] and updated by Section 3 [47, 49..52] defined in [RFC4328] and updated by Section 4
[48, 53..58] defined in [RFC4328] [48, 53..58] defined in [RFC4328]
[59..63] defined in Section 3 [59..63] defined in Section 4 of this document
Allocation Policy (as defined in [RFC4328]): Allocation Policy (as defined in [RFC4328]):
[0..31743] Assigned by IANA via IETF Standards Track RFC [0..31743] Assigned by IANA via IETF Standards Track RFC
Action. Action.
[31744..32767] Assigned temporarily for Experimental Usage [31744..32767] Assigned temporarily for Experimental Usage
[32768..65535] Not assigned. Before any assignments can be [32768..65535] Not assigned. Before any assignments can be
made in this range, there MUST be a Standards made in this range, there MUST be a Standards
Track RFC that specifies IANA Considerations Track RFC that specifies IANA Considerations
that covers the range being assigned. that covers the range being assigned.
"Signal Type" subregistry to the "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling Parameters" will be defined by this
document as below:
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) [this document]
5 Reserved (for future use) [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 [this document]
10 ODU0 (i.e., 1.25 Gbps) [this document]
11 ODU2e (i.e., 10Gbps for FC1200 [this document]
and GE LAN)
12~19 Reserved (for future use) [this document]
20 ODUflex(CBR) (i.e., 1.25*N Gbps) [this document]
21 ODUflex(GFP-F), resizable [this document]
(i.e., 1.25*N Gbps)
22 ODUflex(GFP-F), non resizable [this document]
(i.e., 1.25*N Gbps)
23~255 Reserved (for future use) [this document]
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.
Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1
Functional Specification", RFC 2205, September 1997.
[RFC2210] Wroclawski, J., "The Use of RSVP with IETF Integrated
Services", RFC 2210, September 1997.
[RFC3209] D. Awduche et al, "RSVP-TE: Extensions to RSVP for LSP [RFC3209] D. Awduche et al, "RSVP-TE: Extensions to RSVP for LSP
Tunnels", RFC3209, December 2001. Tunnels", RFC3209, December 2001.
[RFC3471] Berger, L., Editor, "Generalized Multi-Protocol Label [RFC3471] Berger, L., Editor, "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling Functional Description", RFC Switching (GMPLS) Signaling Functional Description", RFC
3471, January 2003. 3471, January 2003.
[RFC3473] L. Berger, Ed., "Generalized Multi-Protocol Label Switching [RFC3473] L. Berger, Ed., "Generalized Multi-Protocol Label Switching
(GMPLS) Signaling Resource ReserVation Protocol-Traffic (GMPLS) Signaling Resource ReserVation Protocol-Traffic
Engineering (RSVP-TE) Extensions", RFC 3473, January 2003. Engineering (RSVP-TE) Extensions", RFC 3473, January 2003.
skipping to change at page 21, line 7 skipping to change at page 22, line 41
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 11.2. Informative References
[OTN-FWK] Fatai Zhang et al, "Framework for GMPLS and PCE Control of [OTN-FWK] Fatai Zhang et al, "Framework for GMPLS and PCE Control of
G.709 Optical Transport Networks", Work in Progress: draft- G.709 Optical Transport Networks", Work in Progress: draft-
ietf-ccamp-gmpls-g709-framework, November 2012. ietf-ccamp-gmpls-g709-framework, November 2012.
[OTN-INFO] S. Belotti et al, "Information model for G.709 Optical [OTN-INFO] S. Belotti et al, "Information model for G.709 Optical
Transport Networks (OTN)", Work in Progress: draft-ietf- Transport Networks (OTN)", Work in Progress: draft-ietf-
ccamp-otn-g709-info-model, November 2012. ccamp-otn-g709-info-model, January 2013.
[OTN-OSPF] D. Ceccarelli et al, "Traffic Engineering Extensions to [OTN-OSPF] D. Ceccarelli et al, "Traffic Engineering Extensions to
OSPF for Generalized MPLS (GMPLS) Control of Evolving G.709 OSPF for Generalized MPLS (GMPLS) Control of Evolving G.709
OTN Networks", Work in Progress: draft-ietf-ccamp-gmpls- OTN Networks", Work in Progress: draft-ietf-ccamp-gmpls-
ospf-g709v3, November 2012. ospf-g709v3, January 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.
[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 [RFC5920] Fang, L., Ed., "Security Framework for MPLS and GMPLS
Networks", RFC5920, July 2010. 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.
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
skipping to change at page 26, line 7 skipping to change at page 27, line 32
on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
WARRANTY THAT THE USE OF THE INFORMATION THEREIN WILL NOT INFRINGE WARRANTY THAT THE USE OF THE INFORMATION THEREIN WILL NOT INFRINGE
ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. FOR A PARTICULAR PURPOSE.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
 End of changes. 83 change blocks. 
222 lines changed or deleted 317 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/