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