draft-ietf-ccamp-gmpls-ospf-g709v3-09.txt   draft-ietf-ccamp-gmpls-ospf-g709v3-10.txt 
CCAMP Working Group D. Ceccarelli, Ed. CCAMP Working Group D. Ceccarelli, Ed.
Internet-Draft Ericsson Internet-Draft Ericsson
Intended status: Standards Track F. Zhang Intended status: Standards Track F. Zhang
Expires: April 4, 2014 Huawei Technologies Expires: April 24, 2014 Huawei Technologies
S. Belotti S. Belotti
Alcatel-Lucent Alcatel-Lucent
R. Rao R. Rao
Infinera Corporation Infinera Corporation
J. Drake J. Drake
Juniper Juniper
October 1, 2013 October 21, 2013
Traffic Engineering Extensions to OSPF for Generalized MPLS (GMPLS) Traffic Engineering Extensions to OSPF for Generalized MPLS (GMPLS)
Control of Evolving G.709 OTN Networks Control of Evolving G.709 OTN Networks
draft-ietf-ccamp-gmpls-ospf-g709v3-09 draft-ietf-ccamp-gmpls-ospf-g709v3-10
Abstract Abstract
This document describes Open Shortest Path First - Traffic This document describes Open Shortest Path First - Traffic
Engineering (OSPF-TE) routing protocol extensions to support Engineering (OSPF-TE) routing protocol extensions to support
Generalized MPLS (GMPLS) control of Optical Transport Networks (OTN) Generalized MPLS (GMPLS) control of Optical Transport Networks (OTN)
specified in ITU-T Recommendation G.709 as published in 2012. It specified in ITU-T Recommendation G.709 as published in 2012. It
extends mechanisms defined in RFC4203. extends mechanisms defined in RFC4203.
Status of this Memo Status of this Memo
skipping to change at page 1, line 42 skipping to change at page 1, line 42
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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."
This Internet-Draft will expire on April 4, 2014. This Internet-Draft will expire on April 24, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 19 skipping to change at page 2, line 19
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. OSPF-TE Extensions . . . . . . . . . . . . . . . . . . . . . . 3 2. OSPF-TE Extensions . . . . . . . . . . . . . . . . . . . . . . 3
3. TE-Link Representation . . . . . . . . . . . . . . . . . . . . 5 3. TE-Link Representation . . . . . . . . . . . . . . . . . . . . 5
4. ISCD format extensions . . . . . . . . . . . . . . . . . . . . 5 4. ISCD format extensions . . . . . . . . . . . . . . . . . . . . 6
4.1. Switching Capability Specific Information . . . . . . . . 7 4.1. Switching Capability Specific Information . . . . . . . . 7
4.1.1. Switching Capability Specific Information for 4.1.1. Switching Capability Specific Information for
fixed containers . . . . . . . . . . . . . . . . . . . 8 fixed containers . . . . . . . . . . . . . . . . . . . 8
4.1.2. Switching Capability Specific Information for 4.1.2. Switching Capability Specific Information for
variable containers . . . . . . . . . . . . . . . . . 8 variable containers . . . . . . . . . . . . . . . . . 8
4.1.3. Switching Capability Specific Information - Field 4.1.3. Switching Capability Specific Information - Field
values and explanation . . . . . . . . . . . . . . . . 9 values and explanation . . . . . . . . . . . . . . . . 9
5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.1. MAX LSP Bandwidth fields in the ISCD . . . . . . . . . . . 12 5.1. MAX LSP Bandwidth fields in the ISCD . . . . . . . . . . . 12
5.2. Example of T,S and TS granularity utilization . . . . . . 14 5.2. Example of T,S and TS granularity utilization . . . . . . 14
5.2.1. Example of different TS Granularities . . . . . . . . 15 5.2.1. Example of different TS Granularities . . . . . . . . 15
5.3. Example of ODUflex advertisement . . . . . . . . . . . . . 17 5.3. Example of ODUflex advertisement . . . . . . . . . . . . . 18
5.4. Example of single stage muxing . . . . . . . . . . . . . . 20 5.4. Example of single stage muxing . . . . . . . . . . . . . . 20
5.5. Example of multi stage muxing - Unbundled link . . . . . . 22 5.5. Example of multi stage muxing - Unbundled link . . . . . . 22
5.6. Example of multi stage muxing - Bundled links . . . . . . 24 5.6. Example of multi stage muxing - Bundled links . . . . . . 24
5.7. Example of component links with non homogeneous 5.7. Example of component links with non-homogeneous
hierarchies . . . . . . . . . . . . . . . . . . . . . . . 25 hierarchies . . . . . . . . . . . . . . . . . . . . . . . 25
6. Compatibility . . . . . . . . . . . . . . . . . . . . . . . . 27 6. OSPFv2 scalability . . . . . . . . . . . . . . . . . . . . . . 28
7. Security Considerations . . . . . . . . . . . . . . . . . . . 28 7. Compatibility . . . . . . . . . . . . . . . . . . . . . . . . 29
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 8. Security Considerations . . . . . . . . . . . . . . . . . . . 29
8.1. Switching types . . . . . . . . . . . . . . . . . . . . . 28 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29
8.2. New TLVs . . . . . . . . . . . . . . . . . . . . . . . . . 28 9.1. Switching types . . . . . . . . . . . . . . . . . . . . . 29
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 29 9.2. New sub-TLVs . . . . . . . . . . . . . . . . . . . . . . . 30
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 31 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 30
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 32 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 33
11.1. Normative References . . . . . . . . . . . . . . . . . . . 32 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 33
11.2. Informative References . . . . . . . . . . . . . . . . . . 32 12.1. Normative References . . . . . . . . . . . . . . . . . . . 33
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 33 12.2. Informative References . . . . . . . . . . . . . . . . . . 33
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 34
1. Introduction 1. Introduction
G.709 Optical Transport Network (OTN) [G.709-2012] includes new fixed G.709 Optical Transport Network (OTN) [G.709-2012] includes new fixed
and flexible ODU (Optical channel Data Unit) containers, two types of and flexible ODU (Optical channel Data Unit) containers, two types of
Tributary Slots (i.e. 1.25Gbps and 2.5Gbps), and supports various Tributary Slots (i.e., 1.25Gbps and 2.5Gbps), and supports various
multiplexing relationships (e.g., ODUj multiplexed into ODUk (j<k)), multiplexing relationships (e.g., ODUj multiplexed into ODUk (j<k)),
two different tributary slots for ODUk (K=1, 2, 3) and ODUflex two different tributary slots for ODUk (K=1, 2, 3) and ODUflex
service type. In order to present this information in routing, this service type. In order to present this information in routing, this
document provides OTN technology specific encoding for use in GMPLS document provides OTN technology specific encoding for use in GMPLS
OSPF-TE as defined in [RFC4203]. OSPF-TE as defined in [RFC4203].
For a short overview of OTN evolution and implications of OTN For a short overview of OTN evolution and implications of OTN
requirements on GMPLS routing please refer to [OTN-FWK]. The requirements on GMPLS routing please refer to [OTN-FWK]. The
information model and an evaluation against the current solution are information model and an evaluation against the current solution are
provided in [OTN-INFO]. provided in [OTN-INFO].
Routing information for Optical Channel Layer (OCh) (i.e. wavelength) Routing information for Optical Channel Layer (OCh) (i.e.,
is out of the scope of this document. Please refer to [RFC6163] and wavelength) is beyond the scope of this document. Please refer to
[RFC6566] for further information. [RFC6163] and [RFC6566] for further information.
The reader is supposed to be familiar with OTN framework [OTN-FWK]
and GMPLS evaluation against OTN [OTN-INFO].
1.1. Terminology 1.1. 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].
2. OSPF-TE Extensions 2. OSPF-TE Extensions
In terms of GMPLS based OTN networks, each OTUk can be viewed as a In terms of GMPLS based OTN networks, each OTUk can be viewed as a
skipping to change at page 3, line 45 skipping to change at page 3, line 48
of ODUj (j<k). of ODUj (j<k).
Each TE Link State Advertisement (LSA) can carry a top-level link Each TE Link State Advertisement (LSA) can carry a top-level link
Type Length Value (TLV) with several nested sub-TLVs to describe Type Length Value (TLV) with several nested sub-TLVs to describe
different attributes of a TE link. Two top-level TLVs are defined in different attributes of a TE link. Two top-level TLVs are defined in
[RFC3630]. (1) The Router Address TLV (referred to as the Node TLV) [RFC3630]. (1) The Router Address TLV (referred to as the Node TLV)
and (2) the TE link TLV. One or more sub-TLVs can be nested into the and (2) the TE link TLV. One or more sub-TLVs can be nested into the
two top-level TLVs. The sub-TLV set for the two top-level TLVs are two top-level TLVs. The sub-TLV set for the two top-level TLVs are
also defined in [RFC3630] and [RFC4203]. also defined in [RFC3630] and [RFC4203].
As discussed in [OTN-FWK] and [OTN-INFO], OSPF-TE must be extended so As discussed in [OTN-FWK] and [OTN-INFO], OSPF-TE must be extended to
to be able to advertise the termination and switching capabilities be able to advertise the termination and switching capabilities of
related to each different ODUj and ODUk/OTUk (Optical Transport Unit) each different ODUj and ODUk/OTUk (Optical Transport Unit) and the
and the advertisement of related multiplexing capabilities. These advertisement of related multiplexing capabilities. These
capabilities are carried in the Interface Switching Capability capabilities are carried in the Interface Switching Capability
Descriptor (ISCD) Switching Capability-specific information field Descriptor (ISCD) Switching Capability-specific information field
using formats defined in this document. As discussed in [SWCAP- using formats defined in this document. As discussed in [SWCAP-
UPDT], the use of a technology specific Switching Capability-specific UPDT], the use of a technology specific Switching Capability-specific
information field necessitates the definition of a new Switching information field necessitates the definition of a new Switching
Capability value and associated new Switching Capability. Capability value and associated new Switching Capability.
In the following we will use ODUj to indicate a service type that is In the following, we will use ODUj to indicate a service type that is
multiplexed into a higher order ODU, ODUk to indicate a higher order multiplexed into a higher order ODU, ODUk to indicate a higher order
ODU including an ODUj and ODUk/OTUk to indicate the layer mapped into ODU including an ODUj and ODUk/OTUk to indicate the layer mapped into
the OTUk. Moreover ODUj(S) and ODUk(S) are used to indicate ODUj and the OTUk. Moreover, ODUj(S) and ODUk(S) are used to indicate ODUj
ODUk supporting switching capability only, and the ODUj->ODUk format and ODUk supporting switching capability only, and the ODUj->ODUk
is used to indicate the ODUj into ODUk multiplexing capability. format is used to indicate the ODUj into ODUk multiplexing
capability.
This notation can be repeated as needed depending on the number of This notation can be repeated as needed depending on the number of
multiplexing levels. In the following the term "multiplexing tree" multiplexing levels. In the following, the term "multiplexing tree"
is used to identify a multiplexing hierarchy where the root is always is used to identify a multiplexing hierarchy where the root is always
a server ODUk/OTUk and any other supported multiplexed container is a server ODUk/OTUk and any other supported multiplexed container is
represented with increasing granularity until reaching the leaf of represented with increasing granularity until reaching the leaf of
the tree. The tree can be structured with more than one branch if the tree. The tree can be structured with more than one branch if
the server ODUk/OTUk supports more than one hierarchy. the server ODUk/OTUk supports more than one hierarchy.
If for example a multiplexing hierarchy like the following one is For example, if a multiplexing or example a multiplexing hierarchy
considered: like the following one is considered:
ODU2 ODU0 ODUflex ODU0 ODU2 ODU0 ODUflex ODU0
\ / \ / \ / \ /
| | | |
ODU3 ODU2 ODU3 ODU2
\ / \ /
\ / \ /
\ / \ /
\ / \ /
ODU4 ODU4
skipping to change at page 5, line 26 skipping to change at page 5, line 28
|Switch |<- OTUk Link ->|Switch |<- OTUk Link ->|Switch | |Switch |<- OTUk Link ->|Switch |<- OTUk Link ->|Switch |
| A | | B | | C | | A | | B | | C |
+-------+ +-------+ +-------+ +-------+ +-------+ +-------+
|<-- TE-Link -->| |<-- TE-Link -->| |<-- TE-Link -->| |<-- TE-Link -->|
Figure 1: OTUk TE-Links Figure 1: OTUk TE-Links
It is possible to create TE-Links that span more than one hop by It is possible to create TE-Links that span more than one hop by
creating FAs between non-adjacent nodes (see Figure 2). As in the creating FAs between non-adjacent nodes (see Figure 2). As in the
one hop case multiple hop TE-links advertise ODU switching capacity. one hop case, multiple hop TE-links advertise ODU switching capacity.
+-------+ +-------+ +-------+ +-------+ +-------+ +-------+
| OTN | | OTN | | OTN | | OTN | | OTN | | OTN |
|Switch |<- OTUk Link ->|Switch |<- OTUk Link ->|Switch | |Switch |<- OTUk Link ->|Switch |<- OTUk Link ->|Switch |
| A | | B | | C | | A | | B | | C |
+-------+ +-------+ +-------+ +-------+ +-------+ +-------+
ODUk Switched ODUk Switched
|<------------- ODUk Link ------------->| |<------------- ODUk Link ------------->|
|<-------------- TE-Link--------------->| |<-------------- TE-Link--------------->|
skipping to change at page 6, line 7 skipping to change at page 6, line 15
4. ISCD format extensions 4. ISCD format extensions
The ISCD describes the switching capability of an interface and is The ISCD describes the switching capability of an interface and is
defined in [RFC4203]. This document defines a new Switching defined in [RFC4203]. This document defines a new Switching
Capability value for OTN [G.709-2012] as follows: Capability value for OTN [G.709-2012] as follows:
Value Type Value Type
----- ---- ----- ----
110 (TBA by IANA) OTN-TDM capable (OTN-TDM) 110 (TBA by IANA) OTN-TDM capable (OTN-TDM)
When supporting the extensions defined in this document, the When supporting the extensions defined in this document, for both
Switching Capability and Encoding values MUST be used as follows: fixed and flexible ODUs, the Switching Capability and Encoding values
MUST be used as follows:
- Switching Capability = OTN-TDM - Switching Capability = OTN-TDM
- Encoding Type = G.709 ODUk (Digital Path) as defined in [RFC4328] - Encoding Type = G.709 ODUk (Digital Path) as defined in [RFC4328]
Both for fixed and flexible ODUs the same switching type and encoding The same switching type and encoding values must be used for both
values MUST be used. When Switching Capability and Encoding fields fixed and flexible ODUs. When Switching Capability and Encoding
are set to values as stated above, the Interface Switching Capability fields are set to values as stated above, the Interface Switching
Descriptor MUST be interpreted as defined in [RFC4203]. Capability Descriptor MUST be interpreted as defined in [RFC4203].
Maximum LSP Bandwidth Maximum LSP Bandwidth
The MAX LSP Bandwidth field is used according to [RFC4203]: i.e. 0 <= The MAX LSP Bandwidth field is used according to [RFC4203]: i.e., 0
MAX LSP Bandwidth <= ODUk/OTUk and intermediate values are those on <= MAX LSP Bandwidth <= ODUk/OTUk, and intermediate values are those
the branch of OTN switching hierarchy supported by the interface. on the branch of OTN switching hierarchy supported by the interface.
E.g. in the OTU4 link it could be possible to have ODU4 as MAX LSP For example, in the OTU4 link it could be possible to have ODU4 as
Bandwidth for some priorities, ODU3 for others, ODU2 for some others MAX LSP Bandwidth for some priorities, ODU3 for others, ODU2 for some
etc. The bandwidth unit is in bytes per second and the encoding MUST others, etc. The bandwidth unit is in bytes per second and the
be in Institute of Electrical and Electronic Engineers (IEEE) encoding MUST be in Institute of Electrical and Electronic Engineers
floating point format. The discrete values for various ODUs is shown (IEEE) floating point format. The discrete values for various ODUs
in the table below (please note that there are 1000 bits in a kbit is shown in the table below (please note that there are 1000 bits in
according to normal practices in telecommunications). a kbit according to normal practices in telecommunications).
+---------------------+------------------------------+-----------------+ +---------------------+------------------------------+-----------------+
| ODU Type | ODU nominal bit rate |Value in Byte/Sec| | ODU Type | ODU nominal bit rate |Value in Byte/Sec|
| | |(floating p. val)| | | |(floating p. val)|
+---------------------+------------------------------+-----------------+ +---------------------+------------------------------+-----------------+
| ODU0 | 1 244 160 kbit/s | 0x4D1450C0 | | ODU0 | 1,244,160 kbit/s | 0x4D1450C0 |
| ODU1 | 239/238 x 2 488 320 kbit/s | 0x4D94F048 | | ODU1 | 239/238 x 2,488,320 kbit/s | 0x4D94F048 |
| ODU2 | 239/237 x 9 953 280 kbit/s | 0x4E959129 | | ODU2 | 239/237 x 9,953,280 kbit/s | 0x4E959129 |
| ODU3 | 239/236 x 39 813 120 kbit/s | 0x4F963367 | | ODU3 | 239/236 x 39,813,120 kbit/s | 0x4F963367 |
| ODU4 | 239/227 x 99 532 800 kbit/s | 0x504331E3 | | ODU4 | 239/227 x 99,532,800 kbit/s | 0x504331E3 |
| ODU2e | 239/237 x 10 312 500 kbit/s | 0x4E9AF70A | | ODU2e | 239/237 x 10,312,500 kbit/s | 0x4E9AF70A |
| | | |
| ODUflex for CBR | 239/238 x client signal | MAX LSP |
| Client signals | bit rate | BANDWIDTH |
| | | | | | | |
| ODUflex for CBR | | MAX LSP |
| Client signals | 239/238 x client signal | BANDWIDTH |
| | bit rate | |
| ODUflex for GFP-F | | MAX LSP | | ODUflex for GFP-F | | MAX LSP |
|Mapped client signal | Configured bit rate | BANDWIDTH | |Mapped client signal | Configured bit rate | BANDWIDTH |
| | | | | | | |
| | | | | | | |
|ODU flex resizable | Configured bit rate | MAX LSP | |ODU flex resizable | Configured bit rate | MAX LSP |
| | | BANDWIDTH | | | | BANDWIDTH |
+---------------------+------------------------------+-----------------+ +---------------------+------------------------------+-----------------+
A single ISCD MAY be used for the advertisement of unbundled or A single ISCD MAY be used for the advertisement of unbundled or
bundled links supporting homogeneous multiplexing hierarchies and the bundled links supporting homogeneous multiplexing hierarchies and the
same TS (Tributary Slot) granularity. A different ISCD MUST be used same TS (Tributary Slot) granularity. A different ISCD MUST be used
for each different muxing hierarchy (muxing tree in the following for each different muxing hierarchy (muxing tree in the following
examples) and different TS granularity supported within the TE Link. examples) and different TS granularity supported within the TE Link.
In case a recived LSA is not formatted accordingly to the
requirements indicated in this document, the problem SHOULD be logged
and the wrongly formatted LSA, TLV or Sub-TLV MUST NOT be used for
the path computation until a newer version correctly formatted is
received.
4.1. Switching Capability Specific Information 4.1. Switching Capability Specific Information
The technology specific part of the OTN-TDM ISCD may include a The technology specific part of the OTN-TDM ISCD may include a
variable number of sub-TLVs called Bandwidth sub-TLVs. Each sub-TLV variable number of sub-TLVs called Bandwidth sub-TLVs. Each sub-TLV
is encoded with the TLV header as defined in [RFC3630] section 2.3.2. is encoded with the sub-TLV header as defined in [RFC3630] section
The muxing hierarchy tree MUST be encoded as an order independent 2.3.2. The muxing hierarchy tree MUST be encoded as an order
list. Two types of Bandwidth TLV are defined (TBA by IANA). Note independent list. Two types of Bandwidth sub-TLV are defined (TBA by
that type values are defined in this document and not in [RFC3630]. IANA). Note that type values are defined in this document and not in
[RFC3630].
- Type 1 - Unreserved Bandwidth for fixed containers - Type 1 - Unreserved Bandwidth for fixed containers
- Type 2 - Unreserved/MAX LSP Bandwidth for flexible containers - Type 2 - Unreserved/MAX LSP Bandwidth for flexible containers
The Switching Capability-specific information (SCSI) MUST include one The Switching Capability-Specific Information (SCSI) MUST include one
Type 1 sub-TLV for each fixed container and one Type 2 sub-TLV for Type 1 sub-TLV for each fixed container and one Type 2 sub-TLV for
each variable container. Each container type is identified by a each variable container. Each container type is identified by a
Signal Type. Signal Type values are defined in [OTN-SIG]. Signal Type. Signal Type values are defined in [OTN-SIG].
With respect to ODUflex, three different signal types are allowed: 20 With respect to ODUflex, three different signal types are allowed: 20
- ODUflex Constant Bit Rate (CBR), 21 - ODUflex Generic Framing - ODUflex Constant Bit Rate (CBR), 21 - ODUflex Generic Framing
Procedure-Frame mapped (GFP-F) resizable and 22 - ODUflex (GFP-F) non Procedure-Frame mapped (GFP-F) resizable and 22 - ODUflex (GFP-F)
resizable. Each MUST always be advertised in separate Type 2 TLVs as non-resizable. Each MUST always be advertised in separate Type 2
each uses different adaptation functions [G.805]. In the case that sub-TLVs as each uses different adaptation functions [G.805]. In the
both GFP-F resizable and non resizable (i.e. 21 and 22) are case that both GFP-F resizable and non-resizable (i.e., 21 and 22)
supported, only Signal Type 21 SHALL be advertised as this type also are supported, only Signal Type 21 SHALL be advertised as this type
implies support for type 22 adaptation. also implies support for type 22 adaptation.
4.1.1. Switching Capability Specific Information for fixed containers 4.1.1. Switching Capability Specific Information for fixed containers
The format of the Bandwidth TLV for fixed containers is depicted in The format of the Bandwidth sub-TLV for fixed containers is depicted
the following figure: in the following figure:
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 = 1 (Unres-fix) | Length | | Type = 1 (Unres-fix) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Signal type | Num of stages |T|S| TSG | Res | Priority | | Signal type | Num of stages |T|S| TSG | Res | Priority |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stage#1 | ... | Stage#N | Padding | | Stage#1 | ... | Stage#N | Padding |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unreserved ODUj at Prio 0 | ..... | | Unreserved ODUj at Prio 0 | ..... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unreserved ODUj at Prio 7 | Unreserved Padding | | Unreserved ODUj at Prio 7 | Unreserved Padding |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: Bandwidth TLV - Type 1 - Figure 3: Bandwidth sub-TLV - Type 1 -
The values of the fields shown in figure 4 are explained in section The values of the fields shown in figure 4 are explained in section
4.1.3. 4.1.3.
4.1.2. Switching Capability Specific Information for variable 4.1.2. Switching Capability Specific Information for variable
containers containers
The format of the Bandwidth TLV for variable containers is depicted The format of the Bandwidth sub-TLV for variable containers is
in the following figure: depicted in the following figure:
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 (Unres/MAX-var) | Length | | Type = 2 (Unres/MAX-var) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Signal type | Num of stages |T|S| TSG | Res | Priority | | Signal type | Num of stages |T|S| TSG | Res | Priority |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stage#1 | ... | Stage#N | Padding | | Stage#1 | ... | Stage#N | Padding |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unreserved Bandwidth at priority 0 | | Unreserved Bandwidth at priority 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unreserved Bandwidth at priority 7 | | Unreserved Bandwidth at priority 7 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAX LSP Bandwidth at priority 0 | | MAX LSP Bandwidth at priority 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAX LSP Bandwidth at priority 7 | | MAX LSP Bandwidth at priority 7 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: Bandwidth TLV - Type 2 - Figure 4: Bandwidth sub-TLV - Type 2 -
The values of the fields shown in figure 4 are explained in section The values of the fields shown in figure 4 are explained in section
4.1.3. 4.1.3.
4.1.3. Switching Capability Specific Information - Field values and 4.1.3. Switching Capability Specific Information - Field values and
explanation explanation
The fields in the Bandwidth TLV MUST be filled as follows: The fields in the Bandwidth sub-TLV MUST be filled as follows:
- Signal Type (8 bits): Indicates the ODU type being advertised. - Signal Type (8 bits): Indicates the ODU type being advertised.
Values are defined in [OTN-SIG]. Values are defined in [OTN-SIG].
- Number of stages (8 bits): This field indicates the number of - Number of stages (8 bits): This field indicates the number of
multiplexing stages used to transport the indicated signal type. multiplexing stages used to transport the indicated signal type.
It MUST be set to the number of stages represented in the TLV. It MUST be set to the number of stages represented in the sub-TLV.
- Flags (8 bits): - Flags (8 bits):
- T Flag (bit 17): Indicates whether the advertised bandwidth - T Flag (bit 17): Indicates whether the advertised bandwidth
can be terminated. When the signal type can be terminated T can be terminated. When the signal type can be terminated T
MUST be set, while when the signal type cannot be terminated T MUST be set, while when the signal type cannot be terminated T
MUST be cleared. MUST be cleared.
- S Flag (bit 18): Indicates whether the advertised bandwidth - S Flag (bit 18): Indicates whether the advertised bandwidth
can be switched. When the signal type can be switched S MUST can be switched. When the signal type can be switched S MUST
skipping to change at page 10, line 31 skipping to change at page 10, line 31
- 3 - 1.25Gbps only - 3 - 1.25Gbps only
- 4-7 - Reserved - 4-7 - Reserved
A value of 1 MUST be used on interfaces which are configured to A value of 1 MUST be used on interfaces which are configured to
support the fall back procedures defined in [G.798-a2]. A value support the fall back procedures defined in [G.798-a2]. A value
of 2 MUST be used on interfaces that only support 2.5Gbps time of 2 MUST be used on interfaces that only support 2.5Gbps time
slots, such as [RFC4328] interfaces. A value of 3 MUST be used on slots, such as [RFC4328] interfaces. A value of 3 MUST be used on
interfaces that are configured to only support 1.25Gbps time interfaces that are configured to only support 1.25Gbps time
slots. A value of 0 MUST be used for non multiplexed signal types slots. A value of 0 MUST be used for non-multiplexed signal types
(i.e. a non OTN client). (i.e., a non-OTN client).
- Res (3 bits): reserved bits. MUST be set to 0 and ignored on - Res (3 bits): reserved bits. MUST be set to 0 and ignored on
receipt. receipt.
- Priority (8 bits): a bitmap used to indicate which priorities - Priority (8 bits): A bitmap used to indicate which priorities
are being advertised. The bitmap is in ascending order, with the are being advertised. The bitmap is in ascending order, with the
leftmost bit representing priority level 0 (i.e. the highest) and leftmost bit representing priority level 0 (i.e., the highest) and
the rightmost bit representing priority level 7 (i.e. the lowest). the rightmost bit representing priority level 7 (i.e., the
A bit MUST be set (1) corresponding to each priority represented lowest). A bit MUST be set (1) corresponding to each priority
in the TLV, and MUST NOT be set (0) when the corresponding represented in the sub-TLV, and MUST NOT be set (0) when the
priority is not represented. At least one priority level MUST be corresponding priority is not represented. At least one priority
advertised that, unless overridden by local policy, SHALL be at level MUST be advertised that, unless overridden by local policy,
priority level 0. SHALL be at priority level 0.
- Stage (8 bits): Each Stage field indicates a signal type in the - Stage (8 bits): Each Stage field indicates a signal type in the
multiplexing hierarchy used to transport the signal indicated in multiplexing hierarchy used to transport the signal indicated in
the Signal Type field. The number of Stage fields included in a the Signal Type field. The number of Stage fields included in a
TLV MUST equal the value of the Number of Stages field. The Stage sub-TLV MUST equal the value of the Number of Stages field. The
fields MUST be ordered to match the data plane in ascending order Stage fields MUST be ordered to match the data plane in ascending
(from the lowest order ODU to the highest order ODU). The values order (from the lowest order ODU to the highest order ODU). The
of the Stage field are the same as those defined for the Signal values of the Stage field are the same as those defined for the
Type field. When the Number of stage field carries a 0, then the Signal Type field. When the Number of stage field carries a 0,
Stage and Padding fields MUST be omitted. then the Stage and Padding fields MUST be omitted.
- Padding (variable): The Padding field is used to ensure the 32 - Padding (variable): The Padding field is used to ensure the 32
bit alignment of stage fields. The length of the Padding field is bit alignment of stage fields. The length of the Padding field is
always a multiple of 8 bits (1 byte). Its length can be always a multiple of 8 bits (1 byte). Its length can be
calculated, in bytes, as: 4 - ( "value of Number of Stages field" calculated, in bytes, as: 4 - ( "value of Number of Stages field"
% 4). The Padding field MUST be set to a zero (0) value on % 4). The Padding field MUST be set to a zero (0) value on
transmission and MUST be ignored on receipt. transmission and MUST be ignored on receipt.
- Unreserved ODUj (16 bits): This field indicates the Unreserved - Unreserved ODUj (16 bits): This field indicates the Unreserved
Bandwidth at a particular priority level. This field MUST be set Bandwidth at a particular priority level. This field MUST be set
skipping to change at page 12, line 23 skipping to change at page 12, line 23
5.1. MAX LSP Bandwidth fields in the ISCD 5.1. MAX LSP Bandwidth fields in the ISCD
This example shows how the MAX LSP Bandwidth fields of the ISCD are This example shows how the MAX LSP Bandwidth fields of the ISCD are
filled accordingly to the evolving of the TE-link bandwidth filled accordingly to the evolving of the TE-link bandwidth
occupancy. In the example an OTU4 link is considered, with supported occupancy. In the example an OTU4 link is considered, with supported
priorities 0,2,4,7 and muxing hierarchy ODU1->ODU2->ODU3->ODU4. priorities 0,2,4,7 and muxing hierarchy ODU1->ODU2->ODU3->ODU4.
At time T0, with the link completely free, the advertisement would At time T0, with the link completely free, the advertisement would
be: be:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SwCap=OTN_TDM | Encoding = 12 | Reserved (all zeros) | | SwCap=OTN_TDM | Encoding = 12 | Reserved (all zeros) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAX LSP Bandwidth at priority 0 = 100Gbps | | MAX LSP Bandwidth at priority 0 = 100Gbps |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAX LSP Bandwidth at priority 1 = 0 | | MAX LSP Bandwidth at priority 1 = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAX LSP Bandwidth at priority 2 = 100Gbps | | MAX LSP Bandwidth at priority 2 = 100Gbps |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAX LSP Bandwidth at priority 3 = 0 | | MAX LSP Bandwidth at priority 3 = 0 |
skipping to change at page 12, line 48 skipping to change at page 12, line 48
| MAX LSP Bandwidth at priority 5 = 0 | | MAX LSP Bandwidth at priority 5 = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAX LSP Bandwidth at priority 6 = 0 | | MAX LSP Bandwidth at priority 6 = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAX LSP Bandwidth at priority 7 = 100Gbps | | MAX LSP Bandwidth at priority 7 = 100Gbps |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Switching Capability Specific Information | | Switching Capability Specific Information |
| (variable length) | | (variable length) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5: Example 1 - MAX LSP Bandwidth fields in the ISCD @T0 Figure 5: Example 1 - MAX LSP Bandwidth fields in the ISCD at T0
At time T1 an ODU3 at priority 2 is set-up, so for priority 0 the MAX At time T1, an ODU3 at priority 2 is set-up, so for priority 0 the
LSP Bandwidth is still equal to the ODU4 bandwidth, while for MAX LSP Bandwidth is still equal to the ODU4 bandwidth, while for
priorities from 2 to 7 (excluding the non supported ones) the MAX LSP priorities from 2 to 7 (excluding the non-supported ones) the MAX LSP
Bandwidth is equal to ODU3, as no more ODU4s are available and the Bandwidth is equal to ODU3, as no more ODU4s are available and the
next supported ODUj in the hierarchy is ODU3.The advertisement is next supported ODUj in the hierarchy is ODU3. The advertisement is
updated as follows: updated 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SwCap=OTN_TDM | Encoding = 12 | Reserved (all zeros) | | SwCap=OTN_TDM | Encoding = 12 | Reserved (all zeros) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAX LSP Bandwidth at priority 0 = 100Gbps | | MAX LSP Bandwidth at priority 0 = 100Gbps |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAX LSP Bandwidth at priority 1 = 0 | | MAX LSP Bandwidth at priority 1 = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAX LSP Bandwidth at priority 2 = 40Gbps | | MAX LSP Bandwidth at priority 2 = 40Gbps |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAX LSP Bandwidth at priority 3 = 0 | | MAX LSP Bandwidth at priority 3 = 0 |
skipping to change at page 13, line 37 skipping to change at page 13, line 37
| MAX LSP Bandwidth at priority 5 = 0 | | MAX LSP Bandwidth at priority 5 = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAX LSP Bandwidth at priority 6 = 0 | | MAX LSP Bandwidth at priority 6 = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAX LSP Bandwidth at priority 7 = 40Gbps | | MAX LSP Bandwidth at priority 7 = 40Gbps |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Switching Capability Specific Information | | Switching Capability Specific Information |
| (variable length) | | (variable length) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 6: Example 1 - MAX LSP Bandwidth fields in the ISCD @T1 Figure 6: Example 1 - MAX LSP Bandwidth fields in the ISCD at T1
At time T2 an ODU2 at priority 4 is set-up. The first ODU3 is no At time T2, an ODU2 at priority 4 is set-up. The first ODU3 is no
longer available since T1 as it was kept by the ODU3 LSP, while the longer available since T1, as it was kept by the ODU3 LSP, while the
second is no more available and just 3 ODU2 are left in it. ODU2 is second is no more available and just 3 ODU2 are left in it. ODU2 is
now the MAX LSP Bandwidth for priorities higher than 4. The now the MAX LSP Bandwidth for priorities higher than 4. The
advertisement is updated as follows: advertisement is updated 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SwCap=OTN_TDM | Encoding = 12 | Reserved (all zeros) | | SwCap=OTN_TDM | Encoding = 12 | Reserved (all zeros) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAX LSP Bandwidth at priority 0 = 100Gbps | | MAX LSP Bandwidth at priority 0 = 100Gbps |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAX LSP Bandwidth at priority 1 = 0 | | MAX LSP Bandwidth at priority 1 = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAX LSP Bandwidth at priority 2 = 40Gbps | | MAX LSP Bandwidth at priority 2 = 40Gbps |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAX LSP Bandwidth at priority 3 = 0 | | MAX LSP Bandwidth at priority 3 = 0 |
skipping to change at page 14, line 30 skipping to change at page 14, line 30
| MAX LSP Bandwidth at priority 5 = 0 | | MAX LSP Bandwidth at priority 5 = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAX LSP Bandwidth at priority 6 = 0 | | MAX LSP Bandwidth at priority 6 = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAX LSP Bandwidth at priority 7 = 10Gbps | | MAX LSP Bandwidth at priority 7 = 10Gbps |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Switching Capability Specific Information | | Switching Capability Specific Information |
| (variable length) | | (variable length) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 7: Example 1 - MAX LSP Bandwidth fields in the ISCD @T2 Figure 7: Example 1 - MAX LSP Bandwidth fields in the ISCD at T2
5.2. Example of T,S and TS granularity utilization 5.2. Example of T,S and TS granularity utilization
In this example an interface with Tributary Slot Type 1.25Gbps and In this example, an interface with Tributary Slot Type 1.25Gbps and
fallback procedure enabled is considered (TS granularity=1). It fallback procedure enabled is considered (TS granularity=1). It
supports the simple ODU1->ODU2->ODU3 hierarchy and priorities 0 and supports the simple ODU1->ODU2->ODU3 hierarchy and priorities 0 and
3. Suppose that in this interface the ODU3 signal type can be both 3. Suppose that in this interface the ODU3 signal type can be both
switched or terminated, the ODU2 can only be terminated and the ODU1 switched or terminated, the ODU2 can only be terminated, and the ODU1
switched only. Please note that since the ODU1 is not being switched only. Please note that since the ODU1 is not being
advertised to support ODU0 the value of is "ignored" (TS advertised to support ODU0, the value of is "ignored" (TS
granularity=0). For the advertisement of the capabilities of such granularity=0). For the advertisement of the capabilities of such
interface a single ISCD is used and its format is as follows: interface, a single ISCD is used and its format is 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 (Unres-fix) | Length = 12 | | Type = 1 (Unres-fix) | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sig type=ODU1 | #stages= 2 |T0|S1| 0 |0 0 0|1|0|0|1|0|0|0|0| |Sig type=ODU1 | #stages= 2 |0|1| 0 |0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stage#1=ODU2 | Stage#2=ODU3 | Padding (all zeros) | | Stage#1=ODU2 | Stage#2=ODU3 | Padding (all zeros) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unres ODU1 at Prio 0 | Unres ODU1 at Prio 3 | | Unres ODU1 at Prio 0 | Unres ODU1 at Prio 3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 (Unres-fix) | Length = 12 | | Type = 1 (Unres-fix) | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sig type=ODU2 | #stages= 1 |T1|S0| 1 |0 0 0|1|0|0|1|0|0|0|0| |Sig type=ODU2 | #stages= 1 |1|0| 1 |0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stage#1=ODU3 | Padding (all zeros) | | Stage#1=ODU3 | Padding (all zeros) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unres ODU2 at Prio 0 | Unres ODU2 at Prio 3 | | Unres ODU2 at Prio 0 | Unres ODU2 at Prio 3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 (Unres-fix) | Length = 8 | | Type = 1 (Unres-fix) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sig type=ODU3 | #stages= 0 |T1|S1| 1 |0 0 0|1|0|0|1|0|0|0|0| |Sig type=ODU3 | #stages= 0 |1|1| 1 |0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unres ODU3 at Prio 0 | Unres ODU3 at Prio 3 | | Unres ODU3 at Prio 0 | Unres ODU3 at Prio 3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 8: Example 2 - TS granularity, T and S utilization Figure 8: Example 2 - TS granularity, T and S utilization
5.2.1. Example of different TS Granularities 5.2.1. Example of different TS Granularities
In this example two interfaces with homogeneous hierarchies but In this example, two interfaces with homogeneous hierarchies but
different Tributary Slot Types are considered. The first one different Tributary Slot Types are considered. The first one
supports a [RFC4328] interface (TS granularity=2) while the second supports a [RFC4328] interface (TS granularity=2) while the second
one a G.709-2012 interface with fallback procedure disabled (TS one supports G.709-2012 interface with fallback procedure disabled
granularity=3). Both of them support ODU1->ODU2->ODU3 hierarchy and (TS granularity=3). Both of them support ODU1->ODU2->ODU3 hierarchy
priorities 0 and 3. T and S bits values are not relevant to this and priorities 0 and 3. T and S bits values are not relevant to this
example. For the advertisement of the capabilities of such example. For the advertisement of the capabilities of such
interfaces two different ISCDs are used and the format of their SCSIs interfaces, two different ISCDs are used and the format of their
is as follows: SCSIs is as follows:
SCSI of ISCD 1 - TS granularity=2 SCSI of ISCD 1 - TS granularity=2
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 = 1 (Unres-fix) | Length = 12 | | Type = 1 (Unres-fix) | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sig type=ODU1 | #stages= 2 |T0|S1| 0 |0 0 0|1|0|0|1|0|0|0|0| |Sig type=ODU1 | #stages= 2 |0|1| 0 |0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stage#1=ODU2 | Stage#2=ODU3 | Padding (all zeros) | | Stage#1=ODU2 | Stage#2=ODU3 | Padding (all zeros) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unres ODU1 at Prio 0 | Unres ODU1 at Prio 3 | | Unres ODU1 at Prio 0 | Unres ODU1 at Prio 3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 (Unres-fix) | Length = 12 | | Type = 1 (Unres-fix) | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sig type=ODU2 | #stages= 1 |T1|S0| 1 |0 0 0|1|0|0|1|0|0|0|0| |Sig type=ODU2 | #stages= 1 |1|0| 1 |0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stage#1=ODU3 | Padding (all zeros) | | Stage#1=ODU3 | Padding (all zeros) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unres ODU2 at Prio 0 | Unres ODU2 at Prio 3 | | Unres ODU2 at Prio 0 | Unres ODU2 at Prio 3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 (Unres-fix) | Length = 8 | | Type = 1 (Unres-fix) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sig type=ODU3 | #stages= 0 |T1|S1| 2 |0 0 0|1|0|0|1|0|0|0|0| |Sig type=ODU3 | #stages= 0 |1|1| 2 |0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unres ODU3 at Prio 0 | Unres ODU3 at Prio 3 | | Unres ODU3 at Prio 0 | Unres ODU3 at Prio 3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 9: Example 2.1 - Different TS Granularities utilization - ISCD
1
SCSI of ISCD 2 - TS granularity=3 SCSI of ISCD 2 - TS granularity=3
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 = 1 (Unres-fix) | Length = 12 | | Type = 1 (Unres-fix) | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sig type=ODU1 | #stages= 2 |T0|S1| 0 |0 0 0|1|0|0|1|0|0|0|0| |Sig type=ODU1 | #stages= 2 |0|1| 0 |0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stage#1=ODU2 | Stage#2=ODU3 | Padding (all zeros) | | Stage#1=ODU2 | Stage#2=ODU3 | Padding (all zeros) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unres ODU1 at Prio 0 | Unres ODU1 at Prio 3 | | Unres ODU1 at Prio 0 | Unres ODU1 at Prio 3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 (Unres-fix) | Length = 12 | | Type = 1 (Unres-fix) | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sig type=ODU2 | #stages= 1 |T1|S0| 1 |0 0 0|1|0|0|1|0|0|0|0| |Sig type=ODU2 | #stages= 1 |1|0| 1 |0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stage#1=ODU3 | Padding (all zeros) | | Stage#1=ODU3 | Padding (all zeros) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unres ODU2 at Prio 0 | Unres ODU2 at Prio 3 | | Unres ODU2 at Prio 0 | Unres ODU2 at Prio 3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 (Unres-fix) | Length = 8 | | Type = 1 (Unres-fix) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sig type=ODU3 | #stages= 0 |T1|S1| 3 |0 0 0|1|0|0|1|0|0|0|0| |Sig type=ODU3 | #stages= 0 |1|1| 3 |0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unres ODU3 at Prio 0 | Unres ODU3 at Prio 3 | | Unres ODU3 at Prio 0 | Unres ODU3 at Prio 3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 9: Example 2.1 - Different TS Granularities utilization
Figure 10: Example 2.1 - Different TS Granularities utilization -
ISCD 2
A particular case in which hierarchies with the same muxing tree but A particular case in which hierarchies with the same muxing tree but
with different exported TS granularity MUST be considered as non with different exported TS granularity MUST be considered as non-
homogenous hierarchies is the case in which an H-LPS and the client homogenous hierarchies. This is the case in which an H-LPS and the
LSP are terminated on the same egress node. What can happen is that client LSP are terminated on the same egress node. What can happen
a loose Explicit Route Object (ERO) is used at the hop where the is that a loose Explicit Route Object (ERO) is used at the hop where
signaled LSP is nested into the Hierarchical-LSP (H-LSP) (penultimate the signaled LSP is nested into the Hierarchical-LSP (H-LSP)
hop of the LSP). (penultimate hop of the LSP).
In the following figure, node C receives from A a loose ERO towards In the following figure, node C receives from A a loose ERO towards
node E and must choose between the ODU2 H-LSP on if1 or the one on node E and must choose between the ODU2 H-LSP on if1 or the one on
if2. In case the H-LSP on if1 exports a TS=1.25Gbps and if2 a if2. In this case, the H-LSP on if1 exports a TS=1.25Gbps, and if2 a
TS=2.5Gbps and the service LSP being signaled needs a 1.25Gbps TS=2.5Gbps, the service LSP being signaled needs a 1.25Gbps tributary
tributary slot, only the H-LSP on if1 can be used to reach node E. slot, only the H-LSP on if1 can be used to reach node E. For further
For further details please see section 4.1 of the [OTN-INFO]. details, please see section 4.1 of the [OTN-INFO].
ODU0-LSP ODU0-LSP
..........................................................+ ..........................................................+
| | | |
| ODU2-H-LSP | | ODU2-H-LSP |
| +-------------------------------+ | +-------------------------------+
| | | | | |
+--+--+ +-----+ +-----+ if1 +-----+ +-----+ +--+--+ +-----+ +-----+ if1 +-----+ +-----+
| | OTU3 | | OTU3 | |---------| |---------| | | | OTU3 | | OTU3 | |---------| |---------| |
| A +------+ B +------+ C | if2 | D | | E | | A +------+ B +------+ C | if2 | D | | E |
| | | | | |---------| |---------| | | | | | | |---------| |---------| |
+-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+
... Service LSP ... Service LSP
--- H-LSP --- H-LSP
Figure 10: Example - Service LSP and H-LSP terminating on the same Figure 11: Example - Service LSP and H-LSP terminating on the same
node node
5.3. Example of ODUflex advertisement 5.3. Example of ODUflex advertisement
In this example the advertisement of an ODUflex->ODU3 hierarchy is In this example, the advertisement of an ODUflex->ODU3 hierarchy is
shown. In case of ODUflex advertisement the MAX LSP Bandwidth needs shown. In case of ODUflex advertisement, the MAX LSP Bandwidth needs
to be advertised and in some cases also information about the to be advertised and, in some cases, information about the Unreserved
Unreserved bandwidth could be useful. The amount of Unreserved bandwidth could also be useful. The amount of Unreserved bandwidth
bandwidth does not give a clear indication of how many ODUflex LSP does not give a clear indication of how many ODUflex LSP can be set
can be set up either at the MAX LSP Bandwidth or at different rates, up either at the MAX LSP Bandwidth or at different rates, as it gives
as it gives no information about the spatial allocation of the free no information about the spatial allocation of the free TSs.
TSs.
An indication of the amount of Unreserved bandwidth could be useful An indication of the amount of Unreserved bandwidth could be useful
during the path computation process, as shown in the following during the path computation process, as shown in the following
example. Supposing there are two TE-links (A and B) with MAX LSP example. Supposing there are two TE-links (A and B) with MAX LSP
Bandwidth equal to 10 Gbps each. In case 50Gbps of Unreserved Bandwidth equal to 10 Gbps each. In the case where 50Gbps of
Bandwidth are available on Link A, 10Gbps on Link B and 3 ODUflex Unreserved Bandwidth are available on Link A, 10Gbps on Link B, and 3
LSPs of 10 GBps each, have to be restored, for sure only one can be ODUflex LSPs of 10 GBps each have to be restored, for sure only one
restored along Link B and it is probable (but not sure) that two of can be restored along Link B and it is probable, but not certain,
them can be restored along Link A. T, S and TS granularity fields are that two of them can be restored along Link A. T, S and TS
not relevant to this example. granularity fields are not relevant to this example.
In the case of ODUflex advertisement the Type 2 Bandwidth TLV is In the case of ODUflex advertisement, the Type 2 Bandwidth sub-TLV is
used. 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 2 (Unres/MAX-var) | Length = 72 | | Type = 2 (Unres/MAX-var) | Length = 72 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|S. type=ODUflex| #stages= 1 |T|S| TSG |0 0 0| Priority(8) | |S. type=ODUflex| #stages= 1 |X|X|X X X|0 0 0| Priority(8) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stage#1=ODU3 | Padding (all zeros) | | Stage#1=ODU3 | Padding (all zeros) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unreserved Bandwidth at priority 0 | | Unreserved Bandwidth at priority 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unreserved Bandwidth at priority 1 | | Unreserved Bandwidth at priority 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unreserved Bandwidth at priority 2 | | Unreserved Bandwidth at priority 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unreserved Bandwidth at priority 3 | | Unreserved Bandwidth at priority 3 |
skipping to change at page 19, line 47 skipping to change at page 19, line 47
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAX LSP Bandwidth at priority 4 | | MAX LSP Bandwidth at priority 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAX LSP Bandwidth at priority 5 | | MAX LSP Bandwidth at priority 5 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAX LSP Bandwidth at priority 6 | | MAX LSP Bandwidth at priority 6 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAX LSP Bandwidth at priority 7 | | MAX LSP Bandwidth at priority 7 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 11: Example 3 - ODUflex advertisement Figure 12: Example 3 - ODUflex advertisement
5.4. Example of single stage muxing 5.4. Example of single stage muxing
Supposing there is 1 OTU4 component link supporting single stage Supposing there is 1 OTU4 component link supporting single stage
muxing of ODU1, ODU2, ODU3 and ODUflex, the supported hierarchy can muxing of ODU1, ODU2, ODU3 and ODUflex, the supported hierarchy can
be summarized in a tree as in the following figure. For sake of be summarized in a tree as in the following figure. For sake of
simplicity we assume that also in this case only priorities 0 and 3 simplicity, we also assume that only priorities 0 and 3 are
are supported. T, S and TS granularity fields are not relevant to supported. T, S and TS granularity fields are not relevant to this
this example. example.
ODU1 ODU2 ODU3 ODUflex ODU1 ODU2 ODU3 ODUflex
\ \ / / \ \ / /
\ \ / / \ \ / /
\ \/ / \ \/ /
ODU4 ODU4
and the related SCSIs as follows: and the related SCSIs 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 (Unres-fix) | Length = 8 | | Type = 1 (Unres-fix) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sig type=ODU4 | #stages= 0 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| |Sig type=ODU4 | #stages= 0 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unres ODU4 at Prio 0 =1 | Unres ODU4 at Prio 3 =1 | | Unres ODU4 at Prio 0 =1 | Unres ODU4 at Prio 3 =1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 (Unres-fix) | Length = 12 | | Type = 1 (Unres-fix) | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sig type=ODU1 | #stages= 1 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| |Sig type=ODU1 | #stages= 1 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stage#1=ODU4 | Padding (all zeros) | | Stage#1=ODU4 | Padding (all zeros) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unres ODU1 at Prio 0 =40 | Unres ODU1 at Prio 3 =40 | | Unres ODU1 at Prio 0 =40 | Unres ODU1 at Prio 3 =40 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 (Unres-fix) | Length = 12 | | Type = 1 (Unres-fix) | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sig type=ODU2 | #stages= 1 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| |Sig type=ODU2 | #stages= 1 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stage#1=ODU4 | Padding (all zeros) | | Stage#1=ODU4 | Padding (all zeros) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unres ODU2 at Prio 0 =10 | Unres ODU2 at Prio 3 =10 | | Unres ODU2 at Prio 0 =10 | Unres ODU2 at Prio 3 =10 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 (Unres-fix) | Length = 12 | | Type = 1 (Unres-fix) | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sig type=ODU3 | #stages= 1 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| |Sig type=ODU3 | #stages= 1 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stage#1=ODU4 | Padding (all zeros) | | Stage#1=ODU4 | Padding (all zeros) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unres ODU3 at Prio 0 =2 | Unres ODU3 at Prio 3 =2 | | Unres ODU3 at Prio 0 =2 | Unres ODU3 at Prio 3 =2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 2 (Unres/MAX-var) | Length = 24 | | Type = 2 (Unres/MAX-var) | Length = 24 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|S. type=ODUflex| #stages= 1 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| |S. type=ODUflex| #stages= 1 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stage#1=ODU4 | Padding (all zeros) | | Stage#1=ODU4 | Padding (all zeros) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unreserved Bandwidth at priority 0 =100Gbps | | Unreserved Bandwidth at priority 0 =100Gbps |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unreserved Bandwidth at priority 3 =100Gbps | | Unreserved Bandwidth at priority 3 =100Gbps |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAX LSP Bandwidth at priority 0 =100Gbps | | MAX LSP Bandwidth at priority 0 =100Gbps |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAX LSP Bandwidth at priority 3 =100Gbps | | MAX LSP Bandwidth at priority 3 =100Gbps |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 12: Example 4 - Single stage muxing Figure 13: Example 4 - Single stage muxing
5.5. Example of multi stage muxing - Unbundled link 5.5. Example of multi stage muxing - Unbundled link
Supposing there is 1 OTU4 component link with muxing capabilities as Supposing there is 1 OTU4 component link with muxing capabilities as
shown in the following figure: shown in the following figure:
ODU2 ODU0 ODUflex ODU0 ODU2 ODU0 ODUflex ODU0
\ / \ / \ / \ /
| | | |
ODU3 ODU2 ODU3 ODU2
\ / \ /
\ / \ /
\ / \ /
\ / \ /
ODU4 ODU4
and supported priorities 0 and 3, the advertisement is composed by and supported priorities 0 and 3, the advertisement is composed by
the following Bandwidth TLVs (T and S fields are not relevant to this the following Bandwidth sub-TLVs (T and S fields are not relevant to
example): this example):
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 = 1 (Unres-fix) | Length = 8 | | Type = 1 (Unres-fix) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sig type=ODU4 | #stages= 0 |T|S| 1 |0 0 0|1|0|0|1|0|0|0|0| |Sig type=ODU4 | #stages= 0 |X|X| 1 |0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unres ODU4 at Prio 0 =1 | Unres ODU4 at Prio 3 =1 | | Unres ODU4 at Prio 0 =1 | Unres ODU4 at Prio 3 =1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 (Unres-fix) | Length = 12 | | Type = 1 (Unres-fix) | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sig type=ODU3 | #stages= 1 |T|S| 1 |0 0 0|1|0|0|1|0|0|0|0| |Sig type=ODU3 | #stages= 1 |X|X| 1 |0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stage#1=ODU4 | Padding (all zeros) | | Stage#1=ODU4 | Padding (all zeros) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unres ODU3 at Prio 0 =2 | Unres ODU3 at Prio 3 =2 | | Unres ODU3 at Prio 0 =2 | Unres ODU3 at Prio 3 =2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 (Unres-fix) | Length = 12 | | Type = 1 (Unres-fix) | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sig type=ODU2 | #stages= 1 |T|S| 1 |0 0 0|1|0|0|1|0|0|0|0| |Sig type=ODU2 | #stages= 1 |X|X| 1 |0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stage#1=ODU4 | Padding (all zeros) | | Stage#1=ODU4 | Padding (all zeros) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unres ODU2 at Prio 0 =10 | Unres ODU2 at Prio 3 =10 | | Unres ODU2 at Prio 0 =10 | Unres ODU2 at Prio 3 =10 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 (Unres-fix) | Length = 12 | | Type = 1 (Unres-fix) | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sig type=ODU2 | #stages= 2 |T|S| 0 |0 0 0|1|0|0|1|0|0|0|0| |Sig type=ODU2 | #stages= 2 |X|X| 0 |0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stage#1=ODU3 | Stage#2=ODU4 | Padding (all zeros) | | Stage#1=ODU3 | Stage#2=ODU4 | Padding (all zeros) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unres ODU2 at Prio 0 =8 | Unres ODU2 at Prio 3 =8 | | Unres ODU2 at Prio 0 =8 | Unres ODU2 at Prio 3 =8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 (Unres-fix) | Length = 12 | | Type = 1 (Unres-fix) | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sig type=ODU0 | #stages= 2 |T|S| 0 |0 0 0|1|0|0|1|0|0|0|0| |Sig type=ODU0 | #stages= 2 |X|X| 0 |0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stage#1=ODU3 | Stage#2=ODU4 | Padding (all zeros) | | Stage#1=ODU3 | Stage#2=ODU4 | Padding (all zeros) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unres ODU0 at Prio 0 =64 | Unres ODU0 at Prio 3 =64 | | Unres ODU0 at Prio 0 =64 | Unres ODU0 at Prio 3 =64 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 (Unres-fix) | Length = 12 | | Type = 1 (Unres-fix) | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sig type=ODU0 | #stages= 2 |T|S| 0 |0 0 0|1|0|0|1|0|0|0|0| |Sig type=ODU0 | #stages= 2 |X|X| 0 |0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stage#1=ODU2 | Stage#2=ODU4 | Padding (all zeros) | | Stage#1=ODU2 | Stage#2=ODU4 | Padding (all zeros) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unres ODU0 at Prio 0 =80 | Unres ODU0 at Prio 3 =80 | | Unres ODU0 at Prio 0 =80 | Unres ODU0 at Prio 3 =80 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 2 (Unres/MAX-var) | Length = 24 | | Type = 2 (Unres/MAX-var) | Length = 24 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|S.type=ODUflex | #stages= 2 |T|S| 0 |0 0 0|1|0|0|1|0|0|0|0| |S.type=ODUflex | #stages= 2 |X|X| 0 |0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stage#1=ODU2 | Stage#2=ODU4 | Padding (all zeros) | | Stage#1=ODU2 | Stage#2=ODU4 | Padding (all zeros) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unreserved Bandwidth at priority 0 =100Gbps | | Unreserved Bandwidth at priority 0 =100Gbps |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unreserved Bandwidth at priority 3 =100Gbps | | Unreserved Bandwidth at priority 3 =100Gbps |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAX LSP Bandwidth at priority 0 =10Gbps | | MAX LSP Bandwidth at priority 0 =10Gbps |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAX LSP Bandwidth at priority 3 =10Gbps | | MAX LSP Bandwidth at priority 3 =10Gbps |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 13: Example 5 - Multi stage muxing - Unbundled link Figure 14: Example 5 - Multi stage muxing - Unbundled link
5.6. Example of multi stage muxing - Bundled links 5.6. Example of multi stage muxing - Bundled links
In this example 2 OTU4 component links with the same supported TS In this example, 2 OTU4 component links with the same supported TS
granularity and homogeneous muxing hierarchies are considered. The granularity and homogeneous muxing hierarchies are considered. The
following muxing capabilities trees are supported: following muxing capabilities trees are supported:
Component Link#1 Component Link#2 Component Link#1 Component Link#2
ODU2 ODU0 ODU2 ODU0 ODU2 ODU0 ODU2 ODU0
\ / \ / \ / \ /
| | | |
ODU3 ODU3 ODU3 ODU3
| | | |
ODU4 ODU4 ODU4 ODU4
Considering only supported priorities 0 and 3, the advertisement is Considering only supported priorities 0 and 3, the advertisement is
as follows (T, S and TS granularity fields are not relevant to this as follows (T, S and TS granularity fields are not relevant to this
example): example):
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 = 1 (Unres-fix) | Length = 8 | | Type = 1 (Unres-fix) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sig type=ODU4 | #stages= 0 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| |Sig type=ODU4 | #stages= 0 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unres ODU4 at Prio 0 =2 | Unres ODU4 at Prio 3 =2 | | Unres ODU4 at Prio 0 =2 | Unres ODU4 at Prio 3 =2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 (Unres-fix) | Length = 12 | | Type = 1 (Unres-fix) | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sig type=ODU3 | #stages= 1 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| |Sig type=ODU3 | #stages= 1 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stage#1=ODU4 | Padding (all zeros) | | Stage#1=ODU4 | Padding (all zeros) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unres ODU3 at Prio 0 =4 | Unres ODU3 at Prio 3 =4 | | Unres ODU3 at Prio 0 =4 | Unres ODU3 at Prio 3 =4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 (Unres-fix) | Length = 12 | | Type = 1 (Unres-fix) | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sig type=ODU2 | #stages= 2 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| |Sig type=ODU2 | #stages= 2 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stage#1=ODU3 | Stage#2=ODU4 | Padding (all zeros) | | Stage#1=ODU3 | Stage#2=ODU4 | Padding (all zeros) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unres ODU2 at Prio 0 =16 | Unres ODU2 at Prio 3 =16 | | Unres ODU2 at Prio 0 =16 | Unres ODU2 at Prio 3 =16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 (Unres-fix) | Length = 12 | | Type = 1 (Unres-fix) | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sig type=ODU0 | #stages= 2 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| |Sig type=ODU0 | #stages= 2 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stage#1=ODU3 | Stage#2=ODU4 | Padding (all zeros) | | Stage#1=ODU3 | Stage#2=ODU4 | Padding (all zeros) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unres ODU0 at Prio 0 =128 | Unres ODU0 at Prio 3 =128 | | Unres ODU0 at Prio 0 =128 | Unres ODU0 at Prio 3 =128 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 14: Example 6 - Multi stage muxing - Bundled links Figure 15: Example 6 - Multi stage muxing - Bundled links
5.7. Example of component links with non homogeneous hierarchies 5.7. Example of component links with non-homogeneous hierarchies
In this example 2 OTU4 component links with the same supported TS In this example, 2 OTU4 component links with the same supported TS
granularity and non homogeneous muxing hierarchies are considered. granularity and non-homogeneous muxing hierarchies are considered.
The following muxing capabilities trees are supported: The following muxing capabilities trees are supported:
Component Link#1 Component Link#2 Component Link#1 Component Link#2
ODU2 ODU0 ODU1 ODU0 ODU2 ODU0 ODU1 ODU0
\ / \ / \ / \ /
| | | |
ODU3 ODU2 ODU3 ODU2
| | | |
ODU4 ODU4 ODU4 ODU4
Considering only supported priorities 0 and 3, the advertisement uses Considering only supported priorities 0 and 3, the advertisement uses
two different ISCDs, one for each hierarchy (T, S and TS granularity two different ISCDs, one for each hierarchy (T, S and TS granularity
fields are not relevant to this example). In the following figure, fields are not relevant to this example). In the following figure,
the SCSI of each ISCD is shown: the SCSI of each ISCD is shown:
SCSI of ISCD 1 - Component Link#1 SCSI of ISCD 1 - Component Link#1
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 = 1 (Unres-fix) | Length = 8 | | Type = 1 (Unres-fix) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sig type=ODU4 | #stages= 0 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| |Sig type=ODU4 | #stages= 0 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unres ODU4 at Prio 0 =1 | Unres ODU4 at Prio 3 =1 | | Unres ODU4 at Prio 0 =1 | Unres ODU4 at Prio 3 =1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 (Unres-fix) | Length = 12 | | Type = 1 (Unres-fix) | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sig type=ODU3 | #stages= 1 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| |Sig type=ODU3 | #stages= 1 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stage#1=ODU4 | Padding (all zeros) | | Stage#1=ODU4 | Padding (all zeros) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unres ODU3 at Prio 0 =2 | Unres ODU3 at Prio 3 =2 | | Unres ODU3 at Prio 0 =2 | Unres ODU3 at Prio 3 =2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 (Unres-fix) | Length = 12 | | Type = 1 (Unres-fix) | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sig type=ODU2 | #stages= 2 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| |Sig type=ODU2 | #stages= 2 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stage#1=ODU3 | Stage#2=ODU4 | Padding (all zeros) | | Stage#1=ODU3 | Stage#2=ODU4 | Padding (all zeros) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unres ODU2 at Prio 0 =8 | Unres ODU2 at Prio 3 =8 | | Unres ODU2 at Prio 0 =8 | Unres ODU2 at Prio 3 =8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 (Unres-fix) | Length = 12 | | Type = 1 (Unres-fix) | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sig type=ODU0 | #stages= 2 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| |Sig type=ODU0 | #stages= 2 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stage#1=ODU3 | Stage#2=ODU4 | Padding (all zeros) | | Stage#1=ODU3 | Stage#2=ODU4 | Padding (all zeros) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unres ODU0 at Prio 0 =64 | Unres ODU0 at Prio 3 =64 | | Unres ODU0 at Prio 0 =64 | Unres ODU0 at Prio 3 =64 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 16: Example 7 - Multi stage muxing - Non-homogeneous
hierarchies - ISCD 1
SCSI of ISCD 2 - Component Link#2 SCSI of ISCD 2 - Component Link#2
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 = 1 (Unres-fix) | Length = 8 | | Type = 1 (Unres-fix) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sig type=ODU4 | #stages= 0 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| |Sig type=ODU4 | #stages= 0 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unres ODU4 at Prio 0 =1 | Unres ODU4 at Prio 3 =1 | | Unres ODU4 at Prio 0 =1 | Unres ODU4 at Prio 3 =1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 (Unres-fix) | Length = 12 | | Type = 1 (Unres-fix) | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sig type=ODU2 | #stages= 1 |T|S| TSG |0 0 0 |1|0|0|1|0|0|0|0| |Sig type=ODU2 | #stages= 1 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stage#1=ODU4 | Padding (all zeros) | | Stage#1=ODU4 | Padding (all zeros) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unres ODU2 at Prio 0 =10 | Unres ODU2 at Prio 3 =10 | | Unres ODU2 at Prio 0 =10 | Unres ODU2 at Prio 3 =10 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 (Unres-fix) | Length = 12 | | Type = 1 (Unres-fix) | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sig type=ODU1 | #stages= 2 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| |Sig type=ODU1 | #stages= 2 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stage#1=ODU2 | Stage#2=ODU4 | Padding (all zeros) | | Stage#1=ODU2 | Stage#2=ODU4 | Padding (all zeros) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unres ODU1 at Prio 0 =40 | Unres ODU1 at Prio 3 =40 | | Unres ODU1 at Prio 0 =40 | Unres ODU1 at Prio 3 =40 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 (Unres-fix) | Length = 12 | | Type = 1 (Unres-fix) | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sig type=ODU0 | #stages= 2 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| |Sig type=ODU0 | #stages= 2 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stage#1=ODU2 | Stage#2=ODU4 | Padding (all zeros) | | Stage#1=ODU2 | Stage#2=ODU4 | Padding (all zeros) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unres ODU0 at Prio 0 =80 | Unres ODU0 at Prio 3 =80 | | Unres ODU0 at Prio 0 =80 | Unres ODU0 at Prio 3 =80 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 15: Example 7 - Multi stage muxing - Non homogeneous Figure 17: Example 7 - Multi stage muxing - Non-homogeneous
hierarchies hierarchies - ISCD 2
6. Compatibility 6. OSPFv2 scalability
All implementations of this document MAY support also advertisement This document does not introduce OSPF scalability issues with respect
to existing GMPLS encoding and does not require any modification to
flooding frequency. Moreover the design of the encoding has been
carried out taking into account bandwidth optimization, and in
particular:
- Only unreserved and MAX LSP Bandwidth related to supported
priorities is advertised
- With respect of fixed containers, only the number of available
containers is advertised instead of available bandwidth so to use
only 16 bits per container instead of 32 (as per former GMPLS
encoding
In order to further reduce the amount of data advertised it is
RECOMMENDED to bundle component links with homogeneous hierarchies as
described in [RFC4201] and illustrated in Section 5.6.
7. Compatibility
All implementations of this document MAY also support advertisement
as defined in [RFC4328]. When nodes support both advertisement as defined in [RFC4328]. When nodes support both advertisement
methods, implementations MUST support the configuration of which methods, implementations MUST support the configuration of which
advertisement method is followed. The choice of which is used is advertisement method is followed. The choice of which is used is
based on policy and is out of scope of the document. This enables based on policy and beyond the scope of this document. This enables
nodes following each method to identify similar supporting nodes and nodes following each method to identify similar supporting nodes and
compute paths using only the appropriate nodes. compute paths using only the appropriate nodes.
7. Security Considerations 8. Security Considerations
This document extends [RFC4203]. As with[RFC4203], it specifies the This document extends [RFC4203]. As with[RFC4203], it specifies the
contents of Opaque LSAs in OSPFv2. As Opaque LSAs are not used for contents of Opaque LSAs in OSPFv2. As Opaque LSAs are not used for
SPF computation or normal routing, the extensions specified here have SPF computation or normal routing, the extensions specified here have
no direct effect on IP routing. Tampering with GMPLS TE LSAs may no direct effect on IP routing. Tampering with GMPLS TE LSAs may
have an effect on the underlying transport (optical and/or SONET-SDH) have an effect on the underlying transport (optical and/or SONET-SDH)
network. [RFC3630] suggests mechanisms such as [RFC2154] to protect network. [RFC3630] suggests mechanisms such as [RFC2154] to protect
the transmission of this information, and those or other mechanisms the transmission of this information, and those or other mechanisms
should be used to secure and/or authenticate the information carried should be used to secure and/or authenticate the information carried
in the Opaque LSAs. in the Opaque LSAs.
For security threats, defensive techniques, monitoring/detection/ For security threats, defensive techniques, monitoring/detection/
reporting of security attacks and requirements please refer to reporting of security attacks and requirements please refer to
[RFC5920] . [RFC5920].
8. IANA Considerations 9. IANA Considerations
8.1. Switching types 9.1. Switching types
Upon approval of this document, IANA will make the assignment in the Upon approval of this document, IANA will make the assignment in the
"Switching Types" section of the "GMPLS Signaling Parameters" "Switching Types" section of the "GMPLS Signaling Parameters"
registry located at registry located at
http://www.iana.org/assignments/gmpls-sig-parameters: http://www.iana.org/assignments/gmpls-sig-parameters:
Value Name Reference Value Name Reference
--------- -------------------------- ---------- --------- -------------------------- ----------
110 (*) OTN-TDM capable (OTN-TDM) [This.I-D] 110 (*) OTN-TDM capable (OTN-TDM) [This.I-D]
(*) Suggested value (*) Suggested value
Same type of modification needs to applied to the IANA-GMPLS-TC-MIB Same type of modification needs to applied to the IANA-GMPLS-TC-MIB
at https://www.iana.org/assignments/ianagmplstc-mib/ianagmplstc-mib at https://www.iana.org/assignments/ianagmplstc-mib/ianagmplstc-mib
8.2. New TLVs 9.2. New sub-TLVs
This document defines 2 new TLVs that are carried in Interface This document defines 2 new sub-TLVs that are carried in Interface
Switching Capability Descriptors [RFC4203] with Signal Type OTN-TDM. Switching Capability Descriptors [RFC4203] with Signal Type OTN-TDM.
Each sub-TLV includes a 16-bit type identifier (the T-field). The
Each TLV includes a 16-bit type identifier (the T-field). The same same T-field values are applicable to the new sub-TLV.
T-field values are applicable to the new sub-TLV.
Upon approval of this document, IANA will create and maintain a new Upon approval of this document, IANA will create and maintain a new
registry, the "Types for sub-TLVs of OTN-TDM SCSI (Switch Capability sub-registry, the "Types for sub-TLVs of OTN-TDM SCSI (Switch
Specific Information)" registry under the "Open Shortest Path First Capability-Specific Information)" registry under the "Open Shortest
(OSPF) Traffic Engineering TLVs" registry, see http://www.iana.org/ Path First (OSPF) Traffic Engineering TLVs" registry, see http://
assignments/ospf-traffic-eng-tlvs/ospf-traffic-eng-tlvs.xml, with the www.iana.org/assignments/ospf-traffic-eng-tlvs/
TLV types as follows: ospf-traffic-eng-tlvs.xml, with the sub-TLV types as follows:
This document defines new TLV types as follows: This document defines new sub-TLV types as follows:
Value Sub-TLV Reference Value Sub-TLV Reference
--------- -------------------------- ---------- --------- -------------------------- ----------
0 Reserved [This.I-D] 0 Reserved [This.I-D]
1 Unreserved Bandwidth for [This.I-D] 1 Unreserved Bandwidth for [This.I-D]
fixed containers fixed containers
2 Unreserved/MAX Bandwidth for [This.I-D] 2 Unreserved/MAX Bandwidth for [This.I-D]
flexible containers flexible containers
3-65535 Unassigned 3-65535 Unassigned
Types are to be assigned via Standards Action as defined in Types are to be assigned via Standards Action as defined in
[RFC5226]. [RFC5226].
9. Contributors 10. Contributors
Diego Caviglia, Ericsson Diego Caviglia, Ericsson
Via E.Melen, 77 - Genova - Italy Via E.Melen, 77 - Genova - Italy
Email: diego.caviglia@ericsson.com Email: diego.caviglia@ericsson.com
Dan Li, Huawei Technologies Dan Li, Huawei Technologies
Bantian, Longgang District - Shenzhen 518129 P.R.China Bantian, Longgang District - Shenzhen 518129 P.R.China
Email: danli@huawei.com Email: danli@huawei.com
skipping to change at page 31, line 23 skipping to change at page 33, line 4
Steve.Balls@metaswitch.com Steve.Balls@metaswitch.com
Jonathan Hardwick Jonathan Hardwick
Jonathan.Hardwick@metaswitch.com Jonathan.Hardwick@metaswitch.com
Xihua Fu Xihua Fu
fu.xihua@zte.com.cn fu.xihua@zte.com.cn
Cyril Margaria Cyril Margaria
cyril.margaria@nsn.com cyril.margaria@nsn.com
Malcolm Betts Malcolm Betts
Malcolm.betts@zte.com.cn Malcolm.betts@zte.com.cn
10. Acknowledgements 11. Acknowledgements
The authors would like to thank Fred Gruman and Lou Berger for the The authors would like to thank Fred Gruman and Lou Berger for the
precious comments and suggestions. precious comments and suggestions.
11. References 12. References
11.1. Normative References
12.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering [RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering
(TE) Extensions to OSPF Version 2", RFC 3630, (TE) Extensions to OSPF Version 2", RFC 3630,
September 2003. September 2003.
[RFC4201] Kompella, K., Rekhter, Y., and L. Berger, "Link Bundling
in MPLS Traffic Engineering (TE)", RFC 4201, October 2005.
[RFC4203] Kompella, K. and Y. Rekhter, "OSPF Extensions in Support [RFC4203] Kompella, K. and Y. Rekhter, "OSPF Extensions in Support
of Generalized Multi-Protocol Label Switching (GMPLS)", of Generalized Multi-Protocol Label Switching (GMPLS)",
RFC 4203, October 2005. RFC 4203, October 2005.
[RFC4328] Papadimitriou, D., "Generalized Multi-Protocol Label [RFC4328] Papadimitriou, D., "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling Extensions for G.709 Optical Switching (GMPLS) Signaling Extensions for G.709 Optical
Transport Networks Control", RFC 4328, January 2006. Transport Networks Control", RFC 4328, January 2006.
11.2. Informative References 12.2. Informative References
[OTN-FWK] F.Zhang, D.Li, H.Li, S.Belotti, D.Ceccarelli, "Framework [OTN-FWK] F.Zhang, D.Li, H.Li, S.Belotti, D.Ceccarelli, "Framework
for GMPLS and PCE Control of G.709 Optical Transport for GMPLS and PCE Control of G.709 Optical Transport
networks, work in progress networks, work in progress
draft-ietf-ccamp-gmpls-g709-framework-13", June 2013. draft-ietf-ccamp-gmpls-g709-framework-13", June 2013.
[OTN-INFO] [OTN-INFO]
S.Belotti, P.Grandi, D.Ceccarelli, D.Caviglia, F.Zhang, S.Belotti, P.Grandi, D.Ceccarelli, D.Caviglia, F.Zhang,
D.Li, "Information model for G.709 Optical Transport D.Li, "Information model for G.709 Optical Transport
Networks (OTN), work in progress Networks (OTN), work in progress
 End of changes. 135 change blocks. 
243 lines changed or deleted 283 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/