idnits 2.17.00 (12 Aug 2021) /tmp/idnits47725/draft-dhillon-ccamp-flexgrid-ospfte-ext-00.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 document seems to lack an Introduction section. (A line matching the expected section header was found, but with an unexpected indentation: ' 1. Introduction' ) ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 5. Security Considerations' ) ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) (A line matching the expected section header was found, but with an unexpected indentation: ' 6. IANA Considerations' ) ** There is 1 instance of too long lines in the document, the longest one being 1 character in excess of 72. ** The abstract seems to contain references ([2], [3], [11], [RFC4203], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? RFC 2119 keyword, line 130: '... Encoding values MUST be used as follo...' RFC 2119 keyword, line 257: '... o Padding MUST be used to align...' RFC 2119 keyword, line 326: '...advertising node MUST also set Number ...' RFC 2119 keyword, line 331: '...ng one or more priorities MUST set the...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 5, 2014) is 2999 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 section? 'RFC4203' on line 16 looks like a reference -- Missing reference section? '3' on line 411 looks like a reference -- Missing reference section? '1' on line 403 looks like a reference -- Missing reference section? '2' on line 407 looks like a reference -- Missing reference section? '11' on line 442 looks like a reference -- Missing reference section? '10' on line 439 looks like a reference -- Missing reference section? 'RFC2119' on line 398 looks like a reference -- Missing reference section? 'RFC 4203' on line 123 looks like a reference -- Missing reference section? 'FLEX-GRID' on line 439 looks like a reference -- Missing reference section? '9' on line 434 looks like a reference -- Missing reference section? '4' on line 415 looks like a reference -- Missing reference section? '5' on line 419 looks like a reference -- Missing reference section? '6' on line 423 looks like a reference -- Missing reference section? '7' on line 427 looks like a reference -- Missing reference section? '8' on line 430 looks like a reference Summary: 6 errors (**), 0 flaws (~~), 1 warning (==), 16 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Iftekhar Hussain 2 Rajan Rao 3 Marco Sosa 4 Infinera 5 Internet Draft Abinder Dhillon 6 Fujitsu 7 Intended status: Standard Track March 5, 2014 8 Expires: Sept 04, 2014 10 TE extensions to OSPF for GMPLS control of Flex-Grid Networks 11 draft-dhillon-ccamp-flexgrid-ospfte-ext-00.txt 13 Abstract 15 This document specifies the extension to TELINK LSA of OSPF routing 16 protocol [RFC4203] [3] in support of GMPLS [1] for flex-grid 17 networks [2]. 19 This draft is a renamed version of ''draft-dhillon-ccamp-super- 20 channel-ospfte-ext-06.txt'' [11]. To align with ITU terminology, 21 references to super-channel have been removed in the title & other 22 parts of the document. 24 Status of this Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF), its areas, and its working groups. Note that 31 other groups may also distribute working documents as Internet- 32 Drafts. 34 Internet-Drafts are draft documents valid for a maximum of six 35 months and may be updated, replaced, or obsoleted by other documents 36 at any time. It is inappropriate to use Internet-Drafts as 37 reference material or to cite them other than as "work in progress." 39 The list of current Internet-Drafts can be accessed at 40 http://www.ietf.org/ietf/1id-abstracts.txt 42 The list of Internet-Draft Shadow Directories can be accessed at 43 http://www.ietf.org/shadow.html 45 This Internet-Draft will expire on Sept 45, 2014. 47 Copyright Notice 49 Copyright (c) 2012 IETF Trust and the persons identified as the 50 document authors. All rights reserved. 52 This document is subject to BCP 78 and the IETF Trust's Legal 53 Provisions Relating to IETF Documents 54 (http://trustee.ietf.org/license-info) in effect on the date of 55 publication of this document. Please review these documents 56 carefully, as they describe your rights and restrictions with 57 respect to this document. Code Components extracted from this 58 document must include Simplified BSD License text as described in 59 Section 4.e of the Trust Legal Provisions and are provided without 60 warranty as described in the Simplified BSD License. 62 Table of Contents 64 1. Introduction...................................................2 65 2. Terminology....................................................3 66 3. Interface Switching Capability Descriptor......................3 67 3.1. Switch Capability Specific Information ....................5 68 3.2. BW sub TLV: Bit Map format................................5 69 3.2.1. Meaning of sub TLV fields............................5 70 3.3. BW sub TLV: List and Rage format..........................7 71 3.3.1. Meaning of sub TLV fields............................7 72 3.4. BW advertisement procedure................................8 73 4. Examples.......................................................8 74 4.1. Example: BW advertisement without any service present.....8 75 4.2. Example: How to use advertise Bandwidth...................9 76 5. Security Considerations.......................................10 77 6. IANA Considerations...........................................10 78 7. References....................................................10 79 7.1. Normative References.....................................10 80 7.2. Informative References...................................10 81 8. Acknowledgments...............................................11 83 1. Introduction 85 To enable scaling of existing transport systems to ultra-high data 86 rates of 1 Tbps and beyond, next generation systems providing ultra- 87 high capacity optical switching capability are currently being 88 developed. To allow efficient allocation of optical spectral 89 bandwidth for such high bit rate systems, International 90 Telecommunication Union Telecommunication Standardization Sector 91 (ITU-T) is extending the G.694.1 grid standard (termed ''Fixed-Grid'') 92 to include flexible grid (termed ''Flex-Grid'') support [10]. 94 This document defines OSPF-TE extensions in support of flex-grid 95 networks. 97 Figure-1 shows a network capable of switching in Flexible-Grid[10]. 98 The physical media/Fiber is modeled as a TE-Link to advertise 99 spectrum (bandwidth) availability. This information is used during 100 Flex-grid LSP[10] creation([2]). This draft defines extensions to 101 ISCD in support of Flexible-Grid. 103 +-------+ +-------+ +-------+ 104 | SC | | SC | | SC | 105 |Switch |.---Link ---> |Switch |<- Link----- ->|Switch | 106 | A | | B | | C | 107 +-------+ +-------+ +-------+ 109 |<-- TE-Link -->| |<-- TE-Link -->| 111 Figure 1: TE-Links 113 2. Terminology 115 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 116 NOT","SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 117 this document are to be interpreted as described in RFC 2119 118 [RFC2119]. 120 3. Interface Switching Capability Descriptor 122 The Interface Switching Capability Descriptor describes switching 123 capability of an interface [RFC 4203]. This document defines a new 124 Switching Capability value for Flex Grid [FLEX-GRID] as follows: 126 Value Type 127 ----- ---- 128 102 (TBA by IANA) Spectrum-Switch-Capable (SSC) 130 Switching Capability and Encoding values MUST be used as follows: 132 Switching Capability = SSC 133 Encoding Type = Lambda [as defined in RFC3471] 135 The Interface Switching Capability Descriptor is a sub-TLV (of type 136 15) of the Link TLV. The length is the length of value field in 137 Octets. The format of the value field is as shown below: 139 0 1 2 3 140 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 141 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 142 | Switching Cap | Encoding | Reserved | 143 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 144 | Max LSP Bandwidth at priority 0 | 145 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 146 | Max LSP Bandwidth at priority 1 | 147 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 148 | Max LSP Bandwidth at priority 2 | 149 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 150 | Max LSP Bandwidth at priority 3 | 151 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 152 | Max LSP Bandwidth at priority 4 | 153 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 154 | Max LSP Bandwidth at priority 5 | 155 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 156 | Max LSP Bandwidth at priority 6 | 157 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 158 | Max LSP Bandwidth at priority 7 | 159 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 160 | Switching Capability-specific information | 161 | (variable) | 162 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 164 Figure 2: ISCD & SCSI 166 Max LSP Bandwidth will be based on Max Slot Width field in BW-sub-TLV 167 (Ref to section 3.1 for details on BW sub-TLV) and the modulation 168 format used. 170 3.1. Switch Capability Specific Information 172 The technology specific part of the ISCD can include a variable number 173 of sub-TLVs. We propose to encode Slice Information in Bandwidth sub- 174 TLVs under SCSI field. The format of BW sub-TLVs is as shown below. 176 [Editor's note: To provide options similar to Label set field defined 177 in [9], we have included 2 variants to advertise slice level 178 information. These are bit-format and list/range format]. 180 3.2. BW sub TLV: Bit Map format 182 The figure below shows format of Type=1 sub-TLV for encoding slice 183 information in bit-map format. This sub-TLV must be repeated for each 184 priority that is supported on the Te-link. 186 0 1 2 3 187 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 188 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 189 | Type=1 | Length | 190 +---------------------------------------------------------------+ 191 |Slice Spacing | Pri | Reserved | 192 +---------------------------------------------------------------+ 193 | N-Start | Num of Slices | 194 +---------------------------------------------------------------+ 195 | Min Slot Width | Max Slot Width | 196 +---------------------------------------------------------------+ 197 | | 198 | Bit-Map showing Available Slices | 199 | (up to 48 bytes) | 200 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 202 Figure 3: Type=1 BW sub TLV in Bit-Map format 204 3.2.1. Meaning of sub TLV fields 206 o Slice Spacing: 8-bit field (S.S) which can take one of the values 207 as shown in table below. 208 o For e.g., the 12.5GHz spacing is specified by setting this 209 field to value 4. 211 +----------+---------+ 212 |S.S. (GHz)| Value | 213 +----------+---------+ 214 | Reserved | 0 | 215 +----------+---------+ 216 | 100 | 1 | 217 +----------+---------+ 218 | 50 | 2 | 219 +----------+---------+ 220 | 25 | 3 | 221 +----------+---------+ 222 | 12.5 | 4 | 223 +----------+---------+ 224 |Future use| 5 - 15 | 225 +----------+---------+ 227 Table 1: Slice Spacing Values 229 o Priority: 3-bit field 230 o 3-bit field to identify one of the 8 priorities for which 231 Slice information (BW) is advertised. 232 o N-Start: 16-bit field 233 o Is a two's complement integer to specify start of the grid 234 o Use center freq formula to determine start of spectrum 235 o Number of slices: 16-bit field 236 o Total number of slices advertised for the link. This includes 237 (available plus consumed). 238 o Minimum Slot Width: 16-bit field 239 o This is a positive integer value 240 o This field is similar to Min LSP BW field. The value in this 241 field is used to determine the smallest frequency slot width 242 that the advertising node can allocate for an LSP. This is 243 defined by the following equation: 244 Smallest Frequency slot width = Slice Spacing * integer value 245 in 'Minimum Slot Width' field 246 o Maximum Slot Width: 16-bit field 247 o This is a positive integer value 248 o This field is used to determine the Maximum contiguous 249 frequency slot width that the advertising node can allocate 250 for an LSP. This is defined by the following equation: 251 Largest Contiguous Frequency slot width = Slice Spacing * 252 integer value in 'Maximum Slot Width' field 253 o Available slices encoded as bit-map 254 o Each bit represents availability of one slice of width 255 identified by S.S field 256 o Zero: Available ; One: occupied 257 o Padding MUST be used to align with 32 bit boundary. 259 3.3. BW sub TLV: List and Rage format 261 The figure below shows format of Type=2 sub-TLV for encoding slice 262 information in list/range format. This sub-TLV must be repeated for 263 each priority that is supported on the Te-Link. 265 0 1 2 3 266 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 267 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 268 | Type=2 | Length | 269 +---------------------------------------------------------------+ 270 |Slice Spacing | Pri | Res | Num of Entries | 271 +---------------------------------------------------------------+ 272 | Min Slot Width | Max Slot Width | 273 +---------------------------------------------------------------+ 274 | N-Start-1 | N-end-1 | 275 +---------------------------------------------------------------+ 276 | N-Start-2 | N-end-2 | 277 +---------------------------------------------------------------+ 278 | More Entries | 279 +---------------------------------------------------------------+ 280 | N-Start-n | N-end-n | 281 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 283 Figure 4: Type=2 BW sub TLV in List/Range format 285 3.3.1. Meaning of sub TLV fields 287 o The meaning of above fields is same as in Type=1 BW-sub-TLV. For 288 details refer to section 3.2.1. 289 o Slice Spacing, 290 o Priority, 291 o Maximum Slot Width & 292 o Minimum Slot Width 293 o Number of Entries: 16-bit field 294 o Is a positive integer value. 295 o Total number of N-start & N-End rows advertised for the link. 296 o N-Start-x: 16-bit field 297 o Is a two's complement integer value (+ve, -ve or zero) to 298 specify start of the grid. 300 o Use center freq formula to determine start of spectrum 302 o N-end-x: 16-bit field 303 o Is a two's complement integer value (+ve, -ve or zero)to 304 specify end of the list/range. 305 o Use center freq formula to determine end of spectrum 307 3.4. BW advertisement procedure 309 This section describes bandwidth advertisement for Te-Links capable 310 SSC. 312 o Optical nodes capable of Spectrum Switching advertise slices of 313 certain width available based on the frequency spectrum supported 314 by the node (e.g. C band, extended C-band). For example, node(s) 315 supporting extended C-band will advertise 384 slices. 316 o The BW advertisement involves an ISCD containing 317 o Slice information in bit-map format (Type=1 BW-sub-TLV) where 318 each bit corresponds to a single slice of width as identified 319 by S.S field. OR 320 o Slice information in list/range format (Type=2 BW-sub-TLV) 321 where each 32-bit entry represents an individual slice or 322 list or range. 323 o The slice position/numbering in Type=1 sub-TLV is identified based 324 on N-start field. The N-start field is derived based on ITU 325 center frequency formula. 326 o The advertising node MUST also set Number of Slices field. 327 o Minimum & Maximum slot width fields are included to allow for any 328 restrictions on the link for carrying Flex Grid LSPs. 329 o The BW advertisement is priority based and up to 8 priority levels 330 are allowed. 331 o The node capable of supporting one or more priorities MUST set the 332 priority field and include BW-sub TLV for each of the priority 333 supported. 335 4. Examples 337 4.1. Example: BW advertisement without any service present 339 Figure 5 shows an example of BW sub-TLV for a te-link which has no 340 service established over it yet. Attributes of BW sub-TLV in the te- 341 link are: 343 o N-start=-142 for extended C-band (2's complement should be 344 included in this field) 345 o Total number of slices available on the link = 384 (based on 346 Slice spacing = 12.5GHz) 347 o Min SW field shows min consumption of 4 Slices per LSP 348 ( =50GHz) 349 o Max SW field shows up to 400GHz BW allowed per LSP (32x12.5GHz) 350 o 48 bytes showing that all 384 slices are available. 352 0 1 2 3 353 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 354 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 355 | Type=1 | Length | 356 +---------------------------------------------------------------+ 357 |S.S = 4(12.5) | Pri | Reserved | 358 +---------------------------------------------------------------+ 359 | N-Start=-142 | Num of Slices=384 | 360 +---------------------------------------------------------------+ 361 | Min Slot Width=4 | Max Slot Width=32 | 362 +---------------------------------------------------------------+ 363 | | 364 | Bit-Map showing info for 384 slice | 365 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 367 Figure 5: Type=1 BW sub-TLV without any service present 369 4.2. Example: How to use advertise Bandwidth 371 Assume user wants to setup Flex Grid LSP over a single Flex-Grid link 372 with BW requirement = 200GHz and transponder fully tunable. 374 o The path computing node performs the following: 375 o Determine the number of slices required for the LSP (200/S.S = 376 16) 377 o Look for contiguous spectrum availability on each link from BW 378 advertisement (both dir) 379 o Look for 16 contiguous bits in the BW advertisement TLV 380 o If available select the link for LSP creation. 381 o Signal for LSP creation. Once LSP is created, update BW 382 available via new advertisement using the same Bandwidth sub- 383 TLV. 385 5. Security Considerations 387 389 6. IANA Considerations 391 IANA needs to assign a new Grid field value to represent ITU-T Flex- 392 Grid. 394 7. References 396 7.1. Normative References 398 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 399 Requirement Levels", BCP 14, RFC 2119, March 1997. 401 7.2. Informative References 403 [1] Berger, L., Ed., "Generalized Multi-Protocol Label Switching 404 (GMPLS) Signaling Functional Description", RFC 3471, January 405 2003 407 [2] Iftekhar H, Abinder, Zhong , Marco , ''Generalized Label for 408 Optical-Channel Assignment on Flexible Grid'', draft-hussain- 409 ccamp-flexgrid-label-0o.txt, March 2014. 411 [3] K. Kompella, Y., " OSPF Extensions in Support of 412 Generalized Multi-Protocol Label Switching (GMPLS)", RFC 4203, 413 Oct 2005 415 [4] Lee, Y., Ed., "Framework for GMPLS and Path Computation 416 Element (PCE) Control of Wavelength Switched Optical Networks 417 (WSONs)", RFC 6163, April 2011 419 [5] M. Jinno et. al., ''Spectrum-Efficient and Scalable Elastic 420 Optical Path Network: Architecture, Benefits and Enabling 421 Technologies'', IEEE Comm. Mag., Nov. 2009, pp. 66-73. 423 [6] S. Chandrasekhar and X. Liu, ''Terabit Super-Channels for High 424 Spectral Efficiency Transmission '',in Proc. ECOC 2010, paper 425 Tu.3.C.5, Torino (Italy), September 2010. 427 [7] ITU-T Recommendation G.694.1, "Spectral grids for WDM 428 applications: DWDM frequency grid", June 2002 430 [8] Oscar G, et al., ''Framework and Requirements for GMPLS based 431 control of Flexi-grid DWDM networks'', draft-ietf-ccamp-flexi- 432 grid-fwk-00, work in progress. 434 [9] G. Bernstein, Y. Lee, D. Li, W. Imajuku, " General Network 435 Element Constraint Encoding for GMPLS Controlled Networks", 436 work in progress: draft-ietf-ccamp-general-constraint-encode- 437 05, May 2011 439 [10] [FLEX-GRID] "ITU-T Recommendation G.694.1, Spectral grids for 440 WDM applications: DWDM frequency grid", November 2012. 442 [11] Previous version of this draft: OSPFTE extension to support 443 GMPLS for Flex Grid: draft-dhillon-ccamp-super-channel- 444 ospfte-ext-06.txt 446 8. Acknowledgments 448 The authors would like to thank Ashok Kunjidhapatham & Mohit Misra for 449 their valuable comments. 451 Authors' Addresses 453 Rajan Rao 454 Infinera 455 140 Caspian Ct., Sunnyvale, CA 94089 456 Email: rrao@infinera.com 458 Iftekhar Hussain 459 Infinera 460 140 Caspian Ct., Sunnyvale, CA 94089 461 Email: ihussain@infinera.com 463 Marco Sosa 464 Infinera 465 140 Caspian Ct., Sunnyvale, CA 94089 466 Email: msosa@infinera.com 468 Abinder Dhillon 469 Fujitsu 470 Richardson, TX 471 Email: Abinder.Dhillon@us.fujitsu.com 473 Contributor's Addresses 475 Biao Lu 476 Email: blu@infinera.com 478 Subhendu Chattopadhyay 479 Email: schattopadhyay@infinera.com 481 Harpreet Uppal 482 Email: harpreet.uppal@infinera.com