idnits 2.17.1 draft-ggalimbe-ccamp-flexigrid-carrier-label-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 abstract seems to contain references ([ITU.G694.1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 13, 2017) is 2594 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- == Unused Reference: 'RFC6163' is defined on line 410, but no explicit reference was found in the text == Unused Reference: 'RFC5920' is defined on line 416, but no explicit reference was found in the text == Unused Reference: 'RFC3945' is defined on line 420, but no explicit reference was found in the text == Unused Reference: 'RFC3473' is defined on line 425, but no explicit reference was found in the text == Unused Reference: 'RFC2119' is defined on line 438, but no explicit reference was found in the text == Unused Reference: 'ITU.G698.2' is defined on line 443, but no explicit reference was found in the text == Unused Reference: 'ITU.G709' is defined on line 454, but no explicit reference was found in the text == Unused Reference: 'ITU.G872' is defined on line 459, but no explicit reference was found in the text == Unused Reference: 'ITU.G874.1' is defined on line 464, but no explicit reference was found in the text == Unused Reference: 'RFC3410' is defined on line 472, but no explicit reference was found in the text == Unused Reference: 'RFC2629' is defined on line 478, but no explicit reference was found in the text == Unused Reference: 'RFC4181' is defined on line 482, but no explicit reference was found in the text -- Obsolete informational reference (is this intentional?): RFC 2629 (Obsoleted by RFC 7749) Summary: 1 error (**), 0 flaws (~~), 13 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force G. Galimberti, Ed. 3 Internet-Draft D. La Fauci 4 Intended status: Experimental Cisco 5 Expires: September 14, 2017 A. Zanardi, Ed. 6 L. Galvagni 7 FBK-CreateNet 8 March 13, 2017 10 Signaling extensions for Media Channel sub-carriers configuration in 11 Spectrum Switched Optical Networks (SSON) in Lambda Switch Capable (LSC) 12 Optical Line Systems. 13 draft-ggalimbe-ccamp-flexigrid-carrier-label-00 15 Abstract 17 This memo defines the signaling extensions for managing Spectrum 18 Switched Optical Network (SSON) parameters shared between the Client 19 and the Network and inside the Network. This document extends the 20 GMPLS Lambda label format in accordance and extending the parameters 21 defined in ITU-T Recommendation G.694.1.[ITU.G694.1] and its 22 extensions. 24 Copyright Notice 26 Copyright (c) 2011 IETF Trust and the persons identified as the 27 document authors. All rights reserved. 29 Status of This Memo 31 This Internet-Draft is submitted in full conformance with the 32 provisions of BCP 78 and BCP 79. 34 Internet-Drafts are working documents of the Internet Engineering 35 Task Force (IETF). Note that other groups may also distribute 36 working documents as Internet-Drafts. The list of current Internet- 37 Drafts is at http://datatracker.ietf.org/drafts/current/. 39 Internet-Drafts are draft documents valid for a maximum of six months 40 and may be updated, replaced, or obsoleted by other documents at any 41 time. It is inappropriate to use Internet-Drafts as reference 42 material or to cite them other than as "work in progress." 44 This Internet-Draft will expire on September 14, 2017. 46 Copyright Notice 48 Copyright (c) 2017 IETF Trust and the persons identified as the 49 document authors. All rights reserved. 51 This document is subject to BCP 78 and the IETF Trust's Legal 52 Provisions Relating to IETF Documents 53 (http://trustee.ietf.org/license-info) in effect on the date of 54 publication of this document. Please review these documents 55 carefully, as they describe your rights and restrictions with respect 56 to this document. Code Components extracted from this document must 57 include Simplified BSD License text as described in Section 4.e of 58 the Trust Legal Provisions and are provided without warranty as 59 described in the Simplified BSD License. 61 Table of Contents 63 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 64 2. Client interface parameters . . . . . . . . . . . . . . . . . 3 65 3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 4 66 4. Signalling Extensions . . . . . . . . . . . . . . . . . . . . 5 67 4.1. New LSP set-up parameters . . . . . . . . . . . . . . . . 5 68 4.2. Extension to LSP set-up reservation . . . . . . . . . . . 6 69 4.3. RSVP Protocol Extensions considerations . . . . . . . . . 8 70 5. Security Considerations . . . . . . . . . . . . . . . . . . . 8 71 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 72 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 9 73 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 74 8.1. Normative References . . . . . . . . . . . . . . . . . . 9 75 8.2. Informative References . . . . . . . . . . . . . . . . . 11 76 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 78 1. Introduction 80 Generalised Multiprotocol Label Switched (GMPLS) is widely used in 81 Wavelength Switched Optical Network (WSON) to support the optical 82 circuits set-up through the signalling between Core Nodes and Edge 83 Nodes. This extension addresses the use cases described by [RFC7698] 84 Ch.3.3 and supports the information, needed by Spectrum Switched 85 Optical Network (SSON), to signal a Media Channel and the associated 86 carriers set request. The new set of parameters is related to the 87 Media Channel and the carrier routed with it and keep the backward 88 compatibility with the WSON signalling. In particular this memo 89 wants do address the use cases where the SSON LSP (the Media Channel 90 in RFC7698) carries multiple carrier (OTSi) containing same Payload. 91 The set of the carriers can be seen as single Logical circuit. This 92 memo can be considered as the extension of [RFC7699] The contents and 93 the parameters reflect the experimental activity on IP over SSON 94 recently done. 96 Figure 1 shows how the multiple carrier are mapped into a Media 97 Channel. A set of parameters must be shared on the UNI to allow the 98 GMPLS to do the proper routing and Spectrum Assignment and decide the 99 carrier position. 101 +------+ +------+ _________ +------+ +------+ 102 | E.N. | | C.N. | / /\ | C.N. | | E.N. | 103 | OTS1| ----- | || | || | ----- |OTS1 | 104 ==| OTS2| ----- | || Media | || | ----- |OTS2 |== 105 ==| OTS3| ----- | || Channel| || | ----- |OTS3 |== 106 | OTS4| ----- | || | || | ----- |OTS4 | 107 | | | ROADM| \________\/ | ROADM| | | 108 +------+ +------+ +------+ +------+ 109 ^ ^ ^ ^ 110 | | | | 111 +---UNI---+ +---UNI---+ 113 E.N. = Edge Node - UNI Client 114 C.N. = Core Node - UNI Network 115 ROADM = Lambda/Spectrum switch 116 Media Channel = the optical circuit 117 OTSi = Carriers belonging to the same Network Media Channel (or 118 Super Channel) 119 UNI = Signallig interface 121 from Fig. 5.1/G.698.2 123 Figure 1: Multi carrier LSP 125 2. Client interface parameters 127 The Edge Node interface can have one or multiple carriers (OTSi). 128 All the carrier have the same characteristics and are provisionable 129 in terms of: 131 Number of subcarriers: 132 This parameter indicates the number of subcarriers available for 133 the super-channel in case the Transceiver can support multiple 134 carrier circuits. 136 Central frequency (see G.694.1 Table 1): 138 This parameter indicates the Central frequency value that Ss and 139 Rs will be set to work (in THz). See the details in Section 6/ 140 G.694.1 or based on "n" and "k" values in case of multicarrier 141 transceivers. 143 Central frequency granularity: 144 This parameter indicates the Central frequency granularity 145 supported by the transceiver, this value is combined with K and n 146 value to calculate the central frequency on the carrier or sub- 147 carriers. 149 Minimum channel spacing: 150 This is the minimum nominal difference in frequency (in GHz) 151 between two adjacent channels (or carriers) depending on the 152 Transceiver characteristics. 154 Bit rate / Baud rate of optical tributary signals: 155 Optical tributary signal bit (for NRZ signals) rate or Symbol (for 156 Multiple bit per symbol) rate . 158 FEC Coding: 159 This parameter indicate what Forward Error Correction (FEC) code 160 is used at Ss and Rs (R/W) (not mentioned in G.698). . 162 Wavelength Range (see G.694.1): [ITU.G694.1] 163 This parameter indicate minimum and maximum wavelength spectrum in 164 a definite wavelength Band (L, C and S). 166 Modulation format: 167 This parameter indicates the list of supported Modulation Formats 168 and the provisioned Modulation Format.. 170 Inter carrier skew: 171 This parameter indicates, in case of multi-carrier transceivers 172 the maximum skew between the sub-carriers supported by the 173 transceiver. 175 Laser Output power: 176 This parameter provisions the Transceiver Output power, it can be 177 either a setting and measured value. 179 3. Use Cases 181 The use cases are described in draft-kdkgall-ccamp-dwdm-if-mng-ctrl- 182 fwk and [RFC7698] 184 4. Signalling Extensions 186 The extension to the RFC7699 includes the parameter listed above. 187 The above parameters could be added also to [RFC4208]. The [RFC6205] 188 parameters remain valid. 190 4.1. New LSP set-up parameters 192 When the E.N. wants to request to the C.N. a new circuit set-up 193 request or the GMPLS want to signal in the SSON network the Optical 194 Interface characteristics the following parameters will be provided 195 to the C.N.: 197 Number of available subcarriers (c): 198 This parameter is an integer. 200 Total bandwidth request: 201 e.g. 200Gb, 400Gb, 1Tb 203 Policy (strict/loose): 204 Strict/loose referred to B/W and subcarrier number. 206 Subcarrier bandwidth tunability: 207 (optional) e.g. 34Ghz, 48GHz. 209 Figure 2: The format of the this sub-object (Type = TBA, Length = 210 TBA) is as follows: 212 0 1 2 3 213 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 214 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 215 |S|B| Number of Carriers | Client bandwidth | 216 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 217 | Subcarrier frequency tunability (optional) | 218 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 220 Sub-Transponder Mod Format: In the Value Field (96 bits) it is 221 specified 222 S strict number of subcarrier (No = 0, Yes = 1) 223 B strict client bandwidth (No = 0, Yes = 1) 224 - Num Carriers 225 - Client bandwidth (100Gb, 150Gb, 200Gb, 400Gb, 1Tb, etc) 226 - Subcarrier frequency tunability (optional) 228 Figure 2: SSON LSP set-up request 230 4.2. Extension to LSP set-up reservation 232 Once the GMPLS has calculated the Media Channel path, the Spectrum 233 Allocation, the Sub-carrier number and frequency, the modulation 234 format, the FEC and the Transmit power, sends back to the E.N. the 235 path set-up confirmation providing the values of the calculated 236 paramenters: 238 Media Channel: 239 (Grid, C.S., Identifier and n). 241 Number of subcarriers: 242 This parameter indicates the number of subcarriers available for 243 the super-channel in case the Transceiver can support multiple 244 carrier Circuits. 246 Central frequency (see G.694.1 Table 1): 247 Grid, Identifiers, central frequency and granularity. 249 Central frequency granularity: 250 This parameter indicates the Central frequency granularity 251 supported by the transceiver, this value is combined with K and n 252 value to calculate the central frequency on the carrier or sub- 253 carriers. 255 Minimum channel spacing: 256 This is the minimum nominal difference in frequency (in GHz) 257 between two adjacent channels (or carriers) depending on the 258 Transceiver characteristics. 260 Bit rate / Baud rate of optical tributary signals: 261 Optical tributary signal bit (for NRZ signals) rate or Symbol (for 262 Multiple bit per symbol) rate. 264 FEC Coding: 265 This parameter indicate what Forward Error Correction (FEC) code 266 is used at Ss and Rs (R/W) (not mentioned in G.698). . 268 Modulation format: 269 This parameter indicates the list of supported Modulation Formats 270 and the provisioned Modulation Format. 272 Inter carrier skew: 273 This parameter indicates, in case of multi-carrier transceivers 274 the maximum skew between the sub-carriers supported by the 275 transceiver. 277 Laser Output power: 279 This parameter provisions the Transceiver Output power, it can be 280 either a setting and measured value. 282 Circuit Path, RRO, etc: 283 All these info are defined in [RFC4208]. 285 Path Error: 286 e.g. no path exist, all the path error defined in [RFC4208]. 288 Figure 3: The format of this sub-object (Type = TBA, Length = TBA) is 289 as follows: 291 0 1 2 3 292 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 293 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 294 |S|I| Modulation ID | FEC | 295 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 296 | baud rate (Symbol Rate) | 297 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 298 |Grid | C.S. | M.C. Identifier | n | 299 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 301 0 1 2 3 302 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 303 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 304 | Grid| carrier Identifier | j | 305 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 306 | k | 307 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 308 | sub-carrier power | 309 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 311 Sub-Transponder Mod Format: 312 - S: standardized format; 313 - I: input / output (1 / 0) 314 - Modulation IDs: BPSK (1), DC DP BSPSK, QPSK, DP QPSK, 8QAM 315 16QAM, 64QAM, etc. 316 - FEC ...... 317 - Symbol Rate: IEEE float in bauds/s 318 - Number of Carriers in the Media channel 319 - Bits/symbol 320 - Sub-carrier Power 321 - Media channel Grid 322 +----------+---------+ 323 | Grid | Value | 324 +----------+---------+ 325 |ITU-T Flex| 3 | 326 +----------+---------+ 328 - C.S. 329 - n Media channel central frequency 330 - Sub carrier identifier field: sub-carrier 331 identifier inside the mediachannel 332 - J field: granularity of the channel spacing, can be a 333 multiple of 0.01GHz. - default value is 0.1GHz. 334 - K field: positive or negative integer (including 0) to multiply 335 by J and identify the S.C. Position inside the 336 Media Channel, J can be set at default value = 0.1GHz. 338 m=8 339 +-------------------------------X------------------------------+ 340 | | | 341 | sub-carrier sub-carrier | 342 | +----------X----------+ | +----------X----------+ | 343 | | OTSi | | OTSi | | 344 | | o | | | o | | 345 | | | | | | | | 346 -4 -3 -2 -1 0 1 2 3 4 5 6 7 8 9 10 11 12 347 --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- 348 | n=4 | 349 K1 -236 | +236 k2 351 <------------------------ Media Channel -----------------------> 353 Figure 3: OCh_General 355 4.3. RSVP Protocol Extensions considerations 357 The additional information described in the draft, is related to the 358 Media Channel supported traffic. It could be encoded as specific 359 extensions of the SENDER_TSPEC/FLOW_SPEC object for Flexi-Grid 360 networks (see [RFC7792]) 362 5. Security Considerations 364 GMPLS message security uses IPsec, as described in xxxx. This 365 document only defines new UNI objects that are carried in existing 366 UNI messages, similar to the UNI objects in xxx. This document does 367 not introduce new security considerations. 369 6. IANA Considerations 371 T.B.D. 373 7. Contributors 375 Antonello Bonfanti 376 Cisco 377 Via Santa Maria Molgora, 48 c 378 20871 - Vimercate (MB) 379 Italy 380 abonfant@cisco.com 382 8. References 384 8.1. Normative References 386 [RFC7698] Gonzalez de Dios, O., Ed., Casellas, R., Ed., Zhang, F., 387 Fu, X., Ceccarelli, D., and I. Hussain, "Framework and 388 Requirements for GMPLS-Based Control of Flexi-Grid Dense 389 Wavelength Division Multiplexing (DWDM) Networks", 390 RFC 7698, DOI 10.17487/RFC7698, November 2015, 391 . 393 [RFC7699] Farrel, A., King, D., Li, Y., and F. Zhang, "Generalized 394 Labels for the Flexi-Grid in Lambda Switch Capable (LSC) 395 Label Switching Routers", RFC 7699, DOI 10.17487/RFC7699, 396 November 2015, . 398 [RFC6205] Otani, T., Ed. and D. Li, Ed., "Generalized Labels for 399 Lambda-Switch-Capable (LSC) Label Switching Routers", 400 RFC 6205, DOI 10.17487/RFC6205, March 2011, 401 . 403 [RFC7792] Zhang, F., Zhang, X., Farrel, A., Gonzalez de Dios, O., 404 and D. Ceccarelli, "RSVP-TE Signaling Extensions in 405 Support of Flexi-Grid Dense Wavelength Division 406 Multiplexing (DWDM) Networks", RFC 7792, 407 DOI 10.17487/RFC7792, March 2016, 408 . 410 [RFC6163] Lee, Y., Ed., Bernstein, G., Ed., and W. Imajuku, 411 "Framework for GMPLS and Path Computation Element (PCE) 412 Control of Wavelength Switched Optical Networks (WSONs)", 413 RFC 6163, DOI 10.17487/RFC6163, April 2011, 414 . 416 [RFC5920] Fang, L., Ed., "Security Framework for MPLS and GMPLS 417 Networks", RFC 5920, DOI 10.17487/RFC5920, July 2010, 418 . 420 [RFC3945] Mannie, E., Ed., "Generalized Multi-Protocol Label 421 Switching (GMPLS) Architecture", RFC 3945, 422 DOI 10.17487/RFC3945, October 2004, 423 . 425 [RFC3473] Berger, L., Ed., "Generalized Multi-Protocol Label 426 Switching (GMPLS) Signaling Resource ReserVation Protocol- 427 Traffic Engineering (RSVP-TE) Extensions", RFC 3473, 428 DOI 10.17487/RFC3473, January 2003, 429 . 431 [RFC4208] Swallow, G., Drake, J., Ishimatsu, H., and Y. Rekhter, 432 "Generalized Multiprotocol Label Switching (GMPLS) User- 433 Network Interface (UNI): Resource ReserVation Protocol- 434 Traffic Engineering (RSVP-TE) Support for the Overlay 435 Model", RFC 4208, DOI 10.17487/RFC4208, October 2005, 436 . 438 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 439 Requirement Levels", BCP 14, RFC 2119, 440 DOI 10.17487/RFC2119, March 1997, 441 . 443 [ITU.G698.2] 444 International Telecommunications Union, "Amplified 445 multichannel dense wavelength division multiplexing 446 applications with single channel optical interfaces", 447 ITU-T Recommendation G.698.2, November 2009. 449 [ITU.G694.1] 450 International Telecommunications Union, ""Spectral grids 451 for WDM applications: DWDM frequency grid"", 452 ITU-T Recommendation G.698.2, February 2012. 454 [ITU.G709] 455 International Telecommunications Union, "Interface for the 456 Optical Transport Network (OTN)", ITU-T Recommendation 457 G.709, February 2012. 459 [ITU.G872] 460 International Telecommunications Union, "Architecture of 461 optical transport networks", ITU-T Recommendation G.872, 462 October 2012. 464 [ITU.G874.1] 465 International Telecommunications Union, "Optical transport 466 network (OTN): Protocol-neutral management information 467 model for the network element view", ITU-T Recommendation 468 G.874.1, October 2012. 470 8.2. Informative References 472 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 473 "Introduction and Applicability Statements for Internet- 474 Standard Management Framework", RFC 3410, 475 DOI 10.17487/RFC3410, December 2002, 476 . 478 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 479 DOI 10.17487/RFC2629, June 1999, 480 . 482 [RFC4181] Heard, C., Ed., "Guidelines for Authors and Reviewers of 483 MIB Documents", BCP 111, RFC 4181, DOI 10.17487/RFC4181, 484 September 2005, . 486 Authors' Addresses 488 Gabriele Galimberti (editor) 489 Cisco 490 Via S. Maria Molgora, 48 c 491 20871 - Vimercate 492 Italy 494 Phone: +390392091462 495 Email: ggalimbe@cisco.com 497 Domenico La Fauci 498 Cisco 499 Via S. Maria Molgora, 48 c 500 20871 - Vimercate 501 Italy 503 Phone: +390392091946 504 Email: dlafauci@cisco.com 505 Andrea Zanardi (editor) 506 FBK-CreateNet 507 via alla Cascata 56/D 508 38123 Povo, Trento 509 Italy 511 Phone: +390461312450 512 Email: azanardi@fbk.eu 514 Lorenzo Galvagni 515 FBK-CreateNet 516 via alla Cascata 56/D 517 38123 Povo, Trento 518 Italy 520 Phone: +390461312427 521 Email: lgalvagni@fbk.eu