idnits 2.17.1 draft-ietf-ccamp-flexible-grid-ospf-ext-06.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 (September 23, 2016) is 2771 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) -- Possible downref: Non-RFC (?) normative reference: ref. 'G.694.1' Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 CCAMP Working Group Xian Zhang 2 Internet-Draft Haomian Zheng 3 Intended status: Standards Track Huawei 4 Ramon Casellas 5 CTTC 6 O. Gonzalez de Dios 7 Telefonica 8 D. Ceccarelli 9 Ericsson 10 Expires: March 23, 2017 September 23, 2016 12 GMPLS OSPF-TE Extensions in support of Flexi-grid DWDM networks 14 draft-ietf-ccamp-flexible-grid-ospf-ext-06.txt 16 Abstract 18 This memo describes the OSPF-TE extensions in support of GMPLS 19 control of networks that include devices that use the new flexible 20 optical grid. 22 Status of this Memo 24 This Internet-Draft is submitted to IETF in full conformance with 25 the provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF), its areas, and its working groups. Note that 29 other groups may also distribute working documents as Internet- 30 Drafts. 32 Internet-Drafts are draft documents valid for a maximum of six 33 months and may be updated, replaced, or obsoleted by other 34 documents at any time. It is inappropriate to use Internet-Drafts 35 as reference material or to cite them other than as "work in 36 progress." 38 The list of current Internet-Drafts can be accessed at 39 http://www.ietf.org/ietf/1id-abstracts.txt. 41 The list of Internet-Draft Shadow Directories can be accessed at 42 http://www.ietf.org/shadow.html. 44 This Internet-Draft will expire on March 23, 2017. 46 Copyright Notice 47 Copyright (c) 2016 IETF Trust and the persons identified as the 48 document authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal 51 Provisions Relating to IETF Documents 52 (http://trustee.ietf.org/license-info) in effect on the date of 53 publication of this document. Please review these documents 54 carefully, as they describe your rights and restrictions with 55 respect to this document. Code Components extracted from this 56 document must include Simplified BSD License text as described in 57 Section 4.e of the Trust Legal Provisions and are provided without 58 warranty as described in the Simplified BSD License. 60 Table of Contents 62 1. Introduction ................................................. 2 63 2. Terminology .................................................. 3 64 2.1. Conventions Used in this Document ....................... 3 65 3. Requirements for Flexi-grid Routing .......................... 3 66 3.1. Available Frequency Ranges .............................. 4 67 3.2. Application Compliance Considerations ................... 5 68 3.3. Comparison with Fixed-grid DWDM Links ................... 6 69 4. Extensions ................................................... 7 70 4.1. ISCD Extensions for Flexi-grid .......................... 7 71 4.1.1. Switching Capability Specific Information (SCSI).... 8 72 4.1.2. An SCSI Example ................................... 10 73 4.2. Extensions to Port Label Restriction sub-TLV ........... 12 74 5. IANA Considerations ......................................... 13 75 5.1. New Switching Type ..................................... 13 76 5.2. New Sub-TLV ............................................ 13 77 6. Implementation Status ....................................... 14 78 6.1. Centre Tecnologic de Telecomunicacions de Catalunya (CTTC)14 79 7. Acknowledgments ............................................. 15 80 8. Security Considerations ..................................... 15 81 9. Contributors' Addresses ..................................... 15 82 10. References ................................................ 16 83 10.1. Normative References .................................. 16 84 10.2. Informative References ................................ 16 85 Authors' Addresses ............................................ 17 87 1. Introduction 89 [G.694.1] defines the Dense Wavelength Division Multiplexing (DWDM) 90 frequency grids for Wavelength Division Multiplexing (WDM) 91 applications. A frequency grid is a reference set of frequencies 92 used to denote allowed nominal central frequencies that may be used 93 for defining applications. The channel spacing is the frequency 94 spacing between two allowed nominal central frequencies. All of the 95 wavelengths on a fiber should use different central frequencies and 96 occupy a fixed bandwidth of frequency. 98 Fixed grid channel spacing is selected from 12.5 GHz, 25 GHz, 50 GHz, 99 100 GHz and integer multiples of 100 GHz. But [G.694.1] also 100 defines "flexible grids", also known as "flexi-grid". The terms 101 "frequency slot" (i.e., the frequency range allocated to a specific 102 channel and unavailable to other channels within a flexible grid) 103 and "slot width" (i.e., the full width of a frequency slot in a 104 flexible grid) are used to define a flexible grid. 106 [RFC7698] defines a framework and the associated control plane 107 requirements for the GMPLS based control of flexi-grid DWDM networks. 109 [RFC6163] provides a framework for GMPLS and Path Computation 110 Element (PCE) control of Wavelength Switched Optical Networks 111 (WSONs), and [RFC7688] defines the requirements and OSPF-TE 112 extensions in support of GMPLS control of a WSON. 114 [RFC7792] describes requirements and protocol extensions for 115 signaling to set up LSPs in networks that support the flexi-grid, 116 and this document complements [RFC7792] by describing the 117 requirement and extensions for OSPF-TE routing in a flexi-grid 118 network. 120 This draft compliments the efforts to provide extensions to Open 121 Short Path First (OSPF) Traffic-Engineering (TE) protocol so as to 122 support GMPLS control of flexi-grid networks. 124 2. Terminology 126 For terminology related to flexi-grid, please consult [RFC7698] and 127 [G.694.1]. 129 2.1. Conventions Used in this Document 131 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 132 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 133 document are to be interpreted as described in RFC-2119 [RFC2119]. 135 3. Requirements for Flexi-grid Routing 137 The architecture for establishing LSPs in a Spectrum Switched 138 optical Network (SSON) is described in [RFC7698]. 140 A flexi-grid LSP occupies a specific frequency slot, i.e. a range of 141 frequencies. The process of computing a route and the allocation of 142 a frequency slot is referred to as RSA (Routing and Spectrum 143 Assignment). [RFC7698] describes three types of architectural 144 approaches to RSA: combined RSA; separated RSA; and distributed SA. 145 The first two approaches among them could be called "centralized SA" 146 because the spectrum (frequency slot) assignment is performed by a 147 single entity before the signaling procedure. 149 In the case of centralized SA, the assigned frequency slot is 150 specified in the RSVP-TE Path message during the signaling process. 151 In the case of distributed SA, only the requested slot width of the 152 flexi-grid LSP is specified in the Path message, allowing the 153 involved network elements to select the frequency slot to be used. 155 If the capability of switching or converting the whole optical 156 spectrum allocated to an optical spectrum LSP is not available at 157 nodes along the path of the LSP, the LSP is subject to the Optical 158 "Spectrum Continuity Constraint", as described in [RFC7698]. 160 The remainder of this section states the additional extensions on 161 the routing protocols in a flexi-grid network. That is, the 162 additional information that must be collected and passed between 163 nodes in the network by the routing protocols in order to enable 164 correct path computation and signaling in support of LSPs within the 165 network. 167 3.1. Available Frequency Ranges 169 In the case of flexi-grids, the central frequency steps from 193.1 170 THz with 6.25 GHz granularity. The calculation method of central 171 frequency and the frequency slot width of a frequency slot are 172 defined in [G.694.1], i.e., by using nominal central frequency n and 173 the slot width m. 175 On a DWDM link, the allocated or in-use frequency slots must not 176 overlap with each other. However, the border frequencies of two 177 frequency slots may be the same frequency, i.e., the highest 178 frequency of a frequency slot may be the lowest frequency of the 179 next frequency slot. 181 Frequency Slot 1 Frequency Slot 2 182 +-----------+-----------------------+ 183 | | | 184 -9 -8 -7 -6 -5 -4 -3 -2 -1 0 1 2 3 4 5 6 7 8 9 10 11 185 ...+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--... 186 ------------ ------------------------ 187 ^ ^ 188 Central F = 193.1THz Central F = 193.1375 THz 189 Slot width = 25 GHz Slot width = 50 GHz 191 Figure 1 - Two Frequency Slots on a Link 193 Figure 1 shows two adjacent frequency slots on a link. The highest 194 frequency of frequency slot 1 denoted by n=2 is the lowest frequency 195 of slot 2. In this example, it means that the frequency range from 196 n=-2 to n=10 is unavailable to other flexi-grid LSPs. Available 197 central frequencies are advertised for m=1, which means that for an 198 available central frequency n, the frequency slot from central 199 frequency n-1 to central frequency n+1 is available. 201 Hence, in order to clearly show which LSPs can be supported and what 202 frequency slots are unavailable, the available frequency ranges MUST 203 be advertised by the routing protocol for the flexi-grid DWDM links. 204 A set of non-overlapping available frequency ranges MUST be 205 disseminated in order to allow efficient resource management of 206 flexi-grid DWDM links and RSA procedures which are described in 207 Section 4.8 of [RFC7698]. 209 3.2. Application Compliance Considerations 211 As described in [G.694.1], devices or applications that make use of 212 the flexi-grid may not be capable of supporting every possible slot 213 width or position (i.e., central frequency). In other words, 214 applications or implementations may be defined where only a subset 215 of the possible slot widths and positions are required to be 216 supported. 218 For example, an application could be defined where the nominal 219 central frequency granularity is 12.5 GHz (by only requiring values 220 of n that are even) and that only requires slot widths as a multiple 221 of 25 GHz (by only requiring values of m that are even). 223 Hence, in order to support all possible applications and 224 implementations the following information should be advertised for a 225 flexi-grid DWDM link: 227 o Channel Spacing (C.S.): as defined in [RFC7699] for flexi-grid, 228 is set to 5 to denote 6.25GHz. 230 o Central frequency granularity: a multiplier of C.S.. 232 o Slot width granularity: a multiplier of 2*C.S.. 234 o Slot width range: two multipliers of the slot width granularity, 235 each indicate the minimal and maximal slot width supported by a 236 port respectively. 238 The combination of slot width range and slot width granularity can 239 be used to determine the slot widths set supported by a port. 241 3.3. Comparison with Fixed-grid DWDM Links 243 In the case of fixed-grid DWDM links, each wavelength has a pre- 244 defined central frequency and each wavelength maps to a pre-defined 245 central frequency and the usable frequency range is implicit by the 246 channel spacing. All the wavelengths on a DWDM link can be 247 identified with an identifier that mainly convey its central 248 frequency as the label defined in [RFC6205], and the status of the 249 wavelengths (available or not) can be advertised through a routing 250 protocol. 252 Figure 2 shows a link that supports a fixed-grid with 50 GHz channel 253 spacing. The central frequencies of the wavelengths are pre-defined 254 by values of "n" and each wavelength occupies a fixed 50 GHz 255 frequency range as described in [G.694.1]. 257 W(-2) | W(-1) | W(0) | W(1) | W(2) | 258 ...---------+-----------+-----------+-----------+-----------+----... 259 | 50 GHz | 50 GHz | 50 GHz | 50 GHz | 261 n=-2 n=-1 n=0 n=1 n=2 262 ...---+-----------+-----------+-----------+-----------+----------... 263 ^ 264 Central F = 193.1THz 266 Figure 2 - A Link Supports Fixed Wavelengths with 50 GHz Channel 267 Spacing 269 Unlike the fixed-grid DWDM links, on a flexi-grid DWDM link the slot 270 width of the frequency slot is flexible as described in section 3.1. 271 That is, the value of m in the following formula [G.694.1] is 272 uncertain before a frequency slot is actually allocated for a flexi- 273 grid LSP. 275 Slot Width (GHz) = 12.5GHz * m 277 For this reason, the available frequency slot/ranges need to be 278 advertised for a flexi-grid DWDM link instead of the specific 279 "wavelengths" points that are sufficient for a fixed-grid link. 280 Moreover, thus advertisement is represented by the combination of 281 Central Frequency Granularity and Slot Width Granularity. 283 4. Extensions 285 As described in [RFC7698], the network connectivity topology 286 constructed by the links/nodes and node capabilities are the same as 287 for WSON, and can be advertised by the GMPLS routing protocols 288 (refer to section 6.2 of [RFC6163]). In the flexi-grid case, the 289 available frequency ranges instead of the specific "wavelengths" are 290 advertised for the link. This section defines the GMPLS OSPF-TE 291 extensions in support of advertising the available frequency ranges 292 for flexi-grid DWDM links. 294 4.1. ISCD Extensions for Flexi-grid 296 Value Type 298 ----- ---- 300 152 (TBA by IANA) Flexi-Grid-LSC 302 Switching Capability and Encoding values MUST be used as follows: 304 Switching Capability = Flexi-Grid-LSC 306 Encoding Type = lambda [as defined in RFC3471] 308 When Switching Capability and Encoding fields are set to values as 309 stated above, the Interface Switching Capability Descriptor MUST be 310 interpreted as in [RFC4203] with the optional inclusion of one or 311 more Switching Capability Specific Information sub-TLVs. 313 As the "Max LSP Bandwidth at priority x" (x from 0 to 7) fields in 314 the generic part of the Interface Switching Capability Descriptor 315 [RFC4203] are not meaningful for flexi-grid DWDM links, the values 316 of these fields MUST be set to zero and MUST be ignored. The 317 Switching Capability Specific Information (SCSI) as defined below 318 provides the corresponding information for flexi-grid DWDM links. 320 4.1.1. Switching Capability Specific Information (SCSI) 322 The technology specific part of the Flexi-grid ISCD should include 323 the available frequency spectrum resource as well as the max slot 324 widths per priority information. The format of this flex-grid SCSI, 325 the frequency available bitmap TLV, is depicted in the following 326 figure: 328 0 1 2 3 329 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 330 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 331 | Type = 1 | Length | 332 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 333 | Priority | Reserved | 334 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 335 | Max Slot Width at Priority 0 | ... ~ 336 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 337 ~ Max Slot Width at Priority 7 | Unreserved padding | 338 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 339 | C.S. | Starting n | No. of Effective. Bits| 340 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 341 | Bit Map ... ~ 342 ~ ... | padding bits ~ 343 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 345 Type (16 bits): The type of this sub-TLV and is set to 1. 347 Length (16 bits): The length of the value field of this sub-TLV. 349 Priority (8 bits): A bitmap used to indicate which priorities 350 are being advertised. The bitmap is in ascending order, with the 351 leftmost bit representing priority level 0 (i.e., the highest) and 352 the rightmost bit representing priority level 7 (i.e., the 353 lowest). A bit MUST be set (1) corresponding to each priority 354 represented in the sub-TLV, and MUST NOT be set (0) when the 355 corresponding priority is not represented. At least one priority 356 level MUST be advertised that, unless overridden by local policy, 357 SHALL be at priority level 0. 359 Max Slot Width (16 bits): This field indicates maximal frequency 360 slot width supported at a particular priority level. This field 361 MUST be set to max frequency slot width supported in the unit of 362 2*C.S., for a particular priority level. One field MUST be present 363 for each bit set in the Priority field, and is ordered to match the 364 Priority field. Fields MUST NOT be present for priority levels that 365 are not indicated in the Priority field. 367 Unreserved Padding (16 bits): The Padding field is used to 368 ensure the 32 bit alignment of Max Slot Width fields. When 369 present the Unreserved Padding field is 16 bits (2 byte) long. 370 When the number of priorities is odd, the Unreserved Padding field 371 MUST be included. When the number of priorities is even, the 372 Unreserved Padding MUST be omitted. 374 C.S. (4 bits): As defined in [RFC7699] and it is currently set to 5. 376 Starting n (16 bits): as defined in [RFC7699] and this value denotes 377 the starting nominal central frequency point of the frequency 378 availability bitmap sub-TLV. 380 Number of Effective Bits (12 bits): Indicates the number of 381 effective bits in the Bit Map field. 383 Bit Map (variable): Indicates whether a basic frequency slot, 384 characterized by a nominal central frequency and a fixed m value of 385 1, is available or not for flexi-grid LSP setup. The first nominal 386 central frequency is the value of starting n and with the subsequent 387 ones implied by the position in the bitmap. Note that when setting 388 to 1, it means that the corresponding central frequency is available 389 for a flexi-grid LSP with m=1; and when setting to 0, it means the 390 corresponding central frequency is unavailable. Note that a 391 centralized SA process will need to extend this to high values of m 392 by checking a sufficient large number of consecutive basic frequency 393 slots that are available. 395 Padding Bits (variable): Padded after the Bit Map to make it a 396 multiple of four bytes if necessary. Padding bits MUST be set to 0 397 and MUST be ignored on receipt. 399 The Reserved field MUST be set to zero on transmission and SHOULD be 400 ignored on receipt. 402 The starting n MAY be set to the lowest possible nominal central 403 frequency supported by the link. An example is provided in section 404 4.1.2. 406 4.1.2. An SCSI Example 408 Figure 3 shows an example of the available frequency spectrum 409 resource of a flexi-grid DWDM link. 411 -9 -8 -7 -6 -5 -4 -3 -2 -1 0 1 2 3 4 5 6 7 8 9 10 11 412 ...+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--... 413 |--Available Frequency Range--| 415 Figure 3 - Flexi-grid DWDM Link Example 417 The symbol "+" represents the allowed nominal central frequency. The 418 symbol "--" represents a central frequency granularity of 6.25 GHz, 419 as currently be standardized in [G.694.1]. The number on the top of 420 the line represents the "n" in the frequency calculation formula 421 (193.1 + n * 0.00625). The nominal central frequency is 193.1 THz 422 when n equals zero. 424 In this example, it is assumed that the lowest nominal central 425 frequency supported is n= -9 and the highest is n=11. Note they 426 cannot be used as a nominal central frequency for setting up a LSP, 427 but merely as the way to express the supported frequency range. 428 Using the encoding defined in Section 4.1.1, the relevant fields to 429 express the frequency resource availability can be filled as below: 431 0 1 2 3 432 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 433 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 434 | Type = 1 | Length | 435 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 436 | Priority | Reserved | 437 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 438 | Max Slot Width at Priority 0 | ... ~ 439 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 440 ~ Max Slot Width at Priority 7 | Unreserved padding | 441 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 442 | 5 | Starting n (-9) | No. of Effec. Bits(21)| 443 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 444 |0|0|0|0|0|0|0|0|1|1|1|1|1|1|1|1|1|0|0|0|0| padding bits (0s) | 445 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 447 In the above example, the starting n is selected to be the lowest 448 nominal central frequency, i.e. -9. It is observed from the bit map 449 that n = -1 to 7 can be used to set up LSPs. Note other starting n 450 values can be chosen to represent the bit map, for example, the 451 first available nominal central frequency (a.k.a., the first 452 available basic frequency slot) can be chosen and the SCSI will be 453 expressed as the following: 455 0 1 2 3 456 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 457 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 458 | Type = 1 | Length | 459 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 460 | Priority | Reserved | 461 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 462 | Max Slot Width at Priority 0 | ... ~ 463 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 464 ~ Max Slot Width at Priority 7 | Unreserved padding | 465 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 466 | 5 | Starting n (-1) | No. of Effec. Bits(9)| 467 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 468 |1|1|1|1|1|1|1|1|1| padding bits (0s) | 469 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 471 This denotes that other than the advertised available nominal 472 central frequencies, the other nominal central frequencies within 473 the whole frequency range supported by the link are not available 474 for flexi-grid LSP set up. 476 If a LSP with slot width (m) equal to 1 is set up using this link, 477 say using n= -1, then the SCSI information is updated to be the 478 following: 480 0 1 2 3 481 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 482 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 483 | Type = 1 | Length | 484 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 485 | Priority | Reserved | 486 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 487 | Max Slot Width at Priority 0 | ... ~ 488 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 489 ~ Max Slot Width at Priority 7 | Unreserved padding | 490 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 491 | 5 | Starting n (-1) | No. of Effec. Bits(9)| 492 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 493 |0|0|1|1|1|1|1|1|1| padding bits (0s) | 494 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 496 4.2. Extensions to Port Label Restriction sub-TLV 498 As described in Section 3.2, a port that supports flexi-grid may 499 support only a restricted subset of the full flexible grid. The 500 Port Label Restriction sub-TLV is defined in [RFC7579]. It can be 501 used to describe the label restrictions on a port and is carried in 502 the top-level Link TLV as specified in [RFC7580]. A new restriction 503 type, the flexi-grid Restriction Type, is defined here to specify 504 the restrictions on a port to support flexi-grid. 506 0 1 2 3 507 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 508 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 509 | MatrixID | RstType = 5 | Switching Cap | Encoding | 510 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 511 | C.S. | C.F.G | S.W.G | Reserved | 512 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 513 | Min Slot Width | Reserved | 514 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 516 MatrixID (8 bits): As defined in [RFC7579]. 518 RstType (Restriction Type, 8 bits): Takes the value of 5 to indicate 519 the restrictions on a port to support flexi-grid. 521 Switching Cap (Switching Capability, 8 bits): As defined in 522 [RFC7579], MUST be consistent with the one specified in ISCD as 523 described in Section 4.1. 525 Encoding (8 bits): As defined in [RFC7579], must be consistent with 526 the one specified in ISCD as described in Section 4.1. 528 C.S. (4 bits): As defined in [RFC7699] and for flexi-grid is 5 to 529 denote 6.25GHz. 531 C.F.G (Central Frequency Granularity, 8 bits): A positive integer. 532 Its value indicates the multiple of C.S., in terms of central 533 frequency granularity. 535 S.W.G (Slot Width Granularity, 8 bits): A positive integer. Its 536 value indicates the multiple of 2*C.S., in terms of slot width 537 granularity. 539 Min Slot Width (16 bits): A positive integer. Its value indicates 540 the multiple of 2*C.S. (GHz), in terms of the supported minimal slot 541 width. 543 The Reserved field MUST be set to zero on transmission and SHOULD be 544 ignored on receipt. 546 5. IANA Considerations 548 5.1. New Switching Type 550 Upon approval of this document, IANA will make the assignment in the 551 "Switching Types" section of the "GMPLS Signaling Parameters" 552 registry located at http://www.iana.org/assignments/gmpls-sig- 553 parameters: 555 Value Name Reference 557 --------- -------------------------- ---------- 559 152 (*) Flexi-Grid-LSC [This.I-D] 561 (*) Suggested value 563 5.2. New Sub-TLV 565 This document defines one new sub-TLV that are carried in the 566 Interface Switching Capability Descriptors [RFC4203] with Signal 567 Type Flexi-Grid-LSC. 569 Upon approval of this document, IANA will create and maintain a new 570 sub-registry, the "Types for sub-TLVs of Flexi-Grid-LSC SCSI (Switch 571 Capability-Specific Information)" registry under the "Open Shortest 572 Path First (OSPF) Traffic Engineering TLVs" registry, see 573 http://www.iana.org/assignments/ospf-traffic-eng-tlvs/ospf-traffic- 574 eng-tlvs.xml, with the sub-TLV types as follows: 576 This document defines new sub-TLV types as follows: 578 Value Sub-TLV Reference 579 --------- -------------------------- ---------- 580 0 Reserved [This.I-D] 581 1 Frequency availability bitmap [This.I-D] 583 6. Implementation Status 585 [RFC Editor Note: Please remove this entire section prior to 586 publication as an RFC.] 588 This section records the status of known implementations of the 589 protocol defined by this specification at the time of posting of 590 this Internet-Draft, and is based on a proposal described in RFC 591 7942. The description of implementations in this section 592 is intended to assist the IETF in its decision processes in 593 progressing drafts to RFCs. Please note that the listing of any 594 individual implementation here does not imply endorsement by the 595 IETF. Furthermore, no effort has been spent to verify the 596 information presented here that was supplied by IETF contributors. 597 This is not intended as, and must not be construed to be, a catalog 598 of available implementations or their features. Readers are advised 599 to note that other implementations may exist. 601 According to RFC 7942, "this will allow reviewers and working groups 602 to assign due consideration to documents that have the benefit of 603 running code, which may serve as evidence of valuable 604 experimentation and feedback that have made the implemented 605 protocols more mature." It is up to the individual working groups to 606 use this information as they see fit. 608 6.1. Centre Tecnologic de Telecomunicacions de Catalunya (CTTC) 610 Organization Responsible for the Implementation: CTTC - Centre 611 Tecnologic de Telecomunicacions de Catalunya (CTTC), Optical 612 Networks and Systems Department, http://wikiona.cttc.es. 614 Implementation Name and Details: ADRENALINE testbed, 615 http://networks.cttc.es/experimental-testbeds/ 617 Brief Description: Experimental testbed implementation of 618 GMPLS/PCE control plane. 620 Level of Maturity: Implemented as extensions to a mature 621 GMLPS/PCE control plane. It is limited to research / prototyping 622 stages but it has been used successfully for more than the last five 623 years. 625 Coverage: Support for the 64 bit label [RFC7699] for flexi-grid 626 as described in this document, with available label set encoded as 627 bitmap. 629 It is expected that this implementation will evolve to follow the 630 evolution of this document. 632 Licensing: Proprietary 634 Implementation Experience: Implementation of this document 635 reports no issues. General implementation experience has been 636 reported in a number of journal papers. Contact Ramon Casellas for 637 more information or see http://networks.cttc.es/publications/? 638 search=GMPLS&research_area=optical-networks-systems 640 Contact Information: Ramon Casellas: ramon.casellas@cttc.es 642 Interoperability: No report. 644 7. Acknowledgments 646 This work was supported in part by the FP-7 IDEALIST project under 647 grant agreement number 317999. 649 This work was supported in part by NSFC Project 61201260. 651 8. Security Considerations 653 This document extends [RFC4203] and [RFC7580] to carry flex-grid 654 specific information in OSPF Opaque LSAs. This document does not 655 introduce any further security issues other than those discussed in 656 [RFC3630], [RFC4203]. To be more specific, the security mechanisms 657 described in [RFC2328] which apply to Opaque LSAs carried in OSPF 658 still apply. An analysis of the OSPF security is provided in 659 [RFC6863] and applies to the extensions to OSPF in this document as 660 well. 662 9. Contributors' Addresses 664 Adrian Farrel 665 Old Dog Consulting 666 Email: adrian@olddog.co.uk 668 Fatai Zhang 669 Huawei Technologies 670 Email: zhangfatai@huawei.com 671 Lei Wang, 672 Beijing University of Post and Telecommunications 673 Email: wang.lei@bupt.edu.cn 675 Guoying Zhang, 676 China Academy of Telecom Research 677 Email: zhangguoying@ritt.cn 679 10. References 681 10.1. Normative References 683 [RFC2119] S. Bradner, "Key words for use in RFCs to indicate 684 requirements levels", RFC 2119, March 1997. 686 [G.694.1] ITU-T Recommendation G.694.1 (revision 2), "Spectral grids 687 for WDM applications: DWDM frequency grid", February 2012. 689 [RFC4203] K. Kompella, Y. Rekhter, " OSPF Extensions in Support of 690 Generalized Multi-Protocol Label Switching (GMPLS)", 691 October 2005. 693 [RFC7579] Bernstein, G., Lee, Y., Li, D., and W. Imajuku, "General 694 Network Element Constraint Encoding for GMPLS Controlled 695 Networks", RFC 7579, June 2015. 697 [RFC7580] F. Zhang, Y. Lee, J. Han, G. Bernstein and Y. Xu, "OSPF-TE 698 Extensions for General Network Element Constraints ", RFC 699 7580, June 2015. 701 [RFC6205] T. Otani and D. Li, "Generalized Labels for Lambda-Switch- 702 Capable (LSC) Label Switching Routers", RFC 6205, March 703 2011. 705 [RFC7699] King, D., Farrel, A. and Y. Li, "Generalized Labels for 706 the Flexi-Grid in Lambda Switch Capable (LSC) Label 707 Switching Routers", RFC7699, September 2015. 709 10.2. Informative References 711 [RFC6163] Y. Lee, G. Bernstein and W. Imajuku, "Framework for GMPLS 712 and Path Computation Element (PCE) Control of Wavelength 713 Switched Optical Networks (WSONs)", RFC 6163, April 2011. 715 [RFC7792] F.Zhang et al, "RSVP-TE Signaling Extensions in support of 716 Flexible-grid", RFC 7792, November 2015. 718 [RFC7698] Gonzalez de Dios, O., Casellas R., Zhang, F., Fu, X., 719 Ceccarelli, D., and I. Hussain, "Framework and 720 Requirements for GMPLS based control of Flexi-grid DWDM 721 networks', RFC 7698, August 2015. 723 [RFC7688] Y. Lee and G. Bernstein, "GMPLS OSPF Enhancement for 724 Signal and Network Element Compatibility for Wavelength 725 Switched Optical Networks ", RFC7688, August 2015. 727 [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998. 729 [RFC3630] D. Katz, K. Kompella, D. Yeung, " Traffic Engineering 730 (TE) Extensions to OSPF Version 2", September 2003. 732 [RFC6863] Hartman, S. and D. Zhang, "Analysis of OSPF Security 733 According to the Keying and Authentication for Routing 734 Protocols (KARP) Design Guide", RFC 6863, March 2013. 736 Authors' Addresses 738 Xian Zhang 739 Huawei Technologies 740 Email: zhang.xian@huawei.com 742 Haomian Zheng 743 Huawei Technologies 744 Email: zhenghaomian@huawei.com 746 Ramon Casellas, Ph.D. 747 CTTC 748 Spain 749 Phone: +34 936452916 750 Email: ramon.casellas@cttc.es 752 Oscar Gonzalez de Dios 753 Telefonica Investigacion y Desarrollo 754 Emilio Vargas 6 755 Madrid, 28045 756 Spain 757 Phone: +34 913374013 758 Email: ogondio@tid.es 760 Daniele Ceccarelli 761 Ericsson 762 Via A. Negrone 1/A 763 Genova - Sestri Ponente 764 Italy 765 Email: daniele.ceccarelli@ericsson.com