idnits 2.17.1 draft-ggalimbe-ccamp-flexigrid-carrier-label-02.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.G872], [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 seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (October 30, 2017) is 2370 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- == Unused Reference: 'ITU.G698.2' is defined on line 551, but no explicit reference was found in the text == Unused Reference: 'ITU.G709' is defined on line 557, but no explicit reference was found in the text == Unused Reference: 'ITU.G874.1' is defined on line 569, but no explicit reference was found in the text == Unused Reference: 'RFC2119' is defined on line 575, but no explicit reference was found in the text == Unused Reference: 'RFC3473' is defined on line 580, but no explicit reference was found in the text == Unused Reference: 'RFC3945' is defined on line 586, but no explicit reference was found in the text == Unused Reference: 'RFC5920' is defined on line 598, but no explicit reference was found in the text == Unused Reference: 'RFC6163' is defined on line 602, but no explicit reference was found in the text == Unused Reference: 'RFC7699' is defined on line 622, but no explicit reference was found in the text == Unused Reference: 'RFC2629' is defined on line 636, but no explicit reference was found in the text == Unused Reference: 'RFC3410' is defined on line 640, but no explicit reference was found in the text == Unused Reference: 'RFC4181' is defined on line 646, 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 (~~), 14 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: May 3, 2018 A. Zanardi, Ed. 6 L. Galvagni 7 FBK-CreateNet 8 October 30, 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-02 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 in accordance to the model 20 described in RFC 7698. The extensions are in accordance and 21 extending the parameters defined in ITU-T Recommendation 22 G.694.1.[ITU.G694.1] and its extensions and G.872.[ITU.G872]. 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 https://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 May 3, 2018. 46 Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2017 48 Copyright Notice 50 Copyright (c) 2017 IETF Trust and the persons identified as the 51 document authors. All rights reserved. 53 This document is subject to BCP 78 and the IETF Trust's Legal 54 Provisions Relating to IETF Documents 55 (https://trustee.ietf.org/license-info) in effect on the date of 56 publication of this document. Please review these documents 57 carefully, as they describe your rights and restrictions with respect 58 to this document. Code Components extracted from this document must 59 include Simplified BSD License text as described in Section 4.e of 60 the Trust Legal Provisions and are provided without warranty as 61 described in the Simplified BSD License. 63 Table of Contents 65 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 66 2. Client interface parameters . . . . . . . . . . . . . . . . . 3 67 3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 5 68 4. Signalling Extensions . . . . . . . . . . . . . . . . . . . . 5 69 4.1. New LSP set-up parameters . . . . . . . . . . . . . . . . 5 70 4.2. Extension to LSP set-up reservation . . . . . . . . . . . 7 71 4.3. RSVP Protocol Extensions considerations . . . . . . . . . 13 72 5. Security Considerations . . . . . . . . . . . . . . . . . . . 14 73 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 74 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 14 75 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 76 8.1. Normative References . . . . . . . . . . . . . . . . . . 14 77 8.2. Informative References . . . . . . . . . . . . . . . . . 16 78 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 80 1. Introduction 82 Generalised Multiprotocol Label Switched (GMPLS) is widely used in 83 Wavelength Switched Optical Network (WSON) to support the optical 84 circuits set-up through the signalling between Core Nodes and Edge 85 Nodes. This extension addresses the use cases described by [RFC7698] 86 Ch.3.3 and supports the information, needed in Spectrum Switched 87 Optical Network (SSON), to signal a Media Channel and the associated 88 carriers set request. The new set of parameters is related to the 89 Media Channel and the carrier(s) routed with it and keep the backward 90 compatibility with the WSON signalling. In particular this memo 91 wants do address the use cases where the SSON LSP (the Media Channel 92 in RFC7698) carries multiple carrier (OTSi) containing same Payload. 93 The set of the carriers can be seen as single Logical circuit. This 94 memo can be considered as the extension of [RFC7792]. The contents 96 Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2017 98 and the parameters reflect the experimental activity on IP over SSON 99 recently done by some vendors and research consortia. 101 Figure 1 shows how the multiple carrier are mapped into a Media 102 Channel. A set of parameters must be shared on the UNI to allow the 103 GMPLS to do the proper routing and Spectrum Assignment and decide the 104 carrier position. 106 +------+ +------+ _________ +------+ +------+ 107 | E.N. | | C.N. | / /\ | C.N. | | E.N. | 108 | OTS1| ----- | || | || | ----- |OTS1 | 109 ==| OTS2| ----- | || Media | || | ----- |OTS2 |== 110 ==| OTS3| ----- | || Channel| || | ----- |OTS3 |== 111 | OTS4| ----- | || | || | ----- |OTS4 | 112 | | | ROADM| \________\/ | ROADM| | | 113 +------+ +------+ +------+ +------+ 114 ^ ^ ^ ^ 115 | | | | 116 +---UNI---+ +---UNI---+ 118 E.N. = Edge Node - UNI Client 119 C.N. = Core Node - UNI Network 120 ROADM = Lambda/Spectrum switch 121 Media Channel = the optical circuit 122 OTSi = Carriers belonging to the same Network Media Channel (or 123 Super Channel) 124 UNI = Signalig interface 126 from Fig. 5.1/G.698.2 128 Figure 1: Multi carrier LSP 130 2. Client interface parameters 132 The Edge Node interface can have one or multiple carriers (OTSi). 133 All the carrier have the same characteristics and are provisionable 134 in terms of: 136 Number of subcarriers: 137 This parameter indicates the number of subcarriers available for 138 the super-channel in case the Transceiver can support multiple 139 carrier circuits. 141 Central frequency (see G.694.1 Table 1): 143 Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2017 145 This parameter indicates the Central frequency value that Ss and 146 Rs will be set to work (in THz). See the details in Section 6/ 147 G.694.1 or based on "n" value explanation and the following "k" 148 values definition in case of multicarrier transceivers. 150 Central frequency granularity: 151 This parameter indicates the Central frequency granularity 152 supported by the transceiver, this value is combined with k and n 153 value to calculate the central frequency of the carrier or sub- 154 carriers. 156 Minimum channel spacing: 157 This is the minimum nominal difference in frequency (in GHz) 158 between two adjacent channels (or carriers) depending on the 159 Transceiver characteristics. 161 Bit rate / Baud rate of optical tributary signals: 162 Optical Tributary Signal bit (for NRZ signals) rate or Symbol (for 163 Multiple bit per symbol) rate . 165 FEC Coding: 166 This parameter indicate what Forward Error Correction (FEC) code 167 is used at Ss and Rs (R/W) (not mentioned in G.698.2). . 169 Wavelength Range (see G.694.1): [ITU.G694.1] 170 This parameter indicate minimum and maximum wavelength spectrum in 171 a definite wavelength Band (L, C and S). 173 Modulation format: 174 This parameter indicates the list of supported Modulation Formats 175 and the provisioned Modulation Format.. 177 Inter carrier skew: 178 This parameter indicates, in case of multi-carrier transceivers 179 the maximum skew between the sub-carriers supported by the 180 transceiver. 182 Laser Output power: 183 This parameter provisions the Transceiver Output power, it can be 184 either a setting and measured value. 186 receiver input power: 187 This parameter provisions the Min and MAX input pover suppotred by 188 the Transceiver, i.e. Receiver Sensitivity. 190 The above parameters are related to the Edge Node Transceiver and are 191 used by the Core Network GMPLS in order to calculate the optical 192 feasibility and the spectrum allocation. The parameters can be 194 Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2017 196 shared between the Client and the Network via LMP or provisioned in 197 the Network by an EMS or an operator OSS. 199 3. Use Cases 201 The use cases are described in draft-ietf-ccamp-dwdm-if-mng-ctrl-fwk 202 and [RFC7698] 204 4. Signalling Extensions 206 Some of the above parameters can be applied to RFC7792 (SENDER_TSPEC/ 207 FLOWSPEC). The above parameters could be applied to [RFC4208] 208 scenarios but they are valid also in case of non UNI scenarios. The 209 [RFC6205] parameters remain valid. 211 4.1. New LSP set-up parameters 213 When the E.N. wants to request to the C.N. a new circuit set-up 214 request or the GMPLS want to signal in the SSON network the Optical 215 Interface characteristics the following parameters will be provided 216 to the C.N.: 218 Number of available subcarriers (c): 219 This parameter is an integer. 221 Total bandwidth request: 222 e.g. 200Gb, 400Gb, 1Tb 224 Policy (strict/loose): 225 Strict/loose referred to B/W and subcarrier number. 227 Subcarrier bandwidth tunability: 228 (optional) e.g. 34Ghz, 48GHz. 230 Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2017 232 Figure 2: The format of the this sub-object is as follows: 234 The TLV define the resource constraints for the requested Media 235 Channel. 237 0 1 2 3 238 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 239 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 240 |S|B| Reserved | Carrier Number | 241 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 242 | Total Bandwidth | 243 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 245 Figure 2: SSON LSP set-up request 247 Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2017 249 Carrier Number: number of carrier to be allocated for the requested 250 channel (16-bit unsigned integer) 251 If Carrier Number == 0 no constraint set on the number of 252 carriers to be used 254 S strict number of subcarrier 255 - S = 0 the number of requested carriers is the maximum number 256 that can be allocated (a lower value can be allocated if 257 the requested bandwidth is satisfied) 258 - S = 1 the number of requested carriers is strict (must be > 0) 260 Total Bandwidth: the requested total bandwidth to be supported by 261 the Media Channel (32-bit IEEE float, bytes/s) 262 If Total Bandwidth == 0: no bandwidth constraint is defined 263 (B must be 0) 265 B Bandwidth constraints 266 - B = 0: the value is the maximum requested bandwidth (a lower 267 value can be allocated if resources are not available) 268 - B = 1: the requested bandwidth is the minimum value to be 269 allocated (a higher value can be allocated if requested 270 by the physical constraints of the ports) 272 Reserved: unused bit (for future use, should be 0) 274 Note: bandwidth unit is defined in accordance to RFC 3471 275 chap. 3.1.2 Bandwith Encoding specification. Bandwidth higher 276 than 40Gb/s values must be defined (e.g. 100Gb/s, 150Gb/s 277 400Gb/s, etc.) 279 TLV Usage: 280 Head UNI-C PATH: requested traffic constraints, the Head UNI-N node 281 must satisfy when reserving the optical resources and defining 282 the carriers configuration 283 The TLV can be omitted: no traffic constraints is defined (resources 284 allocated by UNI-N based on a local policy) 286 4.2. Extension to LSP set-up reservation 288 Once the GMPLS has calculated the Media Channel path, the Spectrum 289 Allocation, the Sub-carrier number and frequency, the modulation 290 format, the FEC and the Transmit power, sends back to the E.N. the 291 path set-up confirmation providing the values of the calculated 292 paramenters: 294 Media Channel: 295 (Grid, C.S., Identifier m and n). 297 Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2017 299 List of subcarriers: 300 This parameter indicates the subcarriers to be used for the super- 301 channel in case the Transceiver can support multiple carrier 302 Circuits. 304 Central frequency (see G.694.1 Table 1): 305 Grid, Identifiers, central frequency and granularity. 307 Central frequency granularity: 308 This parameter indicates the Central frequency granularity 309 supported by the transceiver, this value is combined with K and n 310 value to calculate the central frequency on the carrier or sub- 311 carriers. 313 Bit rate / Baud rate of optical tributary signals: 314 Optical tributary signal bit (for NRZ signals) rate or Symbol (for 315 Multiple bit per symbol) rate. 317 FEC Coding: 318 This parameter indicate what Forward Error Correction (FEC) code 319 must be used by the Transceivers (not mentioned in G.698). . 321 Modulation format: 322 This parameter indicates the Modulation Formats to be set in the 323 Transceivers. 325 Laser Output power: 326 This parameter provisions the Transceiver Output power, it can be 327 either a setting and measured value. 329 Circuit Path, RRO, etc: 330 All these info are defined in [RFC4208]. 332 Path Error: 333 e.g. no path exist, all the path error defined in [RFC4208]. 335 Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2017 337 Figure 3: The format of this sub-object (Type = TBA, Length = TBA) is 338 as follows: 340 The TLV defines the carriers signal configuration. 341 All carriers in a Media Channel MUST have the same configuration. 343 0 1 2 3 344 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 345 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 346 | Modulation Format | FEC | 347 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 348 | baud rate (Symbol Rate) | 349 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 351 Figure 3: OCh_General 353 Traffic Type 354 - Modulation Format: is the modulation type: 355 BPSK, DC DP BSPSK, QPSK, DP QPSK, 8QAM, 16QAM, 64QAM, 356 Hybrid, etc. 357 - (ITU-T reference) 358 - value > 32768 (first bit is 1): custom defined values 359 Value 0 is reserved to be used if no value is defined 360 - FEC: the signal Forward Error Corrections type (16-bit 361 unsigned integer), the defined values are: 362 - (ITU-T reference) 363 - 32768 (first bit is 1): custom defined values 364 Value 0 is reserved to be used if no value is defined 365 - Baud Rate: the signal symbol rate (IEEE 32-bit float, 366 in bauds/s) 367 Value 0 is reserved to be used if no value is defined 369 Notes: 370 - The request from the Head UNI-C node can specify only a subset 371 of the parameters (e.g. the Modulation and the baud rate but 372 not the FEC) but setting to 0 the undefined parameters. 373 - Custom codes (values > 0x8000) interpretation is a local 374 installation matter. 376 TLV Usage: 377 - Head UNI-C PATH: used to force specific transponder 378 configurations 379 - Head UNI-N RESV: set selected configuration on head node 380 - Tail UNI-N PATH: set selected configuration on tail node 382 Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2017 384 Figure 4: The format of this sub-object (Type = TBA, Length = TBA) is 385 as follows: 387 For Each carrier inside the Media Channel the TLV is used: 389 0 1 2 3 390 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 391 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 392 | Carrier Identifier | j | 393 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 394 | k | 395 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 396 | sub-TLVs | 397 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 399 Figure 4: Sub-Carrier parameters 401 Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2017 403 Carrier set-up: 405 - Carrier identifier field: sub-carrier 406 identifier inside the mediachannel. Identifies the carrier 407 position inside the Media Channel (16-bit unsigned integer) 408 - J field: granularity of the channel spacing, can be a 409 multiple of 0.01GHz. - default value is 0.1GHz. 410 - K field: positive or negative integer (including 0) to multiply 411 by J and identify the Carrier Position inside the 412 Media Channel, offset from media Channel Central frequency 413 - sub-TLVs: additional information related to carriers if needed. 415 In summary Carrier Frequency = MC-C.F. (in THz) + K * J GHz 417 m=8 418 +-------------------------------X------------------------------+ 419 | | | 420 | sub-carrier sub-carrier | 421 | +----------X----------+ | +----------X----------+ | 422 | | OTSi | | OTSi | | 423 | | o | | | o | | 424 | | | | | | | | 425 -4 -3 -2 -1 0 1 2 3 4 5 6 7 8 9 10 11 12 426 --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- 427 | n=4 | 428 K1 -236 | +236 K2 430 <------------------------ Media Channel -----------------------> 432 Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2017 434 Figure 5: The format of this sub-object (Type = TBA, Length = TBD) is 435 as follows: 437 The defined sub-TLVs are: 439 Port Identifier 441 0 1 2 3 442 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 443 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 444 | Type (TBA) | Length (TBD) | 445 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 446 | Port Identifier | 447 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 449 Figure 5: Port Identifier 451 Port Identifier: the local upstream optical logical identifier 452 (32-bits integer, ifindex) 454 Notes: 455 - The Carrier Identifier is the logical circuit sub-lane position, 456 a TLV for each value from 1 to the number of allocated carriers 457 must be present. 459 - The association of a carrier to a local link optical port is a 460 local link association (depending on the local ports physical 461 configuration), the sub-TLV value MUST be set by head/tail nodes 462 (with transit nodes not signaling its value). 463 The local port identifier is the identifier of the local link 464 port on the upstream node (with respect to the LSP nominal 465 direction): 466 - UNI-C port in head UNI link 467 - UNI-N port in tail UNI link 469 TLV Usage: 470 - Head UNI-C PATH: used to force specific carrier frequency/ports 471 [optional use, e.g. with external PCE scenario] 472 - Head UNI-N RESV: set selected configuration on head node 473 - Tail UNI-N PATH: set selected configuration on tail node 475 Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2017 477 Figure 6: The format of this sub-object (Type = TBA, Length = TBD) is 478 as follows: 480 Carrier Power: 482 0 1 2 3 483 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 484 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 485 | Type (TBA) | Length (TBD) | 486 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 487 | carrier power | 488 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 490 Figure 6: Carrier Power 492 Carrier Port: the requested carrier transmit power (32-bits IEEE 493 Float, dBm), optionally used to notify the configured 494 power (in UNI client side) or force the power to the 495 to the UNI client). 497 TLV Usage: 498 - Head UNI-C PATH: used to force specific carrier frequency/ports 499 (optional use, e.g. with external PCE scenario) 500 - Head UNI-N RESV: set selected configuration on head node 501 - Tail UNI-N PATH: set selected configuration on tail node 503 4.3. RSVP Protocol Extensions considerations 505 The additional information described in the draft, is related to the 506 Media Channel supported traffic. It could be encoded in the 507 SENDER_TSPEC/FLOW_SPEC objects by extending the SSON_SENDER_TSPEC/ 508 SSON_FLOW_SPEC defined in RFC 7792 (or defining a new C-Type) with an 509 optional TLV list or it could be encoded in a newly defined entry 510 (new OBJECT or new LSP_ATTRIBUTES OBJECT TLV) 512 This solution is consistent with other technology specific extensions 513 (e.g. SDH), but requires the explicit handling of the extensions by 514 all nodes. 516 Beside this, some of the additional information defined is local to 517 the head/tail UNI link (e.g. the carrier/port association), while the 518 traffic spec info should be valid end-to-end. 520 Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2017 522 5. Security Considerations 524 GMPLS message security uses IPsec, as described in xxxx. This 525 document only defines new UNI objects that are carried in existing 526 UNI messages, similar to the UNI objects in xxx. This document does 527 not introduce new security considerations. 529 6. IANA Considerations 531 T.B.D. 533 7. Contributors 535 Antonello Bonfanti 536 Cisco 537 Via Santa Maria Molgora, 48 c 538 20871 - Vimercate (MB) 539 Italy 540 abonfant@cisco.com 542 8. References 544 8.1. Normative References 546 [ITU.G694.1] 547 International Telecommunications Union, ""Spectral grids 548 for WDM applications: DWDM frequency grid"", 549 ITU-T Recommendation G.698.2, February 2012. 551 [ITU.G698.2] 552 International Telecommunications Union, "Amplified 553 multichannel dense wavelength division multiplexing 554 applications with single channel optical interfaces", 555 ITU-T Recommendation G.698.2, November 2009. 557 [ITU.G709] 558 International Telecommunications Union, "Interface for the 559 Optical Transport Network (OTN)", ITU-T Recommendation 560 G.709, February 2012. 562 [ITU.G872] 563 International Telecommunications Union, "Architecture of 564 optical transport networks", ITU-T Recommendation G.872, 565 October 2012. 567 Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2017 569 [ITU.G874.1] 570 International Telecommunications Union, "Optical transport 571 network (OTN): Protocol-neutral management information 572 model for the network element view", ITU-T Recommendation 573 G.874.1, October 2012. 575 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 576 Requirement Levels", BCP 14, RFC 2119, 577 DOI 10.17487/RFC2119, March 1997, 578 . 580 [RFC3473] Berger, L., Ed., "Generalized Multi-Protocol Label 581 Switching (GMPLS) Signaling Resource ReserVation Protocol- 582 Traffic Engineering (RSVP-TE) Extensions", RFC 3473, 583 DOI 10.17487/RFC3473, January 2003, 584 . 586 [RFC3945] Mannie, E., Ed., "Generalized Multi-Protocol Label 587 Switching (GMPLS) Architecture", RFC 3945, 588 DOI 10.17487/RFC3945, October 2004, 589 . 591 [RFC4208] Swallow, G., Drake, J., Ishimatsu, H., and Y. Rekhter, 592 "Generalized Multiprotocol Label Switching (GMPLS) User- 593 Network Interface (UNI): Resource ReserVation Protocol- 594 Traffic Engineering (RSVP-TE) Support for the Overlay 595 Model", RFC 4208, DOI 10.17487/RFC4208, October 2005, 596 . 598 [RFC5920] Fang, L., Ed., "Security Framework for MPLS and GMPLS 599 Networks", RFC 5920, DOI 10.17487/RFC5920, July 2010, 600 . 602 [RFC6163] Lee, Y., Ed., Bernstein, G., Ed., and W. Imajuku, 603 "Framework for GMPLS and Path Computation Element (PCE) 604 Control of Wavelength Switched Optical Networks (WSONs)", 605 RFC 6163, DOI 10.17487/RFC6163, April 2011, 606 . 608 [RFC6205] Otani, T., Ed. and D. Li, Ed., "Generalized Labels for 609 Lambda-Switch-Capable (LSC) Label Switching Routers", 610 RFC 6205, DOI 10.17487/RFC6205, March 2011, 611 . 613 Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2017 615 [RFC7698] Gonzalez de Dios, O., Ed., Casellas, R., Ed., Zhang, F., 616 Fu, X., Ceccarelli, D., and I. Hussain, "Framework and 617 Requirements for GMPLS-Based Control of Flexi-Grid Dense 618 Wavelength Division Multiplexing (DWDM) Networks", 619 RFC 7698, DOI 10.17487/RFC7698, November 2015, 620 . 622 [RFC7699] Farrel, A., King, D., Li, Y., and F. Zhang, "Generalized 623 Labels for the Flexi-Grid in Lambda Switch Capable (LSC) 624 Label Switching Routers", RFC 7699, DOI 10.17487/RFC7699, 625 November 2015, . 627 [RFC7792] Zhang, F., Zhang, X., Farrel, A., Gonzalez de Dios, O., 628 and D. Ceccarelli, "RSVP-TE Signaling Extensions in 629 Support of Flexi-Grid Dense Wavelength Division 630 Multiplexing (DWDM) Networks", RFC 7792, 631 DOI 10.17487/RFC7792, March 2016, 632 . 634 8.2. Informative References 636 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 637 DOI 10.17487/RFC2629, June 1999, 638 . 640 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 641 "Introduction and Applicability Statements for Internet- 642 Standard Management Framework", RFC 3410, 643 DOI 10.17487/RFC3410, December 2002, 644 . 646 [RFC4181] Heard, C., Ed., "Guidelines for Authors and Reviewers of 647 MIB Documents", BCP 111, RFC 4181, DOI 10.17487/RFC4181, 648 September 2005, . 650 Authors' Addresses 652 Gabriele Galimberti (editor) 653 Cisco 654 Via S. Maria Molgora, 48 c 655 20871 - Vimercate 656 Italy 658 Phone: +390392091462 659 Email: ggalimbe@cisco.com 661 Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2017 663 Domenico La Fauci 664 Cisco 665 Via S. Maria Molgora, 48 c 666 20871 - Vimercate 667 Italy 669 Phone: +390392091946 670 Email: dlafauci@cisco.com 672 Andrea Zanardi (editor) 673 FBK-CreateNet 674 via alla Cascata 56/D 675 38123 Povo, Trento 676 Italy 678 Phone: +390461312450 679 Email: azanardi@fbk.eu 681 Lorenzo Galvagni 682 FBK-CreateNet 683 via alla Cascata 56/D 684 38123 Povo, Trento 685 Italy 687 Phone: +390461312427 688 Email: lgalvagni@fbk.eu