idnits 2.17.1 draft-ietf-ccamp-gmpls-ospf-g709v3-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([G.709-2012]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: - Unreserved ODUj (16 bits): This field indicates the Unreserved Bandwidth at a particular priority level. This field MUST be set to the number of ODUs at the indicated the Signal Type for a particular priority level. One field MUST be present for each bit set in the Priority field, and is ordered to match the Priority field. Fields MUST not be present for priority levels that are not indicated in the Priority field.This field is REQUIRED for Type 1 (fixed container) TLVs, and MUST NOT be used for Type 2 TLVs. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: - Maximum LSP Bandwidth (32 bit): This field indicates the maximum bandwidth that can be allocated for a single LSP at a particular priority level. This field MUST be set to the maximum bandwidth, in bits/s in IEEE floating point format, available to a single LSP at the indicated Signal Type for a particular priority level. One field MUST be present for each bit set in the Priority field, and is ordered to match the Priority field. Fields MUST not be present for priority levels that are not indicated in the Priority field. This field is REQUIRED for Type 2 (variable container) TLVs, and MUST NOT be used for Type 1 TLVs. The advertisement of the MAX LSP bandwidth MUST take into account HO OPUk bit rate tolerance and be calculated according to the following formula: -- The document date (January 8, 2013) is 4124 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'G.805' is mentioned on line 307, but not defined == Outdated reference: A later version (-15) exists of draft-ietf-ccamp-gmpls-g709-framework-11 == Outdated reference: A later version (-13) exists of draft-ietf-ccamp-otn-g709-info-model-05 == Outdated reference: A later version (-12) exists of draft-ietf-ccamp-gmpls-signaling-g709v3-05 Summary: 1 error (**), 0 flaws (~~), 7 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 CCAMP Working Group D. Ceccarelli, Ed. 3 Internet-Draft D. Caviglia 4 Intended status: Standards Track Ericsson 5 Expires: July 12, 2013 F. Zhang 6 D. Li 7 Huawei Technologies 8 S. Belotti 9 P. Grandi 10 Alcatel-Lucent 11 R. Rao 12 K. Pithewan 13 Infinera Corporation 14 J. Drake 15 Juniper 16 January 8, 2013 18 Traffic Engineering Extensions to OSPF for Generalized MPLS (GMPLS) 19 Control of Evolving G.709 OTN Networks 20 draft-ietf-ccamp-gmpls-ospf-g709v3-05 22 Abstract 24 ITU-T Recommendation G.709 [G.709-2012] has introduced new fixed and 25 flexible Optical Data Unit (ODU) containers, enabling optimized 26 support for an increasingly abundant service mix. 28 This document describes Open Shortest Path First - Traffic 29 Engineering (OSPF-TE) routing protocol extensions to support 30 Generalized MPLS (GMPLS) control of all currently defined ODU 31 containers, in support of both sub-lambda and lambda level routing 32 granularity. 34 Status of this Memo 36 This Internet-Draft is submitted in full conformance with the 37 provisions of BCP 78 and BCP 79. 39 Internet-Drafts are working documents of the Internet Engineering 40 Task Force (IETF). Note that other groups may also distribute 41 working documents as Internet-Drafts. The list of current Internet- 42 Drafts is at http://datatracker.ietf.org/drafts/current/. 44 Internet-Drafts are draft documents valid for a maximum of six months 45 and may be updated, replaced, or obsoleted by other documents at any 46 time. It is inappropriate to use Internet-Drafts as reference 47 material or to cite them other than as "work in progress." 48 This Internet-Draft will expire on July 12, 2013. 50 Copyright Notice 52 Copyright (c) 2013 IETF Trust and the persons identified as the 53 document authors. All rights reserved. 55 This document is subject to BCP 78 and the IETF Trust's Legal 56 Provisions Relating to IETF Documents 57 (http://trustee.ietf.org/license-info) in effect on the date of 58 publication of this document. Please review these documents 59 carefully, as they describe your rights and restrictions with respect 60 to this document. Code Components extracted from this document must 61 include Simplified BSD License text as described in Section 4.e of 62 the Trust Legal Provisions and are provided without warranty as 63 described in the Simplified BSD License. 65 Table of Contents 67 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 68 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 69 2. OSPF-TE Extensions . . . . . . . . . . . . . . . . . . . . . . 4 70 3. TE-Link Representation . . . . . . . . . . . . . . . . . . . . 6 71 4. ISCD format extensions . . . . . . . . . . . . . . . . . . . . 7 72 4.1. Switch Capability Specific Information . . . . . . . . . . 8 73 4.1.1. Switch Capability Specific Information for fixed 74 containers . . . . . . . . . . . . . . . . . . . . . . 9 75 4.1.2. Switch Capability Specific Information for 76 variable containers . . . . . . . . . . . . . . . . . 9 77 4.1.3. Switch Capability Specific Information - Field 78 values and explanation . . . . . . . . . . . . . . . . 10 79 5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 80 5.1. MAX LSP Bandwidth fields in the ISCD . . . . . . . . . . . 13 81 5.2. Example of T,S and TSG utilization . . . . . . . . . . . . 15 82 5.2.1. Example of different TSGs . . . . . . . . . . . . . . 16 83 5.3. Example of ODUflex advertisement . . . . . . . . . . . . . 18 84 5.4. Example of single stage muxing . . . . . . . . . . . . . . 20 85 5.5. Example of multi stage muxing - Unbundled link . . . . . . 22 86 5.6. Example of multi stage muxing - Bundled links . . . . . . 24 87 5.7. Example of component links with non homogeneous 88 hierarchies . . . . . . . . . . . . . . . . . . . . . . . 25 89 6. Compatibility . . . . . . . . . . . . . . . . . . . . . . . . 27 90 7. Security Considerations . . . . . . . . . . . . . . . . . . . 28 91 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 92 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 29 93 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 31 94 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 31 95 11.1. Normative References . . . . . . . . . . . . . . . . . . . 31 96 11.2. Informative References . . . . . . . . . . . . . . . . . . 31 97 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 32 99 1. Introduction 101 G.709 Optican Transport Network (OTN) [G.709-2012] includes new fixed 102 and flexible ODU containers, two types of Tributary Slots (i.e., 103 1.25Gbps and 2.5Gbps), and supports various multiplexing 104 relationships (e.g., ODUj multiplexed into ODUk (jODUk format 152 is used to indicate the ODUj into ODUk multiplexing capability. 154 This notation can be repeated as needed depending on the number of 155 multiplexing levels. In the following the term "multiplexing tree" 156 is used to identify a multiplexing hierarchy where the root is always 157 a server ODUk/OTUk and any other supported multiplexed container is 158 represented with increasing granularity until reaching the leaf of 159 the tree. The tree can be structured with more than one branch if 160 the server ODUk/OTUk supports more than one hierarchy. 162 If for example a multiplexing hierarchy like the following one is 163 considered: 165 ODU2 ODU0 ODUflex ODU0 166 \ / \ / 167 | | 168 ODU3 ODU2 169 \ / 170 \ / 171 \ / 172 \ / 173 ODU4 175 The ODU4 is the root of the muxing tree, ODU3 and ODU2 are containers 176 directly multiplexed into the server and then ODU2, ODU0 are the 177 leaves of the ODU3 branch, while ODUflex and ODU0 are the leaves of 178 the ODU2 one. This means that on this traffic card it is possible to 179 have the following multiplexing capabilities: 181 ODU2->ODU3->ODU4 182 ODU0->ODU3->ODU4 183 ODUflex->ODU2->ODU4 184 ODU0->ODU2->ODU4 186 3. TE-Link Representation 188 G.709 ODUk/OTUk Links are represented as TE-Links in GMPLS Traffic 189 Engineering Topology for supporting ODUj layer switching. These TE- 190 Links can be modeled in multiple ways. 192 OTUk physical Link(s) can be modeled as a TE-Link(s). The TE-Link is 193 refferd to as OTUk-TE-Link. The OTUk-TE-Link advertises ODUj 194 switching capacity. The advertised capacity could include ODUk 195 switching capacity. Figure-1 below provides an illustration of one 196 hop ODUk TE-links. 198 +-------+ +-------+ +-------+ 199 | OTN | | OTN | | OTN | 200 |Switch |<- OTUk Link ->|Switch |<- OTUk Link ->|Switch | 201 | A | | B | | C | 202 +-------+ +-------+ +-------+ 204 |<-- TE-Link -->| |<-- TE-Link -->| 206 Figure 1: ODUk TE-Links 208 It is possible to create TE-Links that span more than one hop by 209 creating FA between non-adjacent nodes. Such TE-Links are also 210 termed ODUk-TE-Links. As in the one hop case, these types of ODUk- 211 TE-Links also advertise ODUj switching capacity. The advertised 212 capacity could include ODUk switching capacity. 214 +-------+ +-------+ +-------+ 215 | OTN | | OTN | | OTN | 216 |Switch |<- OTUk Link ->|Switch |<- OTUk Link ->|Switch | 217 | A | | B | | C | 218 +-------+ +-------+ +-------+ 219 ODUk Switched 221 |<------------- ODUk Link ------------->| 222 |<-------------- TE-Link--------------->| 224 Figure 2: Multiple hop TE-Link 226 4. ISCD format extensions 228 The ISCD describes the switching capability of an interface 229 [RFC4202]. This document defines a new Switching Capability value 230 for OTN [G.709-2012] as follows: 232 Value Type 233 ----- ---- 234 110 (TBA by IANA) OTN-TDM capable (OTN-TDM) 236 When supporting the extensions defined in this document, the 237 Switching Capability and Encoding values MUST be used as follows: 239 - Switching Capability = OTN-TDM 240 - Encoding Type = G.709 ODUk (Digital Path) [as defined in RFC4328] 242 Both for fixed and flexible ODUs the same switching type and encoding 243 values MUST be used. When Switching Capability and Encoding fields 244 are set to values as stated above, the Interface Switching Capability 245 Descriptor MUST be interpreted as defined in [RFC4203]. 247 Maximum LSP Bandwidth 249 The MAX LSP bandwidth field MUST be used according to [RFC4203]: i.e. 250 0 <= Max LSP Bandwidth <= ODUk/OTUk and intermediate values are those 251 on the branch of OTN switching hierarchy supported by the interface. 252 E.g. in the OTU4 link it could be possible to have ODU4 as MAX LSP 253 Bandwidth for some priorities, ODU3 for others, ODU2 for some others 254 etc. The bandwidth unit MUST be in bytes per second and the encoding 255 MUST be in Institute of Electrical and Electronic Engineers (IEEE) 256 floating point format. The discrete values for various ODUs is shown 257 in the table below. 259 +---------------------+------------------------------+-----------------+ 260 | ODU Type | ODU nominal bit rate |Value in Byte/Sec| 261 +---------------------+------------------------------+-----------------+ 262 | ODU0 | 1 244 160 kbits/s | 0x4D1450C0 | 263 | ODU1 | 239/238 x 2 488 320 kbit/s | 0x4D94F048 | 264 | ODU2 | 239/237 x 9 953 280 kbit/s | 0x4E959129 | 265 | ODU3 | 239/236 x 39 813 120 kbit/s | 0X4F963367 | 266 | ODU4 | 239/227 x 99 532 800 kbit/s | 0x504331E3 | 267 | ODU2e | 239/237 x 10 312 500 kbit/s | 0x4E9AF70A | 268 | | | | 269 | ODUflex for CBR | | MAX LSP | 270 | Client signals | 239/238 x client signal | BANDWIDTH | 271 | | bit rate | | 272 | ODUflex for GFP-F | | MAX LSP | 273 |Mapped client signal | Configured bit rate | BANDWIDTH | 274 | | | | 275 | | | | 276 |ODU flex resizable | Configured bit rate | MAX LSP | 277 | | | BANDWIDTH | 278 +---------------------+------------------------------+-----------------+ 280 A single ISCD MAY be used for the advertisement of unbundled or 281 bundled links supporting homogeneous multiplexing hierarchies and the 282 same Tributary Slot Granularity (TSG). A different ISCD MUST be used 283 for each different muxing hierarchy (muxing tree in the following 284 examples) and different TSG supported within the TE Link. 286 Component links with different hierarchies or TSG MUST NOT be 287 bundled. 289 4.1. Switch Capability Specific Information 291 The technology specific part of the OTN ISCD may include a variable 292 number of sub-TLVs called Bandwidth sub-TLVs. Each sub-TLV is 293 encoded with the TLV header as defined in [RFC3630] section 2.3.2. 294 The muxing hierarchy tree MUST be encoded as an order independent 295 list. Two types of Bandwidth TLV are defined (TBA by IANA): 297 - Type 1 - Unreserved Bandwidth for fixed containers 299 - Type 2 - Unreserved/MAX LSP Bandwidth for flexible containers 301 The SCSI MUST include one Type 1 sub-TLV for any fixed container and 302 one Type 2 sub-TLV for any variable container. 304 With respect to ODUflex, ODUflex Constant Bit Rate (CBR) and ODUflex 305 Generig Framing Procedure-Frame mapped (GFP-F) MUST always be 306 advertised in separate TLVs as they use different adaptation 307 functions [G.805]. In the case both GFP-F resizable and non 308 resizable (i.e. 21 and 22) are supported, Signal Type 21 implicitely 309 supports also signal Signal Type 22, so only Signal Type 21 MUST be 310 advertised. Signal Type 22 MUST be used only for non resizable 311 resources. 313 4.1.1. Switch Capability Specific Information for fixed containers 315 The format of the Bandwidth TLV for fixed containers is depicted in 316 the following figure: 318 0 1 2 3 319 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 320 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 321 | Type = 1 (Unres-fix) | Length | 322 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 323 | Signal type | Num of stages |T|S| TSG | Res | Priority | 324 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 325 | Stage#1 | ... | Stage#N | Padding | 326 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 327 | Unreserved ODUj at Prio 0 | ..... | 328 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 329 | Unreserved ODUj at Prio 7 | Unreserved Padding | 330 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 332 Figure 3: Bandwidth TLV - Type 1 - 334 The values of the fields shown in figure 4 are explained in section 335 4.1.3. 337 4.1.2. Switch Capability Specific Information for variable containers 339 The format of the Bandwidth TLV for variable containers is depicted 340 in the following figure: 342 0 1 2 3 343 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 344 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 345 | Type = 2 (Unres/MAX-var) | Length | 346 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 347 | Signal type | Num of stages |T|S| TSG | Res | Priority | 348 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 349 | Stage#1 | ... | Stage#N | Padding | 350 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 351 | Unreserved Bandwidth at priority 0 | 352 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 353 | ... | 354 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 355 | Unreserved Bandwidth at priority 7 | 356 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 357 | MAX LSP Bandwidth at priority 0 | 358 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 359 | ... | 360 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 361 | MAX LSP Bandwidth at priority 7 | 362 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 364 Figure 4: Bandwidth TLV - Type 2 - 366 The values of the fields shown in figure 4 are explained in section 367 4.1.3. 369 4.1.3. Switch Capability Specific Information - Field values and 370 explanation 372 The fields in the Bandwidth TLV MUST be filled as follows: 374 - Signal Type (8 bits): Indicates the ODU type being advertised. 375 Values are defined in [OTN-SIG]. 377 - Number of stages (8 bits): This field indicates the number of 378 multiplexing stages used to transport the indicated signal type. 379 It MUST be set to the number of stages represented in the TLV. 381 - Flags (8 bits): 383 - T Flag (bit 17): Indicates whether the advertised bandwidth 384 can be terminated. When the signal type can be terminated T 385 MUST be set, while when the signal type cannot be terminated T 386 MUST be cleared. 388 - S Flag (bit 18): Indicates whether the advertised bandwidth 389 can be switched. When the signal type can be switched S MUST 390 be set, while when the signal type cannot be switched S MUST be 391 cleared. 393 The value 0 in both T and S bits MUST NOT be used. 395 - TSG: Tributary Slot Granularity (3 bits): Used for the 396 advertisement of the supported Tributary Slot granularity. The 397 following values MUST be used: 399 - 0 - Ignored 401 - 1 - 1.25 Gbps/2.5Gbps 403 - 2 - 2.5 Gbps only 405 - 3 - 1.25 Gbps only 407 - 4-7 - Reserved 409 Value 1 MUST be used on those interfaces where the fallback 410 procedure is enabled and the default value of 1.25 Gbps can be 411 falled back to 2.5 if needed. Value 2 MUST be used on [RFC4328] 412 interfaces while value 3 MUST be used on [G.709-2012] interfaces 413 where the fallback procedure is unsupported/disabled. Value 0 414 MUST be used for non multiplexed signal (i.e. non OTN client). 416 - Res (3 bits): reserved bits. MUST be set to 0 and ignored on 417 receipt. 419 - Priority (8 bits): field with 1 flag for each priority. A bit 420 MUST be set (1) for each corresponding priority represented in the 421 TLV and MUST NOT be set (0) when the related priority is not 422 represented. At least one priority level MUST be advertised. A 423 value of zero (0) MUST be used when not overridden by local 424 policy. 426 - Stage (8 bits): Each Stage field indicates the signal type 427 beloning to the muxing branch used to transport the signal 428 indicated in the Signal Type field. The number of Stage fields 429 included in a TLV MUST equal the value of the Number of Stages 430 field. The Stage fields MUST be ordered to match the data plane 431 in ascending order (from the lowest order ODU to the highest order 432 ODU). The values of the Stage fields MUST be the same ones 433 defined for the Signal Type field. If the number of stages is 0, 434 then the Stage and Padding fields MUST be omitted. 436 - Padding (variable): The Padding field is used to ensure the 32 437 bit alignment of stage fields. The length of the Padding field is 438 always a multiple of 8 bits (1 byte). Its length can be 439 calculated, in bytes, as: 4- "value of Number of Stages field". 440 When present, the Padding field MUST be set to a zero (0) value on 441 transmission and MUST be ignored on receipt. 443 - Unreserved ODUj (16 bits): This field indicates the Unreserved 444 Bandwidth at a particular priority level. This field MUST be set 445 to the number of ODUs at the indicated the Signal Type for a 446 particular priority level. One field MUST be present for each bit 447 set in the Priority field, and is ordered to match the Priority 448 field. Fields MUST not be present for priority levels that are 449 not indicated in the Priority field.This field is REQUIRED for 450 Type 1 (fixed container) TLVs, and MUST NOT be used for Type 2 451 TLVs. 453 Unreserved Padding (variable): The Padding field is used to ensure 454 the 32 bit alignment of Unreserved ODUj fields. The length of the 455 Unreserved Padding field is always a multiple of 16 bits (2 byte). 456 Its length can be calculated, in multiple of 2 bytes, as: "number 457 of priorities indicated in Priorities field" % 2 . When present, 458 the Unreserved Padding field MUST be set to a zero (0) value on 459 transmission and MUST be ignored on receipt. 461 - Maximum LSP Bandwidth (32 bit): This field indicates the maximum 462 bandwidth that can be allocated for a single LSP at a particular 463 priority level. This field MUST be set to the maximum bandwidth, 464 in bits/s in IEEE floating point format, available to a single LSP 465 at the indicated Signal Type for a particular priority level. One 466 field MUST be present for each bit set in the Priority field, and 467 is ordered to match the Priority field. Fields MUST not be 468 present for priority levels that are not indicated in the Priority 469 field. This field is REQUIRED for Type 2 (variable container) 470 TLVs, and MUST NOT be used for Type 1 TLVs. The advertisement of 471 the MAX LSP bandwidth MUST take into account HO OPUk bit rate 472 tolerance and be calculated according to the following formula: 474 Max LSP BW = (# available TS) * (ODTUk.ts nominal bit rate) * 475 (1-HO OPUk bit rate tolerance) 477 5. Examples 479 The examples in the following pages are not normative and are not 480 intended to imply or mandate any specific implementation. 482 5.1. MAX LSP Bandwidth fields in the ISCD 484 This example shows how the MAX LSP Bandwidth fields of the ISCD are 485 filled accordingly to the evolving of the TE-link bandwidth 486 occupancy. In the example an OTU4 link is considered, with supported 487 priorities 0,2,4,7 and muxing hierarchy ODU1->ODU2->ODU3->ODU4. 489 At time T0, with the link completely free, the advertisement would 490 be: 492 0 1 2 3 493 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 494 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 495 | SwCap=OTN_TDM | Encoding = 12 | Reserved (all zeros) | 496 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 497 | Max LSP Bandwidth at priority 0 = 100Gbps | 498 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 499 | Max LSP Bandwidth at priority 1 = 0 | 500 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 501 | Max LSP Bandwidth at priority 2 = 100Gbps | 502 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 503 | Max LSP Bandwidth at priority 3 = 0 | 504 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 505 | Max LSP Bandwidth at priority 4 = 100Gbps | 506 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 507 | Max LSP Bandwidth at priority 5 = 0 | 508 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 509 | Max LSP Bandwidth at priority 6 = 0 | 510 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 511 | Max LSP Bandwidth at priority 7 = 100Gbps | 512 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 513 | Switch Capability Specific Information | 514 | (variable length) | 515 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 517 Figure 5: Example 1 - MAX LSP Bandwidth fields in the ISCD @T0 519 At time T1 an ODU3 at priority 2 is set-up, so for priority 0 the MAX 520 LSP Bandwidth is still equal to the ODU4 bandwidth, while for 521 priorities from 2 to 7 (excluding the non supported ones) the MAX LSP 522 Bandwidth is equal to ODU3, as no more ODU4s are available and the 523 next supported ODUj in the hierarchy is ODU3.The advertisement is 524 updated as follows: 526 0 1 2 3 527 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 528 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 529 | SwCap=OTN_TDM | Encoding = 12 | Reserved (all zeros) | 530 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 531 | Max LSP Bandwidth at priority 0 = 100Gbps | 532 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 533 | Max LSP Bandwidth at priority 1 = 0 | 534 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 535 | Max LSP Bandwidth at priority 2 = 40Gbps | 536 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 537 | Max LSP Bandwidth at priority 3 = 0 | 538 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 539 | Max LSP Bandwidth at priority 4 = 40Gbps | 540 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 541 | Max LSP Bandwidth at priority 5 = 0 | 542 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 543 | Max LSP Bandwidth at priority 6 = 0 | 544 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 545 | Max LSP Bandwidth at priority 7 = 40Gbps | 546 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 547 | Switch Capability Specific Information | 548 | (variable length) | 549 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 551 Figure 6: Example 1 - MAX LSP Bandwidth fields in the ISCD @T1 553 At time T2 an ODU2 at priority 4 is set-up. The first ODU3 is no 554 longer available since T1 as it was kept by the ODU3 LSP, while the 555 second is no more available and just 3 ODU2 are left in it. ODU2 is 556 now the MAX LSP bandwidth for priorities higher than 4. The 557 advertisement is updated as follows: 559 0 1 2 3 560 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 561 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 562 | SwCap=OTN_TDM | Encoding = 12 | Reserved (all zeros) | 563 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 564 | Max LSP Bandwidth at priority 0 = 100Gbps | 565 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 566 | Max LSP Bandwidth at priority 1 = 0 | 567 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 568 | Max LSP Bandwidth at priority 2 = 40Gbps | 569 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 570 | Max LSP Bandwidth at priority 3 = 0 | 571 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 572 | Max LSP Bandwidth at priority 4 = 10Gbps | 573 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 574 | Max LSP Bandwidth at priority 5 = 0 | 575 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 576 | Max LSP Bandwidth at priority 6 = 0 | 577 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 578 | Max LSP Bandwidth at priority 7 = 10Gbps | 579 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 580 | Switch Capability Specific Information | 581 | (variable length) | 582 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 584 Figure 7: Example 1 - MAX LSP Bandwidth fields in the ISCD @T2 586 5.2. Example of T,S and TSG utilization 588 In this example an interface with Tributary Slot Type 1.25 Gbps and 589 fallback procedure enabled is considered (TSG=1). It supports the 590 simple ODU1->ODU2->ODU3 hierarchy and priorities 0 and 3. Suppose 591 that in this interface the ODU3 signal type can be both switched or 592 terminated, the ODU2 can only be terminated and the ODU1 switched 593 only. For the advertisement of the capabilities of such interface a 594 single ISCD is used and its format is as follows: 596 0 1 2 3 597 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 598 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 599 | Type = 1 (Unres-fix) | Length = 12 | 600 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 601 |Sig type=ODU1 | #stages= 2 |T0|S1|001| Res |1|0|0|1|0|0|0|0| 602 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 603 | Stage#1=ODU2 | Stage#2=ODU3 | Padding (all zeros) | 604 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 605 | Unres ODU1 at Prio 0 | Unres ODU1 at Prio 3 | 606 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 607 | Type = 1 (Unres-fix) | Length = 12 | 608 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 609 |Sig type=ODU2 | #stages= 1 |T1|S0|001| Res |1|0|0|1|0|0|0|0| 610 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 611 | Stage#1=ODU3 | Padding (all zeros) | 612 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 613 | Unres ODU2 at Prio 0 | Unres ODU2 at Prio 3 | 614 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 615 | Type = 1 (Unres-fix) | Length = 8 | 616 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 617 |Sig type=ODU3 | #stages= 0 |T1|S1|001| Res |1|0|0|1|0|0|0|0| 618 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 619 | Unres ODU3 at Prio 0 | Unres ODU3 at Prio 3 | 620 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 622 Figure 8: Example 2 - TSG, T and S utilization 624 5.2.1. Example of different TSGs 626 In this example two interfaces with homogeneous hierarchies but 627 different Tributary Slot Types are considered. The first one 628 supports a [RFC4328] interface (TSG=2) while the second one a G.709- 629 2012 interface with fallback procedure disabled (TSG=3). Both of 630 them support ODU1->ODU2->ODU3 hierarchy and priorities 0 and 3. T 631 and S bits values are not relevant to this example. For the 632 advertisement of the capabilities of such interfaces two different 633 ISCDs are used and the format of their SCSIs is as follows: 635 SCSI of ISCD 1 - TSG=2 636 0 1 2 3 637 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 638 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 639 | Type = 1 (Unres-fix) | Length = 12 | 640 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 641 |Sig type=ODU1 | #stages= 2 |T|S| 2 |0 0 0|1|0|0|1|0|0|0|0| 642 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 643 | Stage#1=ODU2 | Stage#2=ODU3 | Padding (all zeros) | 644 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 645 | Unres ODU1 at Prio 0 | Unres ODU1 at Prio 3 | 646 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 648 SCSI of ISCD 2 - TSG=3 649 0 1 2 3 650 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 651 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 652 | Type = 1 (Unres-fix) | Length = 12 | 653 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 654 |Sig type=ODU1 | #stages= 2 |T|S| 3 |0 0 0|1|0|0|1|0|0|0|0| 655 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 656 | Stage#1=ODU2 | Stage#2=ODU3 | Padding (all zeros) | 657 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 658 | Unres ODU1 at Prio 0 | Unres ODU1 at Prio 3 | 659 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 661 Figure 9: Example 2.1 - Different TSGs utilization 663 A particular case in which hierarchies with the same muxing tree but 664 with different exported TSG MUST be considered as non homogenous 665 hierarchies is the case in which an H-LPS and the client LSP are 666 terminated on the same egress node. What can happen is that a loose 667 Explicit Route Object (ERO) is used at the hop where the signaled LSP 668 is nested into the Hierarchical-LSP (H-LSP) (penultimate hop of the 669 LSP). 671 In the following figure, node C receives from A a loose ERO towards 672 node E and must choose between the ODU2 H-LSP on if1 or the one on 673 if2. In case the H-LSP on if1 exports a TS=1.25Gbps and if2 a 674 TS=2.5Gbps and the service LSP being signaled needs a 1.25Gbps 675 tributary slot, only the H-LSP on if1 can be used to reach node E. 676 For further details please see section 4.1 of the [OTN-INFO]. 678 ODU0-LSP 679 ..........................................................+ 680 | | 681 | ODU2-H-LSP | 682 | +-------------------------------+ 683 | | | 684 +--+--+ +-----+ +-----+ if1 +-----+ +-----+ 685 | | OTU3 | | OTU3 | |---------| |---------| | 686 | A +------+ B +------+ C | if2 | D | | E | 687 | | | | | |---------| |---------| | 688 +-----+ +-----+ +-----+ +-----+ +-----+ 690 ... Service LSP 691 --- H-LSP 693 Figure 10: Example - Service LSP and H-LSP terminating on the same 694 node 696 5.3. Example of ODUflex advertisement 698 In this example the advertisement of an ODUflex->ODU3 hierarchy is 699 shown. In case of ODUflex advertisement the MAX LSP bandwidth needs 700 to be advertised and in some cases also information about the 701 Unreserved bandwidth could be useful. The amount of Unreserved 702 bandwidth does not give a clear indication of how many ODUflex LSP 703 can be set up either at the MAX LSP Bandwidth or at different rates, 704 as it gives no information about the spatial allocation of the free 705 TSs. 707 An indication of the amount of Unreserved bandwidth could be useful 708 during the path computation process, as shown in the following 709 example. Supposing there are two TE-links (A and B) with MAX LSP 710 Bandwidth equal to 10 Gbps each. In case 50Gbps of Unreserved 711 Bandwidth are available on Link A, 10Gbps on Link B and 3 ODUflex 712 LSPs of 10 GBps each, have to be restored, for sure only one can be 713 restored along Link B and it is probable (but not sure) that two of 714 them can be restored along Link A. T, S and TSG fields are not 715 relevant to this example. 717 In the case of ODUflex advertisement the Type 2 Bandwidth TLV is 718 used. 720 0 1 2 3 721 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 722 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 723 | Type = 2 (Unres/MAX-var) | Length = 72 | 724 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 725 |S. type=ODUflex| #stages= 1 |T|S| TSG |0 0 0| Priority(8) | 726 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 727 | Stage#1=ODU3 | Padding (all zeros) | 728 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 729 | Unreserved Bandwidth at priority 0 | 730 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 731 | Unreserved Bandwidth at priority 1 | 732 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 733 | Unreserved Bandwidth at priority 2 | 734 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 735 | Unreserved Bandwidth at priority 3 | 736 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 737 | Unreserved Bandwidth at priority 4 | 738 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 739 | Unreserved Bandwidth at priority 5 | 740 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 741 | Unreserved Bandwidth at priority 6 | 742 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 743 | Unreserved Bandwidth at priority 7 | 744 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 745 | MAX LSP Bandwidth at priority 0 | 746 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 747 | MAX LSP Bandwidth at priority 1 | 748 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 749 | MAX LSP Bandwidth at priority 2 | 750 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 751 | MAX LSP Bandwidth at priority 3 | 752 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 753 | MAX LSP Bandwidth at priority 4 | 754 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 755 | MAX LSP Bandwidth at priority 5 | 756 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 757 | MAX LSP Bandwidth at priority 6 | 758 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 759 | MAX LSP Bandwidth at priority 7 | 760 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 762 Figure 11: Example 3 - ODUflex advertisement 764 5.4. Example of single stage muxing 766 Supposing there is 1 OTU4 component link supporting single stage 767 muxing of ODU1, ODU2, ODU3 and ODUflex, the supported hierarchy can 768 be summarized in a tree as in the following figure. For sake of 769 simplicity we assume that also in this case only priorities 0 and 3 770 are supported. T, S and TSG fields are not relevant to this example. 772 ODU1 ODU2 ODU3 ODUflex 773 \ \ / / 774 \ \ / / 775 \ \/ / 776 ODU4 778 and the related SCSIs as follows: 780 0 1 2 3 781 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 782 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 783 | Type = 1 (Unres-fix) | Length = 8 | 784 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 785 |Sig type=ODU4 | #stages= 0 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 786 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 787 | Unres ODU4 at Prio 0 =1 | Unres ODU4 at Prio 3 =1 | 788 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 789 | Type = 1 (Unres-fix) | Length = 12 | 790 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 791 |Sig type=ODU1 | #stages= 1 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 792 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 793 | Stage#1=ODU4 | Padding (all zeros) | 794 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 795 | Unres ODU1 at Prio 0 =40 | Unres ODU1 at Prio 3 =40 | 796 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 797 | Type = 1 (Unres-fix) | Length = 12 | 798 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 799 |Sig type=ODU2 | #stages= 1 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 800 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 801 | Stage#1=ODU4 | Padding (all zeros) | 802 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 803 | Unres ODU2 at Prio 0 =10 | Unres ODU2 at Prio 3 =10 | 804 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 805 | Type = 1 (Unres-fix) | Length = 12 | 806 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 807 |Sig type=ODU3 | #stages= 1 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 808 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 809 | Stage#1=ODU4 | Padding (all zeros) | 810 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 811 | Unres ODU3 at Prio 0 =2 | Unres ODU3 at Prio 3 =2 | 812 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 813 | Type = 2 (Unres/MAX-var) | Length = 24 | 814 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 815 |S. type=ODUflex| #stages= 1 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 816 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 817 | Stage#1=ODU4 | Padding (all zeros) | 818 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 819 | Unreserved Bandwidth at priority 0 =100Gbps | 820 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 821 | Unreserved Bandwidth at priority 3 =100Gbps | 822 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 823 | MAX LSP Bandwidth at priority 0 =100Gbps | 824 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 825 | MAX LSP Bandwidth at priority 3 =100Gbps | 826 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 827 Figure 12: Example 4 - Single stage muxing 829 5.5. Example of multi stage muxing - Unbundled link 831 Supposing there is 1 OTU4 component link with muxing capabilities as 832 shown in the following figure: 834 ODU2 ODU0 ODUflex ODU0 835 \ / \ / 836 | | 837 ODU3 ODU2 838 \ / 839 \ / 840 \ / 841 \ / 842 ODU4 844 and supported pririties 0 and 3, the advertisement is composed by the 845 following Bandwidth TLVs (T, S and TSG fields are not relevant to 846 this example): 848 0 1 2 3 849 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 850 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 851 | Type = 1 (Unres-fix) | Length = 8 | 852 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 853 |Sig type=ODU4 | #stages= 0 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 854 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 855 | Unres ODU4 at Prio 0 =1 | Unres ODU4 at Prio 3 =1 | 856 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 857 | Type = 1 (Unres-fix) | Length = 12 | 858 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 859 |Sig type=ODU3 | #stages= 1 |T|S| TSG | Res |1|0|0|1|0|0|0|0| 860 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 861 | Stage#1=ODU4 | Padding (all zeros) | 862 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 863 | Unres ODU3 at Prio 0 =2 | Unres ODU3 at Prio 3 =2 | 864 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 865 | Type = 1 (Unres-fix) | Length = 12 | 866 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 867 |Sig type=ODU2 | #stages= 1 |T|S|0 0 0| Res |1|0|0|1|0|0|0|0| 868 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 869 | Stage#1=ODU4 | Padding (all zeros) | 870 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 871 | Unres ODU2 at Prio 0 =10 | Unres ODU2 at Prio 3 =10 | 872 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 873 | Type = 1 (Unres-fix) | Length = 12 | 874 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 875 |Sig type=ODU2 | #stages= 2 |T|S|0 0 0| Res |1|0|0|1|0|0|0|0| 876 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 877 | Stage#1=ODU3 | Stage#2=ODU4 | Padding (all zeros) | 878 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 879 | Unres ODU2 at Prio 0 =8 | Unres ODU2 at Prio 3 =8 | 880 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 881 | Type = 1 (Unres-fix) | Length = 12 | 882 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 883 |Sig type=ODU0 | #stages= 2 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 884 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 885 | Stage#1=ODU3 | Stage#2=ODU4 | Padding (all zeros) | 886 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 887 | Unres ODU0 at Prio 0 =64 | Unres ODU0 at Prio 3 =64 | 888 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 889 | Type = 1 (Unres-fix) | Length = 12 | 890 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 891 |Sig type=ODU0 | #stages= 2 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 892 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 893 | Stage#1=ODU2 | Stage#2=ODU4 | Padding (all zeros) | 894 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 895 | Unres ODU0 at Prio 0 =80 | Unres ODU0 at Prio 3 =80 | 896 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 897 | Type = 2 (Unres/MAX-var) | Length = 24 | 898 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 899 |S.type=ODUflex | #stages= 2 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 900 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 901 | Stage#1=ODU2 | Stage#2=ODU4 | Padding (all zeros) | 902 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 903 | Unreserved Bandwidth at priority 0 =100Gbps | 904 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 905 | Unreserved Bandwidth at priority 3 =100Gbps | 906 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 907 | MAX LSP Bandwidth at priority 0 =10Gbps | 908 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 909 | MAX LSP Bandwidth at priority 3 =10Gbps | 910 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 912 Figure 13: Example 5 - Multi stage muxing - Unbundled link 914 5.6. Example of multi stage muxing - Bundled links 916 In this example 2 OTU4 component links with the same supported TSG 917 and homogeneous muxing hierarchies are considered. The following 918 muxing capabilities trees are supported: 920 Component Link#1 Component Link#2 921 ODU2 ODU0 ODU2 ODU0 922 \ / \ / 923 | | 924 ODU3 ODU3 925 | | 926 ODU4 ODU4 928 Considering only supported priorities 0 and 3, the advertisement is 929 as follows (T, S and TSG fields are not relevant to this example): 931 0 1 2 3 932 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 933 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 934 | Type = 1 (Unres-fix) | Length = 8 | 935 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 936 |Sig type=ODU4 | #stages= 0 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 937 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 938 | Unres ODU4 at Prio 0 =2 | Unres ODU4 at Prio 3 =2 | 939 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 940 | Type = 1 (Unres-fix) | Length = 12 | 941 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 942 |Sig type=ODU3 | #stages= 1 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 943 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 944 | Stage#1=ODU4 | Padding (all zeros) | 945 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 946 | Unres ODU3 at Prio 0 =4 | Unres ODU3 at Prio 3 =4 | 947 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 948 | Type = 1 (Unres-fix) | Length = 12 | 949 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 950 |Sig type=ODU2 | #stages= 2 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 951 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 952 | Stage#1=ODU3 | Stage#2=ODU4 | Padding (all zeros) | 953 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 954 | Unres ODU2 at Prio 0 =16 | Unres ODU2 at Prio 3 =16 | 955 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 956 | Type = 1 (Unres-fix) | Length = 12 | 957 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 958 |Sig type=ODU0 | #stages= 2 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 959 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 960 | Stage#1=ODU3 | Stage#2=ODU4 | Padding (all zeros) | 961 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 962 | Unres ODU0 at Prio 0 =128 | Unres ODU0 at Prio 3 =128 | 963 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 965 Figure 14: Example 6 - Multi stage muxing - Bundled links 967 5.7. Example of component links with non homogeneous hierarchies 969 In this example 2 OTU4 component links with the same supported TSG 970 and non homogeneous muxing hierarchies are considered. The following 971 muxing capabilities trees are supported: 973 Component Link#1 Component Link#2 974 ODU2 ODU0 ODU1 ODU0 975 \ / \ / 976 | | 977 ODU3 ODU2 978 | | 979 ODU4 ODU4 981 Considering only supported priorities 0 and 3, the advertisement uses 982 two different ISCDs, one for each hierarchy (T, S and TSG fields are 983 not relevant to this example). In the following figure, the SCSI of 984 each ISCD is shown: 986 SCSI of ISCD 1 - Component Link#1 988 0 1 2 3 989 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 990 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 991 | Type = 1 (Unres-fix) | Length = 8 | 992 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 993 |Sig type=ODU4 | #stages= 0 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 994 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 995 | Unres ODU4 at Prio 0 =1 | Unres ODU4 at Prio 3 =1 | 996 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 997 | Type = 1 (Unres-fix) | Length = 12 | 998 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 999 |Sig type=ODU3 | #stages= 1 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 1000 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1001 | Stage#1=ODU4 | Padding (all zeros) | 1002 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1003 | Unres ODU3 at Prio 0 =2 | Unres ODU3 at Prio 3 =2 | 1004 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1005 | Type = 1 (Unres-fix) | Length = 12 | 1006 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1007 |Sig type=ODU2 | #stages= 2 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 1008 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1009 | Stage#1=ODU3 | Stage#2=ODU4 | Padding (all zeros) | 1010 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1011 | Unres ODU2 at Prio 0 =8 | Unres ODU2 at Prio 3 =8 | 1012 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1013 | Type = 1 (Unres-fix) | Length = 12 | 1014 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1015 |Sig type=ODU0 | #stages= 2 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 1016 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1017 | Stage#1=ODU3 | Stage#2=ODU4 | Padding (all zeros) | 1018 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1019 | Unres ODU0 at Prio 0 =64 | Unres ODU0 at Prio 3 =64 | 1020 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1022 SCSI of ISCD 2 - Component Link#2 1024 0 1 2 3 1025 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 1026 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1027 | Type = 1 (Unres-fix) | Length = 8 | 1028 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1029 |Sig type=ODU4 | #stages= 0 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 1030 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1031 | Unres ODU4 at Prio 0 =1 | Unres ODU4 at Prio 3 =1 | 1032 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1033 | Type = 1 (Unres-fix) | Length = 12 | 1034 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1035 |Sig type=ODU2 | #stages= 1 |T|S| TSG | Res |1|0|0|1|0|0|0|0| 1036 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1037 | Stage#1=ODU4 | Padding (all zeros) | 1038 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1039 | Unres ODU2 at Prio 0 =10 | Unres ODU2 at Prio 3 =10 | 1040 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1041 | Type = 1 (Unres-fix) | Length = 12 | 1042 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1043 |Sig type=ODU1 | #stages= 2 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 1044 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1045 | Stage#1=ODU2 | Stage#2=ODU4 | Padding (all zeros) | 1046 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1047 | Unres ODU1 at Prio 0 =40 | Unres ODU1 at Prio 3 =40 | 1048 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1049 | Type = 1 (Unres-fix) | Length = 12 | 1050 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1051 |Sig type=ODU0 | #stages= 2 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 1052 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1053 | Stage#1=ODU2 | Stage#2=ODU4 | Padding (all zeros) | 1054 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1055 | Unres ODU0 at Prio 0 =80 | Unres ODU0 at Prio 3 =80 | 1056 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1058 Figure 15: Example 7 - Multi stage muxing - Non homogeneous 1059 hierarchies 1061 6. Compatibility 1063 All implementations of this document MAY support also advertisement 1064 as defined in [RFC4328]. When nodes support both advertisement 1065 methods, implementations MUST support the configuration of which 1066 advertisement method is followed. The choice of which is used is 1067 based on policy and is out of scope of the document. This enables 1068 nodes following each method to identify similar supporting nodes and 1069 compute paths using only the appropriate nodes. 1071 7. Security Considerations 1073 This document, as [RFC4203], specifies the contents of Opaque LSAs in 1074 OSPFv2. As Opaque LSAs are not used for SPF computation or normal 1075 routing, the extensions specified here have no direct effect on IP 1076 routing. Tampering with GMPLS TE LSAs may have an effect on the 1077 underlying transport (optical and/or SONET-SDH) network. [RFC3630] 1078 suggests mechanisms such as [RFC2154] to protect the transmission of 1079 this information, and those or other mechanisms should be used to 1080 secure and/or authenticate the information carried in the Opaque 1081 LSAs. 1083 For security threats, defensive techniques, monitoring/detection/ 1084 reporting of security attacks and requirements please refer to 1085 [RFC5920] . 1087 8. IANA Considerations 1089 Upon approval of this document, IANA will make the assignment in the 1090 "Switching Types" section of the "GMPLS Signaling Parameters" 1091 registry located at 1092 http://www.iana.org/assignments/gmpls-sig-parameters: 1094 Value Type Reference 1095 --------- -------------------------- ---------- 1096 110 (*) OTN-TDM capable (OTN-TDM) [This.I-D] 1098 (*) Suggested value 1100 This document defines 2 new TLVs that are carried in Interface 1101 Switching Capability Descriptors [RFC4203] with Signal Type OTN-TDM. 1102 Each TLV includes a 16-bit type identifier (the T-field). The same 1103 T-field values are applicable to the new sub-TLV. 1105 Upon approval of this document, IANA will create and maintain a new 1106 registry, the "sub-TLVs of the OTN-TDM Interface Switching Capability 1107 Descriptor TLV" registry under the "Open Shortest Path First (OSPF) 1108 Traffic Engineering TLVs" registry, see http://www.iana.org/ 1109 assignments/ospf-traffic-eng-tlvs/ospf-traffic-eng-tlvs.xml, with the 1110 TLV types as follows: 1112 - TLV Type (T-field value) 1113 - TLV Name 1114 - Whether allowed on ISCD sub-TLV 1116 This document defines new TLV types as follows: 1118 - TLV Type = 1 1119 - TLV Name = Unreserved Bandwidth for fixed containers 1120 - allowed on ISCD sub-TLV 1122 - TLV Type = 2 1123 - TLV Name = Unreserved Bandwidth for fixed containers 1124 - allowed on ISCD sub-TLV 1126 New TLV type values may be allocated only by an IETF Consensus 1127 action. The request Registration Procedures are Standards Action. 1129 9. Contributors 1131 Xiaobing Zi, Huawei Technologies 1133 Email: zixiaobing@huawei.com 1135 Francesco Fondelli, Ericsson 1137 Email: francesco.fondelli@ericsson.com 1139 Marco Corsi 1141 EMail: corsi.marco@gmail.com 1143 Eve Varma, Alcatel-Lucent 1145 EMail: eve.varma@alcatel-lucent.com 1146 Jonathan Sadler, Tellabs 1148 EMail: jonathan.sadler@tellabs.com 1150 Lyndon Ong, Ciena 1152 EMail: lyong@ciena.com 1154 Ashok Kunjidhapatham 1156 akunjidhapatham@infinera.com 1158 Snigdho Bardalai 1160 sbardalai@infinera.com 1162 Steve Balls 1164 Steve.Balls@metaswitch.com 1166 Jonathan Hardwick 1168 Jonathan.Hardwick@metaswitch.com 1170 Xihua Fu 1172 fu.xihua@zte.com.cn 1174 Cyril Margaria 1176 cyril.margaria@nsn.com 1177 Malcolm Betts 1179 Malcolm.betts@zte.com.cn 1181 10. Acknowledgements 1183 The authors would like to thank Fred Gruman and Lou Berger for the 1184 precious comments and suggestions. 1186 11. References 1188 11.1. Normative References 1190 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1191 Requirement Levels", BCP 14, RFC 2119, March 1997. 1193 [RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering 1194 (TE) Extensions to OSPF Version 2", RFC 3630, 1195 September 2003. 1197 [RFC4202] Kompella, K. and Y. Rekhter, "Routing Extensions in 1198 Support of Generalized Multi-Protocol Label Switching 1199 (GMPLS)", RFC 4202, October 2005. 1201 [RFC4203] Kompella, K. and Y. Rekhter, "OSPF Extensions in Support 1202 of Generalized Multi-Protocol Label Switching (GMPLS)", 1203 RFC 4203, October 2005. 1205 [RFC4328] Papadimitriou, D., "Generalized Multi-Protocol Label 1206 Switching (GMPLS) Signaling Extensions for G.709 Optical 1207 Transport Networks Control", RFC 4328, January 2006. 1209 11.2. Informative References 1211 [G.709-2012] 1212 ITU-T, "Draft revised G.709, version 4", consented 1213 by ITU-T in 2012. 1215 [OTN-FWK] F.Zhang, D.Li, H.Li, S.Belotti, D.Ceccarelli, "Framework 1216 for GMPLS and PCE Control of G.709 Optical Transport 1217 networks, work in progress 1218 draft-ietf-ccamp-gmpls-g709-framework-11", November 2012. 1220 [OTN-INFO] 1221 S.Belotti, P.Grandi, D.Ceccarelli, D.Caviglia, F.Zhang, 1222 D.Li, "Information model for G.709 Optical Transport 1223 Networks (OTN), work in progress 1224 draft-ietf-ccamp-otn-g709-info-model-05", November 2012. 1226 [OTN-SIG] F.Zhang, G.Zhang, S.Belotti, D.Ceccarelli, K.Pithewan, 1227 "Generalized Multi-Protocol Label Switching (GMPLS) 1228 Signaling Extensions for the evolving G.709 Optical 1229 Transport Networks Control, work in progress 1230 draft-ietf-ccamp-gmpls-signaling-g709v3-05", 1231 November 2012. 1233 [RFC2154] Murphy, S., Badger, M., and B. Wellington, "OSPF with 1234 Digital Signatures", RFC 2154, June 1997. 1236 [RFC5920] Fang, L., "Security Framework for MPLS and GMPLS 1237 Networks", RFC 5920, July 2010. 1239 [RFC6163] Lee, Y., Bernstein, G., and W. Imajuku, "Framework for 1240 GMPLS and Path Computation Element (PCE) Control of 1241 Wavelength Switched Optical Networks (WSONs)", RFC 6163, 1242 April 2011. 1244 [RFC6566] Lee, Y., Bernstein, G., Li, D., and G. Martinelli, "A 1245 Framework for the Control of Wavelength Switched Optical 1246 Networks (WSONs) with Impairments", RFC 6566, March 2012. 1248 Authors' Addresses 1250 Daniele Ceccarelli (editor) 1251 Ericsson 1252 Via A. Negrone 1/A 1253 Genova - Sestri Ponente 1254 Italy 1256 Email: daniele.ceccarelli@ericsson.com 1258 Diego Caviglia 1259 Ericsson 1260 Via A. Negrone 1/A 1261 Genova - Sestri Ponente 1262 Italy 1264 Email: diego.caviglia@ericsson.com 1265 Fatai Zhang 1266 Huawei Technologies 1267 F3-5-B R&D Center, Huawei Base 1268 Shenzhen 518129 P.R.China Bantian, Longgang District 1269 Phone: +86-755-28972912 1271 Email: zhangfatai@huawei.com 1273 Dan Li 1274 Huawei Technologies 1275 F3-5-B R&D Center, Huawei Base 1276 Shenzhen 518129 P.R.China Bantian, Longgang District 1277 Phone: +86-755-28973237 1279 Email: danli@huawei.com 1281 Sergio Belotti 1282 Alcatel-Lucent 1283 Via Trento, 30 1284 Vimercate 1285 Italy 1287 Email: sergio.belotti@alcatel-lucent.com 1289 Pietro Vittorio Grandi 1290 Alcatel-Lucent 1291 Via Trento, 30 1292 Vimercate 1293 Italy 1295 Email: pietro_vittorio.grandi@alcatel-lucent.com 1297 Rajan Rao 1298 Infinera Corporation 1299 169, Java Drive 1300 Sunnyvale, CA-94089 1301 USA 1303 Email: rrao@infinera.com 1304 Khuzema Pithewan 1305 Infinera Corporation 1306 169, Java Drive 1307 Sunnyvale, CA-94089 1308 USA 1310 Email: kpithewan@infinera.com 1312 John E Drake 1313 Juniper 1315 Email: jdrake@juniper.net