draft-ietf-ccamp-gmpls-signaling-g709v3-11.txt   draft-ietf-ccamp-gmpls-signaling-g709v3-12.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: January 02, 2014 July 02, 2013 Expires: March 13, 2014 September 13, 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-11.txt draft-ietf-ccamp-gmpls-signaling-g709v3-12.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 January 02, 2014. This Internet-Draft will expire on March 13, 2014.
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 the ODU-related portions of RFC4328 to This document updates the ODU-related portions of RFC4328 to provide
to provide the extensions to the Generalized Multi-Protocol Label the extensions to the Generalized Multi-Protocol Label Switching
Switching (GMPLS) signaling to control the full set of OTN features (GMPLS) signaling to control the full set of OTN features including
including ODU0, ODU4, ODU2e and ODUflex. ODU0, 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 ...... 7 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 .... 11 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 .............................................. 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. Operations, Administration and Maintenance (OAM) Considerations19
9. Security Considerations ...................................... 20 9. Control Plane Backward Compatibility Considerations........... 20
10. IANA Considerations.......................................... 20 10. Security Considerations .................................... 20
11. References .................................................. 22 11. IANA Considerations.......................................... 20
11.1. Normative References ................................... 22 12. References .................................................. 22
11.2. Informative References ................................. 23 12.1. Normative References ................................... 22
12. Contributors ................................................ 24 12.2. Informative References ................. ............... 23
13. Authors' Addresses .......................................... 24 13. Contributors ................................................ 24
14. Acknowledgment .............................................. 26 14. Authors' Addresses .......................................... 26
15. Acknowledgment .............................................. 27
1. Introduction 1. Introduction
With the evolution and deployment of OTN technology, it is necessary With the evolution and deployment of Optical Transport Network (OTN)
that appropriate enhanced control technology support be provided for technology, it is necessary that appropriate enhanced control
[G709-2012]. technology support be provided for [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 the ODU-related portions of [RFC4328] to provide Resource updates the ODU-related portions of [RFC4328] to provide Resource
ReserVation Protocol-Traffic Engineering (RSVP-TE) extensions to support ReserVation Protocol-Traffic Engineering (RSVP-TE) extensions to
of control for [G709-2012]. support of 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
and ODUflex containers are specified in [G709-2012]. The and ODUflex containers are specified in [G709-2012]. The
corresponding new Signal Types are summarized below: corresponding new Signal Types are summarized below:
- 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 (i.e., 1.25Gbps) is also described A new Tributary Slot granularity (i.e., 1.25Gbps) is also described
in [G709-2012]. Thus, there are now two TS granularities for the in [G709-2012]. Thus, there are now two Tributary Slot (TS)
foundation OTN ODU1, ODU2 and ODU3 containers. The TS granularity at granularities for the foundation OTN ODU1, ODU2 and ODU3 containers.
2.5Gbps is used on legacy interfaces while the new 1.25Gbps is used The TS granularity at 2.5Gbps is used on the legacy interfaces while
on the new interfaces. the new 1.25Gbps 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), [G709-2012] encompasses the multiplexing of ODUj (j = 0, 1, 2, 4), [G709-2012] encompasses the multiplexing of ODUj (j = 0, 1, 2,
2e, 3, flex) into an ODUk (k > j), as described in Section 3.1.2 of 2e, 3, flex) into an ODUk (k > j), as described in 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].
skipping to change at page 5, line 21 skipping to change at page 5, line 16
40Gbps) via 2.5Gbps TS granularity. 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 TS granularity, 2.5G TS granularity or any one of them via 1.25G TS granularity, 2.5G TS granularity or ODU-any defined
(i.e., TS granularity Auto_Negotiation is enabled). Since the G-PID below. Since the G-PID type "ODUk" defined in [RFC4328] is only used
type "ODUk" defined in [RFC4328] is only used for 2.5Gbps TS for 2.5Gbps TS granularity, two new G-PID types are defined as
granularity, two new G-PID types are defined as follows: 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 TS granularity. 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 TS granularity (i.e., the Gbps via 1.25 or 2.5Gbps TS granularity (i.e., the
fallback procedure is enabled and the default value of fallback procedure is enabled and the default value of
1.25Gbps TS granularity can be fallen back to 2.5Gbps 1.25Gbps TS granularity can be fallen back to 2.5Gbps
if needed). if needed).
skipping to change at page 7, line 8 skipping to change at page 6, line 49
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 OTN-TDM FLOWSPEC objects. The objects in the OTN-TDM SENDER_TSPEC object in the Path message and the OTN-
have the following class and type: TDM FLOWSPEC object in the Resv message. The objects 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 7, line 45 skipping to change at page 7, line 40
9 OCh at 100Gbps 9 OCh at 100Gbps
10 ODU0 (i.e., 1.25Gbps) 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 (Number of Virtual Components): 16 bits
As defined in [RFC4328] Section 3.2.3. This field MUST be set to As defined in [RFC4328] Section 3.2.3. This field MUST be set to
0 for ODUflex Signal Types. 0 for ODUflex Signal Types.
Multiplier (MT): 16 bits Multiplier (MT): 16 bits
As defined in [RFC4328] Section 3.2.4. This field MUST be set to As defined in [RFC4328] Section 3.2.4. This field MUST be set to
1 for ODUflex Signal Types. 1 for ODUflex Signal Types.
Bit_Rate: 32 bits Bit_Rate: 32 bits
skipping to change at page 10, line 35 skipping to change at page 10, line 31
N2 = ceiling (2.5Gbps * (1 + 100ppm) / 1,249,384.632 Kbps) = 3 N2 = ceiling (2.5Gbps * (1 + 100ppm) / 1,249,384.632 Kbps) = 3
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 TSs, 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 TSs, 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 TSs, 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 be
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 object. There is no Adspec associated with the OTN-TDM SENDER_TSPEC object.
Either the Adspec is omitted or an Int-serv Adspec with the Default Either the Adspec is omitted or an Int-serv Adspec with the Default
skipping to change at page 12, line 4 skipping to change at page 11, line 46
used 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 object is used to indicate how the LO
ODUj signal is multiplexed into the HO ODUk link. Note that the LO ODUj signal is multiplexed into the HO ODUk link. Note that the LO
OUDj signal type is indicated by Traffic Parameters, while the type OUDj signal type is indicated by Traffic Parameters, while the type
of HO ODUk link is identified by the selected interface carried in of HO ODUk link is identified by the selected interface carried in
the IF_ID RSVP_HOP object. the 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.
- In case of ODUj mapped into OTUk (j=k), the TPN is not needed - In case of ODUj mapped into OTUk (j=k), the TPN is not needed
and this field MUST be set to 0. and this field MUST be set to 0.
Per [G709-2012], The TPN is used to allow for correct demultiplexing Per [G709-2012], The TPN is used to allow for correct demultiplexing
in the data plane. When an LO ODUj is multiplexed into HO ODUk in the data plane. When an LO ODUj is multiplexed into HO ODUk
occupying one or more TSs, a new TPN value is configured at the two occupying one or more TSs, a new TPN value is configured at the two
ends of the HO ODUk link and is put into the related MSI byte(s) in ends of the HO ODUk link and is put into the related MSI byte(s) in
the OPUk overhead at the (traffic) ingress end of the link, so that the OPUk overhead at the (traffic) ingress end of the link, so that
the other end of the link can learn which TS(s) is/are used by the LO the other end of the link can learn which TS(s) is/are used by the LO
ODUj in the data plane. ODUj in the data plane.
skipping to change at page 14, line 13 skipping to change at page 14, line 13
and MUST be ignored on receipt. 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 Switching Type and corresponding G-PID in the
GENERALIZED_LABEL_REQUEST object, which MUST be processed as defined GENERALIZED_LABEL_REQUEST object, which MUST be processed as defined
in [RFC3473]. 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) subobject to indicate the label in each hops along the path.
the TPN in the Label ERO subobject need not be assigned by the Note that the TPN in the Label ERO subobject need not be assigned by
ingress node. In this case, the node MUST assign a valid TPN value the ingress node. When the TPN is assigned by a node, the node MUST
and then put this value into TPN field of the GENERALIZED_LABEL assign a valid TPN value and then put this value into TPN field of
object when receiving a Path message. the GENERALIZED_LABEL 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 object on the out outgoing node MUST generate an UPSTREAM_LABEL Object on the outgoing interface
interface to indicate the reserved TSs of ODUk and the assigned TPN to indicate the reserved TSs of ODUk and the assigned TPN value in
value in the upstream direction. This UPSTREAM_LABEL object is sent the upstream direction. This UPSTREAM_LABEL object is sent to the
to the downstream node via Path massage for upstream resource downstream node via Path massage for upstream resource reservation.
reservation.
The ingress node or upstream node MAY generate LABEL_SET object to The ingress node or upstream node MAY generate LABEL_SET object to
indicate which labels on the outgoing interface in the downstream indicate which labels on the outgoing interface in the downstream
direction are acceptable. The downstream node will restrict its direction are acceptable. The downstream node will restrict its
choice of labels, i.e., TS resource and TPN value, to one which is in choice of labels, i.e., TS resource and TPN value, to one which is in
the LABEL_SET object. 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
object 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 labels 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 a When an upstream node receives a Resv message containing a
GENERALIZED_LABEL object with an OTN-TDM label, it MUST firstly GENERALIZED_LABEL object with an OTN-TDM label, it MUST firstly
identify which ODU Signal Type is multiplexed or mapped into which identify which ODU Signal Type is multiplexed or mapped into which
ODU Signal Type accordingly to the Traffic Parameters and the IF_ID ODU Signal Type according to the Traffic Parameters and the IF_ID
RSVP_HOP object 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 granularity the Bit Map field. The node determines the TS granularity
(according to the total TS number of the ODUk, or pre-configured (according to the total TS number of the ODUk, or pre-configured
TS granularity), so that the node can multiplex the ODUj into the TS granularity), so that the node can multiplex the ODUj into the
ODUk based on the TS granularity. The node MUST also retrieve the ODUk based on the TS granularity. The node MUST also retrieve the
TPN value assigned by its downstream neighbor node from the label, 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 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 in the data plane, so that the downstream neighbor node can check
whether the TPN received from the data plane is consistent with whether the TPN received from the data plane is consistent with
the ExMSI and 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
available resources (i.e., available tributary slots of ODUk) that available resources (i.e., available tributary slots of ODUk) that
will be reserved for the LSP, and send the label to its upstream will be reserved for the LSP, and send the label to its upstream
neighbor 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 When an upstream node receives a Resv message containing a
GENERALIZED_LABEL object with an OTN-TDM label, the node MUST verify GENERALIZED_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 ResvErr message with a "Routing problem/Unacceptable MUST generate a ResvErr message with a "Routing problem/Unacceptable
label value" indication. Per [RFC3473], the generated ResvErr label value" indication. Per [RFC3473], the generated ResvErr
message MAY include an ACCEPTABLE_LABEL_SET object. With the message MAY include an ACCEPTABLE_LABEL_SET object. With the
exception of label semantics, downstream node processing a received exception of label semantics, downstream node processing a received
ResvErr message and of ACCEPTABLE_LABEL_SET object is not modified ResvErr message and of ACCEPTABLE_LABEL_SET object is not modified by
by this document. 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 PathErr 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 a PathErr message label semantics, the upstream nodes processing received a PathErr
and of ACCEPTABLE_LABEL_SET object is not modified by this document. message 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
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;
- The indicated resources (i.e., the number of "1" in the Bit Map - The indicated resources (i.e., the number of "1" in the Bit Map
field) are inconsistent with the Traffic Parameters. field) are inconsistent with the Traffic Parameters.
6.3. Supporting Virtual Concatenation and Multiplication 6.3. Supporting Virtual Concatenation and Multiplication
Per [RFC6344], the Virtual Concatenation Groups (VCGs) can be created Per [RFC6344], the Virtual Concatenation Groups (VCGs) can be created
using Co-Signaled style or Multiple LSPs style. using Co-Signaled style or Multiple LSPs style.
In case of Co-Signaled style, the explicit ordered list of all labels In case of Co-Signaled style, the explicit ordered list of all labels
MUST reflect the order of VCG members, which is similar to [RFC4328]. MUST reflect the order of VCG members, which is similar to [RFC4328].
In case of multiplexed virtually concatenated signals (NVC > 1), the In case of multiplexed virtually concatenated signals (NVC > 1), the
skipping to change at page 19, line 44 skipping to change at page 19, line 44
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 GENERALIZED_LABEL a Resv message carrying both the old and new GENERALIZED_LABEL
objects in the 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(s) is/are decreased and descriptor MUST determine which TS(s) is/are decreased and
trigger the first step of LCR protocol (i.e., LCR handshake) trigger the first step of LCR protocol (i.e., LCR handshake)
between itself and its downstream neighbor node. between itself and its downstream neighbor node.
8. Control Plane Backward Compatibility Considerations 8. Operations, Administration and Maintenance (OAM) Considerations
Regarding OTN OAM configuration, it could be done through either
Network Management Systems (NMS) or GMPLS control plane as defined in
[TDM-OAM]. [RFC4783] SHOULD be used for communication of alarm
information in GMPLS based OTN.
Management Information Base (MIB) may need be extended to read new
information (e.g, OTN-TDM Generalized Label, OTN-TDM SENDER_TSPEC/
FLOWSPEC) from the OTN devices. This is out of scope of this
document.
More information about the management aspects for GMPLS based OTN
refer to Section 5.7 of [OTN-FWK].
9. 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].
o Nodes supporting this document MAY support [RFC4328] signaling. o Nodes supporting this document MAY support [RFC4328] signaling.
o A node supporting both sets of procedures (i.e., [RFC4328] and o A node supporting both sets of procedures (i.e., [RFC4328] and
this document) is not REQUIRED to signal an LSP using both this document) is not REQUIRED to signal an LSP using both
procedures, i.e., to act as a signaling version translator. procedures, i.e., to act as a signaling version translator.
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 10. Security Considerations
This document is a modification to [RFC3473] and [RFC4328], and only This document is a modification to [RFC3473] and [RFC4328], and only
differs in specific information communicated. As such, this document differs in specific information communicated. As such, this document
introduces no new security considerations to the existing GMPLS introduces no new security considerations to the existing GMPLS
signaling protocols. Referring to [RFC3473] and [RFC4328], further signaling protocols. Referring to [RFC3473] and [RFC4328], further
details of the specific security measures are provided. Additionally, details of the specific security measures are provided. Additionally,
[RFC5920] provides an overview of security vulnerabilities and [RFC5920] provides an overview of security vulnerabilities and
protection mechanisms for the GMPLS control plane. protection mechanisms for the GMPLS control plane.
10. IANA Considerations 11. IANA Considerations
Upon approval of this document, IANA will make the following Upon approval of this document, IANA will make the following
assignments in the "Class Types or C-Types 9 FLOWSPEC" and "Class assignments in the "Class Types or C-Types 9 FLOWSPEC" and "Class
Types or C-Types 12 SENDER_TSPEC" section of the "RSVP Parameters" Types or C-Types 12 SENDER_TSPEC" section of the "RSVP Parameters"
registry located at http://www.iana.org/assignments/rsvp- registry located at http://www.iana.org/assignments/rsvp-
parameters/rsvp-parameters.xml. parameters/rsvp-parameters.xml.
Value Description Reference Value Description Reference
7(*) OTN-TDM [This.I-D] 7(*) OTN-TDM [This.I-D]
(*) Suggested value (*) 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.
The new G-PIDs should be shown in the TC MIB managed by IANA at
https://www.iana.org/assignments/ianagmplstc-mib/ianagmplstc-
mib.xhtml.
Value Type Technology Reference Value Type Technology Reference
===== ====================== ========== ===== ====================== ==========
47 G.709 ODU-2.5G G.709 ODUk [RFC4328] 47 G.709 ODU-2.5G G.709 ODUk [RFC4328]
(IANA to update Type field) [This.I-D] (IANA to update Type field) [This.I-D]
56 SBCON/ESCON G.709 ODUk, [RFC4328] 56 SBCON/ESCON G.709 ODUk, [RFC4328]
(IANA to update Type field) Lambda, Fiber [This.I-D] (IANA to update Type field) Lambda, Fiber [This.I-D]
59* Framed GFP G.709 ODUk [This.I-D] 59* Framed GFP G.709 ODUk [This.I-D]
60* STM-1 G.709 ODUk [This.I-D] 60* STM-1 G.709 ODUk [This.I-D]
61* STM-4 G.709 ODUk [This.I-D] 61* STM-4 G.709 ODUk [This.I-D]
skipping to change at page 22, line 17 skipping to change at page 22, line 31
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 New values are to be assigned via Standards Action as defined in
[RFC5226]. [RFC5226].
11. References 12. References
11.1. Normative References 12.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.
[RFC2210] Wroclawski, J., "The Use of RSVP with IETF Integrated [RFC2210] Wroclawski, J., "The Use of RSVP with IETF Integrated
Services", RFC 2210, September 1997. Services", RFC 2210, September 1997.
skipping to change at page 23, line 5 skipping to change at page 23, line 17
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.
[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.
[RFC4506] M. Eisler, Ed., "XDR: External Data Representation
Standard", RFC 4506, May 2006.
[RFC4783] L. Berger, Ed., "GMPLS - Communication of Alarm
Information", RFC 4783, December 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.
[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, July 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
Standard", RFC 4506, May 2006.
[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 12.2. Informative References
[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.
[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, June 2013. ietf-ccamp-gmpls-g709-framework, August 2013.
[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, June 2013. ccamp-otn-g709-info-model, July 2013.
[OTN-OSPF] D. Ceccarelli et al, "Traffic Engineering Extensions to [TDM-OAM] A. Kern, A. Takacs, "GMPLS RSVP-TE Extensions for
OSPF for Generalized MPLS (GMPLS) Control of Evolving G.709 SONET/SDH and OTN OAM Configuration", draft-ietf-ccamp-
OTN Networks", Work in Progress: draft-ietf-ccamp-gmpls- rsvp-te-sdh-otn-oam-ext, Work in Progress.
ospf-g709v3, June 2013.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 13. Contributors
IANA Considerations Section in RFCs", BCP 26, RFC 5226, May
2008.
[RFC5920] Fang, L., Ed., "Security Framework for MPLS and GMPLS Yi Lin
Networks", RFC 5920, July 2010. Huawei Technologies
F3-5-B R&D Center, Huawei Base
Bantian, Longgang District
Shenzhen 518129 P.R.China
Phone: +86-755-28972914
Email: yi.lin@huawei.com
12. Contributors Yunbin Xu
China Academy of Telecommunication Research of MII
11 Yue Tan Nan Jie Beijing, P.R.China
Phone: +86-10-68094134
Email: xuyunbin@mail.ritt.com.cn
Pietro Grandi
Alcatel-Lucent
Optics CTO
Via Trento 30 20059 Vimercate (Milano) Italy
+39 039 6864930
Email: pietro_vittorio.grandi@alcatel-lucent.it
Diego Caviglia
Ericsson
Via A. Negrone 1/A
Genova - Sestri Ponente
Italy
Email: diego.caviglia@ericsson.com
Rajan Rao
Infinera Corporation
169, Java Drive
Sunnyvale, CA-94089
USA
Email: rrao@infinera.com
John E Drake
Juniper
Email: jdrake@juniper.net
Igor Bryskin
Adva Optical
EMail: IBryskin@advaoptical.com
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
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
Email: lyong@ciena.com Email: lyong@ciena.com
Biao Lu, infinera Biao Lu, infinera
Email: blu@infinera.com Email: blu@infinera.com
13. Authors' Addresses 14. Authors' Addresses
Fatai Zhang (editor) Fatai Zhang (editor)
Huawei Technologies Huawei Technologies
F3-5-B R&D Center, Huawei Base F3-5-B R&D Center, Huawei Base
Bantian, Longgang District Bantian, Longgang District
Shenzhen 518129 P.R.China Shenzhen 518129 P.R.China
Phone: +86-755-28972912 Phone: +86-755-28972912
Email: zhangfatai@huawei.com Email: zhangfatai@huawei.com
Guoying Zhang Guoying Zhang
skipping to change at page 25, line 27 skipping to change at page 27, line 9
Genova - Sestri Ponente Genova - Sestri Ponente
Italy Italy
Email: daniele.ceccarelli@ericsson.com Email: daniele.ceccarelli@ericsson.com
Khuzema Pithewan Khuzema Pithewan
Infinera Corporation Infinera Corporation
169, Java Drive 169, Java Drive
Sunnyvale, CA-94089, USA Sunnyvale, CA-94089, USA
Email: kpithewan@infinera.com Email: kpithewan@infinera.com
Yi Lin 15. Acknowledgment
Huawei Technologies
F3-5-B R&D Center, Huawei Base
Bantian, Longgang District
Shenzhen 518129 P.R.China
Phone: +86-755-28972914
Email: yi.lin@huawei.com
Yunbin Xu
China Academy of Telecommunication Research of MII
11 Yue Tan Nan Jie Beijing, P.R.China
Phone: +86-10-68094134
Email: xuyunbin@mail.ritt.com.cn
Pietro Grandi
Alcatel-Lucent
Optics CTO
Via Trento 30 20059 Vimercate (Milano) Italy
+39 039 6864930
Email: pietro_vittorio.grandi@alcatel-lucent.it
Diego Caviglia
Ericsson
Via A. Negrone 1/A
Genova - Sestri Ponente
Italy
Email: diego.caviglia@ericsson.com
Rajan Rao
Infinera Corporation
169, Java Drive
Sunnyvale, CA-94089
USA
Email: rrao@infinera.com
John E Drake
Juniper
Email: jdrake@juniper.net
Igor Bryskin
Adva Optical
EMail: IBryskin@advaoptical.com
14. Acknowledgment
The authors would like to thank Lou Berger and Deborah Brungard for The authors would like to thank Lou Berger, Deborah Brungard and
their useful comments to the document. Xiaobing Zi for their useful comments to the document.
Intellectual Property Intellectual Property
The IETF Trust takes no position regarding the validity or scope of The IETF Trust takes no position regarding the validity or scope of
any Intellectual Property Rights or other rights that might be any Intellectual Property Rights or other rights that might be
claimed to pertain to the implementation or use of the technology claimed to pertain to the implementation or use of the technology
described in any IETF Document or the extent to which any license described in any IETF Document or the extent to which any license
under such rights might or might not be available; nor does it under such rights might or might not be available; nor does it
represent that it has made any independent effort to identify any represent that it has made any independent effort to identify any
such rights. such rights.
 End of changes. 63 change blocks. 
152 lines changed or deleted 178 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/