draft-ietf-ccamp-gmpls-signaling-g709v3-02.txt   draft-ietf-ccamp-gmpls-signaling-g709v3-03.txt 
Network Working Group Fatai Zhang, Ed. Network Working Group Fatai Zhang, Ed.
Internet Draft Huawei Internet Draft Huawei
Category: Standards Track Guoying Zhang Category: Standards Track Guoying Zhang
CATR CATR
Sergio Belotti Sergio Belotti
Alcatel-Lucent Alcatel-Lucent
D. Ceccarelli D. Ceccarelli
Ericsson Ericsson
Khuzema Pithewan Khuzema Pithewan
Infinera Infinera
Expires: September 9, 2012 March 9, 2012 Expires: January 13, 2013 July 13, 2012
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-02.txt draft-ietf-ccamp-gmpls-signaling-g709v3-03.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 September 9, 2012. This Internet-Draft will expire on January 13, 2013.
Abstract Abstract
Recent progress in ITU-T Recommendation G.709 standardization has Recent progress in ITU-T Recommendation G.709 standardization has
introduced new ODU containers (ODU0, ODU4, ODU2e and ODUflex) and introduced new ODU containers (ODU0, ODU4, ODU2e and ODUflex) and
enhanced Optical Transport Networking (OTN) flexibility. Several enhanced Optical Transport Networking (OTN) flexibility. Several
recent documents have proposed ways to modify GMPLS signaling recent documents have proposed ways to modify GMPLS signaling
protocols to support these new OTN features. protocols to support these new OTN features.
It is important that a single solution is developed for use in GMPLS It is important that a single solution is developed for use in GMPLS
skipping to change at page 2, line 27 skipping to change at page 2, line 27
features including ODU0, ODU4, ODU2e and ODUflex. features including 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 ................................................... 4 2. Terminology ................................................. 4
3. GMPLS Extensions for the Evolving G.709 - Overview ............ 4 3. GMPLS Extensions for the Evolving G.709 - Overview ........... 4
4. Generalized Label Request ..................................... 5 4. Generalized Label Request .................................... 5
5. Extensions for Traffic Parameters for the Evolving G.709 ...... 5 5. Extensions for Traffic Parameters for the Evolving G.709 ..... 6
5.1. Usage of ODUflex(CBR) Traffic Parameters ................. 7 5.1. Usage of ODUflex(CBR) Traffic Parameters ................ 8
5.2. Usage of ODUflex(GFP) Traffic Parameters ................. 9 5.2. Usage of ODUflex(GFP) Traffic Parameters ............... 10
6. Generalized Label ............................................. 9 6. Generalized Label ........................................... 11
6.1. New definition of ODU Generalized Label ................. 10 6.1. New definition of ODU Generalized Label ................ 11
6.2. Examples ................................................ 12 6.2. Examples ............................................... 14
6.3. Label Distribution Procedure ............................ 14 6.3. Label Distribution Procedure ........................... 15
6.3.1. Notification on Label Error ........................ 15 6.3.1. Notification on Label Error ....................... 16
6.4. Supporting Virtual Concatenation and Multiplication ..... 15 6.4. Supporting Virtual Concatenation and Multiplication .... 17
7. Supporting Multiplexing Hierarchy ............................ 16 7. Supporting Multiplexing Hierarchy ........................... 17
7.1. ADAPTATION Object ....................................... 17 7.1. Extension to LSP_ATTRIBUTES Object ..................... 18
7.2. ODU FA-LSP Creation ..................................... 19 7.2. ODU FA-LSP Creation .................................... 19
8. Supporting Hitless Adjustment of ODUflex (GFP) ............... 20 8. Supporting Hitless Adjustment of ODUflex (GFP) .............. 20
9. Control Plane Backward Compatibility Considerations........... 21 9. Control Plane Backward Compatibility Considerations.......... 21
10. Security Considerations ..................................... 22 10. Security Considerations................................. ... 22
11. IANA Considerations.......................................... 22 11. IANA Considerations.................................. ...... 22
12. References .................................................. 23 12. References ................................................. 23
12.1. Normative References ................................... 23 12.1. Normative References................................... 23
12.2. Informative References ................................. 24 12.2. Informative References................................. 25
13. Contributors ................................................ 25 13. Contributors ............................................... 25
14. Authors' Addresses .......................................... 25 14. Authors' Addresses ......................................... 26
15. Acknowledgment .............................................. 28 15. Acknowledgment ............................................. 28
1. Introduction 1. Introduction
Generalized Multi-Protocol Label Switching (GMPLS) [RFC3945] extends Generalized Multi-Protocol Label Switching (GMPLS) [RFC3945] extends
MPLS to include Layer-2 Switching (L2SC), Time-Division Multiplex MPLS to include Layer-2 Switching (L2SC), Time-Division Multiplex
(e.g., SONET/SDH, PDH, and ODU), Wavelength (OCh, Lambdas) Switching, (e.g., SONET/SDH, PDH, and ODU), Wavelength (OCh, Lambdas) Switching,
and Spatial Switching (e.g., incoming port or fiber to outgoing port and Spatial Switching (e.g., incoming port or fiber to outgoing port
or fiber). [RFC3471] presents a functional description of the or fiber). [RFC3471] presents a functional description of the
extensions to Multi-Protocol Label Switching (MPLS) signaling extensions to Multi-Protocol Label Switching (MPLS) signaling
required to support Generalized MPLS. RSVP-TE-specific formats and required to support Generalized MPLS. RSVP-TE-specific formats and
skipping to change at page 3, line 36 skipping to change at page 3, line 36
Networks (OTN), as specified in the ITU-T Recommendation G.709 [G709- Networks (OTN), as specified in the ITU-T Recommendation G.709 [G709-
V1], for ODUk deployments without multiplexing. V1], for ODUk deployments without multiplexing.
In addition to increasing need to support ODUk multiplexing, the In addition to increasing need to support ODUk multiplexing, the
evolution of OTN has introduced additional containers and new evolution of OTN has introduced additional containers and new
flexibility. For example, ODU0, ODU2e, ODU4 containers and ODUflex flexibility. For example, ODU0, ODU2e, ODU4 containers and ODUflex
are developed in [G709-V3]. are developed in [G709-V3].
In addition, the following issues require consideration: In addition, the following issues require consideration:
- Support for Hitless Adjustment of ODUflex (GFP) (HAO), which is - Support for Hitless Adjustment of ODUflex (GFP) (HAO), which is
defined in [G.7044]. defined in [G.7044].
- Support for Tributary Port Number. The Tributary Port Number - Support for Tributary Port Number. The Tributary Port Number
has to be negotiated on each link for flexible assignment of has to be negotiated on each link for flexible assignment of
tributary ports to tributary slots in case of LO-ODU over HO- tributary ports to tributary slots in case of LO-ODU over HO-
ODU (e.g., ODU2 into ODU3). ODU (e.g., ODU2 into ODU3).
Therefore, it is clear that [RFC4328] has to be updated or superceded Therefore, it is clear that [RFC4328] has to be updated or superceded
in order to support ODUk multiplexing, as well as other ODU in order to support ODUk multiplexing, as well as other ODU
enhancements introduced by evolution of OTN standards. enhancements introduced by evolution of OTN standards.
This document updates [RFC4328] extending the G.709 ODUk traffic This document updates [RFC4328] extending the G.709 ODUk traffic
parameters and also presents a new OTN label format which is very parameters and also presents a new OTN label format which is very
skipping to change at page 4, line 26 skipping to change at page 4, line 26
- 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 (TS) granularity (i.e., 1.25 Gbps) is also A new Tributary Slot Granularity (TSG) (i.e., 1.25 Gbps) is also
described in [G709-V3]. Thus, there are now two TS granularities for described in [G709-V3]. Thus, there are now two TS granularities for
the foundation OTN ODU1, ODU2 and ODU3 containers. The TS granularity the foundation OTN ODU1, ODU2 and ODU3 containers. The TS granularity
at 2.5 Gbps is used on legacy interfaces while the new 1.25 Gbps is at 2.5 Gbps is used on legacy interfaces while the new 1.25 Gbps is
used on the new interfaces. used on the new interfaces.
In addition to the support of ODUk mapping into OTUk (k = 1, 2, 3, 4), In addition to the support of ODUk mapping into OTUk (k = 1, 2, 3, 4),
the evolving OTN [G.709-V3] encompasses the multiplexing of ODUj (j = the evolving OTN [G.709-V3] encompasses the multiplexing of ODUj (j =
0, 1, 2, 2e, 3, flex) into an ODUk (k > j), as described in Section 0, 1, 2, 2e, 3, flex) into an ODUk (k > j), as described in Section
3.1.2 of [OTN-FWK]. 3.1.2 of [OTN-FWK].
skipping to change at page 5, line 25 skipping to change at page 5, line 25
code-points for the LSP Encoding Type (i.e., G.709 ODUk (Digital Path) 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 order and G.709 Optical Channel) and adding a list of G-PID values in order
to accommodate [G709-v1]. to accommodate [G709-v1].
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-V3] in introduced to indicate the ODUk switching capability [G709-V3] 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 (101, TBA by IANA) is defined in
[OTN-OSPF]. [OTN-OSPF].
This document also updates the G-PID values defined in [RFC4328]:
Value G-PID Type
----- ----------
47 ODU-2.5G: transport of Digital Paths at 2.5, 10 and 40
Gbps via 2.5Gbps TSG
49 CBRa: asynchronous Constant Bit Rate (i.e., mapping of
CBR2G5, CBR10G and CBR40G)
50 CBRb: bit synchronous Constant Bit Rate (i.e., mapping of
CBR2G5, CBR10G, CBR40G, CBR10G3 and supra-2.488 CBR
Gbit/s signal (carried by OPUflex))
32 ATM: mapping at 1.25, 2.5, 10 and 40 Gbps
51 BSOT: non-specific client Bit Stream with Octet Timing (i.e.,
Mapping of 1.25, 2.5, 10, 40 and 100 Gbps Bit Stream)
52 BSNT: non-specific client Bit Stream without Octet Timing
(i.e., Mapping of 1.25, 2.5, 10, 40 and 100 Gbps Bit
Stream)
Note: Values 32, 47, 49 and 50 include mapping of SDH.
In the case of ODU multiplexing, the LO ODU (i.e., the client signal)
may be multiplexed into HO ODU 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 [RFC4328] is only used for 2.5Gbps TSG, two new G-
PID types are needed:
- ODU-1.25G: transport of Digital Paths at 1.25, 2.5, 10, 40 and
100 Gbps via 1.25Gbps TSG
- 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
procedure is enabled and the default value of 1.25Gbps
TSG can be fallen back to 2.5Gbps if needed)
In addition, some other new G-PID types are defined to support other
new client signals described in [G709-V3]:
- CBRc: Mapping of constant bit-rate signals with justification
into OPUk (k = 0, 1, 2, 3, 4) via GMP (i.e., mapping of
sub-1.238, supra-1.238 to sub-2.488, close-to 9.995,
close-to 40.149 and close-to 104.134 Gbit/s CBR client
signal)
- 1000BASE-X: Mapping of a 1000BASE-X signal via timing
transparent transcoding into OPU0
- FC-1200: Mapping of a FC-1200 signal via timing transparent
transcoding into OPU2e
The following table summarizes the new G-PID values with respect to
the LSP Encoding Type:
Value G-PID Type LSP Encoding Type
----- ---------- -----------------
59(TBA) G.709 ODU-1.25G G.709 ODUk
60(TBA) G.709 ODU-any G.709 ODUk
61(TBA) CBRc G.709 ODUk
62(TBA) 1000BASE-X G.709 ODUk (k=0)
63(TBA) FC-1200 G.709 ODUk (k=2e)
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 G.709 are defined as follows: The traffic parameters for G.709 are defined as 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 | NMC/ Tolerance | | Signal Type | Reserved | NMC/ Tolerance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NVC | Multiplier (MT) | | NVC | Multiplier (MT) |
skipping to change at page 6, line 32 skipping to change at page 8, line 8
end circuit involving dissimilar OTN link types. For example, ODU2e end circuit involving dissimilar OTN link types. For example, ODU2e
requires 9 TS on ODU3 and 8 TS on ODU4. Usage of NMC field is requires 9 TS on ODU3 and 8 TS on ODU4. Usage of NMC field is
deprecated and should be used only with [RFC4328] generalized label deprecated and should be used only with [RFC4328] generalized label
format for backwards compatibility reasons. For the new generalized format for backwards compatibility reasons. For the new generalized
label format as defined in this document this field is interpreted as label format as defined in this document this field is interpreted as
Tolerance. Tolerance.
In case of ODUflex(CBR), the Bit_Rate and Tolerance fields MUST be In case of ODUflex(CBR), the Bit_Rate and Tolerance fields MUST be
used together to represent the actual bandwidth of ODUflex, where: used together to represent the actual bandwidth of ODUflex, where:
- The Bit_Rate field indicates the nominal bit rate of ODUflex(CBR) - The Bit_Rate field indicates the nominal bit rate of ODUflex(CBR)
expressed in bytes per second, encoded as a 32-bit IEEE single- expressed in bytes per second, encoded as a 32-bit IEEE single-
precision floating-point number (referring to [RFC4506] and precision floating-point number (referring to [RFC4506] and
[IEEE]). The value contained in the Bit Rate field has to keep [IEEE]). The value contained in the Bit Rate field has to keep
into account both 239/238 factor and the Transcoding factor. into account both 239/238 factor and the Transcoding factor.
- The Tolerance field indicates the bit rate tolerance (part per - The Tolerance field indicates the bit rate tolerance (part per
million, ppm) of the ODUflex(CBR) encoded as an unsigned integer, million, ppm) of the ODUflex(CBR) encoded as an unsigned integer,
which is bounded in 0~100ppm. which is bounded in 0~100ppm.
For example, for an ODUflex(CBR) service with Bit_Rate = 2.5Gbps and For example, for an ODUflex(CBR) service with Bit_Rate = 2.5Gbps and
Tolerance = 100ppm, the actual bandwidth of the ODUflex is: Tolerance = 100ppm, the actual bandwidth of the ODUflex is:
2.5Gbps * (1 +/- 100ppm) 2.5Gbps * (1 +/- 100ppm)
In case of ODUflex(GFP), the Bit_Rate field is used to indicate the In case of ODUflex(GFP), the Bit_Rate field is used to indicate the
nominal bit rate of the ODUflex(GFP), which implies the number of nominal bit rate of the ODUflex(GFP), which implies the number of
skipping to change at page 10, line 26 skipping to change at page 12, line 4
In order to be compatible with new types of ODU signal and new types In order to be compatible with new types of ODU signal and new types
of tributary slot, the following new ODU label format MUST be used: of tributary slot, the following new ODU label format MUST be used:
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 ......... ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The ODU Generalized Label is used to indicate how the LO ODUj signal The ODU 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 ODUk type is indicated by traffic parameters, while the type of HO ODUk
link can be figured out locally according to the identifier of the link can be figured out locally according to the identifier of the
selected interface carried in the IF_ID RSVP_HOP Object. selected interface carried in the IF_ID RSVP_HOP Object.
TPN (12 bits): indicates the Tributary Port Number (TPN) for the TPN (12 bits): indicates the Tributary Port Number (TPN) for the
assigned Tributary Slot(s). 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.
As per [G709-V3], The TPN is used to allow for correct demultiplexing As per [G709-V3], 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 15, line 18 skipping to change at page 16, line 43
Note also that the TPN in the label_ERO MAY not be assigned (i.e., Note also that the TPN in the label_ERO MAY not be assigned (i.e.,
TPN field = 0) if the TPN is requested to be assigned locally. TPN field = 0) if the TPN is requested to be assigned locally.
6.3.1. Notification on Label Error 6.3.1. Notification on Label Error
When receiving an ODUk label from the neighbor node, the node SHOULD When receiving an ODUk label from the neighbor node, the node SHOULD
check the integrity of the label. An error message containing an check the integrity of the label. An error message containing an
"Unacceptable label value" indication ([RFC3209]) SHOULD be sent if "Unacceptable label value" indication ([RFC3209]) SHOULD be sent if
one of the following cases occurs: one of the following cases occurs:
- 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 reserved resources (i.e., the number of "1" in the Bit Map - The reserved resources (i.e., the number of "1" in the Bit Map
field) do not match with the Traffic Parameters. field) do not match with the Traffic Parameters.
6.4. Supporting Virtual Concatenation and Multiplication 6.4. Supporting Virtual Concatenation and Multiplication
As per [RFC6344], the VCGs can be created using Co-Signaled style or As per [RFC6344], the VCGs can be created using Co-Signaled style or
Multiple LSPs style. 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
reflects the order of VCG members, which is similar to [RFC4328]. In reflects the order of VCG members, which is similar to [RFC4328]. In
case of multiplexed virtually concatenated signals (NVC > 1), the case of multiplexed virtually concatenated signals (NVC > 1), the
skipping to change at page 16, line 37 skipping to change at page 18, line 21
| N1 +---------+ N2 +=========+ N3 +=========+ N4 +---------+ N5 | | N1 +---------+ N2 +=========+ N3 +=========+ N4 +---------+ N5 |
+----+ +----+ +----+ +----+ +----+ +----+ +----+ +----+ +----+ +----+
ODU3 link ODU3 link ODU3 link ODU3 link ODU3 link ODU3 link ODU3 link ODU3 link
Figure 2 - Example of multiplexing hierarchy Figure 2 - Example of multiplexing hierarchy
The control plane signaling should support the provisioning of The control plane signaling should support the provisioning of
hierarchical multiplexing. Two methods are provided below (taking hierarchical multiplexing. Two methods are provided below (taking
Figure 2 as example): Figure 2 as example):
- Using the multi-layer network signaling described in [RFC4206], - Using the multi-layer network signaling described in [RFC4206],
[RFC6107] and [RFC6001] (including related modifications, if [RFC6107] and [RFC6001] (including related modifications, if
needed). That is, when the signaling message for ODUO connection needed). That is, when the signaling message for ODUO connection
arrives at N2, a new RSVP session between N2 and N4 is triggered arrives at N2, a new RSVP session between N2 and N4 is triggered
to create the ODU2 connection. This ODU2 connection is treated as to create the ODU2 connection. This ODU2 connection is treated as
a Forwarding Adjacency (FA) after it is created. And then the a Forwarding Adjacency (FA) after it is created. And then the
signaling procedure for the ODU0 connection can be continued using signaling procedure for the ODU0 connection can be continued using
the resource of the ODU2 FA. the resource of the ODU2 FA.
- The ODU2 FA-LSP is created in advance based on network planning, - The ODU2 FA-LSP is created in advance based on network planning,
which is treated as an FA. Then the ODU0 connection can be created which is treated as an FA. Then the ODU0 connection can be created
using the resource of the ODU2 FA. In this case, the ODU2 FA-LSP using the resource of the ODU2 FA. In this case, the ODU2 FA-LSP
and inner ODU0 connections are created separately. and inner ODU0 connections are created separately.
For both methods, when creating an FA-LSP(e.g., ODU2 FA-LSP), the For both methods, when creating an FA-LSP(e.g., ODU2 FA-LSP), the
penultimate hop needs to choose a correct outgoing interface for the penultimate hop needs to choose a correct outgoing interface for the
ODU2 connection, so that the destination node can support ODU2 connection, so that the destination node can support
multiplexing and de-multiplexing LO ODU signal(e.g., ODU0). In order multiplexing and de-multiplexing LO ODU signal(e.g., ODU0). In order
to choose a correct outgoing interface for the penultimate hop of the to choose a correct outgoing interface for the penultimate hop of the
FA-LSP, multiplexing capability (i.e., what client signal type that FA-LSP, multiplexing capability (i.e., what client signal type that
can be adapted directly to this FA-LSP) should be carried in the can be adapted directly to this FA-LSP) should be carried in the
signaling to setup this FA-LSP. In addition, when Auto_Negotiation in signaling to setup this FA-LSP. In addition, when Auto_Negotiation in
the data plane is not enabled, TS granularity may also be needed. the data plane is not enabled, TS granularity may also be needed.
7.1. ADAPTATION Object 7.1. Extension to LSP_ATTRIBUTES Object
In order to create ODU FA-LSP (i.e., the server layer LSP) for
carrying the client LSP, a new object called ADAPTATION Object is
introduced, with two TLVs defined in this document:
- Type 1 = Server TSG signaling
- Type 2 = Hierarchy signaling
(1) Type=1 - Server TSG TLV
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 (TSG) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TSG | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TSG: Tributary Slot Granularity (8bit): Used for signaling the server
layer TSG:
- 0 - Reserved
- 1 - either 1.25Gbps or 2.5Gbps
- 2 - 2.5Gbps
- 3 - 1.25Gbps
- 4~255 - Reserved
Where value 1 is used where the fallback procedure at the source end
of FA is enabled and the default value of 1.25Gbps can be fallen back
to 2.5Gbps. This means that either 1.25 Gpbs or 2.5 Gbps can be used
as the server TSG at the sink end of FA.
Values 2 and 3 are used to signal a 2.5Gbps or 1.25Gbps interfaces
respectively and there is no chance to modify it.
Other values are reserved for future extension.
(2) Type=2 - Hierarchy TLV In order to indicate the adaptation information for a requested FA-
LSP (i.e., the server layer LSP) to carry the client LSP, a new type
of Attributes TLV of the LSP_ATTRIBUTES Object (Class-Num = 197, C-
Type = 1, defined in [RFC5420]) is defined:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 2 (Hierarchy) | Length | | Type = 2 (ODU adaptation) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LSP Enc. Type |Switching Type | Signal Type | Mapping | | Reserved | Signal Type | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| ... | | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LSP Enc. Type |Switching Type | Signal Type | Mapping | | Reserved | Signal Type | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
A Hierarchy TLV for each branch of the client signal multiplexing One or more ODU adaptation TLVs can be carried to indicate the
supported by the server LSP MUST be used. Inside each TLV a row for desired adaptation capabilities. Each of an ODU adaptation TLV for
each stage of the hierarchy MUST be included. each branch of the client signal multiplexing supported by the server
LSP MUST be used. Inside each TLV a row for each stage of the
hierarchy MUST be included.
A row for the server stage MUST NOT be included as it is already A row for the server stage MUST NOT be included as it is already
signaled via the Traffic Parameters. signaled via the Traffic Parameters.
The number of stages is implicitly inferred from the length value. The number of stages is implicitly inferred from the length value.
The meaning of the fields is defined as follow: Signal Type: as defined in [RFC4328] and this document.
LSP Encoding Type and Switching Type: These fields can assume any
value inherited from the Generalized Label Request Object in GMPLS
signaling, defined in [RFC3471] and following related RFCs and
drafts.
Signal Type: In the case of non OTN signal types, this field MUST
be set to 0, while in the case of OTN signal types if MUST be
filled accordingly to [RFC4328] and this document.
Mapping: This field indicates the mapping function used in each
client-server relationship of the hierarchy. The values of this
field are listed below:
Value Type
----- ------
0 Reserved
1 AMP
2 BMP
3 GMP
4 GFP-F
5 GFP-T
6-255 Reserved
For example, in order to create ODU3 FA-LSP passing through a set of For example, in order to create ODU3 FA-LSP passing through a set of
ODU4 links to perform ODU1->ODU2->ODU3 hierarchy, the Hierarchy TLV ODU4 links to perform ODU1->ODU2->ODU3 hierarchy, the ODU adaptation
can be used to indicate the ODU2 into ODU3 multiplexing and ODU1 into TLV can be used to indicate the ODU2 into ODU3 multiplexing and ODU1
ODU2 multiplexing stages. into ODU2 multiplexing stages.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 2 (Hierarchy) | Length = 8 | | Type = 2 (ODU adaptation) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Enc.=12(ODUk) | Switching=101 | Sig. = ODU2 | Mapping = AMP | | Reserved | Sig. = ODU2 | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Enc.=12(ODUk) | Switching=101 | Sig. = ODU1 | Mapping = AMP | | Reserved | Sig. = ODU1 | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
7.2. ODU FA-LSP Creation 7.2. ODU FA-LSP Creation
When creating an ODU FA-LSP, the source node (e.g., node N2 in Figure When creating an ODU FA-LSP to carry lower ODU, the source node (e.g.,
2) can include the ADAPTATION object to specify the desired hierarchy node N2 in Figure 2) can include the LSP_ATTRIBUTES object to specify
capabilities. the desired ODU adaptation capabilities.
On receiving the Path message, the penultimate node on the FA-LSP On receiving the Path message, the penultimate node on the FA-LSP
(e.g., node N3 in Figure 2) MUST select an outgoing link which has (e.g., node N3 in Figure 2) MUST select an outgoing link which can
the ability to carry the requested ODU FA-LSP which can support the support the TS granularity (indicated in the G-PID filed in Section 4)
TS granularity and the multiplexing hierarchy listed in the and the multiplexing hierarchy (listed in the LSP_ATTRIBUTES object).
ADAPTATION object at the remote end of the link (Note that such If no link supporting the specified hierarchy capabilities or TSG, a
remote capability information can be obtained through LMP, routing ParhErr message with Error Code = 38 (LSP Hierarchy Issue) and Error
protocol or configuration). Then the penultimate node uses the IF_ID Value = y1(TBA) MUST be sent back to upstream.
RSVP_HOP Object to indicate the selected link for carrying the FA-LSP,
as described in [RFC3473]. If no link supporting the specified
hierarchy capabilities, a ParhErr message with Error Code = 38 (LSP
Hierarchy Issue) and Error Value = y1(new value) MUST be sent back to
upstream.
Other intermediate nodes along the FA-LSP don't need to process the Intermediate nodes (except end points and penultimate node) along the
ADAPTATION object, just forwarding it to the next node in the Path FA-LSP don't need to process the ODU adaptation TLV, which SHOULD be
message, without any modification. forwarded to the next node in the Path message without any
modification.
8. Supporting Hitless Adjustment of ODUflex (GFP) 8. Supporting Hitless Adjustment of ODUflex (GFP)
[G.7044] describes the procedure of ODUflex (GFP) hitless resizing [G.7044] describes the procedure of ODUflex (GFP) hitless resizing
using LCR (Link Connection Resize) and BWR (Bandwidth Resize) using LCR (Link Connection Resize) and BWR (Bandwidth Resize)
protocols in OTN data plane. protocols in OTN data plane.
For the control plane, signaling messages are required to initiate For the control plane, signaling messages are required to initiate
the adjustment procedure. Section 2.5 and Section 4.6.4 of [RFC3209] the adjustment procedure. Section 2.5 and Section 4.6.4 of [RFC3209]
describe how the Share Explicit (SE) style is used in TE network for describe how the Share Explicit (SE) style is used in TE network for
skipping to change at page 21, line 31 skipping to change at page 21, line 46
be taken into consideration when the new nodes (supporting [G709-V3] be taken into consideration when the new nodes (supporting [G709-V3]
and RSVP-TE extensions defined in this document) and the legacy nodes and RSVP-TE extensions defined in this document) and the legacy nodes
(supporting [G709-V1] and [RFC4328]) are interworking. (supporting [G709-V1] and [RFC4328]) are interworking.
The backward compatibility needs to be considered only when The backward compatibility needs to be considered only when
controlling ODU1 or ODU2 or ODU3 connection, because legacy nodes can controlling ODU1 or ODU2 or ODU3 connection, because legacy nodes can
only support these three ODU signal types. In such case, new nodes only support these three ODU signal types. In such case, new nodes
can fall back to use signaling message defined in [RFC4328] when can fall back to use signaling message defined in [RFC4328] when
detecting legacy node on the path. More detailedly: detecting legacy node on the path. More detailedly:
o When receiving Path message using [RFC4328] (i.e., Switching Type o When receiving Path message using [RFC4328] (i.e., Switching Type
= 100), a new node SHOULD follow [RFC4328] to process and reply it. = 100), a new node SHOULD follow [RFC4328] to process and reply it.
o A source node of an ODU LSP can send Path message using new OTN o A source node of an ODU LSP can send Path message using new OTN
control message (with new Switching Type = 101, TBA by IANA). If control message (with new Switching Type = 101, TBA by IANA). If
there is legacy node on the LSP, it will fail to process the there is legacy node on the LSP, it will fail to process the
Generalized Label Request Object because of unknown of the new Generalized Label Request Object because of unknown of the new
Switching Type, and reply a PathErr message indicating unknown of Switching Type, and reply a PathErr message indicating unknown of
this object. The source node MAY re-signal the Path message using this object. The source node MAY re-signal the Path message using
[RFC4328], depending on local policies. [RFC4328], depending on local policies.
o Alternatively, if a new node has known that its neighbor only o Alternatively, if a new node has known that its neighbor only
supports [RFC4328] in advance (e.g., through manual configuration supports [RFC4328] in advance (e.g., through manual configuration
or auto discovery mechanism), the new node MAY act as an RSVP or auto discovery mechanism), the new node MAY act as an RSVP
agent to translate new RSVP-TE message into old one before sending agent to translate new RSVP-TE message into old one before sending
to its neighbor. to its neighbor.
No special compatibility consideration needs to be taken if the No special compatibility consideration needs to be taken if the
legacy device has updated its control plane to support this document. legacy device has updated its control plane to support this document.
10. Security Considerations 10. Security Considerations
skipping to change at page 22, line 32 skipping to change at page 22, line 46
o G.709 FLOWSPEC Object: Class = 9, C-Type = 5 [RFC4328] o G.709 FLOWSPEC Object: Class = 9, C-Type = 5 [RFC4328]
- Generalized Label Object: - Generalized Label Object:
The new defined ODU label (Section 6) is a kind of generalized The new defined ODU label (Section 6) is a kind of generalized
label. Therefore, the Class-Num and C-Type of the ODU label is label. Therefore, the Class-Num and C-Type of the ODU label is
the same as that of generalized label described in [RFC3473], the same as that of generalized label described in [RFC3473],
i.e., Class-Num = 16, C-Type = 2. i.e., Class-Num = 16, C-Type = 2.
- ADAPTATION Object: - LSP_ATTIBUTES Object:
New object with Class-Num = xx, C-Type = xx. See Section 7 for New TLV with Type = 2 (TBA). This TLV is carried in the
the detail definition. LSP_ATTIBUTES Object (Class-Num = 197, C-Type = 1). See Section 7
for the detail definition.
- Error Code = 38 (LSP Hierarchy Issue, referring to [RFC6107]): - Error Code = 38 (LSP Hierarchy Issue, referring to [RFC6107]):
A new Error Value is added to the Error Code "LSP Hierarchy A new Error Value is added to the Error Code "LSP Hierarchy
Issue": Issue":
Error Value Error case Error Value Error case
-------------------------------------------------------------- --------------------------------------------------------------
y1 Last hop of an ODU FA-LSP doesn't support y1 Last hop of an ODU FA-LSP doesn't support
specified adaption capabilities (Section 7.2). specified adaptation capabilities (Section 7.2).
- Error Code = x2: - Error Code = x2:
New Error Code, indicating errors occurring when controlling a New Error Code, indicating errors occurring when controlling a
resizable ODUflex connection. resizable ODUflex connection.
Error Value Error case Error Value Error case
-------------------------------------------------------------- --------------------------------------------------------------
y1 Do not support hitless assignment of ODUflex (GFP) y1 Do not support hitless assignment of ODUflex (GFP)
(Section 8). (Section 8).
skipping to change at page 24, line 10 skipping to change at page 24, line 26
[RFC6107] K. Shiomoto, A. Farrel, "Procedures for Dynamically [RFC6107] K. Shiomoto, A. Farrel, "Procedures for Dynamically
Signaled Hierarchical Label Switched Paths", RFC6107, Signaled Hierarchical Label Switched Paths", RFC6107,
February 2011. February 2011.
[RFC6001] Dimitri Papadimitriou et al, "Generalized Multi-Protocol [RFC6001] Dimitri Papadimitriou et al, "Generalized Multi-Protocol
Label Switching (GMPLS) Protocol Extensions for Multi-Layer Label Switching (GMPLS) Protocol Extensions for Multi-Layer
and Multi-Region Networks (MLN/MRN)", RFC6001, February 21, and Multi-Region Networks (MLN/MRN)", RFC6001, February 21,
2010. 2010.
[RFC5420] A. Farrel, Ed., "Encoding of Attributes for MPLS LSP
Establishment Using Resource Reservation Protocol Traffic
Engineering (RSVP-TE)", RFC5420, February 2009.
[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", draft-ietf-ccamp-gmpls- G.709 Optical Transport Networks", draft-ietf-ccamp-gmpls-
g709-framework-05.txt, September 9, 2011. g709-framework, Work in Progress, June 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)", draft-ietf-ccamp-otn-g709-info- Transport Networks (OTN)", draft-ietf-ccamp-otn-g709-info-
model-01.txt, September 21, 2011. model, Work in Progress, January 2012.
[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", draft-ietf-ccamp-gmpls-ospf-g709v3-00.txt, OTN Networks", draft-ietf-ccamp-gmpls-ospf-g709v3, Work in
October 13, 2011 Progress, April 2012.
[OTN-LMP] Fatai Zhang, Ed., "Link Management Protocol (LMP) [OTN-LMP] Fatai Zhang, Ed., "Link Management Protocol (LMP)
extensions for G.709 Optical Transport Networks", draft- extensions for G.709 Optical Transport Networks", draft-
zhang-ccamp-gmpls-g.709-lmp-discovery-04.txt, April 6, 2011. zhang-ccamp-gmpls-g.709-lmp-discovery, Work in Progress,
July 2012.
[G709-V3] ITU-T, "Interfaces for the Optical Transport Network (OTN) [G709-V3] ITU-T, "Interfaces for the Optical Transport Network (OTN)
", G.709/Y.1331, December 2009. ", G.709/Y.1331, December 2009.
[G709-V3-A2] ITU-T, "Interfaces for the Optical Transport Network [G709-V3-A2] ITU-T, "Interfaces for the Optical Transport Network
(OTN) Amendment 2", G.709/y.1331 Amendment 2, April 2011. (OTN) Amendment 2", G.709/y.1331 Amendment 2, April 2011.
12.2. Informative References 12.2. Informative References
[G709-V1] ITU-T, "Interface for the Optical Transport Network (OTN)," [G709-V1] ITU-T, "Interface for the Optical Transport Network (OTN),"
 End of changes. 45 change blocks. 
148 lines changed or deleted 163 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/