idnits 2.17.1 draft-ietf-ccamp-gmpls-ospf-g709v3-09.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 1, 2013) is 3832 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 223, but not defined == Missing Reference: 'G.805' is mentioned on line 303, but not defined == Missing Reference: 'G.798-a2' is mentioned on line 406, 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 (~~), 8 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 4, 2014 Huawei Technologies 6 S. Belotti 7 Alcatel-Lucent 8 R. Rao 9 Infinera Corporation 10 J. Drake 11 Juniper 12 October 1, 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-09 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 4, 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 . . . . . . . . . . . . . . . . . . . . 5 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 . . . . . . . . . . . . . 17 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. Compatibility . . . . . . . . . . . . . . . . . . . . . . . . 27 83 7. Security Considerations . . . . . . . . . . . . . . . . . . . 28 84 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 85 8.1. Switching types . . . . . . . . . . . . . . . . . . . . . 28 86 8.2. New TLVs . . . . . . . . . . . . . . . . . . . . . . . . . 28 87 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 29 88 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 31 89 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 32 90 11.1. Normative References . . . . . . . . . . . . . . . . . . . 32 91 11.2. Informative References . . . . . . . . . . . . . . . . . . 32 92 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 33 94 1. Introduction 96 G.709 Optical Transport Network (OTN) [G.709-2012] includes new fixed 97 and flexible ODU (Optical channel Data Unit) containers, two types of 98 Tributary Slots (i.e. 1.25Gbps and 2.5Gbps), and supports various 99 multiplexing relationships (e.g., ODUj multiplexed into ODUk (jODUk format 150 is used to indicate the ODUj into ODUk multiplexing capability. 152 This notation can be repeated as needed depending on the number of 153 multiplexing levels. In the following the term "multiplexing tree" 154 is used to identify a multiplexing hierarchy where the root is always 155 a server ODUk/OTUk and any other supported multiplexed container is 156 represented with increasing granularity until reaching the leaf of 157 the tree. The tree can be structured with more than one branch if 158 the server ODUk/OTUk supports more than one hierarchy. 160 If for example a multiplexing hierarchy like the following one is 161 considered: 163 ODU2 ODU0 ODUflex ODU0 164 \ / \ / 165 | | 166 ODU3 ODU2 167 \ / 168 \ / 169 \ / 170 \ / 171 ODU4 173 The ODU4 is the root of the muxing tree, ODU3 and ODU2 are containers 174 directly multiplexed into the server and then ODU2, ODU0 are the 175 leaves of the ODU3 branch, while ODUflex and ODU0 are the leaves of 176 the ODU2 one. This means that it is possible to have the following 177 multiplexing capabilities: 179 ODU2->ODU3->ODU4 180 ODU0->ODU3->ODU4 181 ODUflex->ODU2->ODU4 182 ODU0->ODU2->ODU4 184 3. TE-Link Representation 186 G.709 ODUk/OTUk Links are represented as TE-Links in GMPLS Traffic 187 Engineering Topology for supporting ODUj layer switching. These TE- 188 Links can be modeled in multiple ways. 190 OTUk physical Link(s) can be modeled as a TE-Link(s). Figure 1 below 191 provides an illustration of one hop OTUk TE-links. 193 +-------+ +-------+ +-------+ 194 | OTN | | OTN | | OTN | 195 |Switch |<- OTUk Link ->|Switch |<- OTUk Link ->|Switch | 196 | A | | B | | C | 197 +-------+ +-------+ +-------+ 199 |<-- TE-Link -->| |<-- TE-Link -->| 201 Figure 1: OTUk TE-Links 203 It is possible to create TE-Links that span more than one hop by 204 creating FAs between non-adjacent nodes (see Figure 2). As in the 205 one hop case multiple hop TE-links advertise ODU switching capacity. 207 +-------+ +-------+ +-------+ 208 | OTN | | OTN | | OTN | 209 |Switch |<- OTUk Link ->|Switch |<- OTUk Link ->|Switch | 210 | A | | B | | C | 211 +-------+ +-------+ +-------+ 212 ODUk Switched 214 |<------------- ODUk Link ------------->| 215 |<-------------- TE-Link--------------->| 217 Figure 2: Multiple hop TE-Link 219 4. ISCD format extensions 221 The ISCD describes the switching capability of an interface and is 222 defined in [RFC4203]. This document defines a new Switching 223 Capability value for OTN [G.709-2012] as follows: 225 Value Type 226 ----- ---- 227 110 (TBA by IANA) OTN-TDM capable (OTN-TDM) 229 When supporting the extensions defined in this document, the 230 Switching Capability and Encoding values MUST be used as follows: 232 - Switching Capability = OTN-TDM 233 - Encoding Type = G.709 ODUk (Digital Path) as defined in [RFC4328] 235 Both for fixed and flexible ODUs the same switching type and encoding 236 values MUST be used. When Switching Capability and Encoding fields 237 are set to values as stated above, the Interface Switching Capability 238 Descriptor MUST be interpreted as defined in [RFC4203]. 240 Maximum LSP Bandwidth 242 The MAX LSP Bandwidth field is used according to [RFC4203]: i.e. 0 <= 243 MAX LSP Bandwidth <= ODUk/OTUk and intermediate values are those on 244 the branch of OTN switching hierarchy supported by the interface. 245 E.g. in the OTU4 link it could be possible to have ODU4 as MAX LSP 246 Bandwidth for some priorities, ODU3 for others, ODU2 for some others 247 etc. The bandwidth unit is in bytes per second and the encoding MUST 248 be in Institute of Electrical and Electronic Engineers (IEEE) 249 floating point format. The discrete values for various ODUs is shown 250 in the table below (please note that there are 1000 bits in a kbit 251 according to normal practices in telecommunications). 253 +---------------------+------------------------------+-----------------+ 254 | ODU Type | ODU nominal bit rate |Value in Byte/Sec| 255 | | |(floating p. val)| 256 +---------------------+------------------------------+-----------------+ 257 | ODU0 | 1 244 160 kbit/s | 0x4D1450C0 | 258 | ODU1 | 239/238 x 2 488 320 kbit/s | 0x4D94F048 | 259 | ODU2 | 239/237 x 9 953 280 kbit/s | 0x4E959129 | 260 | ODU3 | 239/236 x 39 813 120 kbit/s | 0x4F963367 | 261 | ODU4 | 239/227 x 99 532 800 kbit/s | 0x504331E3 | 262 | ODU2e | 239/237 x 10 312 500 kbit/s | 0x4E9AF70A | 263 | | | | 264 | ODUflex for CBR | | MAX LSP | 265 | Client signals | 239/238 x client signal | BANDWIDTH | 266 | | bit rate | | 267 | ODUflex for GFP-F | | MAX LSP | 268 |Mapped client signal | Configured bit rate | BANDWIDTH | 269 | | | | 270 | | | | 271 |ODU flex resizable | Configured bit rate | MAX LSP | 272 | | | BANDWIDTH | 273 +---------------------+------------------------------+-----------------+ 275 A single ISCD MAY be used for the advertisement of unbundled or 276 bundled links supporting homogeneous multiplexing hierarchies and the 277 same TS (Tributary Slot) granularity. A different ISCD MUST be used 278 for each different muxing hierarchy (muxing tree in the following 279 examples) and different TS granularity supported within the TE Link. 281 4.1. Switching Capability Specific Information 283 The technology specific part of the OTN-TDM ISCD may include a 284 variable number of sub-TLVs called Bandwidth sub-TLVs. Each sub-TLV 285 is encoded with the TLV header as defined in [RFC3630] section 2.3.2. 286 The muxing hierarchy tree MUST be encoded as an order independent 287 list. Two types of Bandwidth TLV are defined (TBA by IANA). Note 288 that type values are defined in this document and not in [RFC3630]. 290 - Type 1 - Unreserved Bandwidth for fixed containers 292 - Type 2 - Unreserved/MAX LSP Bandwidth for flexible containers 294 The Switching Capability-specific information (SCSI) MUST include one 295 Type 1 sub-TLV for each fixed container and one Type 2 sub-TLV for 296 each variable container. Each container type is identified by a 297 Signal Type. Signal Type values are defined in [OTN-SIG]. 299 With respect to ODUflex, three different signal types are allowed: 20 300 - ODUflex Constant Bit Rate (CBR), 21 - ODUflex Generic Framing 301 Procedure-Frame mapped (GFP-F) resizable and 22 - ODUflex (GFP-F) non 302 resizable. Each MUST always be advertised in separate Type 2 TLVs as 303 each uses different adaptation functions [G.805]. In the case that 304 both GFP-F resizable and non resizable (i.e. 21 and 22) are 305 supported, only Signal Type 21 SHALL be advertised as this type also 306 implies support for type 22 adaptation. 308 4.1.1. Switching Capability Specific Information for fixed containers 310 The format of the Bandwidth TLV for fixed containers is depicted in 311 the following figure: 313 0 1 2 3 314 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 315 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 316 | Type = 1 (Unres-fix) | Length | 317 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 318 | Signal type | Num of stages |T|S| TSG | Res | Priority | 319 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 320 | Stage#1 | ... | Stage#N | Padding | 321 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 322 | Unreserved ODUj at Prio 0 | ..... | 323 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 324 | Unreserved ODUj at Prio 7 | Unreserved Padding | 325 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 327 Figure 3: Bandwidth TLV - Type 1 - 329 The values of the fields shown in figure 4 are explained in section 330 4.1.3. 332 4.1.2. Switching Capability Specific Information for variable 333 containers 335 The format of the Bandwidth TLV for variable containers is depicted 336 in the following figure: 338 0 1 2 3 339 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 340 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 341 | Type = 2 (Unres/MAX-var) | Length | 342 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 343 | Signal type | Num of stages |T|S| TSG | Res | Priority | 344 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 345 | Stage#1 | ... | Stage#N | Padding | 346 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 347 | Unreserved Bandwidth at priority 0 | 348 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 349 | ... | 350 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 351 | Unreserved Bandwidth at priority 7 | 352 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 353 | MAX LSP Bandwidth at priority 0 | 354 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 355 | ... | 356 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 357 | MAX LSP Bandwidth at priority 7 | 358 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 360 Figure 4: Bandwidth TLV - Type 2 - 362 The values of the fields shown in figure 4 are explained in section 363 4.1.3. 365 4.1.3. Switching Capability Specific Information - Field values and 366 explanation 368 The fields in the Bandwidth TLV MUST be filled as follows: 370 - Signal Type (8 bits): Indicates the ODU type being advertised. 371 Values are defined in [OTN-SIG]. 373 - Number of stages (8 bits): This field indicates the number of 374 multiplexing stages used to transport the indicated signal type. 375 It MUST be set to the number of stages represented in the TLV. 377 - Flags (8 bits): 379 - T Flag (bit 17): Indicates whether the advertised bandwidth 380 can be terminated. When the signal type can be terminated T 381 MUST be set, while when the signal type cannot be terminated T 382 MUST be cleared. 384 - S Flag (bit 18): Indicates whether the advertised bandwidth 385 can be switched. When the signal type can be switched S MUST 386 be set, while when the signal type cannot be switched S MUST be 387 cleared. 389 The value 0 in both T and S bits MUST NOT be used. 391 - TS Granularity: Tributary Slot Granularity (3 bits): Used for 392 the advertisement of the supported Tributary Slot granularity. 393 The following values MUST be used: 395 - 0 - Ignored 397 - 1 - 1.25Gbps/2.5Gbps 399 - 2 - 2.5Gbps only 401 - 3 - 1.25Gbps only 403 - 4-7 - Reserved 405 A value of 1 MUST be used on interfaces which are configured to 406 support the fall back procedures defined in [G.798-a2]. A value 407 of 2 MUST be used on interfaces that only support 2.5Gbps time 408 slots, such as [RFC4328] interfaces. A value of 3 MUST be used on 409 interfaces that are configured to only support 1.25Gbps time 410 slots. A value of 0 MUST be used for non multiplexed signal types 411 (i.e. a non OTN client). 413 - Res (3 bits): reserved bits. MUST be set to 0 and ignored on 414 receipt. 416 - Priority (8 bits): a bitmap used to indicate which priorities 417 are being advertised. The bitmap is in ascending order, with the 418 leftmost bit representing priority level 0 (i.e. the highest) and 419 the rightmost bit representing priority level 7 (i.e. the lowest). 420 A bit MUST be set (1) corresponding to each priority represented 421 in the TLV, and MUST NOT be set (0) when the corresponding 422 priority is not represented. At least one priority level MUST be 423 advertised that, unless overridden by local policy, SHALL be at 424 priority level 0. 426 - Stage (8 bits): Each Stage field indicates a signal type in the 427 multiplexing hierarchy used to transport the signal indicated in 428 the Signal Type field. The number of Stage fields included in a 429 TLV MUST equal the value of the Number of Stages field. The Stage 430 fields MUST be ordered to match the data plane in ascending order 431 (from the lowest order ODU to the highest order ODU). The values 432 of the Stage field are the same as those defined for the Signal 433 Type field. When the Number of stage field carries a 0, then the 434 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 % 4). 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. 451 - Unreserved Padding (16 bits): The Padding field is used to 452 ensure the 32 bit alignment of Unreserved ODUj fields. When 453 present the Unreserved Padding field is 16 bits (2 byte) long. 454 When the number of priorities is odd, the Unreserved Padding field 455 MUST be included. When the number of priorities is even, the 456 Unreserved Padding MUST be omitted. 458 - Unreserved Bandwidth (32 bits): This field indicates the 459 Unreserved Bandwidth at a particular priority level. This field 460 MUST be set to the bandwidth, in Bytes/sec in IEEE floating point 461 format, available at the indicated Signal Type for a particular 462 priority level. One field MUST be present for each bit set in the 463 Priority field, and is ordered to match the Priority field. 464 Fields MUST NOT be present for priority levels that are not 465 indicated in the Priority field. 467 - Maximum LSP Bandwidth (32 bit): This field indicates the maximum 468 bandwidth that can be allocated for a single LSP at a particular 469 priority level. This field MUST be set to the maximum bandwidth, 470 in Bytes/sec in IEEE floating point format, available to a single 471 LSP at the indicated Signal Type for a particular priority level. 472 One field MUST be present for each bit set in the Priority field, 473 and is ordered to match the Priority field. Fields MUST NOT be 474 present for priority levels that are not indicated in the Priority 475 field. The advertisement of the MAX LSP Bandwidth MUST take into 476 account HO OPUk bit rate tolerance and be calculated according to 477 the following formula: 479 Max LSP BW = (# available TSs) * (ODTUk.ts nominal bit rate) * 480 (1-HO OPUk bit rate tolerance) 482 5. Examples 484 The examples in the following pages are not normative and are not 485 intended to imply or mandate any specific implementation. 487 5.1. MAX LSP Bandwidth fields in the ISCD 489 This example shows how the MAX LSP Bandwidth fields of the ISCD are 490 filled accordingly to the evolving of the TE-link bandwidth 491 occupancy. In the example an OTU4 link is considered, with supported 492 priorities 0,2,4,7 and muxing hierarchy ODU1->ODU2->ODU3->ODU4. 494 At time T0, with the link completely free, the advertisement would 495 be: 497 0 1 2 3 498 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 499 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 500 | SwCap=OTN_TDM | Encoding = 12 | Reserved (all zeros) | 501 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 502 | MAX LSP Bandwidth at priority 0 = 100Gbps | 503 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 504 | MAX LSP Bandwidth at priority 1 = 0 | 505 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 506 | MAX LSP Bandwidth at priority 2 = 100Gbps | 507 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 508 | MAX LSP Bandwidth at priority 3 = 0 | 509 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 510 | MAX LSP Bandwidth at priority 4 = 100Gbps | 511 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 512 | MAX LSP Bandwidth at priority 5 = 0 | 513 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 514 | MAX LSP Bandwidth at priority 6 = 0 | 515 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 516 | MAX LSP Bandwidth at priority 7 = 100Gbps | 517 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 518 | Switching Capability Specific Information | 519 | (variable length) | 520 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 522 Figure 5: Example 1 - MAX LSP Bandwidth fields in the ISCD @T0 524 At time T1 an ODU3 at priority 2 is set-up, so for priority 0 the MAX 525 LSP Bandwidth is still equal to the ODU4 bandwidth, while for 526 priorities from 2 to 7 (excluding the non supported ones) the MAX LSP 527 Bandwidth is equal to ODU3, as no more ODU4s are available and the 528 next supported ODUj in the hierarchy is ODU3.The advertisement is 529 updated as follows: 531 0 1 2 3 532 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 533 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 534 | SwCap=OTN_TDM | Encoding = 12 | Reserved (all zeros) | 535 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 536 | MAX LSP Bandwidth at priority 0 = 100Gbps | 537 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 538 | MAX LSP Bandwidth at priority 1 = 0 | 539 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 540 | MAX LSP Bandwidth at priority 2 = 40Gbps | 541 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 542 | MAX LSP Bandwidth at priority 3 = 0 | 543 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 544 | MAX LSP Bandwidth at priority 4 = 40Gbps | 545 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 546 | MAX LSP Bandwidth at priority 5 = 0 | 547 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 548 | MAX LSP Bandwidth at priority 6 = 0 | 549 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 550 | MAX LSP Bandwidth at priority 7 = 40Gbps | 551 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 552 | Switching Capability Specific Information | 553 | (variable length) | 554 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 556 Figure 6: Example 1 - MAX LSP Bandwidth fields in the ISCD @T1 558 At time T2 an ODU2 at priority 4 is set-up. The first ODU3 is no 559 longer available since T1 as it was kept by the ODU3 LSP, while the 560 second is no more available and just 3 ODU2 are left in it. ODU2 is 561 now the MAX LSP Bandwidth for priorities higher than 4. The 562 advertisement is updated as follows: 564 0 1 2 3 565 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 566 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 567 | SwCap=OTN_TDM | Encoding = 12 | Reserved (all zeros) | 568 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 569 | MAX LSP Bandwidth at priority 0 = 100Gbps | 570 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 571 | MAX LSP Bandwidth at priority 1 = 0 | 572 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 573 | MAX LSP Bandwidth at priority 2 = 40Gbps | 574 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 575 | MAX LSP Bandwidth at priority 3 = 0 | 576 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 577 | MAX LSP Bandwidth at priority 4 = 10Gbps | 578 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 579 | MAX LSP Bandwidth at priority 5 = 0 | 580 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 581 | MAX LSP Bandwidth at priority 6 = 0 | 582 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 583 | MAX LSP Bandwidth at priority 7 = 10Gbps | 584 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 585 | Switching Capability Specific Information | 586 | (variable length) | 587 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 589 Figure 7: Example 1 - MAX LSP Bandwidth fields in the ISCD @T2 591 5.2. Example of T,S and TS granularity utilization 593 In this example an interface with Tributary Slot Type 1.25Gbps and 594 fallback procedure enabled is considered (TS granularity=1). It 595 supports the simple ODU1->ODU2->ODU3 hierarchy and priorities 0 and 596 3. Suppose that in this interface the ODU3 signal type can be both 597 switched or terminated, the ODU2 can only be terminated and the ODU1 598 switched only. Please note that since the ODU1 is not being 599 advertised to support ODU0 the value of is "ignored" (TS 600 granularity=0). For the advertisement of the capabilities of such 601 interface a single ISCD is used and its format is as follows: 603 0 1 2 3 604 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 605 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 606 | Type = 1 (Unres-fix) | Length = 12 | 607 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 608 |Sig type=ODU1 | #stages= 2 |T0|S1| 0 |0 0 0|1|0|0|1|0|0|0|0| 609 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 610 | Stage#1=ODU2 | Stage#2=ODU3 | Padding (all zeros) | 611 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 612 | Unres ODU1 at Prio 0 | Unres ODU1 at Prio 3 | 613 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 614 | Type = 1 (Unres-fix) | Length = 12 | 615 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 616 |Sig type=ODU2 | #stages= 1 |T1|S0| 1 |0 0 0|1|0|0|1|0|0|0|0| 617 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 618 | Stage#1=ODU3 | Padding (all zeros) | 619 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 620 | Unres ODU2 at Prio 0 | Unres ODU2 at Prio 3 | 621 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 622 | Type = 1 (Unres-fix) | Length = 8 | 623 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 624 |Sig type=ODU3 | #stages= 0 |T1|S1| 1 |0 0 0|1|0|0|1|0|0|0|0| 625 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 626 | Unres ODU3 at Prio 0 | Unres ODU3 at Prio 3 | 627 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 629 Figure 8: Example 2 - TS granularity, T and S utilization 631 5.2.1. Example of different TS Granularities 633 In this example two interfaces with homogeneous hierarchies but 634 different Tributary Slot Types are considered. The first one 635 supports a [RFC4328] interface (TS granularity=2) while the second 636 one a G.709-2012 interface with fallback procedure disabled (TS 637 granularity=3). Both of them support ODU1->ODU2->ODU3 hierarchy and 638 priorities 0 and 3. T and S bits values are not relevant to this 639 example. For the advertisement of the capabilities of such 640 interfaces two different ISCDs are used and the format of their SCSIs 641 is as follows: 643 SCSI of ISCD 1 - TS granularity=2 644 0 1 2 3 645 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 646 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 647 | Type = 1 (Unres-fix) | Length = 12 | 648 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 649 |Sig type=ODU1 | #stages= 2 |T0|S1| 0 |0 0 0|1|0|0|1|0|0|0|0| 650 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 651 | Stage#1=ODU2 | Stage#2=ODU3 | Padding (all zeros) | 652 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 653 | Unres ODU1 at Prio 0 | Unres ODU1 at Prio 3 | 654 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 655 | Type = 1 (Unres-fix) | Length = 12 | 656 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 657 |Sig type=ODU2 | #stages= 1 |T1|S0| 1 |0 0 0|1|0|0|1|0|0|0|0| 658 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 659 | Stage#1=ODU3 | Padding (all zeros) | 660 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 661 | Unres ODU2 at Prio 0 | Unres ODU2 at Prio 3 | 662 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 663 | Type = 1 (Unres-fix) | Length = 8 | 664 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 665 |Sig type=ODU3 | #stages= 0 |T1|S1| 2 |0 0 0|1|0|0|1|0|0|0|0| 666 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 667 | Unres ODU3 at Prio 0 | Unres ODU3 at Prio 3 | 668 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 670 SCSI of ISCD 2 - TS granularity=3 671 0 1 2 3 672 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 673 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 674 | Type = 1 (Unres-fix) | Length = 12 | 675 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 676 |Sig type=ODU1 | #stages= 2 |T0|S1| 0 |0 0 0|1|0|0|1|0|0|0|0| 677 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 678 | Stage#1=ODU2 | Stage#2=ODU3 | Padding (all zeros) | 679 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 680 | Unres ODU1 at Prio 0 | Unres ODU1 at Prio 3 | 681 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 682 | Type = 1 (Unres-fix) | Length = 12 | 683 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 684 |Sig type=ODU2 | #stages= 1 |T1|S0| 1 |0 0 0|1|0|0|1|0|0|0|0| 685 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 686 | Stage#1=ODU3 | Padding (all zeros) | 687 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 688 | Unres ODU2 at Prio 0 | Unres ODU2 at Prio 3 | 689 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 690 | Type = 1 (Unres-fix) | Length = 8 | 691 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 692 |Sig type=ODU3 | #stages= 0 |T1|S1| 3 |0 0 0|1|0|0|1|0|0|0|0| 693 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 694 | Unres ODU3 at Prio 0 | Unres ODU3 at Prio 3 | 695 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 696 Figure 9: Example 2.1 - Different TS Granularities utilization 698 A particular case in which hierarchies with the same muxing tree but 699 with different exported TS granularity MUST be considered as non 700 homogenous hierarchies is the case in which an H-LPS and the client 701 LSP are terminated on the same egress node. What can happen is that 702 a loose Explicit Route Object (ERO) is used at the hop where the 703 signaled LSP is nested into the Hierarchical-LSP (H-LSP) (penultimate 704 hop of the LSP). 706 In the following figure, node C receives from A a loose ERO towards 707 node E and must choose between the ODU2 H-LSP on if1 or the one on 708 if2. In case the H-LSP on if1 exports a TS=1.25Gbps and if2 a 709 TS=2.5Gbps and the service LSP being signaled needs a 1.25Gbps 710 tributary slot, only the H-LSP on if1 can be used to reach node E. 711 For further details please see section 4.1 of the [OTN-INFO]. 713 ODU0-LSP 714 ..........................................................+ 715 | | 716 | ODU2-H-LSP | 717 | +-------------------------------+ 718 | | | 719 +--+--+ +-----+ +-----+ if1 +-----+ +-----+ 720 | | OTU3 | | OTU3 | |---------| |---------| | 721 | A +------+ B +------+ C | if2 | D | | E | 722 | | | | | |---------| |---------| | 723 +-----+ +-----+ +-----+ +-----+ +-----+ 725 ... Service LSP 726 --- H-LSP 728 Figure 10: Example - Service LSP and H-LSP terminating on the same 729 node 731 5.3. Example of ODUflex advertisement 733 In this example the advertisement of an ODUflex->ODU3 hierarchy is 734 shown. In case of ODUflex advertisement the MAX LSP Bandwidth needs 735 to be advertised and in some cases also information about the 736 Unreserved bandwidth could be useful. The amount of Unreserved 737 bandwidth does not give a clear indication of how many ODUflex LSP 738 can be set up either at the MAX LSP Bandwidth or at different rates, 739 as it gives no information about the spatial allocation of the free 740 TSs. 742 An indication of the amount of Unreserved bandwidth could be useful 743 during the path computation process, as shown in the following 744 example. Supposing there are two TE-links (A and B) with MAX LSP 745 Bandwidth equal to 10 Gbps each. In case 50Gbps of Unreserved 746 Bandwidth are available on Link A, 10Gbps on Link B and 3 ODUflex 747 LSPs of 10 GBps each, have to be restored, for sure only one can be 748 restored along Link B and it is probable (but not sure) that two of 749 them can be restored along Link A. T, S and TS granularity fields are 750 not relevant to this example. 752 In the case of ODUflex advertisement the Type 2 Bandwidth TLV is 753 used. 755 0 1 2 3 756 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 757 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 758 | Type = 2 (Unres/MAX-var) | Length = 72 | 759 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 760 |S. type=ODUflex| #stages= 1 |T|S| TSG |0 0 0| Priority(8) | 761 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 762 | Stage#1=ODU3 | Padding (all zeros) | 763 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 764 | Unreserved Bandwidth at priority 0 | 765 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 766 | Unreserved Bandwidth at priority 1 | 767 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 768 | Unreserved Bandwidth at priority 2 | 769 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 770 | Unreserved Bandwidth at priority 3 | 771 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 772 | Unreserved Bandwidth at priority 4 | 773 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 774 | Unreserved Bandwidth at priority 5 | 775 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 776 | Unreserved Bandwidth at priority 6 | 777 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 778 | Unreserved Bandwidth at priority 7 | 779 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 780 | MAX LSP Bandwidth at priority 0 | 781 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 782 | MAX LSP Bandwidth at priority 1 | 783 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 784 | MAX LSP Bandwidth at priority 2 | 785 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 786 | MAX LSP Bandwidth at priority 3 | 787 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 788 | MAX LSP Bandwidth at priority 4 | 789 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 790 | MAX LSP Bandwidth at priority 5 | 791 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 792 | MAX LSP Bandwidth at priority 6 | 793 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 794 | MAX LSP Bandwidth at priority 7 | 795 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 797 Figure 11: Example 3 - ODUflex advertisement 799 5.4. Example of single stage muxing 801 Supposing there is 1 OTU4 component link supporting single stage 802 muxing of ODU1, ODU2, ODU3 and ODUflex, the supported hierarchy can 803 be summarized in a tree as in the following figure. For sake of 804 simplicity we assume that also in this case only priorities 0 and 3 805 are supported. T, S and TS granularity fields are not relevant to 806 this example. 808 ODU1 ODU2 ODU3 ODUflex 809 \ \ / / 810 \ \ / / 811 \ \/ / 812 ODU4 814 and the related SCSIs as follows: 816 0 1 2 3 817 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 818 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 819 | Type = 1 (Unres-fix) | Length = 8 | 820 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 821 |Sig type=ODU4 | #stages= 0 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 822 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 823 | Unres ODU4 at Prio 0 =1 | Unres ODU4 at Prio 3 =1 | 824 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 825 | Type = 1 (Unres-fix) | Length = 12 | 826 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 827 |Sig type=ODU1 | #stages= 1 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 828 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 829 | Stage#1=ODU4 | Padding (all zeros) | 830 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 831 | Unres ODU1 at Prio 0 =40 | Unres ODU1 at Prio 3 =40 | 832 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 833 | Type = 1 (Unres-fix) | Length = 12 | 834 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 835 |Sig type=ODU2 | #stages= 1 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 836 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 837 | Stage#1=ODU4 | Padding (all zeros) | 838 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 839 | Unres ODU2 at Prio 0 =10 | Unres ODU2 at Prio 3 =10 | 840 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 841 | Type = 1 (Unres-fix) | Length = 12 | 842 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 843 |Sig type=ODU3 | #stages= 1 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 844 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 845 | Stage#1=ODU4 | Padding (all zeros) | 846 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 847 | Unres ODU3 at Prio 0 =2 | Unres ODU3 at Prio 3 =2 | 848 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 849 | Type = 2 (Unres/MAX-var) | Length = 24 | 850 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 851 |S. type=ODUflex| #stages= 1 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 852 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 853 | Stage#1=ODU4 | Padding (all zeros) | 854 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 855 | Unreserved Bandwidth at priority 0 =100Gbps | 856 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 857 | Unreserved Bandwidth at priority 3 =100Gbps | 858 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 859 | MAX LSP Bandwidth at priority 0 =100Gbps | 860 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 861 | MAX LSP Bandwidth at priority 3 =100Gbps | 862 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 863 Figure 12: Example 4 - Single stage muxing 865 5.5. Example of multi stage muxing - Unbundled link 867 Supposing there is 1 OTU4 component link with muxing capabilities as 868 shown in the following figure: 870 ODU2 ODU0 ODUflex ODU0 871 \ / \ / 872 | | 873 ODU3 ODU2 874 \ / 875 \ / 876 \ / 877 \ / 878 ODU4 880 and supported priorities 0 and 3, the advertisement is composed by 881 the following Bandwidth TLVs (T and S fields are not relevant to this 882 example): 884 0 1 2 3 885 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 886 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 887 | Type = 1 (Unres-fix) | Length = 8 | 888 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 889 |Sig type=ODU4 | #stages= 0 |T|S| 1 |0 0 0|1|0|0|1|0|0|0|0| 890 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 891 | Unres ODU4 at Prio 0 =1 | Unres ODU4 at Prio 3 =1 | 892 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 893 | Type = 1 (Unres-fix) | Length = 12 | 894 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 895 |Sig type=ODU3 | #stages= 1 |T|S| 1 |0 0 0|1|0|0|1|0|0|0|0| 896 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 897 | Stage#1=ODU4 | Padding (all zeros) | 898 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 899 | Unres ODU3 at Prio 0 =2 | Unres ODU3 at Prio 3 =2 | 900 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 901 | Type = 1 (Unres-fix) | Length = 12 | 902 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 903 |Sig type=ODU2 | #stages= 1 |T|S| 1 |0 0 0|1|0|0|1|0|0|0|0| 904 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 905 | Stage#1=ODU4 | Padding (all zeros) | 906 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 907 | Unres ODU2 at Prio 0 =10 | Unres ODU2 at Prio 3 =10 | 908 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 909 | Type = 1 (Unres-fix) | Length = 12 | 910 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 911 |Sig type=ODU2 | #stages= 2 |T|S| 0 |0 0 0|1|0|0|1|0|0|0|0| 912 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 913 | Stage#1=ODU3 | Stage#2=ODU4 | Padding (all zeros) | 914 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 915 | Unres ODU2 at Prio 0 =8 | Unres ODU2 at Prio 3 =8 | 916 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 917 | Type = 1 (Unres-fix) | Length = 12 | 918 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 919 |Sig type=ODU0 | #stages= 2 |T|S| 0 |0 0 0|1|0|0|1|0|0|0|0| 920 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 921 | Stage#1=ODU3 | Stage#2=ODU4 | Padding (all zeros) | 922 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 923 | Unres ODU0 at Prio 0 =64 | Unres ODU0 at Prio 3 =64 | 924 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 925 | Type = 1 (Unres-fix) | Length = 12 | 926 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 927 |Sig type=ODU0 | #stages= 2 |T|S| 0 |0 0 0|1|0|0|1|0|0|0|0| 928 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 929 | Stage#1=ODU2 | Stage#2=ODU4 | Padding (all zeros) | 930 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 931 | Unres ODU0 at Prio 0 =80 | Unres ODU0 at Prio 3 =80 | 932 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 933 | Type = 2 (Unres/MAX-var) | Length = 24 | 934 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 935 |S.type=ODUflex | #stages= 2 |T|S| 0 |0 0 0|1|0|0|1|0|0|0|0| 936 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 937 | Stage#1=ODU2 | Stage#2=ODU4 | Padding (all zeros) | 938 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 939 | Unreserved Bandwidth at priority 0 =100Gbps | 940 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 941 | Unreserved Bandwidth at priority 3 =100Gbps | 942 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 943 | MAX LSP Bandwidth at priority 0 =10Gbps | 944 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 945 | MAX LSP Bandwidth at priority 3 =10Gbps | 946 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 948 Figure 13: Example 5 - Multi stage muxing - Unbundled link 950 5.6. Example of multi stage muxing - Bundled links 952 In this example 2 OTU4 component links with the same supported TS 953 granularity and homogeneous muxing hierarchies are considered. The 954 following muxing capabilities trees are supported: 956 Component Link#1 Component Link#2 957 ODU2 ODU0 ODU2 ODU0 958 \ / \ / 959 | | 960 ODU3 ODU3 961 | | 962 ODU4 ODU4 964 Considering only supported priorities 0 and 3, the advertisement is 965 as follows (T, S and TS granularity fields are not relevant to this 966 example): 968 0 1 2 3 969 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 970 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 971 | Type = 1 (Unres-fix) | Length = 8 | 972 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 973 |Sig type=ODU4 | #stages= 0 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 974 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 975 | Unres ODU4 at Prio 0 =2 | Unres ODU4 at Prio 3 =2 | 976 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 977 | Type = 1 (Unres-fix) | Length = 12 | 978 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 979 |Sig type=ODU3 | #stages= 1 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 980 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 981 | Stage#1=ODU4 | Padding (all zeros) | 982 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 983 | Unres ODU3 at Prio 0 =4 | Unres ODU3 at Prio 3 =4 | 984 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 985 | Type = 1 (Unres-fix) | Length = 12 | 986 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 987 |Sig type=ODU2 | #stages= 2 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 988 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 989 | Stage#1=ODU3 | Stage#2=ODU4 | Padding (all zeros) | 990 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 991 | Unres ODU2 at Prio 0 =16 | Unres ODU2 at Prio 3 =16 | 992 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 993 | Type = 1 (Unres-fix) | Length = 12 | 994 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 995 |Sig type=ODU0 | #stages= 2 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 996 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 997 | Stage#1=ODU3 | Stage#2=ODU4 | Padding (all zeros) | 998 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 999 | Unres ODU0 at Prio 0 =128 | Unres ODU0 at Prio 3 =128 | 1000 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1002 Figure 14: Example 6 - Multi stage muxing - Bundled links 1004 5.7. Example of component links with non homogeneous hierarchies 1006 In this example 2 OTU4 component links with the same supported TS 1007 granularity and non homogeneous muxing hierarchies are considered. 1008 The following muxing capabilities trees are supported: 1010 Component Link#1 Component Link#2 1011 ODU2 ODU0 ODU1 ODU0 1012 \ / \ / 1013 | | 1014 ODU3 ODU2 1015 | | 1016 ODU4 ODU4 1018 Considering only supported priorities 0 and 3, the advertisement uses 1019 two different ISCDs, one for each hierarchy (T, S and TS granularity 1020 fields are not relevant to this example). In the following figure, 1021 the SCSI of each ISCD is shown: 1023 SCSI of ISCD 1 - Component Link#1 1025 0 1 2 3 1026 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 1027 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1028 | Type = 1 (Unres-fix) | Length = 8 | 1029 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1030 |Sig type=ODU4 | #stages= 0 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 1031 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1032 | Unres ODU4 at Prio 0 =1 | Unres ODU4 at Prio 3 =1 | 1033 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1034 | Type = 1 (Unres-fix) | Length = 12 | 1035 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1036 |Sig type=ODU3 | #stages= 1 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 1037 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1038 | Stage#1=ODU4 | Padding (all zeros) | 1039 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1040 | Unres ODU3 at Prio 0 =2 | Unres ODU3 at Prio 3 =2 | 1041 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1042 | Type = 1 (Unres-fix) | Length = 12 | 1043 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1044 |Sig type=ODU2 | #stages= 2 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 1045 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1046 | Stage#1=ODU3 | Stage#2=ODU4 | Padding (all zeros) | 1047 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1048 | Unres ODU2 at Prio 0 =8 | Unres ODU2 at Prio 3 =8 | 1049 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1050 | Type = 1 (Unres-fix) | Length = 12 | 1051 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1052 |Sig type=ODU0 | #stages= 2 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 1053 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1054 | Stage#1=ODU3 | Stage#2=ODU4 | Padding (all zeros) | 1055 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1056 | Unres ODU0 at Prio 0 =64 | Unres ODU0 at Prio 3 =64 | 1057 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1059 SCSI of ISCD 2 - Component Link#2 1061 0 1 2 3 1062 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 1063 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1064 | Type = 1 (Unres-fix) | Length = 8 | 1065 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1066 |Sig type=ODU4 | #stages= 0 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 1067 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1068 | Unres ODU4 at Prio 0 =1 | Unres ODU4 at Prio 3 =1 | 1069 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1070 | Type = 1 (Unres-fix) | Length = 12 | 1071 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1072 |Sig type=ODU2 | #stages= 1 |T|S| TSG |0 0 0 |1|0|0|1|0|0|0|0| 1073 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1074 | Stage#1=ODU4 | Padding (all zeros) | 1075 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1076 | Unres ODU2 at Prio 0 =10 | Unres ODU2 at Prio 3 =10 | 1077 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1078 | Type = 1 (Unres-fix) | Length = 12 | 1079 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1080 |Sig type=ODU1 | #stages= 2 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 1081 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1082 | Stage#1=ODU2 | Stage#2=ODU4 | Padding (all zeros) | 1083 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1084 | Unres ODU1 at Prio 0 =40 | Unres ODU1 at Prio 3 =40 | 1085 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1086 | Type = 1 (Unres-fix) | Length = 12 | 1087 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1088 |Sig type=ODU0 | #stages= 2 |T|S| TSG |0 0 0|1|0|0|1|0|0|0|0| 1089 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1090 | Stage#1=ODU2 | Stage#2=ODU4 | Padding (all zeros) | 1091 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1092 | Unres ODU0 at Prio 0 =80 | Unres ODU0 at Prio 3 =80 | 1093 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1095 Figure 15: Example 7 - Multi stage muxing - Non homogeneous 1096 hierarchies 1098 6. Compatibility 1100 All implementations of this document MAY support also advertisement 1101 as defined in [RFC4328]. When nodes support both advertisement 1102 methods, implementations MUST support the configuration of which 1103 advertisement method is followed. The choice of which is used is 1104 based on policy and is out of scope of the document. This enables 1105 nodes following each method to identify similar supporting nodes and 1106 compute paths using only the appropriate nodes. 1108 7. Security Considerations 1110 This document extends [RFC4203]. As with[RFC4203], it specifies the 1111 contents of Opaque LSAs in OSPFv2. As Opaque LSAs are not used for 1112 SPF computation or normal routing, the extensions specified here have 1113 no direct effect on IP routing. Tampering with GMPLS TE LSAs may 1114 have an effect on the underlying transport (optical and/or SONET-SDH) 1115 network. [RFC3630] suggests mechanisms such as [RFC2154] to protect 1116 the transmission of this information, and those or other mechanisms 1117 should be used to secure and/or authenticate the information carried 1118 in the Opaque LSAs. 1120 For security threats, defensive techniques, monitoring/detection/ 1121 reporting of security attacks and requirements please refer to 1122 [RFC5920] . 1124 8. IANA Considerations 1126 8.1. Switching types 1128 Upon approval of this document, IANA will make the assignment in the 1129 "Switching Types" section of the "GMPLS Signaling Parameters" 1130 registry located at 1131 http://www.iana.org/assignments/gmpls-sig-parameters: 1133 Value Name Reference 1134 --------- -------------------------- ---------- 1135 110 (*) OTN-TDM capable (OTN-TDM) [This.I-D] 1137 (*) Suggested value 1139 Same type of modification needs to applied to the IANA-GMPLS-TC-MIB 1140 at https://www.iana.org/assignments/ianagmplstc-mib/ianagmplstc-mib 1142 8.2. New TLVs 1144 This document defines 2 new TLVs that are carried in Interface 1145 Switching Capability Descriptors [RFC4203] with Signal Type OTN-TDM. 1147 Each TLV includes a 16-bit type identifier (the T-field). The same 1148 T-field values are applicable to the new sub-TLV. 1150 Upon approval of this document, IANA will create and maintain a new 1151 registry, the "Types for sub-TLVs of OTN-TDM SCSI (Switch Capability 1152 Specific Information)" registry under the "Open Shortest Path First 1153 (OSPF) Traffic Engineering TLVs" registry, see http://www.iana.org/ 1154 assignments/ospf-traffic-eng-tlvs/ospf-traffic-eng-tlvs.xml, with the 1155 TLV types as follows: 1157 This document defines new TLV types as follows: 1159 Value Sub-TLV Reference 1160 --------- -------------------------- ---------- 1161 0 Reserved [This.I-D] 1162 1 Unreserved Bandwidth for [This.I-D] 1163 fixed containers 1164 2 Unreserved/MAX Bandwidth for [This.I-D] 1165 flexible containers 1166 3-65535 Unassigned 1168 Types are to be assigned via Standards Action as defined in 1169 [RFC5226]. 1171 9. Contributors 1173 Diego Caviglia, Ericsson 1175 Via E.Melen, 77 - Genova - Italy 1177 Email: diego.caviglia@ericsson.com 1179 Dan Li, Huawei Technologies 1181 Bantian, Longgang District - Shenzhen 518129 P.R.China 1183 Email: danli@huawei.com 1185 Pietro Vittorio Grandi, Alcatel-Lucent 1187 Via Trento, 30 - Vimercate - Italy 1188 Email: pietro_vittorio.grandi@alcatel-lucent.com 1190 Khuzema Pithewan, Infinera Corporation 1192 140 Caspian CT., Sunnyvale - CA - USA 1194 Email: kpithewan@infinera.com 1196 Xiaobing Zi, Huawei Technologies 1198 Email: zixiaobing@huawei.com 1200 Francesco Fondelli, Ericsson 1202 Email: francesco.fondelli@ericsson.com 1204 Marco Corsi 1206 EMail: corsi.marco@gmail.com 1208 Eve Varma, Alcatel-Lucent 1210 EMail: eve.varma@alcatel-lucent.com 1212 Jonathan Sadler, Tellabs 1214 EMail: jonathan.sadler@tellabs.com 1216 Lyndon Ong, Ciena 1218 EMail: lyong@ciena.com 1219 Ashok Kunjidhapatham 1221 akunjidhapatham@infinera.com 1223 Snigdho Bardalai 1225 sbardalai@infinera.com 1227 Steve Balls 1229 Steve.Balls@metaswitch.com 1231 Jonathan Hardwick 1233 Jonathan.Hardwick@metaswitch.com 1235 Xihua Fu 1237 fu.xihua@zte.com.cn 1239 Cyril Margaria 1241 cyril.margaria@nsn.com 1243 Malcolm Betts 1245 Malcolm.betts@zte.com.cn 1247 10. Acknowledgements 1249 The authors would like to thank Fred Gruman and Lou Berger for the 1250 precious comments and suggestions. 1252 11. References 1253 11.1. Normative References 1255 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1256 Requirement Levels", BCP 14, RFC 2119, March 1997. 1258 [RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering 1259 (TE) Extensions to OSPF Version 2", RFC 3630, 1260 September 2003. 1262 [RFC4203] Kompella, K. and Y. Rekhter, "OSPF Extensions in Support 1263 of Generalized Multi-Protocol Label Switching (GMPLS)", 1264 RFC 4203, October 2005. 1266 [RFC4328] Papadimitriou, D., "Generalized Multi-Protocol Label 1267 Switching (GMPLS) Signaling Extensions for G.709 Optical 1268 Transport Networks Control", RFC 4328, January 2006. 1270 11.2. Informative References 1272 [OTN-FWK] F.Zhang, D.Li, H.Li, S.Belotti, D.Ceccarelli, "Framework 1273 for GMPLS and PCE Control of G.709 Optical Transport 1274 networks, work in progress 1275 draft-ietf-ccamp-gmpls-g709-framework-13", June 2013. 1277 [OTN-INFO] 1278 S.Belotti, P.Grandi, D.Ceccarelli, D.Caviglia, F.Zhang, 1279 D.Li, "Information model for G.709 Optical Transport 1280 Networks (OTN), work in progress 1281 draft-ietf-ccamp-otn-g709-info-model-09", June 2013. 1283 [OTN-SIG] F.Zhang, G.Zhang, S.Belotti, D.Ceccarelli, K.Pithewan, 1284 "Generalized Multi-Protocol Label Switching (GMPLS) 1285 Signaling Extensions for the evolving G.709 Optical 1286 Transport Networks Control, work in progress 1287 draft-ietf-ccamp-gmpls-signaling-g709v3-11", June 2013. 1289 [RFC2154] Murphy, S., Badger, M., and B. Wellington, "OSPF with 1290 Digital Signatures", RFC 2154, June 1997. 1292 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 1293 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 1294 May 2008. 1296 [RFC5920] Fang, L., "Security Framework for MPLS and GMPLS 1297 Networks", RFC 5920, July 2010. 1299 [RFC6163] Lee, Y., Bernstein, G., and W. Imajuku, "Framework for 1300 GMPLS and Path Computation Element (PCE) Control of 1301 Wavelength Switched Optical Networks (WSONs)", RFC 6163, 1302 April 2011. 1304 [RFC6566] Lee, Y., Bernstein, G., Li, D., and G. Martinelli, "A 1305 Framework for the Control of Wavelength Switched Optical 1306 Networks (WSONs) with Impairments", RFC 6566, March 2012. 1308 [SWCAP-UPDT] 1309 F.Zhang, D.Li, H.Li, S.Belotti, D.Ceccarelli, "Framework 1310 for GMPLS and PCE Control of G.709 Optical Transport 1311 networks, work in progress 1312 draft-ietf-ccamp-gmpls-g709-framework-13", June 2013. 1314 Authors' Addresses 1316 Daniele Ceccarelli (editor) 1317 Ericsson 1318 Via E.Melen 77 1319 Genova - Erzelli 1320 Italy 1322 Email: daniele.ceccarelli@ericsson.com 1324 Fatai Zhang 1325 Huawei Technologies 1326 F3-5-B R&D Center, Huawei Base 1327 Shenzhen 518129 P.R.China Bantian, Longgang District 1328 Phone: +86-755-28972912 1330 Email: zhangfatai@huawei.com 1332 Sergio Belotti 1333 Alcatel-Lucent 1334 Via Trento, 30 1335 Vimercate 1336 Italy 1338 Email: sergio.belotti@alcatel-lucent.com 1339 Rajan Rao 1340 Infinera Corporation 1341 140, Caspian CT. 1342 Sunnyvale, CA-94089 1343 USA 1345 Email: rrao@infinera.com 1347 John E Drake 1348 Juniper 1350 Email: jdrake@juniper.net