idnits 2.17.1 draft-ietf-ccamp-gmpls-ospf-g709v3-10.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 : ---------------------------------------------------------------------------- == There are 1 instance of lines with non-RFC2606-compliant FQDNs in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 21, 2013) is 3839 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.709-2012' is mentioned on line 228, but not defined == Missing Reference: 'G.805' is mentioned on line 315, but not defined == Missing Reference: 'G.798-a2' is mentioned on line 418, but not defined == Outdated reference: A later version (-15) exists of draft-ietf-ccamp-gmpls-g709-framework-13 == Outdated reference: A later version (-13) exists of draft-ietf-ccamp-otn-g709-info-model-09 == Outdated reference: A later version (-12) exists of draft-ietf-ccamp-gmpls-signaling-g709v3-11 -- Obsolete informational reference (is this intentional?): RFC 5226 (Obsoleted by RFC 8126) == Outdated reference: A later version (-15) exists of draft-ietf-ccamp-gmpls-g709-framework-13 -- Duplicate reference: draft-ietf-ccamp-gmpls-g709-framework, mentioned in 'SWCAP-UPDT', was also mentioned in 'OTN-FWK'. Summary: 0 errors (**), 0 flaws (~~), 9 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 CCAMP Working Group D. Ceccarelli, Ed. 3 Internet-Draft Ericsson 4 Intended status: Standards Track F. Zhang 5 Expires: April 24, 2014 Huawei Technologies 6 S. Belotti 7 Alcatel-Lucent 8 R. Rao 9 Infinera Corporation 10 J. Drake 11 Juniper 12 October 21, 2013 14 Traffic Engineering Extensions to OSPF for Generalized MPLS (GMPLS) 15 Control of Evolving G.709 OTN Networks 16 draft-ietf-ccamp-gmpls-ospf-g709v3-10 18 Abstract 20 This document describes Open Shortest Path First - Traffic 21 Engineering (OSPF-TE) routing protocol extensions to support 22 Generalized MPLS (GMPLS) control of Optical Transport Networks (OTN) 23 specified in ITU-T Recommendation G.709 as published in 2012. It 24 extends mechanisms defined in RFC4203. 26 Status of this Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at http://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on April 24, 2014. 43 Copyright Notice 45 Copyright (c) 2013 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (http://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 62 2. OSPF-TE Extensions . . . . . . . . . . . . . . . . . . . . . . 3 63 3. TE-Link Representation . . . . . . . . . . . . . . . . . . . . 5 64 4. ISCD format extensions . . . . . . . . . . . . . . . . . . . . 6 65 4.1. Switching Capability Specific Information . . . . . . . . 7 66 4.1.1. Switching Capability Specific Information for 67 fixed containers . . . . . . . . . . . . . . . . . . . 8 68 4.1.2. Switching Capability Specific Information for 69 variable containers . . . . . . . . . . . . . . . . . 8 70 4.1.3. Switching Capability Specific Information - Field 71 values and explanation . . . . . . . . . . . . . . . . 9 72 5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 73 5.1. MAX LSP Bandwidth fields in the ISCD . . . . . . . . . . . 12 74 5.2. Example of T,S and TS granularity utilization . . . . . . 14 75 5.2.1. Example of different TS Granularities . . . . . . . . 15 76 5.3. Example of ODUflex advertisement . . . . . . . . . . . . . 18 77 5.4. Example of single stage muxing . . . . . . . . . . . . . . 20 78 5.5. Example of multi stage muxing - Unbundled link . . . . . . 22 79 5.6. Example of multi stage muxing - Bundled links . . . . . . 24 80 5.7. Example of component links with non-homogeneous 81 hierarchies . . . . . . . . . . . . . . . . . . . . . . . 25 82 6. OSPFv2 scalability . . . . . . . . . . . . . . . . . . . . . . 28 83 7. Compatibility . . . . . . . . . . . . . . . . . . . . . . . . 29 84 8. Security Considerations . . . . . . . . . . . . . . . . . . . 29 85 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29 86 9.1. Switching types . . . . . . . . . . . . . . . . . . . . . 29 87 9.2. New sub-TLVs . . . . . . . . . . . . . . . . . . . . . . . 30 88 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 30 89 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 33 90 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 33 91 12.1. Normative References . . . . . . . . . . . . . . . . . . . 33 92 12.2. Informative References . . . . . . . . . . . . . . . . . . 33 93 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 34 95 1. Introduction 97 G.709 Optical Transport Network (OTN) [G.709-2012] includes new fixed 98 and flexible ODU (Optical channel Data Unit) containers, two types of 99 Tributary Slots (i.e., 1.25Gbps and 2.5Gbps), and supports various 100 multiplexing relationships (e.g., ODUj multiplexed into ODUk (jODUk 154 format is used to indicate the ODUj into ODUk multiplexing 155 capability. 157 This notation can be repeated as needed depending on the number of 158 multiplexing levels. In the following, the term "multiplexing tree" 159 is used to identify a multiplexing hierarchy where the root is always 160 a server ODUk/OTUk and any other supported multiplexed container is 161 represented with increasing granularity until reaching the leaf of 162 the tree. The tree can be structured with more than one branch if 163 the server ODUk/OTUk supports more than one hierarchy. 165 For example, if a multiplexing or example a multiplexing hierarchy 166 like the following one is considered: 168 ODU2 ODU0 ODUflex ODU0 169 \ / \ / 170 | | 171 ODU3 ODU2 172 \ / 173 \ / 174 \ / 175 \ / 176 ODU4 178 The ODU4 is the root of the muxing tree, ODU3 and ODU2 are containers 179 directly multiplexed into the server and then ODU2, ODU0 are the 180 leaves of the ODU3 branch, while ODUflex and ODU0 are the leaves of 181 the ODU2 one. This means that it is possible to have the following 182 multiplexing capabilities: 184 ODU2->ODU3->ODU4 185 ODU0->ODU3->ODU4 186 ODUflex->ODU2->ODU4 187 ODU0->ODU2->ODU4 189 3. TE-Link Representation 191 G.709 ODUk/OTUk Links are represented as TE-Links in GMPLS Traffic 192 Engineering Topology for supporting ODUj layer switching. These TE- 193 Links can be modeled in multiple ways. 195 OTUk physical Link(s) can be modeled as a TE-Link(s). Figure 1 below 196 provides an illustration of one hop OTUk 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: OTUk TE-Links 208 It is possible to create TE-Links that span more than one hop by 209 creating FAs between non-adjacent nodes (see Figure 2). As in the 210 one hop case, multiple hop TE-links advertise ODU switching capacity. 212 +-------+ +-------+ +-------+ 213 | OTN | | OTN | | OTN | 214 |Switch |<- OTUk Link ->|Switch |<- OTUk Link ->|Switch | 215 | A | | B | | C | 216 +-------+ +-------+ +-------+ 217 ODUk Switched 219 |<------------- ODUk Link ------------->| 220 |<-------------- TE-Link--------------->| 222 Figure 2: Multiple hop TE-Link 224 4. ISCD format extensions 226 The ISCD describes the switching capability of an interface and is 227 defined in [RFC4203]. This document defines a new Switching 228 Capability value for OTN [G.709-2012] as follows: 230 Value Type 231 ----- ---- 232 110 (TBA by IANA) OTN-TDM capable (OTN-TDM) 234 When supporting the extensions defined in this document, for both 235 fixed and flexible ODUs, the Switching Capability and Encoding values 236 MUST be used as follows: 238 - Switching Capability = OTN-TDM 239 - Encoding Type = G.709 ODUk (Digital Path) as defined in [RFC4328] 241 The same switching type and encoding values must be used for both 242 fixed and flexible ODUs. When Switching Capability and Encoding 243 fields are set to values as stated above, the Interface Switching 244 Capability Descriptor MUST be interpreted as defined in [RFC4203]. 246 Maximum LSP Bandwidth 248 The MAX LSP Bandwidth field is used according to [RFC4203]: i.e., 0 249 <= MAX LSP Bandwidth <= ODUk/OTUk, and intermediate values are those 250 on the branch of OTN switching hierarchy supported by the interface. 251 For example, in the OTU4 link it could be possible to have ODU4 as 252 MAX LSP Bandwidth for some priorities, ODU3 for others, ODU2 for some 253 others, etc. The bandwidth unit is in bytes per second and the 254 encoding MUST be in Institute of Electrical and Electronic Engineers 255 (IEEE) floating point format. The discrete values for various ODUs 256 is shown in the table below (please note that there are 1000 bits in 257 a kbit according to normal practices in telecommunications). 259 +---------------------+------------------------------+-----------------+ 260 | ODU Type | ODU nominal bit rate |Value in Byte/Sec| 261 | | |(floating p. val)| 262 +---------------------+------------------------------+-----------------+ 263 | ODU0 | 1,244,160 kbit/s | 0x4D1450C0 | 264 | ODU1 | 239/238 x 2,488,320 kbit/s | 0x4D94F048 | 265 | ODU2 | 239/237 x 9,953,280 kbit/s | 0x4E959129 | 266 | ODU3 | 239/236 x 39,813,120 kbit/s | 0x4F963367 | 267 | ODU4 | 239/227 x 99,532,800 kbit/s | 0x504331E3 | 268 | ODU2e | 239/237 x 10,312,500 kbit/s | 0x4E9AF70A | 269 | | | | 270 | ODUflex for CBR | 239/238 x client signal | MAX LSP | 271 | Client signals | bit rate | BANDWIDTH | 272 | | | | 273 | ODUflex for GFP-F | | MAX LSP | 274 |Mapped client signal | Configured bit rate | BANDWIDTH | 275 | | | | 276 | | | | 277 |ODU flex resizable | Configured bit rate | MAX LSP | 278 | | | BANDWIDTH | 279 +---------------------+------------------------------+-----------------+ 281 A single ISCD MAY be used for the advertisement of unbundled or 282 bundled links supporting homogeneous multiplexing hierarchies and the 283 same TS (Tributary Slot) granularity. A different ISCD MUST be used 284 for each different muxing hierarchy (muxing tree in the following 285 examples) and different TS granularity supported within the TE Link. 287 In case a recived LSA is not formatted accordingly to the 288 requirements indicated in this document, the problem SHOULD be logged 289 and the wrongly formatted LSA, TLV or Sub-TLV MUST NOT be used for 290 the path computation until a newer version correctly formatted is 291 received. 293 4.1. Switching Capability Specific Information 295 The technology specific part of the OTN-TDM ISCD may include a 296 variable number of sub-TLVs called Bandwidth sub-TLVs. Each sub-TLV 297 is encoded with the sub-TLV header as defined in [RFC3630] section 298 2.3.2. The muxing hierarchy tree MUST be encoded as an order 299 independent list. Two types of Bandwidth sub-TLV are defined (TBA by 300 IANA). Note that type values are defined in this document and not in 301 [RFC3630]. 303 - Type 1 - Unreserved Bandwidth for fixed containers 304 - Type 2 - Unreserved/MAX LSP Bandwidth for flexible containers 306 The Switching Capability-Specific Information (SCSI) MUST include one 307 Type 1 sub-TLV for each fixed container and one Type 2 sub-TLV for 308 each variable container. Each container type is identified by a 309 Signal Type. Signal Type values are defined in [OTN-SIG]. 311 With respect to ODUflex, three different signal types are allowed: 20 312 - ODUflex Constant Bit Rate (CBR), 21 - ODUflex Generic Framing 313 Procedure-Frame mapped (GFP-F) resizable and 22 - ODUflex (GFP-F) 314 non-resizable. Each MUST always be advertised in separate Type 2 315 sub-TLVs as each uses different adaptation functions [G.805]. In the 316 case that both GFP-F resizable and non-resizable (i.e., 21 and 22) 317 are supported, only Signal Type 21 SHALL be advertised as this type 318 also implies support for type 22 adaptation. 320 4.1.1. Switching Capability Specific Information for fixed containers 322 The format of the Bandwidth sub-TLV for fixed containers is depicted 323 in the following figure: 325 0 1 2 3 326 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 327 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 328 | Type = 1 (Unres-fix) | Length | 329 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 330 | Signal type | Num of stages |T|S| TSG | Res | Priority | 331 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 332 | Stage#1 | ... | Stage#N | Padding | 333 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 334 | Unreserved ODUj at Prio 0 | ..... | 335 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 336 | Unreserved ODUj at Prio 7 | Unreserved Padding | 337 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 339 Figure 3: Bandwidth sub-TLV - Type 1 - 341 The values of the fields shown in figure 4 are explained in section 342 4.1.3. 344 4.1.2. Switching Capability Specific Information for variable 345 containers 347 The format of the Bandwidth sub-TLV for variable containers is 348 depicted in the following figure: 350 0 1 2 3 351 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 352 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 353 | Type = 2 (Unres/MAX-var) | Length | 354 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 355 | Signal type | Num of stages |T|S| TSG | Res | Priority | 356 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 357 | Stage#1 | ... | Stage#N | Padding | 358 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 359 | Unreserved Bandwidth at priority 0 | 360 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 361 | ... | 362 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 363 | Unreserved Bandwidth at priority 7 | 364 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 365 | MAX LSP Bandwidth at priority 0 | 366 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 367 | ... | 368 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 369 | MAX LSP Bandwidth at priority 7 | 370 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 372 Figure 4: Bandwidth sub-TLV - Type 2 - 374 The values of the fields shown in figure 4 are explained in section 375 4.1.3. 377 4.1.3. Switching Capability Specific Information - Field values and 378 explanation 380 The fields in the Bandwidth sub-TLV MUST be filled as follows: 382 - Signal Type (8 bits): Indicates the ODU type being advertised. 383 Values are defined in [OTN-SIG]. 385 - Number of stages (8 bits): This field indicates the number of 386 multiplexing stages used to transport the indicated signal type. 387 It MUST be set to the number of stages represented in the sub-TLV. 389 - Flags (8 bits): 391 - T Flag (bit 17): Indicates whether the advertised bandwidth 392 can be terminated. When the signal type can be terminated T 393 MUST be set, while when the signal type cannot be terminated T 394 MUST be cleared. 396 - S Flag (bit 18): Indicates whether the advertised bandwidth 397 can be switched. When the signal type can be switched S MUST 398 be set, while when the signal type cannot be switched S MUST be 399 cleared. 401 The value 0 in both T and S bits MUST NOT be used. 403 - TS Granularity: Tributary Slot Granularity (3 bits): Used for 404 the advertisement of the supported Tributary Slot granularity. 405 The following values MUST be used: 407 - 0 - Ignored 409 - 1 - 1.25Gbps/2.5Gbps 411 - 2 - 2.5Gbps only 413 - 3 - 1.25Gbps only 415 - 4-7 - Reserved 417 A value of 1 MUST be used on interfaces which are configured to 418 support the fall back procedures defined in [G.798-a2]. A value 419 of 2 MUST be used on interfaces that only support 2.5Gbps time 420 slots, such as [RFC4328] interfaces. A value of 3 MUST be used on 421 interfaces that are configured to only support 1.25Gbps time 422 slots. A value of 0 MUST be used for non-multiplexed signal types 423 (i.e., a non-OTN client). 425 - Res (3 bits): reserved bits. MUST be set to 0 and ignored on 426 receipt. 428 - Priority (8 bits): A bitmap used to indicate which priorities 429 are being advertised. The bitmap is in ascending order, with the 430 leftmost bit representing priority level 0 (i.e., the highest) and 431 the rightmost bit representing priority level 7 (i.e., the 432 lowest). A bit MUST be set (1) corresponding to each priority 433 represented in the sub-TLV, and MUST NOT be set (0) when the 434 corresponding priority is not represented. At least one priority 435 level MUST be advertised that, unless overridden by local policy, 436 SHALL be at priority level 0. 438 - Stage (8 bits): Each Stage field indicates a signal type in the 439 multiplexing hierarchy used to transport the signal indicated in 440 the Signal Type field. The number of Stage fields included in a 441 sub-TLV MUST equal the value of the Number of Stages field. The 442 Stage fields MUST be ordered to match the data plane in ascending 443 order (from the lowest order ODU to the highest order ODU). The 444 values of the Stage field are the same as those defined for the 445 Signal Type field. When the Number of stage field carries a 0, 446 then the Stage and Padding fields MUST be omitted. 448 - Padding (variable): The Padding field is used to ensure the 32 449 bit alignment of stage fields. The length of the Padding field is 450 always a multiple of 8 bits (1 byte). Its length can be 451 calculated, in bytes, as: 4 - ( "value of Number of Stages field" 452 % 4). The Padding field MUST be set to a zero (0) value on 453 transmission and MUST be ignored on receipt. 455 - Unreserved ODUj (16 bits): This field indicates the Unreserved 456 Bandwidth at a particular priority level. This field MUST be set 457 to the number of ODUs at the indicated the Signal Type for a 458 particular priority level. One field MUST be present for each bit 459 set in the Priority field, and is ordered to match the Priority 460 field. Fields MUST NOT be present for priority levels that are 461 not indicated in the Priority field. 463 - Unreserved Padding (16 bits): The Padding field is used to 464 ensure the 32 bit alignment of Unreserved ODUj fields. When 465 present the Unreserved Padding field is 16 bits (2 byte) long. 466 When the number of priorities is odd, the Unreserved Padding field 467 MUST be included. When the number of priorities is even, the 468 Unreserved Padding MUST be omitted. 470 - Unreserved Bandwidth (32 bits): This field indicates the 471 Unreserved Bandwidth at a particular priority level. This field 472 MUST be set to the bandwidth, in Bytes/sec in IEEE floating point 473 format, available at the indicated Signal Type for a particular 474 priority level. One field MUST be present for each bit set in the 475 Priority field, and is ordered to match the Priority field. 476 Fields MUST NOT be present for priority levels that are not 477 indicated in the Priority field. 479 - Maximum LSP Bandwidth (32 bit): This field indicates the maximum 480 bandwidth that can be allocated for a single LSP at a particular 481 priority level. This field MUST be set to the maximum bandwidth, 482 in Bytes/sec in IEEE floating point format, available to a single 483 LSP at the indicated Signal Type for a particular priority level. 484 One field MUST be present for each bit set in the Priority field, 485 and is ordered to match the Priority field. Fields MUST NOT be 486 present for priority levels that are not indicated in the Priority 487 field. The advertisement of the MAX LSP Bandwidth MUST take into 488 account HO OPUk bit rate tolerance and be calculated according to 489 the following formula: 491 Max LSP BW = (# available TSs) * (ODTUk.ts nominal bit rate) * 492 (1-HO OPUk bit rate tolerance) 494 5. Examples 496 The examples in the following pages are not normative and are not 497 intended to imply or mandate any specific implementation. 499 5.1. MAX LSP Bandwidth fields in the ISCD 501 This example shows how the MAX LSP Bandwidth fields of the ISCD are 502 filled accordingly to the evolving of the TE-link bandwidth 503 occupancy. In the example an OTU4 link is considered, with supported 504 priorities 0,2,4,7 and muxing hierarchy ODU1->ODU2->ODU3->ODU4. 506 At time T0, with the link completely free, the advertisement would 507 be: 509 0 1 2 3 510 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 511 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 512 | SwCap=OTN_TDM | Encoding = 12 | Reserved (all zeros) | 513 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 514 | MAX LSP Bandwidth at priority 0 = 100Gbps | 515 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 516 | MAX LSP Bandwidth at priority 1 = 0 | 517 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 518 | MAX LSP Bandwidth at priority 2 = 100Gbps | 519 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 520 | MAX LSP Bandwidth at priority 3 = 0 | 521 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 522 | MAX LSP Bandwidth at priority 4 = 100Gbps | 523 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 524 | MAX LSP Bandwidth at priority 5 = 0 | 525 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 526 | MAX LSP Bandwidth at priority 6 = 0 | 527 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 528 | MAX LSP Bandwidth at priority 7 = 100Gbps | 529 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 530 | Switching Capability Specific Information | 531 | (variable length) | 532 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 534 Figure 5: Example 1 - MAX LSP Bandwidth fields in the ISCD at T0 536 At time T1, an ODU3 at priority 2 is set-up, so for priority 0 the 537 MAX LSP Bandwidth is still equal to the ODU4 bandwidth, while for 538 priorities from 2 to 7 (excluding the non-supported ones) the MAX LSP 539 Bandwidth is equal to ODU3, as no more ODU4s are available and the 540 next supported ODUj in the hierarchy is ODU3. The advertisement is 541 updated as follows: 543 0 1 2 3 544 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 545 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 546 | SwCap=OTN_TDM | Encoding = 12 | Reserved (all zeros) | 547 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 548 | MAX LSP Bandwidth at priority 0 = 100Gbps | 549 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 550 | MAX LSP Bandwidth at priority 1 = 0 | 551 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 552 | MAX LSP Bandwidth at priority 2 = 40Gbps | 553 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 554 | MAX LSP Bandwidth at priority 3 = 0 | 555 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 556 | MAX LSP Bandwidth at priority 4 = 40Gbps | 557 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 558 | MAX LSP Bandwidth at priority 5 = 0 | 559 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 560 | MAX LSP Bandwidth at priority 6 = 0 | 561 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 562 | MAX LSP Bandwidth at priority 7 = 40Gbps | 563 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 564 | Switching Capability Specific Information | 565 | (variable length) | 566 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 568 Figure 6: Example 1 - MAX LSP Bandwidth fields in the ISCD at T1 570 At time T2, an ODU2 at priority 4 is set-up. The first ODU3 is no 571 longer available since T1, as it was kept by the ODU3 LSP, while the 572 second is no more available and just 3 ODU2 are left in it. ODU2 is 573 now the MAX LSP Bandwidth for priorities higher than 4. The 574 advertisement is updated as follows: 576 0 1 2 3 577 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 578 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 579 | SwCap=OTN_TDM | Encoding = 12 | Reserved (all zeros) | 580 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 581 | MAX LSP Bandwidth at priority 0 = 100Gbps | 582 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 583 | MAX LSP Bandwidth at priority 1 = 0 | 584 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 585 | MAX LSP Bandwidth at priority 2 = 40Gbps | 586 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 587 | MAX LSP Bandwidth at priority 3 = 0 | 588 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 589 | MAX LSP Bandwidth at priority 4 = 10Gbps | 590 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 591 | MAX LSP Bandwidth at priority 5 = 0 | 592 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 593 | MAX LSP Bandwidth at priority 6 = 0 | 594 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 595 | MAX LSP Bandwidth at priority 7 = 10Gbps | 596 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 597 | Switching Capability Specific Information | 598 | (variable length) | 599 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 601 Figure 7: Example 1 - MAX LSP Bandwidth fields in the ISCD at T2 603 5.2. Example of T,S and TS granularity utilization 605 In this example, an interface with Tributary Slot Type 1.25Gbps and 606 fallback procedure enabled is considered (TS granularity=1). It 607 supports the simple ODU1->ODU2->ODU3 hierarchy and priorities 0 and 608 3. Suppose that in this interface the ODU3 signal type can be both 609 switched or terminated, the ODU2 can only be terminated, and the ODU1 610 switched only. Please note that since the ODU1 is not being 611 advertised to support ODU0, the value of is "ignored" (TS 612 granularity=0). For the advertisement of the capabilities of such 613 interface, a single ISCD is used and its format is as follows: 615 0 1 2 3 616 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 617 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 618 | Type = 1 (Unres-fix) | Length = 12 | 619 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 620 |Sig type=ODU1 | #stages= 2 |0|1| 0 |0 0 0|1|0|0|1|0|0|0|0| 621 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 622 | Stage#1=ODU2 | Stage#2=ODU3 | Padding (all zeros) | 623 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 624 | Unres ODU1 at Prio 0 | Unres ODU1 at Prio 3 | 625 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 626 | Type = 1 (Unres-fix) | Length = 12 | 627 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 628 |Sig type=ODU2 | #stages= 1 |1|0| 1 |0 0 0|1|0|0|1|0|0|0|0| 629 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 630 | Stage#1=ODU3 | Padding (all zeros) | 631 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 632 | Unres ODU2 at Prio 0 | Unres ODU2 at Prio 3 | 633 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 634 | Type = 1 (Unres-fix) | Length = 8 | 635 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 636 |Sig type=ODU3 | #stages= 0 |1|1| 1 |0 0 0|1|0|0|1|0|0|0|0| 637 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 638 | Unres ODU3 at Prio 0 | Unres ODU3 at Prio 3 | 639 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 641 Figure 8: Example 2 - TS granularity, T and S utilization 643 5.2.1. Example of different TS Granularities 645 In this example, two interfaces with homogeneous hierarchies but 646 different Tributary Slot Types are considered. The first one 647 supports a [RFC4328] interface (TS granularity=2) while the second 648 one supports G.709-2012 interface with fallback procedure disabled 649 (TS granularity=3). Both of them support ODU1->ODU2->ODU3 hierarchy 650 and priorities 0 and 3. T and S bits values are not relevant to this 651 example. For the advertisement of the capabilities of such 652 interfaces, two different ISCDs are used and the format of their 653 SCSIs is as follows: 655 SCSI of ISCD 1 - TS granularity=2 656 0 1 2 3 657 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 658 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 659 | Type = 1 (Unres-fix) | Length = 12 | 660 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 661 |Sig type=ODU1 | #stages= 2 |0|1| 0 |0 0 0|1|0|0|1|0|0|0|0| 662 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 663 | Stage#1=ODU2 | Stage#2=ODU3 | Padding (all zeros) | 664 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 665 | Unres ODU1 at Prio 0 | Unres ODU1 at Prio 3 | 666 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 667 | Type = 1 (Unres-fix) | Length = 12 | 668 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 669 |Sig type=ODU2 | #stages= 1 |1|0| 1 |0 0 0|1|0|0|1|0|0|0|0| 670 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 671 | Stage#1=ODU3 | Padding (all zeros) | 672 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 673 | Unres ODU2 at Prio 0 | Unres ODU2 at Prio 3 | 674 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 675 | Type = 1 (Unres-fix) | Length = 8 | 676 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 677 |Sig type=ODU3 | #stages= 0 |1|1| 2 |0 0 0|1|0|0|1|0|0|0|0| 678 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 679 | Unres ODU3 at Prio 0 | Unres ODU3 at Prio 3 | 680 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 682 Figure 9: Example 2.1 - Different TS Granularities utilization - ISCD 683 1 685 SCSI of ISCD 2 - TS granularity=3 686 0 1 2 3 687 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 688 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 689 | Type = 1 (Unres-fix) | Length = 12 | 690 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 691 |Sig type=ODU1 | #stages= 2 |0|1| 0 |0 0 0|1|0|0|1|0|0|0|0| 692 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 693 | Stage#1=ODU2 | Stage#2=ODU3 | Padding (all zeros) | 694 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 695 | Unres ODU1 at Prio 0 | Unres ODU1 at Prio 3 | 696 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 697 | Type = 1 (Unres-fix) | Length = 12 | 698 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 699 |Sig type=ODU2 | #stages= 1 |1|0| 1 |0 0 0|1|0|0|1|0|0|0|0| 700 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 701 | Stage#1=ODU3 | Padding (all zeros) | 702 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 703 | Unres ODU2 at Prio 0 | Unres ODU2 at Prio 3 | 704 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 705 | Type = 1 (Unres-fix) | Length = 8 | 706 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 707 |Sig type=ODU3 | #stages= 0 |1|1| 3 |0 0 0|1|0|0|1|0|0|0|0| 708 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 709 | Unres ODU3 at Prio 0 | Unres ODU3 at Prio 3 | 710 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 712 Figure 10: Example 2.1 - Different TS Granularities utilization - 713 ISCD 2 715 A particular case in which hierarchies with the same muxing tree but 716 with different exported TS granularity MUST be considered as non- 717 homogenous hierarchies. This is the case in which an H-LPS and the 718 client LSP are terminated on the same egress node. What can happen 719 is that a loose Explicit Route Object (ERO) is used at the hop where 720 the signaled LSP is nested into the Hierarchical-LSP (H-LSP) 721 (penultimate hop of the LSP). 723 In the following figure, node C receives from A a loose ERO towards 724 node E and must choose between the ODU2 H-LSP on if1 or the one on 725 if2. In this case, the H-LSP on if1 exports a TS=1.25Gbps, and if2 a 726 TS=2.5Gbps, the service LSP being signaled needs a 1.25Gbps tributary 727 slot, only the H-LSP on if1 can be used to reach node E. For further 728 details, please see section 4.1 of the [OTN-INFO]. 730 ODU0-LSP 731 ..........................................................+ 732 | | 733 | ODU2-H-LSP | 734 | +-------------------------------+ 735 | | | 736 +--+--+ +-----+ +-----+ if1 +-----+ +-----+ 737 | | OTU3 | | OTU3 | |---------| |---------| | 738 | A +------+ B +------+ C | if2 | D | | E | 739 | | | | | |---------| |---------| | 740 +-----+ +-----+ +-----+ +-----+ +-----+ 742 ... Service LSP 743 --- H-LSP 745 Figure 11: Example - Service LSP and H-LSP terminating on the same 746 node 748 5.3. Example of ODUflex advertisement 750 In this example, the advertisement of an ODUflex->ODU3 hierarchy is 751 shown. In case of ODUflex advertisement, the MAX LSP Bandwidth needs 752 to be advertised and, in some cases, information about the Unreserved 753 bandwidth could also be useful. The amount of Unreserved bandwidth 754 does not give a clear indication of how many ODUflex LSP can be set 755 up either at the MAX LSP Bandwidth or at different rates, as it gives 756 no information about the spatial allocation of the free TSs. 758 An indication of the amount of Unreserved bandwidth could be useful 759 during the path computation process, as shown in the following 760 example. Supposing there are two TE-links (A and B) with MAX LSP 761 Bandwidth equal to 10 Gbps each. In the case where 50Gbps of 762 Unreserved Bandwidth are available on Link A, 10Gbps on Link B, and 3 763 ODUflex LSPs of 10 GBps each have to be restored, for sure only one 764 can be restored along Link B and it is probable, but not certain, 765 that two of them can be restored along Link A. T, S and TS 766 granularity fields are not relevant to this example. 768 In the case of ODUflex advertisement, the Type 2 Bandwidth sub-TLV is 769 used. 771 0 1 2 3 772 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 773 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 774 | Type = 2 (Unres/MAX-var) | Length = 72 | 775 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 776 |S. type=ODUflex| #stages= 1 |X|X|X X X|0 0 0| Priority(8) | 777 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 778 | Stage#1=ODU3 | Padding (all zeros) | 779 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 780 | Unreserved Bandwidth at priority 0 | 781 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 782 | Unreserved Bandwidth at priority 1 | 783 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 784 | Unreserved Bandwidth at priority 2 | 785 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 786 | Unreserved Bandwidth at priority 3 | 787 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 788 | Unreserved Bandwidth at priority 4 | 789 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 790 | Unreserved Bandwidth at priority 5 | 791 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 792 | Unreserved Bandwidth at priority 6 | 793 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 794 | Unreserved Bandwidth at priority 7 | 795 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 796 | MAX LSP Bandwidth at priority 0 | 797 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 798 | MAX LSP Bandwidth at priority 1 | 799 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 800 | MAX LSP Bandwidth at priority 2 | 801 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 802 | MAX LSP Bandwidth at priority 3 | 803 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 804 | MAX LSP Bandwidth at priority 4 | 805 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 806 | MAX LSP Bandwidth at priority 5 | 807 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 808 | MAX LSP Bandwidth at priority 6 | 809 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 810 | MAX LSP Bandwidth at priority 7 | 811 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 813 Figure 12: Example 3 - ODUflex advertisement 815 5.4. Example of single stage muxing 817 Supposing there is 1 OTU4 component link supporting single stage 818 muxing of ODU1, ODU2, ODU3 and ODUflex, the supported hierarchy can 819 be summarized in a tree as in the following figure. For sake of 820 simplicity, we also assume that only priorities 0 and 3 are 821 supported. T, S and TS granularity fields are not relevant to this 822 example. 824 ODU1 ODU2 ODU3 ODUflex 825 \ \ / / 826 \ \ / / 827 \ \/ / 828 ODU4 830 and the related SCSIs as follows: 832 0 1 2 3 833 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 834 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 835 | Type = 1 (Unres-fix) | Length = 8 | 836 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 837 |Sig type=ODU4 | #stages= 0 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0| 838 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 839 | Unres ODU4 at Prio 0 =1 | Unres ODU4 at Prio 3 =1 | 840 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 841 | Type = 1 (Unres-fix) | Length = 12 | 842 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 843 |Sig type=ODU1 | #stages= 1 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0| 844 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 845 | Stage#1=ODU4 | Padding (all zeros) | 846 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 847 | Unres ODU1 at Prio 0 =40 | Unres ODU1 at Prio 3 =40 | 848 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 849 | Type = 1 (Unres-fix) | Length = 12 | 850 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 851 |Sig type=ODU2 | #stages= 1 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0| 852 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 853 | Stage#1=ODU4 | Padding (all zeros) | 854 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 855 | Unres ODU2 at Prio 0 =10 | Unres ODU2 at Prio 3 =10 | 856 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 857 | Type = 1 (Unres-fix) | Length = 12 | 858 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 859 |Sig type=ODU3 | #stages= 1 |X|X|X X X|0 0 0|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 = 2 (Unres/MAX-var) | Length = 24 | 866 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 867 |S. type=ODUflex| #stages= 1 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0| 868 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 869 | Stage#1=ODU4 | Padding (all zeros) | 870 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 871 | Unreserved Bandwidth at priority 0 =100Gbps | 872 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 873 | Unreserved Bandwidth at priority 3 =100Gbps | 874 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 875 | MAX LSP Bandwidth at priority 0 =100Gbps | 876 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 877 | MAX LSP Bandwidth at priority 3 =100Gbps | 878 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 879 Figure 13: Example 4 - Single stage muxing 881 5.5. Example of multi stage muxing - Unbundled link 883 Supposing there is 1 OTU4 component link with muxing capabilities as 884 shown in the following figure: 886 ODU2 ODU0 ODUflex ODU0 887 \ / \ / 888 | | 889 ODU3 ODU2 890 \ / 891 \ / 892 \ / 893 \ / 894 ODU4 896 and supported priorities 0 and 3, the advertisement is composed by 897 the following Bandwidth sub-TLVs (T and S fields are not relevant to 898 this example): 900 0 1 2 3 901 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 902 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 903 | Type = 1 (Unres-fix) | Length = 8 | 904 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 905 |Sig type=ODU4 | #stages= 0 |X|X| 1 |0 0 0|1|0|0|1|0|0|0|0| 906 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 907 | Unres ODU4 at Prio 0 =1 | Unres ODU4 at Prio 3 =1 | 908 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 909 | Type = 1 (Unres-fix) | Length = 12 | 910 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 911 |Sig type=ODU3 | #stages= 1 |X|X| 1 |0 0 0|1|0|0|1|0|0|0|0| 912 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 913 | Stage#1=ODU4 | Padding (all zeros) | 914 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 915 | Unres ODU3 at Prio 0 =2 | Unres ODU3 at Prio 3 =2 | 916 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 917 | Type = 1 (Unres-fix) | Length = 12 | 918 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 919 |Sig type=ODU2 | #stages= 1 |X|X| 1 |0 0 0|1|0|0|1|0|0|0|0| 920 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 921 | Stage#1=ODU4 | Padding (all zeros) | 922 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 923 | Unres ODU2 at Prio 0 =10 | Unres ODU2 at Prio 3 =10 | 924 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 925 | Type = 1 (Unres-fix) | Length = 12 | 926 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 927 |Sig type=ODU2 | #stages= 2 |X|X| 0 |0 0 0|1|0|0|1|0|0|0|0| 928 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 929 | Stage#1=ODU3 | Stage#2=ODU4 | Padding (all zeros) | 930 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 931 | Unres ODU2 at Prio 0 =8 | Unres ODU2 at Prio 3 =8 | 932 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 933 | Type = 1 (Unres-fix) | Length = 12 | 934 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 935 |Sig type=ODU0 | #stages= 2 |X|X| 0 |0 0 0|1|0|0|1|0|0|0|0| 936 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 937 | Stage#1=ODU3 | Stage#2=ODU4 | Padding (all zeros) | 938 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 939 | Unres ODU0 at Prio 0 =64 | Unres ODU0 at Prio 3 =64 | 940 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 941 | Type = 1 (Unres-fix) | Length = 12 | 942 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 943 |Sig type=ODU0 | #stages= 2 |X|X| 0 |0 0 0|1|0|0|1|0|0|0|0| 944 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 945 | Stage#1=ODU2 | Stage#2=ODU4 | Padding (all zeros) | 946 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 947 | Unres ODU0 at Prio 0 =80 | Unres ODU0 at Prio 3 =80 | 948 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 949 | Type = 2 (Unres/MAX-var) | Length = 24 | 950 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 951 |S.type=ODUflex | #stages= 2 |X|X| 0 |0 0 0|1|0|0|1|0|0|0|0| 952 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 953 | Stage#1=ODU2 | Stage#2=ODU4 | Padding (all zeros) | 954 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 955 | Unreserved Bandwidth at priority 0 =100Gbps | 956 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 957 | Unreserved Bandwidth at priority 3 =100Gbps | 958 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 959 | MAX LSP Bandwidth at priority 0 =10Gbps | 960 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 961 | MAX LSP Bandwidth at priority 3 =10Gbps | 962 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 964 Figure 14: Example 5 - Multi stage muxing - Unbundled link 966 5.6. Example of multi stage muxing - Bundled links 968 In this example, 2 OTU4 component links with the same supported TS 969 granularity and homogeneous muxing hierarchies are considered. The 970 following muxing capabilities trees are supported: 972 Component Link#1 Component Link#2 973 ODU2 ODU0 ODU2 ODU0 974 \ / \ / 975 | | 976 ODU3 ODU3 977 | | 978 ODU4 ODU4 980 Considering only supported priorities 0 and 3, the advertisement is 981 as follows (T, S and TS granularity fields are not relevant to this 982 example): 984 0 1 2 3 985 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 986 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 987 | Type = 1 (Unres-fix) | Length = 8 | 988 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 989 |Sig type=ODU4 | #stages= 0 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0| 990 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 991 | Unres ODU4 at Prio 0 =2 | Unres ODU4 at Prio 3 =2 | 992 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 993 | Type = 1 (Unres-fix) | Length = 12 | 994 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 995 |Sig type=ODU3 | #stages= 1 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0| 996 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 997 | Stage#1=ODU4 | Padding (all zeros) | 998 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 999 | Unres ODU3 at Prio 0 =4 | Unres ODU3 at Prio 3 =4 | 1000 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1001 | Type = 1 (Unres-fix) | Length = 12 | 1002 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1003 |Sig type=ODU2 | #stages= 2 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0| 1004 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1005 | Stage#1=ODU3 | Stage#2=ODU4 | Padding (all zeros) | 1006 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1007 | Unres ODU2 at Prio 0 =16 | Unres ODU2 at Prio 3 =16 | 1008 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1009 | Type = 1 (Unres-fix) | Length = 12 | 1010 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1011 |Sig type=ODU0 | #stages= 2 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0| 1012 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1013 | Stage#1=ODU3 | Stage#2=ODU4 | Padding (all zeros) | 1014 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1015 | Unres ODU0 at Prio 0 =128 | Unres ODU0 at Prio 3 =128 | 1016 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1018 Figure 15: Example 6 - Multi stage muxing - Bundled links 1020 5.7. Example of component links with non-homogeneous hierarchies 1022 In this example, 2 OTU4 component links with the same supported TS 1023 granularity and non-homogeneous muxing hierarchies are considered. 1024 The following muxing capabilities trees are supported: 1026 Component Link#1 Component Link#2 1027 ODU2 ODU0 ODU1 ODU0 1028 \ / \ / 1029 | | 1030 ODU3 ODU2 1031 | | 1032 ODU4 ODU4 1034 Considering only supported priorities 0 and 3, the advertisement uses 1035 two different ISCDs, one for each hierarchy (T, S and TS granularity 1036 fields are not relevant to this example). In the following figure, 1037 the SCSI of each ISCD is shown: 1039 SCSI of ISCD 1 - Component Link#1 1041 0 1 2 3 1042 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 1043 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1044 | Type = 1 (Unres-fix) | Length = 8 | 1045 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1046 |Sig type=ODU4 | #stages= 0 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0| 1047 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1048 | Unres ODU4 at Prio 0 =1 | Unres ODU4 at Prio 3 =1 | 1049 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1050 | Type = 1 (Unres-fix) | Length = 12 | 1051 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1052 |Sig type=ODU3 | #stages= 1 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0| 1053 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1054 | Stage#1=ODU4 | Padding (all zeros) | 1055 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1056 | Unres ODU3 at Prio 0 =2 | Unres ODU3 at Prio 3 =2 | 1057 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1058 | Type = 1 (Unres-fix) | Length = 12 | 1059 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1060 |Sig type=ODU2 | #stages= 2 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0| 1061 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1062 | Stage#1=ODU3 | Stage#2=ODU4 | Padding (all zeros) | 1063 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1064 | Unres ODU2 at Prio 0 =8 | Unres ODU2 at Prio 3 =8 | 1065 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1066 | Type = 1 (Unres-fix) | Length = 12 | 1067 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1068 |Sig type=ODU0 | #stages= 2 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0| 1069 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1070 | Stage#1=ODU3 | Stage#2=ODU4 | Padding (all zeros) | 1071 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1072 | Unres ODU0 at Prio 0 =64 | Unres ODU0 at Prio 3 =64 | 1073 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1075 Figure 16: Example 7 - Multi stage muxing - Non-homogeneous 1076 hierarchies - ISCD 1 1078 SCSI of ISCD 2 - Component Link#2 1080 0 1 2 3 1081 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 1082 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1083 | Type = 1 (Unres-fix) | Length = 8 | 1084 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1085 |Sig type=ODU4 | #stages= 0 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0| 1086 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1087 | Unres ODU4 at Prio 0 =1 | Unres ODU4 at Prio 3 =1 | 1088 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1089 | Type = 1 (Unres-fix) | Length = 12 | 1090 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1091 |Sig type=ODU2 | #stages= 1 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0| 1092 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1093 | Stage#1=ODU4 | Padding (all zeros) | 1094 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1095 | Unres ODU2 at Prio 0 =10 | Unres ODU2 at Prio 3 =10 | 1096 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1097 | Type = 1 (Unres-fix) | Length = 12 | 1098 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1099 |Sig type=ODU1 | #stages= 2 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0| 1100 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1101 | Stage#1=ODU2 | Stage#2=ODU4 | Padding (all zeros) | 1102 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1103 | Unres ODU1 at Prio 0 =40 | Unres ODU1 at Prio 3 =40 | 1104 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1105 | Type = 1 (Unres-fix) | Length = 12 | 1106 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1107 |Sig type=ODU0 | #stages= 2 |X|X|X X X|0 0 0|1|0|0|1|0|0|0|0| 1108 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1109 | Stage#1=ODU2 | Stage#2=ODU4 | Padding (all zeros) | 1110 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1111 | Unres ODU0 at Prio 0 =80 | Unres ODU0 at Prio 3 =80 | 1112 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1114 Figure 17: Example 7 - Multi stage muxing - Non-homogeneous 1115 hierarchies - ISCD 2 1117 6. OSPFv2 scalability 1119 This document does not introduce OSPF scalability issues with respect 1120 to existing GMPLS encoding and does not require any modification to 1121 flooding frequency. Moreover the design of the encoding has been 1122 carried out taking into account bandwidth optimization, and in 1123 particular: 1125 - Only unreserved and MAX LSP Bandwidth related to supported 1126 priorities is advertised 1128 - With respect of fixed containers, only the number of available 1129 containers is advertised instead of available bandwidth so to use 1130 only 16 bits per container instead of 32 (as per former GMPLS 1131 encoding 1133 In order to further reduce the amount of data advertised it is 1134 RECOMMENDED to bundle component links with homogeneous hierarchies as 1135 described in [RFC4201] and illustrated in Section 5.6. 1137 7. Compatibility 1139 All implementations of this document MAY also support advertisement 1140 as defined in [RFC4328]. When nodes support both advertisement 1141 methods, implementations MUST support the configuration of which 1142 advertisement method is followed. The choice of which is used is 1143 based on policy and beyond the scope of this document. This enables 1144 nodes following each method to identify similar supporting nodes and 1145 compute paths using only the appropriate nodes. 1147 8. Security Considerations 1149 This document extends [RFC4203]. As with[RFC4203], it specifies the 1150 contents of Opaque LSAs in OSPFv2. As Opaque LSAs are not used for 1151 SPF computation or normal routing, the extensions specified here have 1152 no direct effect on IP routing. Tampering with GMPLS TE LSAs may 1153 have an effect on the underlying transport (optical and/or SONET-SDH) 1154 network. [RFC3630] suggests mechanisms such as [RFC2154] to protect 1155 the transmission of this information, and those or other mechanisms 1156 should be used to secure and/or authenticate the information carried 1157 in the Opaque LSAs. 1159 For security threats, defensive techniques, monitoring/detection/ 1160 reporting of security attacks and requirements please refer to 1161 [RFC5920]. 1163 9. IANA Considerations 1165 9.1. Switching types 1167 Upon approval of this document, IANA will make the assignment in the 1168 "Switching Types" section of the "GMPLS Signaling Parameters" 1169 registry located at 1170 http://www.iana.org/assignments/gmpls-sig-parameters: 1172 Value Name Reference 1173 --------- -------------------------- ---------- 1174 110 (*) OTN-TDM capable (OTN-TDM) [This.I-D] 1176 (*) Suggested value 1178 Same type of modification needs to applied to the IANA-GMPLS-TC-MIB 1179 at https://www.iana.org/assignments/ianagmplstc-mib/ianagmplstc-mib 1181 9.2. New sub-TLVs 1183 This document defines 2 new sub-TLVs that are carried in Interface 1184 Switching Capability Descriptors [RFC4203] with Signal Type OTN-TDM. 1185 Each sub-TLV includes a 16-bit type identifier (the T-field). The 1186 same T-field values are applicable to the new sub-TLV. 1188 Upon approval of this document, IANA will create and maintain a new 1189 sub-registry, the "Types for sub-TLVs of OTN-TDM SCSI (Switch 1190 Capability-Specific Information)" registry under the "Open Shortest 1191 Path First (OSPF) Traffic Engineering TLVs" registry, see http:// 1192 www.iana.org/assignments/ospf-traffic-eng-tlvs/ 1193 ospf-traffic-eng-tlvs.xml, with the sub-TLV types as follows: 1195 This document defines new sub-TLV types as follows: 1197 Value Sub-TLV Reference 1198 --------- -------------------------- ---------- 1199 0 Reserved [This.I-D] 1200 1 Unreserved Bandwidth for [This.I-D] 1201 fixed containers 1202 2 Unreserved/MAX Bandwidth for [This.I-D] 1203 flexible containers 1204 3-65535 Unassigned 1206 Types are to be assigned via Standards Action as defined in 1207 [RFC5226]. 1209 10. Contributors 1211 Diego Caviglia, Ericsson 1212 Via E.Melen, 77 - Genova - Italy 1214 Email: diego.caviglia@ericsson.com 1216 Dan Li, Huawei Technologies 1218 Bantian, Longgang District - Shenzhen 518129 P.R.China 1220 Email: danli@huawei.com 1222 Pietro Vittorio Grandi, Alcatel-Lucent 1224 Via Trento, 30 - Vimercate - Italy 1226 Email: pietro_vittorio.grandi@alcatel-lucent.com 1228 Khuzema Pithewan, Infinera Corporation 1230 140 Caspian CT., Sunnyvale - CA - USA 1232 Email: kpithewan@infinera.com 1234 Xiaobing Zi, Huawei Technologies 1236 Email: zixiaobing@huawei.com 1238 Francesco Fondelli, Ericsson 1240 Email: francesco.fondelli@ericsson.com 1242 Marco Corsi 1244 EMail: corsi.marco@gmail.com 1245 Eve Varma, Alcatel-Lucent 1247 EMail: eve.varma@alcatel-lucent.com 1249 Jonathan Sadler, Tellabs 1251 EMail: jonathan.sadler@tellabs.com 1253 Lyndon Ong, Ciena 1255 EMail: lyong@ciena.com 1257 Ashok Kunjidhapatham 1259 akunjidhapatham@infinera.com 1261 Snigdho Bardalai 1263 sbardalai@infinera.com 1265 Steve Balls 1267 Steve.Balls@metaswitch.com 1269 Jonathan Hardwick 1271 Jonathan.Hardwick@metaswitch.com 1273 Xihua Fu 1275 fu.xihua@zte.com.cn 1276 Cyril Margaria 1278 cyril.margaria@nsn.com 1280 Malcolm Betts 1282 Malcolm.betts@zte.com.cn 1284 11. Acknowledgements 1286 The authors would like to thank Fred Gruman and Lou Berger for the 1287 precious comments and suggestions. 1289 12. References 1291 12.1. Normative References 1293 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1294 Requirement Levels", BCP 14, RFC 2119, March 1997. 1296 [RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering 1297 (TE) Extensions to OSPF Version 2", RFC 3630, 1298 September 2003. 1300 [RFC4201] Kompella, K., Rekhter, Y., and L. Berger, "Link Bundling 1301 in MPLS Traffic Engineering (TE)", RFC 4201, October 2005. 1303 [RFC4203] Kompella, K. and Y. Rekhter, "OSPF Extensions in Support 1304 of Generalized Multi-Protocol Label Switching (GMPLS)", 1305 RFC 4203, October 2005. 1307 [RFC4328] Papadimitriou, D., "Generalized Multi-Protocol Label 1308 Switching (GMPLS) Signaling Extensions for G.709 Optical 1309 Transport Networks Control", RFC 4328, January 2006. 1311 12.2. Informative References 1313 [OTN-FWK] F.Zhang, D.Li, H.Li, S.Belotti, D.Ceccarelli, "Framework 1314 for GMPLS and PCE Control of G.709 Optical Transport 1315 networks, work in progress 1316 draft-ietf-ccamp-gmpls-g709-framework-13", June 2013. 1318 [OTN-INFO] 1319 S.Belotti, P.Grandi, D.Ceccarelli, D.Caviglia, F.Zhang, 1320 D.Li, "Information model for G.709 Optical Transport 1321 Networks (OTN), work in progress 1322 draft-ietf-ccamp-otn-g709-info-model-09", June 2013. 1324 [OTN-SIG] F.Zhang, G.Zhang, S.Belotti, D.Ceccarelli, K.Pithewan, 1325 "Generalized Multi-Protocol Label Switching (GMPLS) 1326 Signaling Extensions for the evolving G.709 Optical 1327 Transport Networks Control, work in progress 1328 draft-ietf-ccamp-gmpls-signaling-g709v3-11", June 2013. 1330 [RFC2154] Murphy, S., Badger, M., and B. Wellington, "OSPF with 1331 Digital Signatures", RFC 2154, June 1997. 1333 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 1334 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 1335 May 2008. 1337 [RFC5920] Fang, L., "Security Framework for MPLS and GMPLS 1338 Networks", RFC 5920, July 2010. 1340 [RFC6163] Lee, Y., Bernstein, G., and W. Imajuku, "Framework for 1341 GMPLS and Path Computation Element (PCE) Control of 1342 Wavelength Switched Optical Networks (WSONs)", RFC 6163, 1343 April 2011. 1345 [RFC6566] Lee, Y., Bernstein, G., Li, D., and G. Martinelli, "A 1346 Framework for the Control of Wavelength Switched Optical 1347 Networks (WSONs) with Impairments", RFC 6566, March 2012. 1349 [SWCAP-UPDT] 1350 F.Zhang, D.Li, H.Li, S.Belotti, D.Ceccarelli, "Framework 1351 for GMPLS and PCE Control of G.709 Optical Transport 1352 networks, work in progress 1353 draft-ietf-ccamp-gmpls-g709-framework-13", June 2013. 1355 Authors' Addresses 1357 Daniele Ceccarelli (editor) 1358 Ericsson 1359 Via E.Melen 77 1360 Genova - Erzelli 1361 Italy 1363 Email: daniele.ceccarelli@ericsson.com 1364 Fatai Zhang 1365 Huawei Technologies 1366 F3-5-B R&D Center, Huawei Base 1367 Shenzhen 518129 P.R.China Bantian, Longgang District 1368 Phone: +86-755-28972912 1370 Email: zhangfatai@huawei.com 1372 Sergio Belotti 1373 Alcatel-Lucent 1374 Via Trento, 30 1375 Vimercate 1376 Italy 1378 Email: sergio.belotti@alcatel-lucent.com 1380 Rajan Rao 1381 Infinera Corporation 1382 140, Caspian CT. 1383 Sunnyvale, CA-94089 1384 USA 1386 Email: rrao@infinera.com 1388 John E Drake 1389 Juniper 1391 Email: jdrake@juniper.net