idnits 2.17.1 draft-ggalimbe-ccamp-flex-if-lmp-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 : ---------------------------------------------------------------------------- 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 (June 30, 2017) is 2492 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 186, but not defined == Unused Reference: 'I-D.kdkgall-ccamp-dwdm-if-mng-ctrl-fwk' is defined on line 285, but no explicit reference was found in the text == Unused Reference: 'ITU.G694.1' is defined on line 291, but no explicit reference was found in the text == Unused Reference: 'ITU.G698.2' is defined on line 296, but no explicit reference was found in the text == Unused Reference: 'ITU.G709' is defined on line 302, but no explicit reference was found in the text == Unused Reference: 'ITU.G872' is defined on line 307, but no explicit reference was found in the text == Unused Reference: 'ITU.G874.1' is defined on line 312, but no explicit reference was found in the text == Unused Reference: 'RFC4054' is defined on line 318, but no explicit reference was found in the text == Unused Reference: 'RFC2629' is defined on line 340, but no explicit reference was found in the text == Unused Reference: 'RFC3410' is defined on line 344, but no explicit reference was found in the text == Unused Reference: 'RFC4181' is defined on line 350, but no explicit reference was found in the text == Outdated reference: A later version (-01) exists of draft-kdkgall-ccamp-dwdm-if-mng-ctrl-fwk-00 -- Obsolete informational reference (is this intentional?): RFC 2629 (Obsoleted by RFC 7749) Summary: 0 errors (**), 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 D. Hiremagalur, Ed. 3 Internet-Draft G. Grammel, Ed. 4 Intended status: Experimental Juniper 5 Expires: January 1, 2018 G. Galimberti, Ed. 6 Cisco 7 R. Kunze 8 Deutsche Telekom 9 June 30, 2017 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-02 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 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 January 1, 2018. 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. 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 . . . . . . . . . . . . . . . . . . . 6 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-kdkgall-ccamp-dwdm-if-mng-ctrl-fwk-00" to the Spectrum 80 Switched Optical Network applications. LMP [RFC4902] provides link 81 property correlation capabilities that can be used between a 82 transceiver device and an Optical Line System (OLS) device. Link 83 property correlation is a procedure by which, intrinsic parameters 84 and capabilities are exchanged between two ends of a link. Link 85 property correlation as defined in RFC3591 allows either end of the 86 link to 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 91 parameters are not yet fully defined by ITU-T do this document can 92 jast be seen as an experimental proposal not binding operators and 93 vendors to require and 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 OADM = Flex-Spectrum Optical Add Drop Mux 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 is to support the Spectrum 164 Switched Optical Network in therms of Number of Sub-carriers 165 available at the transceiver , their characteristics to provide the 166 SSON control plane all the information suitable to calculate the 168 4. Extensions to LMP-WDM Protocol 170 This document defines extensions to [RFC4209] to allow a set of 171 characteristic parameters, to be exchanged between a router or 172 optical switch and the optical line system to which it is attached. 173 In particular, this document defines additional Data Link sub-objects 174 to be carried in the LinkSummary message defined in [RFC4204] and 175 [RFC6205]. The OXC and OLS systems may be managed by different 176 Network management systems and hence may not know the capability and 177 status of their peer. These messages and their usage are defined in 178 subsequent sections of this document. 180 The following new messages are defined for the SSON extension 181 - Multi carrier Transceiver (sub-object Type = TBA) 183 5. Multi carrier Transceiver 185 These are a set of general parameters extending the description in 186 [G698.2] and [G.694.1]. IYU-T working group are working to detail 187 most of parameters and an update of the TLV may be required. 189 The general parameters are 190 1. Modulation identifier: indicates the Transceiver capabilities 191 to support a single or multiple modulation format like: 192 BPSK (1), DC-DP-BSPSK, QPSK, DP-QPSK, QAM16, DP-QAM16, 193 DC-DP-QAM16 194 2. FEC: indicates the FEC types the transceiver can support 195 3. baud rate: number of symbols rate, besically this identify the 196 channel frequency 197 4. Num Carriers: number of subcarriers the trasceiver can support 198 and can be "mapped" in a Mediachannel 199 5. Bits/symbol: number of bit per simbol (aka spectral efficiency) 200 6. Subcarrier band (minimum distance between subcarriers) in GHz 201 7. Guard band (required guard band at the side of media channel) 202 8. Sub-carrier TX Power: output optical power the transceiver can 203 provide 204 9. Sub-carrier RX Power: Input optical power Range the transceiver can 205 support, this is known also as Sensitivity 206 10. Sub-carrier OSNR robustness 207 Figure 3: The format of the this sub-object (Type = TBA, Length = 208 TBA) is as follows: 210 0 1 2 3 211 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 212 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 213 | Type | Length | (Reserved) | 214 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 215 |S|I| Modulation ID | FEC | 216 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 217 | baud rate (Symbol Rate) | 218 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 219 | Number of subcarriers | Bit/Symbol | 220 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 221 | subcarrier band | guard band | 222 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 223 | sub-carrier TX power | 224 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 225 | sub-carrier RX power HIGH | 226 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 227 | sub-carrier RX power LOW | 228 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 229 | sub-carrier OSNR | 230 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 232 - S: standardized format; 233 - I: input / output (1 / 0) 234 - Modulation IDs: BPSK (1), DC DP BSPSK, QPSK, DP QPSK, 8QAM 235 16QAM, 64QAM 236 - FEC 237 - baud rate: Symbol Rate IEEE float in bauds/s 238 - Num Carriers 239 - Bits/symbol 240 - Subcarrier band (minimum distance between subcarriers) 241 - Guard band (required guard band at the side of media channel) 242 - Sub-carrier Transmit Power 243 - Sub-carrier Receive HIGH Power range (Sensitivity) 244 - Sub-carrier Receive LOW Power range (Sensitivity) 245 - Sub-carrier OSNR robustness 247 Figure 3: Multi carrier Transceiver 249 6. Security Considerations 251 LMP message security uses IPsec, as described in [RFC4204]. This 252 document only defines new LMP objects that are carried in existing 253 LMP messages, similar to the LMP objects in [RFC:4209]. This 254 document does not introduce new security considerations. 256 7. IANA Considerations 258 LMP defines the following name spaces and 259 the ways in which IANA can make assignments to these namespaces: 261 - LMP Message Type 262 - LMP Object Class 263 - LMP Object Class type (C-Type) unique within the Object Class 264 - LMP Sub-object Class type (Type) unique within the Object Class 265 This memo introduces the following new assignments: 267 LMP Sub-Object Class names: 269 under DATA_LINK Class name (as defined in ) 270 - Multi carrier Transceiver (sub-object Type = TBA) 272 8. Contributors 274 Zafar Ali 275 Cisco 276 3000 Innovation Drive 277 KANATA 278 ONTARIO K2K 3E8 279 zali@cisco.com 281 9. References 283 9.1. Normative References 285 [I-D.kdkgall-ccamp-dwdm-if-mng-ctrl-fwk] 286 Kunze, R., Grammel, G., Beller, D., and G. Galimberti, "A 287 framework for Management and Control of G.698.2 optical 288 interface parameters", draft-kdkgall-ccamp-dwdm-if-mng- 289 ctrl-fwk-00 (work in progress), October 2015. 291 [ITU.G694.1] 292 International Telecommunications Union, ""Spectral grids 293 for WDM applications: DWDM frequency grid"", 294 ITU-T Recommendation G.698.2, February 2012. 296 [ITU.G698.2] 297 International Telecommunications Union, "Amplified 298 multichannel dense wavelength division multiplexing 299 applications with single channel optical interfaces", 300 ITU-T Recommendation G.698.2, November 2009. 302 [ITU.G709] 303 International Telecommunications Union, "Interface for the 304 Optical Transport Network (OTN)", ITU-T Recommendation 305 G.709, February 2012. 307 [ITU.G872] 308 International Telecommunications Union, "Architecture of 309 optical transport networks", ITU-T Recommendation G.872, 310 October 2012. 312 [ITU.G874.1] 313 International Telecommunications Union, "Optical transport 314 network (OTN): Protocol-neutral management information 315 model for the network element view", ITU-T Recommendation 316 G.874.1, October 2012. 318 [RFC4054] Strand, J., Ed. and A. Chiu, Ed., "Impairments and Other 319 Constraints on Optical Layer Routing", RFC 4054, 320 DOI 10.17487/RFC4054, May 2005, 321 . 323 [RFC4204] Lang, J., Ed., "Link Management Protocol (LMP)", RFC 4204, 324 DOI 10.17487/RFC4204, October 2005, 325 . 327 [RFC4209] Fredette, A., Ed. and J. Lang, Ed., "Link Management 328 Protocol (LMP) for Dense Wavelength Division Multiplexing 329 (DWDM) Optical Line Systems", RFC 4209, 330 DOI 10.17487/RFC4209, October 2005, 331 . 333 [RFC6205] Otani, T., Ed. and D. Li, Ed., "Generalized Labels for 334 Lambda-Switch-Capable (LSC) Label Switching Routers", 335 RFC 6205, DOI 10.17487/RFC6205, March 2011, 336 . 338 9.2. Informative References 340 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 341 DOI 10.17487/RFC2629, June 1999, 342 . 344 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 345 "Introduction and Applicability Statements for Internet- 346 Standard Management Framework", RFC 3410, 347 DOI 10.17487/RFC3410, December 2002, 348 . 350 [RFC4181] Heard, C., Ed., "Guidelines for Authors and Reviewers of 351 MIB Documents", BCP 111, RFC 4181, DOI 10.17487/RFC4181, 352 September 2005, . 354 Authors' Addresses 356 Dharini Hiremagalur (editor) 357 Juniper 358 1194 N Mathilda Avenue 359 Sunnyvale - 94089 California 360 USA 362 Phone: +1408 363 Email: dharinih@juniper.net 365 Gert Grammel (editor) 366 Juniper 367 Oskar-Schlemmer Str. 15 368 80807 Muenchen 369 Germany 371 Phone: +49 1725186386 372 Email: ggrammel@juniper.net 374 Gabriele Galimberti (editor) 375 Cisco 376 Via S. Maria Molgora, 48 377 20871 - Vimercate 378 Italy 380 Phone: +390392091462 381 Email: ggalimbe@cisco.com 382 Ruediger Kunze 383 Deutsche Telekom 384 Dddd, xx 385 Berlin 386 Germany 388 Phone: +49xxxxxxxxxx 389 Email: RKunze@telekom.de