idnits 2.17.1 draft-ggalimbe-ccamp-flex-if-lmp-09.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (November 4, 2019) is 1633 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- == Missing Reference: 'RFC4902' is mentioned on line 80, but not defined == Missing Reference: 'G.694.1' is mentioned on line 188, but not defined == Unused Reference: 'ITU.G694.1' is defined on line 321, but no explicit reference was found in the text == Unused Reference: 'ITU.G698.2' is defined on line 326, but no explicit reference was found in the text == Unused Reference: 'ITU.G709' is defined on line 332, but no explicit reference was found in the text == Unused Reference: 'ITU.G872' is defined on line 337, but no explicit reference was found in the text == Unused Reference: 'ITU.G874.1' is defined on line 342, but no explicit reference was found in the text == Unused Reference: 'RFC2629' is defined on line 365, but no explicit reference was found in the text == Unused Reference: 'RFC3410' is defined on line 369, but no explicit reference was found in the text == Unused Reference: 'RFC4181' is defined on line 375, but no explicit reference was found in the text -- Obsolete informational reference (is this intentional?): RFC 2629 (Obsoleted by RFC 7749) Summary: 0 errors (**), 0 flaws (~~), 11 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force D. Hiremagalur, Ed. 3 Internet-Draft G. Grammel, Ed. 4 Intended status: Experimental Juniper 5 Expires: May 7, 2020 G. Galimberti, Ed. 6 Cisco 7 R. Kunze, Ed. 8 Deutsche Telekom 9 November 4, 2019 11 Extension to the Link Management Protocol (LMP/DWDM -rfc4209) for Dense 12 Wavelength Division Multiplexing (DWDM) Optical Line Systems to manage 13 the application code of optical interface parameters in DWDM application 14 draft-ggalimbe-ccamp-flex-if-lmp-09 16 Abstract 18 This experimental memo defines extensions to LMP(rfc4209) for 19 managing Optical parameters associated with Wavelength Division 20 Multiplexing (WDM) adding a set of parameters related to multicarrier 21 DWDM interfaces to be used in Spectrum Switched Optical Networks 22 (sson). 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 7, 2020. 46 Copyright Notice 48 Copyright (c) 2019 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 (https://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. DWDM line system . . . . . . . . . . . . . . . . . . . . . . 3 65 3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 4 66 4. Extensions to LMP-WDM Protocol . . . . . . . . . . . . . . . 4 67 5. Multi carrier Transceiver . . . . . . . . . . . . . . . . . . 5 68 6. Security Considerations . . . . . . . . . . . . . . . . . . . 7 69 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 70 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 7 71 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 72 9.1. Normative References . . . . . . . . . . . . . . . . . . 7 73 9.2. Informative References . . . . . . . . . . . . . . . . . 8 74 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 76 1. Introduction 78 This experimental extension addresses the use cases described by 79 "draft-ietf-ccamp-dwdm-if-lmp" and extend it to the Spectrum Switched 80 Optical Network applications. LMP [RFC4902] provides link property 81 correlation capabilities that can be used between a transceiver 82 device and an Optical Line System (OLS) device. Link property 83 correlation is a procedure by which, intrinsic parameters and 84 capabilities are exchanged between two ends of a link. Link property 85 correlation as defined in RFC4204 allows either end of the link to 86 supervise the received signal and operate within a commonly 87 understood parameter window. Here the term 'link' refers in 88 particular to the attachment link between OXC and OLS (see Figure 1). 89 The relevant novelty is the interface configuration having a multiple 90 carrier where the client signal is spread on. The parameters are not 91 yet fully defined by ITU-, so this document can jast be seen as an 92 experimental proposal not binding operators and vendors to comply and 93 implement them 95 2. DWDM line system 97 Figure 1 shows a set of reference points (Rs and Ss), for a single- 98 channel connection between transmitter (Tx) and receiver (Rx) 99 devices. Here the DWDM network elements in between those devices 100 include an Optical Multiplexer (OM) and an Optical Demultiplexer 101 (OD). In addition it may include one or more Optical Amplifiers (OA) 102 and one or more Optical Add-Drop Multiplexers (OADM). 104 +-------------------------------------------------+ 105 Ss | DWDM Network Elements | Rs 106 +--+ | | | \ / | | | +--+ 107 Tx L1--|->| \ +------+ +------+ / |--|-->Rx L1 108 +---+ | | | | | +------+ | | | | | +--+ 109 +---+ | | FX | | | | FLEX | | | | FX | | +--+ 110 Tx L2--|->| OM |-->|------|->|ROADM |--|------|->| OD |--|-->Rx L2 111 +---+ | | | | | | | | | | | | +--+ 112 +---+ | | | | | +------+ | | | | | +--+ 113 Tx L3--|->| / | DWDM | | ^ | DWDM | \ |--|-->Rx L3 114 +---+ | | / | Link +----|--|----+ Link | \ | | +--+ 115 +-----------+ | | +----------+ 116 +--+ +--+ 117 | | 118 Rs v | Ss 119 +-----+ +-----+ 120 |RxLx | |TxLx | 121 +-----+ +-----+ 123 Ss = Sender reference point at the DWDM network element 124 tributary output, this can be a set of multiple transceivers 125 carrying the same client payload. 126 Rs = Receiver reference point at the DWDM network element 127 tributary input this can be a set of multiple transceivers 128 carrying the same client payload. 130 FX OM = Flex-Spectrum Optical Mux 131 FX OD = Flex-Spectrum Optical Demux 132 Flex ROADM = Flex-Spectrum Optical Add Drop Mux (reconfigurable) 134 extending Fig. 5.1/G.698.2 136 Figure 1: Linear Single Channel approach 138 Figure 2 Extended LMP Model ( from [RFC4209] ) 140 +------+ Ss +------+ +------+ Rs +------+ 141 | | ----- | | | | ----- | | 142 | OXC1 | ----- | OLS1 | ===== | OLS2 | ----- | OXC2 | 143 | | ----- | | | | ----- | | 144 +------+ +------+ +------+ +------+ 145 ^ ^ ^ ^ ^ ^ 146 | | | | | | 147 | +-----LMP-----+ +-----LMP-----+ | 148 | | 149 +----------------------LMP-----------------------+ 151 OXC : is an entity that contains Multiple carriers transponders 152 OLS : generic Flex-Spectrum optical system, it can be - 153 Optical Mux, Optical Demux, Optical Add 154 Drop Mux, Amplifier etc. 155 OLS to OLS: represents the Optical Multiplex section 156 157 Rs/Ss : reference points in between the OXC and the OLS 159 Figure 2: Extended LMP Model 161 3. Use Cases 163 The set of paramentes exchanged between OXC and OLS is to support the 164 Spectrum Switched Optical Network in therms of Number of Sub-carriers 165 available at the transceiver and their characteristics to provide the 166 SSON control plane all the information suitable to calculate the path 167 and the optical feasibility. This draft extends the "draft-ietf- 168 ccamp-dwdm-if-lmp" to sson applications. 170 4. Extensions to LMP-WDM Protocol 172 This document defines extensions to [RFC4209] to allow a set of 173 characteristic parameters, to be exchanged between a router or 174 optical switch and the optical line system to which it is attached. 175 In particular, this document defines additional Data Link sub-objects 176 to be carried in the LinkSummary message defined in [RFC4204] and 177 [RFC6205]. The OXC and OLS systems may be managed by different 178 Network management systems and hence may not know the capability and 179 status of their peer. These messages and their usage are defined in 180 subsequent sections of this document. 182 The following new messages are defined for the SSON extension 183 - Multi carrier Transceiver (sub-object Type = TBA) 185 5. Multi carrier Transceiver 187 These are a set of general parameters extending the description in 188 [G698.2] and [G.694.1]. ITU-T working groups are working to detail 189 most of parameters and an update of the TLV may be required. 191 Other than the Application Identifier described in [G698.2] and 192 draft-dharinigert-ccamp-dwdm-if-lmp the parameters to describe a 193 multicarrier transceiver are describes as follows: 195 1. Modulation format: indicates the Transceiver capabilities 196 to support a single or multiple modulation format like: 197 BPSK, DC-DP-BSPSK, QPSK, DP-QPSK, QAM16, DP-QAM16, 198 DC-DP-QAM16, 64QAM. Hybrid modulation format are supported as 199 well and the parameter is given in bit per symbol. 200 2. FEC: indicates the FEC types the transceiver can support 201 3. baud rate: symbols rate, basically this identify the 202 channel symbols number per second 203 4. Num Carriers: number of (sub)carriers the trasceiver can support 204 and can be "mapped" in a Mediachannel 205 5. Bits/symbol: number of bit per simbol - fractional in case of 206 hybrid modulation format. (aka spectral efficiency) 207 6. Subcarrier band (minimum distance between subcarriers) in GHz 208 7. Guard band (required guard band at the side of media channel) 209 8. Sub-carrier TX Power: output optical power the transceiver can 210 provide 211 9. Sub-carrier RX Power: Input optical power Range the transceiver 212 can support, this is known also as Sensitivity 213 10 Max-pol-power-difference: max power difference between the 214 polarised components 215 11 Max-pol-skew-difference: maw Skew between polarised signal and 216 subcarriers supported by the transceiver 217 12. Sub-carrier OSNR robustness 219 Figure 3: The format of the this sub-object (Type = TBA, Length = 220 TBA) is as follows: 222 0 1 2 3 223 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 224 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 225 | Type | Length | (Reserved) | 226 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 227 |S|I| Modulation ID | FEC | 228 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 229 | baud rate (Symbol Rate) | 230 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 231 | Number of subcarriers | Bit/Symbol | 232 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 233 | subcarrier band | guard band | 234 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 235 | sub-carrier TX power | 236 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 237 | sub-carrier RX power HIGH | 238 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 239 | sub-carrier RX power LOW | 240 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 241 | Max-pol-power-difference | 242 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 243 | Max-pol-skew-difference | 244 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 245 | sub-carrier OSNR | 246 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 248 - S: standardized format; 249 - I: input / output (1 / 0) 250 - Modulation ID (Format) : is the modulation type: 251 BPSK, DC DP BSPSK, QPSK, DP QPSK, 8QAM, 16QAM, 252 32QAM, 64QAM, etc. 253 - (ITU-T reference) 254 - value > 32768 (first bit is 1): custom defined values 255 Value 0 is reserved to be used if no value is defined 256 - FEC: the signal Forward Error Corrections type (16-bit 257 unsigned integer), the defined values are: 258 - (ITU-T reference) 259 - 32768 (first bit is 1): custom defined values 260 Value 0 is reserved to be used if no value is defined 261 - Baud Rate: the signal symbol rate (IEEE 32-bit float, 262 in bauds/s) 263 Value 0 is reserved to be used if no value is defined 264 - Num Carriers 265 - Bits/symbol(BPS) this indicates the bit per symbol in case of 266 hybrid modulation format. It is an off-set with values from 0 267 to 127 to be applied to the specified Modulation Format and 268 indicates the mix between the selected Modulation Format and its 269 upper adjacent. 270 (e.g. QPSK + 63 BPS indicates that there is a 50% MIX between 271 QPSK and 8-QAM = 2.5 bits per symbol) If value = 0 the 272 standard Modulation Format is applied 273 - Subcarrier band (minimum distance between subcarriers) 274 - Guard band (required guard band at the side of media channel) 275 - Sub-carrier Transmit Power 276 - Sub-carrier Receive HIGH Power range (Sensitivity) 277 - Sub-carrier Receive LOW Power range (Sensitivity) 278 - Sub-carrier OSNR robustness 279 - Max-pol-power-difference 280 - Max-pol-skew-difference 281 - Sub-carrier OSNR 283 Figure 3: Multi carrier Transceiver 285 6. Security Considerations 287 LMP message security uses IPsec, as described in [RFC4204]. This 288 document only defines new LMP objects that are carried in existing 289 LMP messages, similar to the LMP objects in [RFC:4209]. This 290 document does not introduce new security considerations. 292 7. IANA Considerations 294 LMP defines the following name spaces and 295 the ways in which IANA can make assignments to these namespaces: 297 - LMP Message Type 298 - LMP Object Class 299 - LMP Object Class type (C-Type) unique within the Object Class 300 - LMP Sub-object Class type (Type) unique within the Object Class 301 This memo introduces the following new assignments: 303 LMP Sub-Object Class names: 305 under DATA_LINK Class name (as defined in ) 306 - Multi carrier Transceiver (sub-object Type = TBA) 308 8. Contributors 310 Zafar Ali 311 Cisco 312 3000 Innovation Drive 313 KANATA 314 ONTARIO K2K 3E8 315 zali@cisco.com 317 9. References 319 9.1. Normative References 321 [ITU.G694.1] 322 International Telecommunications Union, ""Spectral grids 323 for WDM applications: DWDM frequency grid"", 324 ITU-T Recommendation G.698.2, February 2012. 326 [ITU.G698.2] 327 International Telecommunications Union, "Amplified 328 multichannel dense wavelength division multiplexing 329 applications with single channel optical interfaces", 330 ITU-T Recommendation G.698.2, November 2009. 332 [ITU.G709] 333 International Telecommunications Union, "Interface for the 334 Optical Transport Network (OTN)", ITU-T Recommendation 335 G.709, June 2016. 337 [ITU.G872] 338 International Telecommunications Union, "Architecture of 339 optical transport networks", ITU-T Recommendation G.872, 340 January 2017. 342 [ITU.G874.1] 343 International Telecommunications Union, "Optical transport 344 network (OTN): Protocol-neutral management information 345 model for the network element view", ITU-T Recommendation 346 G.874.1, November 2016. 348 [RFC4204] Lang, J., Ed., "Link Management Protocol (LMP)", RFC 4204, 349 DOI 10.17487/RFC4204, October 2005, 350 . 352 [RFC4209] Fredette, A., Ed. and J. Lang, Ed., "Link Management 353 Protocol (LMP) for Dense Wavelength Division Multiplexing 354 (DWDM) Optical Line Systems", RFC 4209, 355 DOI 10.17487/RFC4209, October 2005, 356 . 358 [RFC6205] Otani, T., Ed. and D. Li, Ed., "Generalized Labels for 359 Lambda-Switch-Capable (LSC) Label Switching Routers", 360 RFC 6205, DOI 10.17487/RFC6205, March 2011, 361 . 363 9.2. Informative References 365 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 366 DOI 10.17487/RFC2629, June 1999, 367 . 369 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 370 "Introduction and Applicability Statements for Internet- 371 Standard Management Framework", RFC 3410, 372 DOI 10.17487/RFC3410, December 2002, 373 . 375 [RFC4181] Heard, C., Ed., "Guidelines for Authors and Reviewers of 376 MIB Documents", BCP 111, RFC 4181, DOI 10.17487/RFC4181, 377 September 2005, . 379 Authors' Addresses 381 Dharini Hiremagalur (editor) 382 Juniper 383 1194 N Mathilda Avenue 384 Sunnyvale - 94089 California 385 USA 387 Phone: +1408 388 Email: dharinih@juniper.net 390 Gert Grammel (editor) 391 Juniper 392 Oskar-Schlemmer Str. 15 393 80807 Muenchen 394 Germany 396 Phone: +49 1725186386 397 Email: ggrammel@juniper.net 399 Gabriele Galimberti (editor) 400 Cisco 401 Via S. Maria Molgora, 48 c 402 20871 - Vimercate 403 Italy 405 Phone: +390392091462 406 Email: ggalimbe@cisco.com 407 Ruediger Kunze (editor) 408 Deutsche Telekom 409 Winterfeldtstr. 21-27 410 10781 Berlin 411 Germany 413 Phone: +491702275321 414 Email: RKunze@telekom.de