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