draft-ietf-ccamp-gmpls-signaling-g709v3-04.txt   draft-ietf-ccamp-gmpls-signaling-g709v3-05.txt 
Network Working Group Fatai Zhang, Ed. Network Working Group Fatai Zhang, Ed.
Internet Draft Huawei Internet Draft Huawei
Category: Standards Track Guoying Zhang Updates: 4328 Guoying Zhang
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: February 27, 2013 August 27, 2012 Expires: May 30, 2013 November 30, 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-04.txt draft-ietf-ccamp-gmpls-signaling-g709v3-05.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 February 27, 2013. This Internet-Draft will expire on May 30, 2013.
Abstract Abstract
Recent progress in ITU-T Recommendation G.709 standardization has ITU-T Recommendation G.709 [G709-2012] has introduced new Optical
introduced new ODU containers (ODU0, ODU4, ODU2e and ODUflex) and channel Data Unit (ODU) containers (ODU0, ODU4, ODU2e and ODUflex)
enhanced Optical Transport Networking (OTN) flexibility. Several and enhanced Optical Transport Networking (OTN) flexibility.
recent documents have proposed ways to modify GMPLS signaling
protocols to support these new OTN features.
It is important that a single solution is developed for use in GMPLS
signaling and routing protocols. This solution must support ODUk
multiplexing capabilities, address all of the new features, be
acceptable to all equipment vendors, and be extensible considering
continued OTN evolution.
This document describes the extensions to the Generalized Multi- This document updates RFC4328 to provide the extensions to the
Protocol Label Switching (GMPLS) signaling to control the evolving Generalized Multi-Protocol Label Switching (GMPLS) signaling to
Optical Transport Networks (OTN) addressing ODUk multiplexing and new control the evolving OTN addressing ODUk multiplexing and new
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 ................................................... 3
3. GMPLS Extensions for the Evolving G.709 - Overview ............ 4 3. GMPLS Extensions for the Evolving G.709 - Overview ............ 3
4. Generalized Label Request ..................................... 5 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
6. Generalized Label ............................................ 11 6. Generalized Label ............................................ 11
6.1. New definition of ODU Generalized Label ................. 11 6.1. OTN-TDM Switching Type Generalized Label ................ 11
6.2. Examples ................................................ 14 6.2. Procedures .............................................. 13
6.3. Label Distribution Procedure ............................ 15 6.2.1. Notification on Label Error ........................ 15
6.3.1. Notification on Label Error ........................ 16 6.3. Supporting Virtual Concatenation and Multiplication ..... 15
6.4. Supporting Virtual Concatenation and Multiplication ..... 17 6.4. Examples ................................................ 15
7. Supporting Hitless Adjustment of ODUflex (GFP) ............... 17 7. Supporting Hitless Adjustment of ODUflex (GFP) ............... 17
8. Control Plane Backward Compatibility Considerations........... 18 8. Control Plane Backward Compatibility Considerations........... 18
9. Security Considerations ...................................... 19 9. Security Considerations ...................................... 19
10. IANA Considerations.......................................... 19 10. IANA Considerations.......................................... 19
11. References .................................................. 20 11. References .................................................. 20
11.1. Normative References ................................... 20 11.1. Normative References ................................... 20
11.2. Informative References ................................. 21 11.2. Informative References ................................. 21
12. Contributors ................................................ 21 12. Contributors ................................................ 21
13. Authors' Addresses .......................................... 22 13. Authors' Addresses .......................................... 22
14. Acknowledgment .............................................. 24 14. Acknowledgment .............................................. 24
1. Introduction 1. Introduction
Generalized Multi-Protocol Label Switching (GMPLS) [RFC3945] extends With the evolution and deployment of OTN technology, it is necessary
MPLS to include Layer-2 Switching (L2SC), Time-Division Multiplex that appropriate enhanced control technology support be provided for
(e.g., SONET/SDH, PDH, and ODU), Wavelength (OCh, Lambdas) Switching, [G709-2012].
and Spatial Switching (e.g., incoming port or fiber to outgoing port
or fiber). [RFC3471] presents a functional description of the
extensions to Multi-Protocol Label Switching (MPLS) signaling
required to support Generalized MPLS. RSVP-TE-specific formats and
mechanisms and technology specific details are defined in [RFC3473].
With the evolution and deployment of G.709 technology, it is
necessary that appropriate enhanced control technology support be
provided for G.709. [RFC4328] describes the control technology
details that are specific to foundation G.709 Optical Transport
Networks (OTN), as specified in the ITU-T Recommendation G.709 [G709-
V1], for ODUk deployments without multiplexing.
In addition to increasing need to support ODUk multiplexing, the
evolution of OTN has introduced additional containers and new
flexibility. For example, ODU0, ODU2e, ODU4 containers and ODUflex
are developed in [G709-V3].
In addition, the following issues require consideration:
- Support for Hitless Adjustment of ODUflex (GFP) (HAO), which is
defined in [G.7044].
- Support for Tributary Port Number. The Tributary Port Number
has to be negotiated on each link for flexible assignment of
tributary ports to tributary slots in case of LO-ODU over HO-
ODU (e.g., ODU2 into ODU3).
Therefore, it is clear that [RFC4328] has to be updated or superceded [OTN-FWK] provides a framework to allow the development of protocol
in order to support ODUk multiplexing, as well as other ODU extensions to support GMPLS and Path Computation Element (PCE)
enhancements introduced by evolution of OTN standards. control of OTN as specified in [G709-2012]. Based on this framework,
[OTN-INFO] evaluates the information needed by the routing and
signaling process in OTNs to support GMPLS control of OTN.
This document updates [RFC4328] extending the G.709 ODUk traffic [RFC4328] describes the control technology details that are specific
parameters and also presents a new OTN label format which is very to the 2001 revision of the G.709 specification. This document
flexible and scalable. updates [RFC4328] to provide Resource ReserVation Protocol-Traffic
Engineering (RSVP-TE) extensions to 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-V3]. The corresponding and ODUflex containers are specified in [G709-2012]. The
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 (TSG) (i.e., 1.25 Gbps) is also A new Tributary Slot Granularity (TS Granularity, TSG) (i.e., 1.25
described in [G709-V3]. Thus, there are now two TS granularities for Gbps) is also described in [G709-2012]. Thus, there are now two TS
the foundation OTN ODU1, ODU2 and ODU3 containers. The TS granularity granularities for the foundation OTN ODU1, ODU2 and ODU3 containers.
at 2.5 Gbps is used on legacy interfaces while the new 1.25 Gbps is
used on the new interfaces.
In addition to the support of ODUk mapping into OTUk (k = 1, 2, 3, 4), The TS granularity at 2.5 Gbps is used on legacy interfaces while the
the evolving OTN [G.709-V3] encompasses the multiplexing of ODUj (j = new 1.25 Gbps is used on the new interfaces.
0, 1, 2, 2e, 3, flex) into an ODUk (k > j), as described in Section
3.1.2 of [OTN-FWK].
Virtual Concatenation (VCAT) of OPUk (OPUk-Xv, k = 1/2/3, X = 1...256) In addition to the support of ODUk mapping into OTUk (k = 1, 2, 3,
is also supported by [OTN-V3]. Note that VCAT of OPU0 / OPU2e / OPU4 4), the evolving OTN [G.709-V3] encompasses the multiplexing of ODUj
/ OPUflex is not supported per [OTN-V3]. (j = 0, 1, 2, 2e, 3, flex) into an ODUk (k > j), as described in
Section 3.1.2 of [OTN-FWK].
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].
Note that VCAT of OPU0 / OPU2e / OPU4 / OPUflex is not supported per
[G709-2012].
[RFC4328] describes GMPLS signaling extensions to support the control [RFC4328] describes GMPLS signaling extensions to support the control
for G.709 Optical Transport Networks (OTN) [G709-V1]. However, for the 2001 revision of the G.709 specification. However, [RFC4328]
[RFC4328] needs to be updated because it does not provide the means needs to be updated because it does not provide the means to signal
to signal all the new signal types and related mapping and all the new signal types and related mapping and multiplexing
multiplexing functionalities. Moreover, it supports only the functionalities. Moreover, it supports only the deprecated auto-
deprecated auto-MSI mode which assumes that the Tributary Port Number Multiframe Structure Identifier (MSI) mode which assumes that the
is automatically assigned in the transmit direction and not checked Tributary Port Number (TPN) is automatically assigned in the transmit
in the receive direction. direction and not checked in the receive direction.
This document extends the G.709 traffic parameters described in This document extends the G.709 traffic parameters described in
[RFC4328] and presents a new flexible and scalable OTN label format. [RFC4328] and presents a new flexible and scalable OTN label format.
Additionally, procedures about Tributary Port Number assignment Additionally, procedures about Tributary Port Number assignment
through control plane are also provided in this document. through control plane are also provided in this document.
4. Generalized Label Request 4. Generalized Label Request
The Generalized Label Request, as described in [RFC3471], carries the The Generalized Label Request, as described in [RFC3471], carries the
LSP Encoding Type, the Switching Type and the Generalized Protocol Label Switched Path (LSP) Encoding Type, the Switching Type and the
Identifier (G-PID). Generalized Protocol Identifier (G-PID).
[RFC4328] extends the Generalized Label Request, introducing two new [RFC4328] extends the Generalized Label Request, introducing two new
code-points for the LSP Encoding Type (i.e., G.709 ODUk (Digital Path) code-points for the LSP Encoding Type (i.e., G.709 ODUk (Digital
and G.709 Optical Channel) and adding a list of G-PID values in order Path) and G.709 Optical Channel) and adding a list of G-PID values in
to accommodate [G709-v1]. order to accommodate the 2001 revision of the G.709 specification.
This document follows these extensions and a new Switching Type is This document follows these extensions and a new Switching Type is
introduced to indicate the ODUk switching capability [G709-V3] in introduced to indicate the ODUk switching capability [G709-2012] in
order to support backward compatibility with [RFC4328], as described order to support backward compatibility with [RFC4328], as described
in [OTN-FWK]. The new Switching Type (101, TBA by IANA) is defined in in [OTN-FWK]. The new Switching Type (101, TBA by IANA) is defined in
[OTN-OSPF]. [OTN-OSPF].
This document also updates the G-PID values defined in [RFC4328]: This document also updates the G-PID values defined in [RFC4328]:
Value G-PID Type Value G-PID Type
----- ---------- ----- ----------
47 ODU-2.5G: transport of Digital Paths (e.g., at 2.5, 10 and
40 Gbps) via 2.5Gbps TSG
47 ODU-2.5G: transport of Digital Paths at 2.5, 10 and 40 Gbps 49 CBRa: asynchronous Constant Bit Rate (CBR) (e.g.,
via 2.5Gbps TSG mapping of CBR2G5, CBR10G and CBR40G)
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 50 CBRb: bit synchronous Constant Bit Rate (e.g., mapping
CBR2G5, CBR10G, CBR40G, CBR10G3 and supra-2.488 CBR of CBR2G5, CBR10G, CBR40G, CBR10G3 and supra-
Gbit/s signal (carried by OPUflex)) 2.488 CBR Gbit/s signal (carried by OPUflex))
32 ATM: mapping at 1.25, 2.5, 10 and 40 Gbps 32 ATM: mapping of Asynchronous Transfer Mode (ATM) cell
stream (e.g., at 1.25, 2.5, 10 and 40 Gbps)
51 BSOT: non-specific client Bit Stream with Octet Timing (i.e., 51 BSOT: non-specific client Bit Stream with Octet Timing
Mapping of 1.25, 2.5, 10, 40 and 100 Gbps Bit Stream) (e.g., Mapping of 1.25, 2.5, 10, 40 and 100 Gbps
Bit Stream)
52 BSNT: non-specific client Bit Stream without Octet Timing 52 BSNT: non-specific client Bit Stream without Octet
(i.e., Mapping of 1.25, 2.5, 10, 40 and 100 Gbps Bit Timing (e.g., Mapping of 1.25, 2.5, 10, 40 and
Stream) 100 Gbps Bit Stream)
Note: Values 32, 47, 49 and 50 include mapping of SDH. Note: Values 32, 47, 49 and 50 include mapping of Synchronous Digital
Hierarchy (SDH).
In the case of ODU multiplexing, the LO ODU (i.e., the client signal) In the case of ODU multiplexing, the Lower Order ODU (LO ODU) (i.e.,
may be multiplexed into HO ODU via 1.25G TSG, 2.5G TSG or any one of the client signal) may be multiplexed into Higher Order ODU (HO ODU)
them (i.e., TSG Auto_Negotiation is enabled). Since the G-PID type via 1.25G TSG, 2.5G TSG or any one of them (i.e., TSG
"ODUk" defined in [RFC4328] is only used for 2.5Gbps TSG, two new G- Auto_Negotiation is enabled). Since the G-PID type "ODUk" defined in
PID types are defined as follows: [RFC4328] is only used for 2.5Gbps TSG, two new G-PID types are
defined as follows:
- ODU-1.25G: transport of Digital Paths at 1.25, 2.5, 10, 40 and - ODU-1.25G: transport of Digital Paths at 1.25, 2.5, 10, 40 and 100
100 Gbps via 1.25Gbps TSG Gbps via 1.25Gbps TSG
- ODU-any: transport of Digital Paths at 1.25, 2.5, 10, 40 and 100 - ODU-any: transport of Digital Paths at 1.25, 2.5, 10, 40 and 100
Gbps via 1.25 or 2.5Gbps TSG (i.e., the fallback Gbps via 1.25 or 2.5Gbps TSG (i.e., the fallback
procedure is enabled and the default value of 1.25Gbps procedure is enabled and the default value of 1.25Gbps
TSG can be fallen back to 2.5Gbps if needed) TSG can be fallen back to 2.5Gbps if needed)
In addition, some other new G-PID types are defined to support other In addition, some other new G-PID types are defined to support other
new client signals described in [G709-V3]: new client signals described in [G709-2012]:
- CBRc: Mapping of constant bit-rate signals with justification - CBRc: Mapping of constant bit-rate signals with justification
into OPUk (k = 0, 1, 2, 3, 4) via GMP (i.e., mapping of into OPUk (k = 0, 1, 2, 3, 4) via Generic Mapping
sub-1.238, supra-1.238 to sub-2.488, close-to 9.995, Procedure (GMP) (i.e., mapping of sub-1.238, supra-
close-to 40.149 and close-to 104.134 Gbit/s CBR client 1.238 to sub-2.488, close-to 9.995, close-to 40.149
signal) and close-to 104.134 Gbit/s CBR client signal)
- 1000BASE-X: Mapping of a 1000BASE-X signal via timing - 1000BASE-X: Mapping of a 1000BASE-X signal via timing transparent
transparent transcoding into OPU0 transcoding into OPU0
- FC-1200: Mapping of a FC-1200 signal via timing transparent - FC-1200: Mapping of a FC-1200 signal via timing transparent
transcoding into OPU2e transcoding into OPU2e
The following table summarizes the new G-PID values with respect to The following table summarizes the new G-PID values with respect to
the LSP Encoding Type: the LSP Encoding Type:
Value G-PID Type LSP Encoding Type Value G-PID Type LSP Encoding Type
----- ---------- ----------------- ----- ---------- -----------------
59(TBA) G.709 ODU-1.25G G.709 ODUk 59(TBA) G.709 ODU-1.25G G.709 ODUk
60(TBA) G.709 ODU-any G.709 ODUk 60(TBA) G.709 ODU-any G.709 ODUk
61(TBA) CBRc G.709 ODUk 61(TBA) CBRc G.709 ODUk
62(TBA) 1000BASE-X G.709 ODUk (k=0) 62(TBA) 1000BASE-X G.709 ODUk (k=0)
63(TBA) FC-1200 G.709 ODUk (k=2e) 63(TBA) FC-1200 G.709 ODUk (k=2e)
Note: Values 59 and 60 include mapping of SDH. Note: Values 59 and 60 include mapping of SDH.
5. Extensions for Traffic Parameters for the Evolving G.709 5. Extensions for Traffic Parameters for the Evolving G.709
The traffic parameters for G.709 are defined as follows: The traffic parameters for OTN-TDM capable Switching Type are carried
in the OTN-TDM SENDER_TSPEC and FLOWSPEC objects. The objects have
the following class and type:
- OTN-TDM SENDER_TSPEC Object: Class = 12, C-Type = 7 (TBA)
- OTN-TDM FLOWSPEC Object: Class = 9, C-Type = 7 (TBA)
The format of traffic parameters in these two objects are defined as
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 | Tolerance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NVC | Multiplier (MT) | | NVC | Multiplier (MT) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Bit_Rate | | Bit_Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Signal Type MUST be extended in order to cover the new Signal The valid Signal Type values defined in [RFC4328] are updated to be:
Type introduced by the evolving OTN. The new Signal Type values are
extended as follows:
Value Type Value Type
----- ---- ----- ----
0 Not significant 0 Not significant
1 ODU1 (i.e., 2.5 Gbps) 1 ODU1 (i.e., 2.5 Gbps)
2 ODU2 (i.e., 10 Gbps) 2 ODU2 (i.e., 10 Gbps)
3 ODU3 (i.e., 40 Gbps) 3 ODU3 (i.e., 40 Gbps)
4 ODU4 (i.e., 100 Gbps) 4 ODU4 (i.e., 100 Gbps)
5 Reserved (for future use) 5 Reserved (for future use)
6 OCh at 2.5 Gbps 6 Optical Channel (Och) at 2.5 Gbps
7 OCh at 10 Gbps 7 OCh at 10 Gbps
8 OCh at 40 Gbps 8 OCh at 40 Gbps
9 OCh at 100 Gbps 9 OCh at 100 Gbps
10 ODU0 (i.e., 1.25 Gbps) 10 ODU0 (i.e., 1.25 Gbps)
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(GFP-F), resizable (i.e., 1.25*N Gbps) 21 ODUflex(Generic Framing Procedure-Framed (GFP-F)),
resizable (i.e., 1.25*N Gbps)
22 ODUflex(GFP-F), non resizable (i.e., 1.25*N Gbps) 22 ODUflex(GFP-F), non resizable (i.e., 1.25*N Gbps)
23~255 Reserved (for future use) 23~255 Reserved (for future use)
NMC/Tolerance:
This field is redefined from the original definition in [RFC4328].
NMC field defined in [RFC4328] cannot be fixed value for an end-to-
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
deprecated and SHOULD be used only with [RFC4328] generalized label
format for backwards compatibility reasons. For the new generalized
label format as defined in this document this field MUST be
interpreted as 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 MUST be 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
tributary slots requested for the ODUflex(GFP). Since the tolerance tributary slots requested for the ODUflex(GFP). Since the tolerance
of ODUflex(GFP) makes no sense on tributary slot resource reservation, of ODUflex(GFP) makes no sense on tributary slot resource
the Tolerance field for ODUflex(GFP) is not necessary and MUST be reservation, the Tolerance field for ODUflex(GFP) is not necessary
filled with 0. and MUST be filled with 0.
In case of other ODUk signal types, the Bit_Rate and Tolerance fields In case of other ODUk signal types, the Bit_Rate and Tolerance fields
are not necessary and MUST be set to 0. are not necessary and MUST be set to 0.
The usage of the NVC and Multiplier (MT) fields are the same as The usage of the NVC and Multiplier (MT) fields are the same as
[RFC4328]. [RFC4328].
Note that the error process on the traffic parameters MUST follow the
rules defined in Section 6 of [RFC4328].
5.1. Usage of ODUflex(CBR) Traffic Parameters 5.1. Usage of ODUflex(CBR) Traffic Parameters
In case of ODUflex(CBR), the information of Bit_Rate and Tolerance in In case of ODUflex(CBR), the information of Bit_Rate and Tolerance in
the ODUflex traffic parameters MUST be used to determine the total the ODUflex traffic parameters MUST be used to determine the total
number of tributary slots N in the HO ODUk link to be reserved. Here: number of tributary slots N in the HO ODUk link to be reserved. Here:
N = Ceiling of N = Ceiling of
ODUflex(CBR) nominal bit rate * (1 + ODUflex(CBR) bit rate tolerance) ODUflex(CBR) nominal bit rate * (1 + ODUflex(CBR) bit rate tolerance)
--------------------------------------------------------------------- ---------------------------------------------------------------------
ODTUk.ts nominal bit rate * (1 - HO OPUk bit rate tolerance) ODTUk.ts nominal bit rate * (1 - HO OPUk bit rate tolerance)
In this formula, the ODUflex(CBR) nominal bit rate is the bit rate of In this formula, the ODUflex(CBR) nominal bit rate is the bit rate of
the ODUflex(CBR) on the line side, i.e., the client signal bit rate the ODUflex(CBR) on the line side, i.e., the client signal bit rate
after applying the 239/238 factor (according to clause 7.3 table 7.2 after applying the 239/238 factor (according to Clause 7.3, Table 7-2
of [G709-V3]) and the transcoding factor T (if needed) on the CBR of [G709-2012]) and the transcoding factor T (if needed) on the CBR
client. According to clauses 17.7.3, 17.7.4 and 17.7.5 of [G709-V3]: client. According to clauses 17.7.3, 17.7.4 and 17.7.5 of [G709-
2012]:
ODUflex(CBR) nominal bit rate = CBR client bit rate * (239/238) / T ODUflex(CBR) nominal bit rate = CBR client bit rate * (239/238) / T
The ODTUk.ts nominal bit rate is the nominal bit rate of the The ODTUk.ts (Optical channel Data Tributary Unit k with ts tributary
tributary slot of ODUk, as shown in Table 1 (referring to [G709-V3]). slots) nominal bit rate is the nominal bit rate of the tributary slot
of ODUk, as shown in Table 1 (referring to Table 7-7 of [G709-2012]).
Table 1 - Actual TS bit rate of ODUk (in Gbps) Table 1 - Actual TS bit rate of ODUk (in Kbps)
ODUk.ts Minimum Nominal Maximum ODUk.ts Minimum Nominal Maximum
---------------------------------------------------------- -----------------------------------------------------------
ODU2.ts 1.249 384 632 1.249 409 620 1.249 434 608 ODU2.ts 1,249,384.632 1,249,409.620 1,249,434.608
ODU3.ts 1.254 678 635 1.254 703 729 1.254 728 823 ODU3.ts 1,254,678.635 1,254,703.729 1,254,728.823
ODU4.ts 1.301 683 217 1.301 709 251 1.301 735 285 ODU4.ts 1,301.683.217 1,301,709.251 1,301,735.285
Note that: Note that:
Minimum bit rate of ODUTk.ts = Minimum bit rate of ODUTk.ts =
ODTUk.ts nominal bit rate * (1 - HO OPUk bit rate tolerance) ODTUk.ts nominal bit rate * (1 - HO OPUk bit rate tolerance)
Maximum bit rate of ODTUk.ts = Maximum bit rate of ODTUk.ts =
ODTUk.ts nominal bit rate * (1 + HO OPUk bit rate tolerance) ODTUk.ts nominal bit rate * (1 + HO OPUk bit rate tolerance)
Where: HO OPUk bit rate tolerance = 20ppm Where: HO OPUk bit rate tolerance = 20ppm
Therefore, a node receiving a PATH message containing ODUflex(CBR) Therefore, a node receiving a PATH message containing ODUflex(CBR)
skipping to change at page 10, line 27 skipping to change at page 10, line 9
=========: TS occupied by ODUflex =========: TS occupied by ODUflex
---------: free TS ---------: free TS
Figure 1 - Example of ODUflex(CBR) Traffic Parameters Figure 1 - Example of ODUflex(CBR) Traffic Parameters
- On the HO ODU4 link between node A and B: - On the HO ODU4 link between node A and B:
The maximum bit rate of the ODUflex(CBR) equals 2.5Gbps * (1 + The maximum bit rate of the ODUflex(CBR) equals 2.5Gbps * (1 +
100ppm), and the minimum bit rate of the tributary slot of ODU4 100ppm), and the minimum bit rate of the tributary slot of ODU4
equals 1.301 683 217Gbps, so the total number of tributary slots equals 1,301,683.217 Kbps, so the total number of tributary slots
N1 to be reserved on this link is: N1 to be reserved on this link is:
N1 = ceiling (2.5Gbps * (1 + 100ppm) / 1.301 683 217Gbps) = 2 N1 = ceiling (2.5Gbps * (1 + 100ppm) / 1,301,683.217 Kbps) = 2
- On the HO ODU2 link between node B and C: - On the HO ODU2 link between node B and C:
The maximum bit rate of the ODUflex equals 2.5Gbps * (1 + 100ppm), The maximum bit rate of the ODUflex equals 2.5Gbps * (1 +
and the minimum bit rate of the tributary slot of ODU2 equals 100ppm), and the minimum bit rate of the tributary slot of ODU2
1.249 384 632Gbps, so the total number of tributary slots N2 to equals 1,249,384.632 Kbps, so the total number of tributary slots
be reserved on this link is: N2 to be reserved on this link is:
N2 = ceiling (2.5Gbps * (1 + 100ppm) / 1.249 384 632Gbps) = 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-V3-A2] recommends that the ODUflex(GFP) will fill an integral [G709-2012] recommends that the ODUflex(GFP) will fill an integral
number of tributary slots of the smallest HO ODUk path over which the number of tributary slots of the smallest HO ODUk path over which the
ODUflex(GFP) may be carried, as shown in Table 2. ODUflex(GFP) may be carried, as shown in Table 2.
Table 2 - Recommended ODUflex(GFP) bit rates and tolerance Table 2 - Recommended ODUflex(GFP) bit rates and tolerance
ODU type | Nominal bit-rate | Tolerance ODU type | Nominal bit-rate | Tolerance
--------------------------------+------------------+----------- --------------------------------+------------------+-----------
ODUflex(GFP) of n TS, 1<=n<=8 | n * ODU2.ts | +/-100 ppm ODUflex(GFP) of n TS, 1<=n<=8 | n * ODU2.ts | +/-100 ppm
ODUflex(GFP) of n TS, 9<=n<=32 | n * ODU3.ts | +/-100 ppm ODUflex(GFP) of n TS, 9<=n<=32 | n * ODU3.ts | +/-100 ppm
ODUflex(GFP) of n TS, 33<=n<=80 | n * ODU4.ts | +/-100 ppm ODUflex(GFP) of n TS, 33<=n<=80 | n * ODU4.ts | +/-100 ppm
skipping to change at page 11, line 26 skipping to change at page 11, line 11
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.
6. Generalized Label 6. Generalized Label
[RFC3471] has defined the Generalized Label which extends the This section defines the format of the OTN-TDM Generalized Label.
traditional label by allowing the representation of not only labels
which are sent in-band with associated data packets, but also labels
which identify time-slots, wavelengths, or space division multiplexed
positions. The format of the corresponding RSVP-TE Generalized Label
object is defined in the Section 2.3 of [RFC3473].
However, for different technologies, it usually needs to use specific
label rather than the Generalized Label. For example, the label
format described in [RFC4606] could be used for SDH/SONET, the label
format in [RFC4328] for G.709.
6.1. New definition of ODU Generalized Label 6.1. OTN-TDM Switching Type Generalized Label
In order to be compatible with new types of ODU signal and new types The following is the Generalized Label format for that MUST be used
of tributary slot, the following new ODU label format MUST be 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 ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
type is indicated by traffic parameters, while the type of HO ODUk
link can be figured out locally according to the identifier of the
selected interface carried in the IF_ID RSVP_HOP Object.
TPN (12 bits): indicates the Tributary Port Number (TPN) for the The OTN-TDM Generalized Label is used to indicate how the LO ODUj
assigned Tributary Slot(s). 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 link is identified by the selected interface carried in the
IF_ID RSVP_HOP Object.
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.
As per [G709-V3], 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.
According to [G709-V3], the TPN field MUST be set as according to the According to [G709-2012], the TPN field MUST be set as according to
following tables: the following tables:
Table 3 - TPN Assignment Rules (2.5Gbps TS granularity) Table 3 - TPN Assignment Rules (2.5Gbps TS granularity)
+-------+-------+----+----------------------------------------------+ +-------+-------+----+----------------------------------------------+
|HO ODUk|LO ODUj|TPN | TPN Assignment Rules | |HO ODUk|LO ODUj|TPN | TPN Assignment Rules |
+-------+-------+----+----------------------------------------------+ +-------+-------+----+----------------------------------------------+
| ODU2 | ODU1 |1~4 |Fixed, = TS# occupied by ODU1 | | ODU2 | ODU1 |1~4 |Fixed, = TS# occupied by ODU1 |
+-------+-------+----+----------------------------------------------+ +-------+-------+----+----------------------------------------------+
| | ODU1 |1~16|Fixed, = TS# occupied by ODU1 | | | ODU1 |1~16|Fixed, = TS# occupied by ODU1 |
| ODU3 +-------+----+----------------------------------------------+ | ODU3 +-------+----+----------------------------------------------+
| | ODU2 |1~4 |Flexible, != other existing LO ODU2s' TPNs | | | ODU2 |1~4 |Flexible, != other existing LO ODU2s' TPNs |
skipping to change at page 13, line 27 skipping to change at page 12, line 45
| | ODU2 |1~4 |Flexible, != other existing LO ODU2s' TPNs | | | ODU2 |1~4 |Flexible, != other existing LO ODU2s' TPNs |
| ODU3 +-------+----+----------------------------------------------+ | ODU3 +-------+----+----------------------------------------------+
| |ODU0 & | |Flexible, != other existing LO ODU0s and | | |ODU0 & | |Flexible, != other existing LO ODU0s and |
| |ODU2e &|1~32|ODU2es and ODUflexes' TPNs | | |ODU2e &|1~32|ODU2es and ODUflexes' TPNs |
| |ODUflex| | | | |ODUflex| | |
+-------+-------+----+----------------------------------------------+ +-------+-------+----+----------------------------------------------+
| ODU4 |Any ODU|1~80|Flexible, != ANY other existing LO ODUs' TPNs | | ODU4 |Any ODU|1~80|Flexible, != ANY other existing LO ODUs' TPNs |
+-------+-------+----+----------------------------------------------+ +-------+-------+----+----------------------------------------------+
Note that in the case of "Flexible", the value of TPN MAY not be Note that in the case of "Flexible", the value of TPN MAY not be
corresponding to the TS number as per [G709-V3]. corresponding to the TS number as per [G709-2012].
Length (12 bits): indicates the number of bit of the Bit Map field, Length (12 bits): indicates the number of bits of the Bit Map field,
i.e., the total number of TS in the HO ODUk link. i.e., the total number of TS in the HO ODUk link. The valid values
for this field are 0, 2, 4, 8, 16, 32 and 80.
In case of an ODUk mapped into OTUk, there is no need to indicate In case of an ODUk mapped into OTUk, there is no need to indicate
which tributary slots will be used, so the length field MUST be set which tributary slots will be used, so the length field MUST be set
to 0. to 0.
Bit Map (variable): indicates which tributary slots in HO ODUk that Bit Map (variable): indicates which tributary slots in HO ODUk that
the LO ODUj will be multiplexed into. The sequence of the Bit Map is the LO ODUj will be multiplexed into. The sequence of the Bit Map is
consistent with the sequence of the tributary slots in HO ODUk. Each consistent with the sequence of the tributary slots in HO ODUk. Each
bit in the bit map represents the corresponding tributary slot in HO bit in the bit map represents the corresponding tributary slot in HO
ODUk with a value of 1 or 0 indicating whether the tributary slot ODUk with a value of 1 or 0 indicating whether the tributary slot
will be used by LO ODUj or not. will be used by LO ODUj or not.
Padded bits are added behind the Bit Map to make the whole label a Padding bits are added after the Bit Map to make the whole label a
multiple of four bytes if necessary. Padded bit MUST be set to 0 and multiple of four bytes if necessary. Padding bits MUST be set to 0
MUST be ignored. and MUST be ignored.
Note that the Length field in the label format MAY also be used to 6.2. Procedures
When a node receives a generalized label request for setting up an
ODUj 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 free resources (i.e., free tributary slots of ODUk) that will be
reserved for the LSP, and send the label to its upstream neighbor
node.
In case of ODUj to ODUk multiplexing, the node MUST firstly determine
the size of the Bit Map field according to the signal 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 slots. The node
MUST also assign a valid TPN, which MUST NOT collide with other TPN
value used by existing LO ODU connections in the selected HO ODU
link, and configure the Expected MSI (ExMSI) using this TPN. Then,
the assigned TPN MUST be filled into the label.
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 Length field
MUST be set to 0 as well.
The node receiving a OTN-TDM generalized label MUST firstly identify
which ODU signal type is multiplexed or mapped into which ODU signal
type accordingly to the traffic parameters and the IF_ID RSVP_HOP
Object in the received message.
In case of ODUj to ODUk multiplexing, the node MUST retrieve the
reserved tributary slots in the ODUk by its downstream neighbor node
according to the position of the bits that are set to 1 in the Bit
Map field. The node determines the TS type (according to the total TS
number of the ODUk, or pre-configured TS type), so that the node,
based on the TS type, can multiplex the ODUj into the ODUk. The node
MUST also retrieve the TPN value assigned by its downstream neighbor
node from the label, and fill the TPN into the related MSI byte(s) in
the OPUk overhead in the data plane, so that the downstream neighbor
node can check whether the TPN received from the data plane is
consistent with the ExMSI and determine whether there is any mismatch
defect.
Note that the Length field in the label format MAY be used to
indicate the TS type of the HO ODUk (i.e., TS granularity at 1.25Gbps indicate the TS type of the HO ODUk (i.e., TS granularity at 1.25Gbps
or 2.5Gbps) since the HO ODUk type can be known from IF_ID RSVP_HOP or 2.5Gbps) since the HO ODUk type can be known from IF_ID RSVP_HOP
Object. In some cases when there is no LMP (Link Management Protocol) Object. In some cases when there is no Link Management Protocol (LMP)
or routing to make the two end points of the link to know the TSG, or routing to make the two end points of the link to know the TSG,
the TSG information used by another end can be deduced from the label the TSG information used by another end can be deduced from the label
format. For example, for HO ODU2 link, the value of the length filed format. For example, for HO ODU2 link, the value of the length filed
will be 4 or 8, which indicates the TS granularity is 2.5Gbps or will be 4 or 8, which indicates the TS granularity is 2.5Gbps or
1.25Gbps, respectively. 1.25Gbps, respectively.
6.2. Examples In case of ODUk to OTUk mapping, the size of Bit Map field MUST be 0
and no additional procedure is needed.
In order to create bidirectional LSP, an upstream node MUST generate
an Upstream Label on the out outgoing interface to indicate the
reserved TSs of ODUk and the assigned TPN value in the upstream
direction. This Upstream Label is sent to the downstream node via
Path massage for upstream resource reservation.
The upstream node MAY generate Label Set to indicate which labels on
the outgoing interface in the downstream direction are acceptable.
The downstream node will restrict its choice of labels, i.e., TS
resource and TPN value, to one which is in the Label Set.
The upstream node MAY also generate Suggested Label to indicate the
preference of TS resource and TPN value on the outgoing interface in
the downstream direction. The downstream node is not REQUIRED to use
the Suggested Label and MAY use another label based on local decision
and send it to the upstream node, as described in [RFC3473].
The ingress node of an LSP MAY include label ERO to indicate the
label in each hops along the path. Note that the TPN in the label ERO
(Explicit Route Object) subobject MAY not be assigned by the ingress
node. In this case, the node MUST assign a valid TPN value and then
put this value into TPN field of the label object when receiving a
Path message.
6.2.1. Notification on Label Error
When receiving an OTN-TDM label from the neighbor node, the node MUST
check whether the label is acceptable. An error message containing an
"Unacceptable label value" indication ([RFC3209]) MUST be sent if one
of the following cases occurs:
- Invalid value in the length field;
- The selected link only supports 2.5Gbps TS granularity while the
Length field in the label along with ODUk signal type indicates
the 1.25Gbps TS granularity;
- The label includes an invalid TPN value that breaks the TPN
assignment rules;
- The indicated resources (i.e., the number of "1" in the Bit Map
field) are inconsistent with the Traffic Parameters.
6.3. Supporting Virtual Concatenation and Multiplication
Per [RFC6344], the Virtual Concatenation Groups (VCGs) can be created
using Co-Signaled style or Multiple LSPs style.
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].
In case of multiplexed virtually concatenated signals (NVC > 1), the
first label MUST indicate the components of the first virtually
concatenated signal; the second label MUST indicate the components of
the second virtually concatenated signal; and so on. In case of
multiplication of multiplexed virtually concatenated signals (MT >
1), the first label MUST indicate the components of the first
multiplexed virtually concatenated signal; the second label MUST
indicate components of the second multiplexed virtually concatenated
signal; and so on.
In case of Multiple LSPs style, multiple control plane LSPs are
created with a single VCG and the VCAT Call SHOULD be used to
associate the control plane LSPs. The procedures are similar to
section 6 of [RFC6344].
6.4. Examples
The following examples are given in order to illustrate the label The following examples are given in order to illustrate the label
format described in the previous sections of this document. format described in Section 5.1 of this document.
(1) ODUk into OTUk mapping: (1) ODUk into OTUk mapping:
In such conditions, the downstream node along an LSP returns a label In such conditions, the downstream node along an LSP returns a label
indicating that the ODUk (k=1, 2, 3, 4) is directly mapped into the indicating that the ODUk (k=1, 2, 3, 4) is directly mapped into the
corresponding OTUk. The following example label indicates an ODU1 corresponding OTUk. The following example label indicates an ODU1
mapped into OTU1. mapped into OTU1.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
skipping to change at page 15, line 28 skipping to change at page 17, line 14
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TPN = 1 | Reserved | Length = 16 | | TPN = 1 | Reserved | Length = 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 1 1 0 1 0 1 0 0 0 0 0 0 0 0 0| Padded Bits (0) | |0 1 1 0 1 0 1 0 0 0 0 0 0 0 0 0| Padded Bits (0) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
This above label indicates an ODU2 multiplexed into the 2nd, 3rd, 5th This above label indicates an ODU2 multiplexed into the 2nd, 3rd, 5th
and 7th tributary slot of ODU3, wherein there are 16 TS in ODU3 (i.e., and 7th tributary slot of ODU3, wherein there are 16 TS in ODU3
the type of the tributary slot is 2.5Gbps), and the TPN value is 1. (i.e., the type of the tributary slot is 2.5Gbps), and the TPN value
is 1.
6.3. Label Distribution Procedure
This document does not change the existing label distribution
procedures [RFC4328] for GMPLS except that the new ODUk label MUST be
processed as follows.
When a node receives a generalized label request for setting up an
ODUj LSP from its upstream neighbor node, the node MUST generate an
ODU label according to the signal type of the requested LSP and the
free resources (i.e., free tributary slots of ODUk) that will be
reserved for the LSP, and send the label to its upstream neighbor
node.
In case of ODUj to ODUk multiplexing, the node MUST firstly 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 1 in the Bit
Map field corresponding to the reserved tributary slots. The node
MUST also assign a valid TPN, which MUST not collide with other TPN
value used by existing LO ODU connections in the selected HO ODU link,
and configure the expected multiplex structure identifier (ExMSI)
using this TPN. Then, the assigned TPN MUST be filled into the label.
In case of ODUk to OTUk mapping, TPN field MUST be set to 0. Bit Map
information is not REQUIRED and MUST not be included, so Length field
MUST be set to 0 as well.
In order to process a received ODU label, the node MUST firstly learn
which ODU signal type is multiplexed or mapped into which ODU signal
type accordingly to the traffic parameters and the IF_ID RSVP_HOP
Object in the received message.
In case of ODUj to ODUk multiplexing, the node MUST retrieve the
reserved tributary slots in the ODUk by its downstream neighbor node
according to the position of the bits that are set to 1 in the Bit
Map field. The node determines the TS type (according to the total TS
number of the ODUk, or pre-configured TS type), so that the node,
based on the TS type, can multiplex the ODUj into the ODUk. The node
MUST also retrieve the TPN value assigned by its downstream neighbor
node from the label, and fill the TPN into the related MSI byte(s) in
the OPUk overhead in the data plane, so that the downstream neighbor
node can check whether the TPN received from the data plane is
consistent with the ExMSI and determine whether there is any mismatch
defect.
In case of ODUk to OTUk mapping, the size of Bit Map field MUST be 0
and no additional procedure is needed.
Note that the procedures of other label related objects (e.g.,
Upstream Label, Label Set) are similar to the one described above.
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.
6.3.1. Notification on Label Error
When receiving an ODUk label from the neighbor node, the node SHOULD
check the integrity of the label. An error message containing an
"Unacceptable label value" indication ([RFC3209]) SHOULD be sent if
one of the following cases occurs:
- Invalid value in the length field.
- The selected link only supports 2.5Gbps TS granularity while the
Length field in the label along with ODUk signal type indicates
the 1.25Gbps TS granularity;
- The label includes an invalid TPN value that breaks the TPN
assignment rules;
- The reserved resources (i.e., the number of "1" in the Bit Map
field) do not match with the Traffic Parameters.
6.4. Supporting Virtual Concatenation and Multiplication
As per [RFC6344], the VCGs can be created using Co-Signaled style or
Multiple LSPs style.
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
case of multiplexed virtually concatenated signals (NVC > 1), the
first label indicates the components of the first virtually
concatenated signal; the second label indicates the components of the
second virtually concatenated signal; and so on. In case of
multiplication of multiplexed virtually concatenated signals (MT > 1),
the first label indicates the components of the first multiplexed
virtually concatenated signal; the second label indicates components
of the second multiplexed virtually concatenated signal; and so on.
In case of Multiple LSPs style, multiple control plane LSPs are
created with a single VCG and the VCAT Call can be used to associate
the control plane LSPs. The procedures are similar to section 6 of
[RFC6344].
7. Supporting Hitless Adjustment of ODUflex (GFP) 7. Supporting Hitless Adjustment of ODUflex (GFP)
[G.7044] describes the procedure of ODUflex (GFP) hitless resizing [G7044] describes the procedure of ODUflex (GFP) hitless resizing
using LCR (Link Connection Resize) and BWR (Bandwidth Resize) using Link Connection Resize (LCR) and Bandwidth Resize (BWR)
protocols in OTN data plane. protocols in OTN data plane.
For the control plane, signaling messages are REQUIRED to initiate For the control plane, signaling messages are REQUIRED to initiate
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 Shared Explicit (SE) style is used in Traffic
bandwidth increasing and decreasing, which SHOULD be still applicable Engineering (TE) network for bandwidth increasing and decreasing,
for triggering the ODUflex (GFP) adjustment procedure in data plane. which is still applicable for triggering the ODUflex (GFP) adjustment
procedure in data plane.
Note that the SE style SHOULD be used at the beginning when creating Note that the SE style MUST be used at the beginning when creating a
a resizable ODUflex connection (Signal Type = 21). Otherwise an error resizable ODUflex connection (Signal Type = 21). Otherwise an error
with Error Code "Conflicting reservation style" SHOULD be generated with Error Code "Conflicting reservation style" MUST be generated
when performing bandwidth adjustment. when performing bandwidth adjustment.
- Bandwidth increasing - Bandwidth increasing
In order to increase the bandwidth of an ODUflex (GFP) connection, In order to increase the bandwidth of an ODUflex (GFP)
a Path message with SE style (keeping Tunnel ID unchanged and connection, a Path message with SE style (keeping Tunnel ID
assigning a new LSP ID) is sent along the path. unchanged and assigning a new LSP ID) MUST be sent along the
path.
A downstream node compares the old Traffic Parameters (stored A downstream node compares the old Traffic Parameters (stored
locally) with the new one carried in the Path message, to locally) with the new one carried in the Path message, to
determine the number of TS to be added. After choosing and determine the number of TS to be added. After choosing and
reserving new free TS, the downstream node sends back a Resv reserving new free TS, the downstream node MUST send back a Resv
message carrying both the old and new LABEL Objects in the SE message carrying both the old and new LABEL Objects in the SE
flow descriptor, so that its upstream neighbor can determine flow descriptor, so that its upstream neighbor can determine
which TS are added. And the LCR protocol between each pair of which TS are added. And the LCR protocol between each pair of
neighbor nodes is triggered. neighbor nodes MUST be triggered.
On the source node, the BWR protocol will be triggered by the On the source node, the BWR protocol will be triggered by the
successful completion of LCR protocols on every hop after Resv successful completion of LCR protocols on every hop after Resv
message is processed. On success of BWR, the source node SHOULD message is processed. On success of BWR, the source node MUST
send a PathTear message to delete the old control state (i.e., send a PathTear message to delete the old control state (i.e.,
the control state of the ODUflex (GFP) before resizing) on the the control state of the ODUflex (GFP) before resizing) on the
control plane. control plane.
- Bandwidth decreasing - Bandwidth decreasing
The SE style SHOULD also be used for ODUflex bandwidth decreasing. The SE style SHOULD also be used for ODUflex bandwidth
For each pair of neighbor nodes, the sending and receiving Resv decreasing. For each pair of neighbor nodes, the sending and
message with old and new LABEL Objects will trigger the first receiving Resv message with old and new LABEL Objects will
step of LCR between them to perform LCR handshake. On the source trigger the first step of LCR between them to perform LCR
node, the BWR protocol will be triggered by the successful handshake. On the source node, the BWR protocol will be triggered
completion of LCR handshake on every hop after Resv message is by the successful completion of LCR handshake on every hop after
processed. On success of BWR, the second step of LCR, i.e., link Resv message is processed. On success of BWR, the second step of
connection decrease procedure will be started on every hop of the LCR, i.e., link connection decrease procedure will be started on
connection. every hop of the connection.
Similarly, after completion of bandwidth decreasing, a ResvErr Similarly, after completion of bandwidth decreasing, a ResvErr
message SHOULD be sent to tear down the old control state. message SHOULD be sent to tear down the old control state.
8. Control Plane Backward Compatibility Considerations 8. Control Plane Backward Compatibility Considerations
As described in [OTN-FWK], since the [RFC4328] has been deployed in As described in [OTN-FWK], since the [RFC4328] has been deployed in
the network for the nodes that support [G709-V1], control plane the network for the nodes that support the 2001 revision of the G.709
backward compatibility SHOULD be taken into consideration. More specification, control plane backward compatibility SHOULD be taken
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 9. Security Considerations
This document introduces no new security considerations to the This document introduces no new security considerations to the
existing GMPLS signaling protocols. Referring to [RFC3473], further existing GMPLS signaling protocols. Referring to [RFC3473] and
details of the specific security measures are provided. Additionally, [RFC4328], further details of the specific security measures are
[GMPLS-SEC] provides an overview of security vulnerabilities and provided. Additionally, [RFC5920] provides an overview of security
protection mechanisms for the GMPLS control plane. vulnerabilities and protection mechanisms for the GMPLS control
plane.
10. IANA Considerations 10. IANA Considerations
- G.709 SENDER_TSPEC and FLOWSPEC objects: Three RSVP C-Types are defined for OTN-TDM Traffic Parameters and
OTN-TDM Generalized Label in this document.
The traffic parameters, which are carried in the G.709 - OTN-TDM SENDER_TSPEC and FLOWSPEC objects:
SENDER_TSPEC and FLOWSPEC objects, do not require any new object
class and type based on [RFC4328]:
o G.709 SENDER_TSPEC Object: Class = 12, C-Type = 5 [RFC4328] o OTN-TDM SENDER_TSPEC Object: Class = 12, C-Type = 7 (see
Section 4)
o G.709 FLOWSPEC Object: Class = 9, C-Type = 5 [RFC4328] o OTN-TDM FLOWSPEC Object: Class = 9, C-Type = 7 (see Section 4)
- Generalized Label Object: - OTN-TDM Generalized Label Object:
The new defined ODU label (Section 6) is a kind of generalized o OTN-TDM Generalized Label Object: Class = 16, C-Type = 2 (see
label. Therefore, the Class-Num and C-Type of the ODU label is Section 5.1)
the same as that of generalized label described in [RFC3473],
i.e., Class-Num = 16, C-Type = 2. IANA will also track the code-point spaces extended and/or updated by
this document. The Generalized PID has been added in the newly
requested registry entry:
- Generalized PID (G-PID):
Name: G-PID
Format: 16-bit number
Values:
[0..31, 36..46] defined in [RFC3471]
[32] defined in [RFC3471] and updated by Section 3
[33..35] defined in [RFC3471] and updated by [RFC4328]
[47, 49..52] defined in [RFC4328] and updated by Section 3
[48, 53..58] defined in [RFC4328]
[59..63] defined in Section 3
Allocation Policy (as defined in [RFC4328]):
[0..31743] Assigned by IANA via IETF Standards Track RFC
Action.
[31744..32767] Assigned temporarily for Experimental Usage
[32768..65535] Not assigned. Before any assignments can be
made in this range, there MUST be a Standards
Track RFC that specifies IANA Considerations
that covers the range being assigned.
11. References 11. References
11.1. Normative References 11.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4328] D. Papadimitriou, Ed. "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling Extensions for G.709 Optical
Transport Networks Control", RFC 4328, Jan 2006.
[RFC3209] D. Awduche et al, "RSVP-TE: Extensions to RSVP for LSP [RFC3209] D. Awduche et al, "RSVP-TE: Extensions to RSVP for LSP
Tunnels", RFC3209, December 2001. Tunnels", RFC3209, December 2001.
[RFC3471] Berger, L., Editor, "Generalized Multi-Protocol Label [RFC3471] Berger, L., Editor, "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling Functional Description", RFC Switching (GMPLS) Signaling Functional Description", RFC
3471, January 2003. 3471, January 2003.
[RFC3473] L. Berger, Ed., "Generalized Multi-Protocol Label Switching [RFC3473] L. Berger, Ed., "Generalized Multi-Protocol Label Switching
(GMPLS) Signaling Resource ReserVation Protocol-Traffic (GMPLS) Signaling Resource ReserVation Protocol-Traffic
Engineering (RSVP-TE) Extensions", RFC 3473, January 2003. Engineering (RSVP-TE) Extensions", RFC 3473, January 2003.
[RFC3945] Mannie, E., "Generalized Multi-Protocol Label Switching [RFC4328] D. Papadimitriou, Ed. "Generalized Multi-Protocol Label
(GMPLS) Architecture", RFC 3945, October 2004. Switching (GMPLS) Signaling Extensions for G.709 Optical
Transport Networks Control", RFC 4328, Jan 2006.
[RFC6344] G. Bernstein et al, "Operating Virtual Concatenation (VCAT) [RFC6344] G. Bernstein et al, "Operating Virtual Concatenation (VCAT)
and the Link Capacity Adjustment Scheme (LCAS) with and the Link Capacity Adjustment Scheme (LCAS) with
Generalized Multi-Protocol Label Switching (GMPLS)", Generalized Multi-Protocol Label Switching (GMPLS)",
RFC6344, August 2011. RFC6344, August 2011.
[OTN-FWK] Fatai Zhang et al, "Framework for GMPLS and PCE Control of
G.709 Optical Transport Networks", draft-ietf-ccamp-gmpls-
g709-framework, Work in Progress, August 2012.
[OTN-INFO] S. Belotti et al, "Information model for G.709 Optical
Transport Networks (OTN)", draft-ietf-ccamp-otn-g709-info-
model, Work in Progress, July 2012.
[OTN-OSPF] D. Ceccarelli et al, "Traffic Engineering Extensions to
OSPF for Generalized MPLS (GMPLS) Control of Evolving G.709
OTN Networks", draft-ietf-ccamp-gmpls-ospf-g709v3, Work in
Progress, April 2012.
[G709-V3] ITU-T, "Interfaces for the Optical Transport Network (OTN)
", G.709/Y.1331, December 2009.
[G709-V3-A2] ITU-T, "Interfaces for the Optical Transport Network
(OTN) Amendment 2", G.709/y.1331 Amendment 2, April 2011.
11.2. Informative References 11.2. Informative References
[G709-V1] ITU-T, "Interface for the Optical Transport Network (OTN)," [OTN-FWK] Fatai Zhang et al, "Framework for GMPLS and PCE Control of
G.709 Recommendation (and Amendment 1), February 2001 G.709 Optical Transport Networks", Work in Progress: draft-
(November 2001). ietf-ccamp-gmpls-g709-framework, November 2012.
[G709-V2] ITU-T, "Interface for the Optical Transport Network (OTN)," [OTN-INFO] S. Belotti et al, "Information model for G.709 Optical
G.709 Recommendation, March 2003. Transport Networks (OTN)", Work in Progress: draft-ietf-
ccamp-otn-g709-info-model, November 2012.
[G798-V2] ITU-T, "Characteristics of optical transport network [OTN-OSPF] D. Ceccarelli et al, "Traffic Engineering Extensions to
hierarchy equipment functional blocks", G.798, December OSPF for Generalized MPLS (GMPLS) Control of Evolving G.709
2006. OTN Networks", Work in Progress: draft-ietf-ccamp-gmpls-
ospf-g709v3, November 2012.
[G798-V3] ITU-T, "Characteristics of optical transport network [G709-2012] ITU-T, "Interfaces for the Optical Transport Network
hierarchy equipment functional blocks", G.798v3, consented (OTN)", G.709/Y.1331 Recommendation, February 2012.
June 2010.
[G.7044] ITU-T, "Hitless adjustment of ODUflex", G.7044 (and [G7044] ITU-T, "Hitless adjustment of ODUflex", G.7044/Y.1347,
Amendment 1), February 2012. October 2011.
[RFC4506] M. Eisler, Ed., "XDR: External Data Representation [RFC4506] M. Eisler, Ed., "XDR: External Data Representation
Standard", RFC 4506, May 2006. Standard", RFC 4506, May 2006.
[IEEE] "IEEE Standard for Binary Floating-Point Arithmetic", [RFC5920] Fang, L., Ed., "Security Framework for MPLS and GMPLS
Networks", RFC5920, July 2010.
[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.
[GMPLS-SEC] Fang, L., Ed., "Security Framework for MPLS and GMPLS
Networks", Work in Progress, October 2009.
12. Contributors 12. Contributors
Jonathan Sadler, Tellabs Jonathan Sadler, Tellabs
Email: jonathan.sadler@tellabs.com Email: jonathan.sadler@tellabs.com
Kam LAM, Alcatel-Lucent Kam LAM, Alcatel-Lucent
Email: kam.lam@alcatel-lucent.com Email: kam.lam@alcatel-lucent.com
Xiaobing Zi, Huawei Technologies Xiaobing Zi, Huawei Technologies
Email: zixiaobing@huawei.com Email: zixiaobing@huawei.com
skipping to change at page 26, line 7 skipping to change at page 26, line 7
on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
WARRANTY THAT THE USE OF THE INFORMATION THEREIN WILL NOT INFRINGE WARRANTY THAT THE USE OF THE INFORMATION THEREIN WILL NOT INFRINGE
ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. FOR A PARTICULAR PURPOSE.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
 End of changes. 101 change blocks. 
394 lines changed or deleted 384 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/