idnits 2.17.1 draft-ggalimbe-ccamp-flexigrid-carrier-label-05.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 22, 2018) is 2012 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- == Unused Reference: 'ITU.G698.2' is defined on line 577, but no explicit reference was found in the text == Unused Reference: 'ITU.G709' is defined on line 583, but no explicit reference was found in the text == Unused Reference: 'ITU.G874.1' is defined on line 595, but no explicit reference was found in the text == Unused Reference: 'RFC2119' is defined on line 601, but no explicit reference was found in the text == Unused Reference: 'RFC3473' is defined on line 606, but no explicit reference was found in the text == Unused Reference: 'RFC3945' is defined on line 612, but no explicit reference was found in the text == Unused Reference: 'RFC5920' is defined on line 624, but no explicit reference was found in the text == Unused Reference: 'RFC6163' is defined on line 628, but no explicit reference was found in the text == Unused Reference: 'RFC7699' is defined on line 648, but no explicit reference was found in the text == Unused Reference: 'RFC2629' is defined on line 662, but no explicit reference was found in the text == Unused Reference: 'RFC3410' is defined on line 666, but no explicit reference was found in the text == Unused Reference: 'RFC4181' is defined on line 672, 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: April 25, 2019 A. Zanardi, Ed. 6 L. Galvagni 7 FBK-CreateNet 8 October 22, 2018 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-05 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 April 25, 2019. 46 Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2018 48 Copyright Notice 50 Copyright (c) 2018 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.2.1. Sub-carrier list content . . . . . . . . . . . . . . 9 72 4.2.2. Sub-carrier sub-TLV . . . . . . . . . . . . . . . . . 10 73 4.3. RSVP Protocol Extensions considerations . . . . . . . . . 12 74 5. Security Considerations . . . . . . . . . . . . . . . . . . . 13 75 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 76 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 13 77 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 78 8.1. Normative References . . . . . . . . . . . . . . . . . . 13 79 8.2. Informative References . . . . . . . . . . . . . . . . . 15 80 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15 82 1. Introduction 84 Generalised Multiprotocol Label Switched (GMPLS) is widely used in 85 Wavelength Switched Optical Network (WSON) to support the optical 86 circuits set-up through the signalling between Core Nodes and Edge 87 Nodes. This extension addresses the use cases described by [RFC7698] 88 Ch.3.3 and supports the information, needed in Spectrum Switched 89 Optical Network (SSON), to signal a Media Channel and the associated 90 carriers set request. The new set of parameters is related to the 91 Media Channel and the carrier(s) routed with it and keep the backward 92 compatibility with the WSON signalling. In particular this memo 93 wants do address the use cases where the SSON LSP (the Media Channel 94 in RFC7698) carries multiple carrier (OTSi) containing same Payload. 95 The set of the carriers can be seen as single Logical circuit. This 97 Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2018 99 memo can be considered as the extension of [RFC7792]. The contents 100 and the parameters reflect the experimental activity on IP over SSON 101 recently done by some vendors and research consortia. 103 Figure 1 shows how the multiple carrier are mapped into a Media 104 Channel. A set of parameters must be shared on the UNI to allow the 105 GMPLS to do the proper routing and Spectrum Assignment and decide the 106 carrier position. 108 +------+ +------+ _________ +------+ +------+ 109 | E.N. | | C.N. | / /\ | C.N. | | E.N. | 110 | OTS1| ----- | || | || | ----- |OTS1 | 111 ==| OTS2| ----- | || Media | || | ----- |OTS2 |== 112 ==| OTS3| ----- | || Channel| || | ----- |OTS3 |== 113 | OTS4| ----- | || | || | ----- |OTS4 | 114 | | | ROADM| \________\/ | ROADM| | | 115 +------+ +------+ +------+ +------+ 116 ^ ^ ^ ^ 117 | | | | 118 +---UNI---+ +---UNI---+ 120 E.N. = Edge Node - UNI Client 121 C.N. = Core Node - UNI Network 122 ROADM = Lambda/Spectrum switch 123 Media Channel = the optical circuit 124 OTSi = Carriers belonging to the same Network Media Channel (or 125 Super Channel) 126 UNI = Signalig interface 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): 142 This parameter indicates the Central frequency value that Ss and 143 Rs will be set to work (in THz). See the details in Section 6/ 145 Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2018 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 193 shared between the Client and the Network via LMP or provisioned to 194 the Network by an EMS or an operator OSS. 196 Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2018 198 3. Use Cases 200 The use cases are described in draft-ietf-ccamp-dwdm-if-mng-ctrl-fwk 201 and [RFC7698] 203 4. Signalling Extensions 205 Some of the above parameters can be applied to RFC7792 (SENDER_TSPEC/ 206 FLOWSPEC). The above parameters could be applied to [RFC4208] 207 scenarios but they are valid also in case of non UNI scenarios. The 208 [RFC6205] parameters remain valid. 210 4.1. New LSP set-up parameters 212 When the E.N. wants to request to the C.N. a new circuit set-up 213 request or the GMPLS wants to signal in the SSON network the Optical 214 Interface characteristics the following parameters will be provided 215 to the C.N.: 217 Number of available subcarriers (c): 218 This parameter is an integer and identifies the number of Client 219 ports connected to the Core ports available to suport the 220 requested circuit 222 Total bandwidth request: 223 e.g. 200Gb, 400Gb, 1Tb - it is the bandwidth (payload) to be 224 carried by the multiple carrier circuit 226 Policy (strict/loose): 227 Strict/loose referred to B/W and subcarrier number. This is to 228 give some flexibility to the GMPLS in order to commit client 229 request. 231 Subcarrier bandwidth tunability: 232 (optional) e.g. 34Ghz, 48GHz. 234 Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2018 236 The TLV define the resource constraints for the requested Media 237 Channel. 239 The format of the this sub-object is as follows: 241 0 1 2 3 242 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 243 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 244 |S|B| Reserved | Carrier Number | 245 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 246 | Total Bandwidth | 247 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 249 Figure 2: SSON LSP set-up request 251 Carrier Number: number of carrier to be allocated for the requested 252 channel (16-bit unsigned integer) 253 If Carrier Number == 0 no constraint set on the number of 254 carriers to be used 256 S strict number of subcarrier 257 - S = 0 the number of requested carriers is the maximum number 258 that can be allocated (a lower value can be allocated if 259 the requested bandwidth is satisfied) 260 - S = 1 the number of requested carriers is strict (must be > 0) 262 Total Bandwidth: the requested total bandwidth to be supported by 263 the Media Channel (32-bit IEEE float, bytes/s) 264 If Total Bandwidth == 0: no bandwidth constraint is defined 265 (B must be 0) 267 B Bandwidth constraints 268 - B = 0: the value is the maximum requested bandwidth (a lower 269 value can be allocated if resources are not available) 270 - B = 1: the requested bandwidth is the minimum value to be 271 allocated (a higher value can be allocated if requested 272 by the physical constraints of the ports) 274 Reserved: unused bit (for future use, should be 0) 276 Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2018 278 Note: bandwidth unit is defined in accordance to RFC 3471 279 chap. 3.1.2 Bandwith Encoding specification. Bandwidth higher 280 than 40Gb/s values must be defined (e.g. 100Gb/s, 150Gb/s 281 400Gb/s, etc.) 283 TLV Usage: 284 Head UNI-C PATH: requested traffic constraints, the Head UNI-N node 285 must satisfy when reserving the optical resources and defining 286 the carriers configuration 287 The TLV can be omitted: no traffic constraints is defined (resources 288 allocated by UNI-N based on a local policy) 290 4.2. Extension to LSP set-up reservation 292 Once the GMPLS has calculated the Media Channel path, the Spectrum 293 Allocation, the Sub-carrier number and frequency, the modulation 294 format, the FEC and the Transmit power, sends back to the E.N. the 295 path set-up confirmation providing the values of the calculated 296 paramenters: 298 Media Channel: 299 (Grid, C.S., Identifier m and n). as indicated in RFC7699 300 Section 4.1 302 Modulation format: 303 This parameter indicates the Modulation Formats to be set in the 304 Transceivers. 306 FEC Coding: 307 This parameter indicate what Forward Error Correction (FEC) code 308 must be used by the Transceivers (not mentioned in G.698). . 310 Bit rate / Baud rate of optical tributary signals: 311 Optical tributary signal bit (for NRZ signals) rate or Symbol (for 312 Multiple bit per symbol) rate. 314 List of subcarriers: 315 This parameter indicates the subcarriers to be used for the super- 316 channel in case the Transceiver can support multiple carrier 317 Circuits. 319 Central frequency granularity (J): 320 This parameter indicates the Central frequency granularity 321 supported by the transceiver, this value is combined with K and n 322 value to calculate the central frequency on the carrier or sub- 323 carriers. 325 Central frequency (see G.694.1 Table 1): 327 Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2018 329 Grid, Identifiers, central frequency and granularity. 331 Laser Output power: 332 This parameter provisions the Transceiver Output power, it can be 333 either a setting and measured value. 335 Circuit Path, RRO, etc: 336 All these info are defined in [RFC4208]. 338 Path Error: 339 e.g. no path exist, all the path error defined in [RFC4208]. 341 The TLV defines the carriers signal configuration. 342 All carriers in a Media Channel MUST have the same configuration. 344 The format of this sub-object (Type = TBA, Length = TBA) is 345 as follows: 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 | Modulation Format | FEC | 351 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 352 | baud rate (Symbol Rate) | 353 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 355 Figure 3: OCh_General 357 Traffic Type 358 - Modulation Format: is the modulation type: 359 BPSK, DC DP BSPSK, QPSK, DP QPSK, 8QAM, 16QAM, 64QAM, 360 Hybrid, etc. 361 - (ITU-T reference) 362 - value > 32768 (first bit is 1): custom defined values 363 Value 0 is reserved to be used if no value is defined 364 - FEC: the signal Forward Error Corrections type (16-bit 365 unsigned integer), the defined values are: 366 - (ITU-T reference) 367 - 32768 (first bit is 1): custom defined values 368 Value 0 is reserved to be used if no value is defined 369 - Baud Rate: the signal symbol rate (IEEE 32-bit float, 370 in bauds/s) 371 Value 0 is reserved to be used if no value is defined 373 Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2018 375 Notes: 376 - The PATH request from the Head UNI-C node can specify all or 377 only a subset of the parameters (e.g. the Modulation and the 378 baud rate as required but not the FEC) setting to 0 for the 379 undefined parameters. 380 When forwarding the PATH message, the UNI-N will set the 381 undefined parameters based on the optical impairment calculation 382 and the constraints giveng by the UNI-C 383 - Custom codes (values > 0x8000) interpretation is a local 384 installation matter. 386 TLV Usage: 387 - Head UNI-C PATH: used to force specific transponder 388 configurations 389 - Head UNI-N RESV: set selected configuration on head node 390 - Tail UNI-N PATH: set selected configuration on tail node 392 4.2.1. Sub-carrier list content 394 For Each carrier inside the Media Channel the TLV is used. 396 The format of this sub-object (Type = TBA, Length = TBA) 397 is as follows: 399 0 1 2 3 400 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 401 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 402 | Carrier Identifier | j | 403 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 404 | k | 405 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 406 | sub-TLVs | 407 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 409 Figure 4: Sub-Carrier parameters 411 Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2018 413 Carrier set-up: 415 - Carrier identifier field: sub-carrier 416 identifier inside the mediachannel. Identifies the carrier 417 position inside the Media Channel (16-bit unsigned integer) 418 The Carrier Identifier is the logical circuit sub-lane 419 position, a TLV for each value from 1 to the number of 420 allocated carriers must be present. 421 - J field: granularity of the channel spacing, can be a 422 multiple of 0.01GHz. - default value is 0.1GHz. 423 - K field: positive or negative integer (including 0) to multiply 424 by J and identify the Carrier Position inside the 425 Media Channel, offset from media Channel Central frequency 426 - sub-TLVs: additional information related to carriers if needed 427 and the ports associated to the carrier. 429 In summary Carrier Frequency = MC-C.F. (in THz) + K * J GHz. 431 m=8 432 +-------------------------------X------------------------------+ 433 | | | 434 | sub-carrier sub-carrier | 435 | +----------X----------+ | +----------X----------+ | 436 | | OTSi | | OTSi | | 437 | | o | | | o | | 438 | | | | | | | | 439 -4 -3 -2 -1 0 1 2 3 4 5 6 7 8 9 10 11 12 440 --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- 441 | n=4 | 442 K1 -236 | +236 K2 444 <------------------------ Media Channel -----------------------> 446 4.2.2. Sub-carrier sub-TLV 448 The defined sub-TLVs are Port Identifiers and Carrier Power 450 Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2018 452 Source Port Identifier 454 The format of this sub-object (Type = TBA, Length = TBD) is 455 as follows: 457 0 1 2 3 458 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 459 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 460 | Type (TBA) | Length (TBD) | 461 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 462 | Source Port Identifier | 463 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 465 Figure 5: Source Port Identifier 467 Source Port Identifier: the HEAD UNI-C optical logical source end 468 point identifier (32-bits integer, ifindex) 470 TLV Usage: 471 - Head UNI-C PATH: used to force specific carrier ports 472 [optional use, e.g. with external PCE scenario] 473 - Tail UNI-N PATH: report selected arrier head ports 474 to tail UNI-C 475 - RESV: report selected configuration to HEAD UNI-C node 477 Destination Port Identifier 479 The format of this sub-object (Type = TBA, Length = TBD) is 480 as follows: 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 | Destination Port Identifier | 488 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 490 Figure 6: Destination Port Identifiers 492 Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2018 494 Destination Port Identifier: the local upstream optical logical 495 destination end point identifier (32-bits integer, ifindex) 497 TLV Usage: 498 - Head UNI-C PATH: used to force specific carrier ports 499 [optional use, e.g. with external PCE scenario] 500 - Tail UNI-N PATH: set selected configuration on tail node 501 - RESV: report selected configuration to HEAD UNI-C node 503 Carrier Power 505 The format of this sub-object (Type = TBA, Length = TBD) 506 is as follows: 508 0 1 2 3 509 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 510 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 511 | Type (TBA) | Length (TBD) | 512 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 513 | carrier power | 514 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 516 Figure 7: Carrier Power 518 Carrier Power: the requested carrier transmit power (32-bits IEEE 519 Float, dBm), optionally used to notify the configured 520 power (in UNI client side) or force the power to the 521 to the UNI client). 523 TLV Usage: 524 - Head UNI-C PATH: used to force specific carrier frequency/ports 525 (optional use, e.g. with external PCE scenario) 526 - Head UNI-N RESV: set selected configuration on head node 527 - Tail UNI-N PATH: set selected configuration on tail node 529 4.3. RSVP Protocol Extensions considerations 531 The additional information described in the draft, is related to the 532 Media Channel supported traffic. It could be encoded in the 533 SENDER_TSPEC/FLOW_SPEC objects by extending the SSON_SENDER_TSPEC/ 534 SSON_FLOW_SPEC defined in RFC 7792 (or defining a new C-Type) with an 535 optional TLV list or it could be encoded in a newly defined entry 536 (new OBJECT or new LSP_ATTRIBUTES OBJECT TLV) 538 This solution is consistent with other technology specific extensions 539 (e.g. SDH), but requires the explicit handling of the extensions by 540 all nodes. 542 Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2018 544 Beside this, some of the additional information defined is local to 545 the head/tail UNI link (e.g. the carrier/port association), while the 546 traffic spec info should be valid end-to-end. 548 5. Security Considerations 550 GMPLS message security uses IPsec, as described in xxxx. This 551 document only defines new UNI objects that are carried in existing 552 UNI messages, similar to the UNI objects in xxx. This document does 553 not introduce new security considerations. 555 6. IANA Considerations 557 T.B.D. 559 7. Contributors 561 Antonello Bonfanti 562 Cisco 563 Via Santa Maria Molgora, 48 c 564 20871 - Vimercate (MB) 565 Italy 566 abonfant@cisco.com 568 8. References 570 8.1. Normative References 572 [ITU.G694.1] 573 International Telecommunications Union, ""Spectral grids 574 for WDM applications: DWDM frequency grid"", 575 ITU-T Recommendation G.698.2, February 2012. 577 [ITU.G698.2] 578 International Telecommunications Union, "Amplified 579 multichannel dense wavelength division multiplexing 580 applications with single channel optical interfaces", 581 ITU-T Recommendation G.698.2, November 2009. 583 [ITU.G709] 584 International Telecommunications Union, "Interface for the 585 Optical Transport Network (OTN)", ITU-T Recommendation 586 G.709, June 2016. 588 Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2018 590 [ITU.G872] 591 International Telecommunications Union, "Architecture of 592 optical transport networks", ITU-T Recommendation G.872, 593 January 2017. 595 [ITU.G874.1] 596 International Telecommunications Union, "Optical transport 597 network (OTN): Protocol-neutral management information 598 model for the network element view", ITU-T Recommendation 599 G.874.1, November 2016. 601 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 602 Requirement Levels", BCP 14, RFC 2119, 603 DOI 10.17487/RFC2119, March 1997, 604 . 606 [RFC3473] Berger, L., Ed., "Generalized Multi-Protocol Label 607 Switching (GMPLS) Signaling Resource ReserVation Protocol- 608 Traffic Engineering (RSVP-TE) Extensions", RFC 3473, 609 DOI 10.17487/RFC3473, January 2003, 610 . 612 [RFC3945] Mannie, E., Ed., "Generalized Multi-Protocol Label 613 Switching (GMPLS) Architecture", RFC 3945, 614 DOI 10.17487/RFC3945, October 2004, 615 . 617 [RFC4208] Swallow, G., Drake, J., Ishimatsu, H., and Y. Rekhter, 618 "Generalized Multiprotocol Label Switching (GMPLS) User- 619 Network Interface (UNI): Resource ReserVation Protocol- 620 Traffic Engineering (RSVP-TE) Support for the Overlay 621 Model", RFC 4208, DOI 10.17487/RFC4208, October 2005, 622 . 624 [RFC5920] Fang, L., Ed., "Security Framework for MPLS and GMPLS 625 Networks", RFC 5920, DOI 10.17487/RFC5920, July 2010, 626 . 628 [RFC6163] Lee, Y., Ed., Bernstein, G., Ed., and W. Imajuku, 629 "Framework for GMPLS and Path Computation Element (PCE) 630 Control of Wavelength Switched Optical Networks (WSONs)", 631 RFC 6163, DOI 10.17487/RFC6163, April 2011, 632 . 634 [RFC6205] Otani, T., Ed. and D. Li, Ed., "Generalized Labels for 635 Lambda-Switch-Capable (LSC) Label Switching Routers", 636 RFC 6205, DOI 10.17487/RFC6205, March 2011, 637 . 639 Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2018 641 [RFC7698] Gonzalez de Dios, O., Ed., Casellas, R., Ed., Zhang, F., 642 Fu, X., Ceccarelli, D., and I. Hussain, "Framework and 643 Requirements for GMPLS-Based Control of Flexi-Grid Dense 644 Wavelength Division Multiplexing (DWDM) Networks", 645 RFC 7698, DOI 10.17487/RFC7698, November 2015, 646 . 648 [RFC7699] Farrel, A., King, D., Li, Y., and F. Zhang, "Generalized 649 Labels for the Flexi-Grid in Lambda Switch Capable (LSC) 650 Label Switching Routers", RFC 7699, DOI 10.17487/RFC7699, 651 November 2015, . 653 [RFC7792] Zhang, F., Zhang, X., Farrel, A., Gonzalez de Dios, O., 654 and D. Ceccarelli, "RSVP-TE Signaling Extensions in 655 Support of Flexi-Grid Dense Wavelength Division 656 Multiplexing (DWDM) Networks", RFC 7792, 657 DOI 10.17487/RFC7792, March 2016, 658 . 660 8.2. Informative References 662 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 663 DOI 10.17487/RFC2629, June 1999, 664 . 666 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 667 "Introduction and Applicability Statements for Internet- 668 Standard Management Framework", RFC 3410, 669 DOI 10.17487/RFC3410, December 2002, 670 . 672 [RFC4181] Heard, C., Ed., "Guidelines for Authors and Reviewers of 673 MIB Documents", BCP 111, RFC 4181, DOI 10.17487/RFC4181, 674 September 2005, . 676 Authors' Addresses 678 Gabriele Galimberti (editor) 679 Cisco 680 Via S. Maria Molgora, 48 c 681 20871 - Vimercate 682 Italy 684 Phone: +390392091462 685 Email: ggalimbe@cisco.com 687 Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2018 689 Domenico La Fauci 690 Cisco 691 Via S. Maria Molgora, 48 c 692 20871 - Vimercate 693 Italy 695 Phone: +390392091946 696 Email: dlafauci@cisco.com 698 Andrea Zanardi (editor) 699 FBK-CreateNet 700 via alla Cascata 56/D 701 38123 Povo, Trento 702 Italy 704 Phone: +390461312450 705 Email: azanardi@fbk.eu 707 Lorenzo Galvagni 708 FBK-CreateNet 709 via alla Cascata 56/D 710 38123 Povo, Trento 711 Italy 713 Phone: +390461312427 714 Email: lgalvagni@fbk.eu