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