idnits 2.17.1 draft-ggalimbe-ccamp-flex-if-lmp-01.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 (March 13, 2017) is 2591 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- == Missing Reference: 'RFC4902' is mentioned on line 82, but not defined == Missing Reference: 'G.694.1' is mentioned on line 188, but not defined == Unused Reference: 'RFC4054' is defined on line 295, but no explicit reference was found in the text == Unused Reference: 'I-D.kdkgall-ccamp-dwdm-if-mng-ctrl-fwk' is defined on line 300, but no explicit reference was found in the text == Unused Reference: 'ITU.G698.2' is defined on line 306, but no explicit reference was found in the text == Unused Reference: 'ITU.G694.1' is defined on line 312, but no explicit reference was found in the text == Unused Reference: 'ITU.G709' is defined on line 317, but no explicit reference was found in the text == Unused Reference: 'ITU.G872' is defined on line 322, but no explicit reference was found in the text == Unused Reference: 'ITU.G874.1' is defined on line 327, but no explicit reference was found in the text == Unused Reference: 'RFC3410' is defined on line 335, but no explicit reference was found in the text == Unused Reference: 'RFC2629' is defined on line 341, but no explicit reference was found in the text == Unused Reference: 'RFC4181' is defined on line 345, 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: September 14, 2017 G. Galimberti, Ed. 6 Cisco 7 R. Kunze 8 Deutsche Telekom 9 D. Beller 10 Nokia 11 March 13, 2017 13 Extension to the Link Management Protocol (LMP/DWDM -rfc4209) for Dense 14 Wavelength Division Multiplexing (DWDM) Optical Line Systems to manage 15 the application code of optical interface parameters in DWDM application 16 draft-ggalimbe-ccamp-flex-if-lmp-01 18 Abstract 20 This experimental memo defines extensions to LMP(rfc4209) for 21 managing Optical parameters associated with Wavelength Division 22 Multiplexing (WDM) adding a set of parameters related to multicarrier 23 DWDM interfaces to be used in Spectrum Switched Optical Networks 24 (sson). 26 Copyright Notice 28 Copyright (c) 2011 IETF Trust and the persons identified as the 29 document authors. All rights reserved. 31 Status of This Memo 33 This Internet-Draft is submitted in full conformance with the 34 provisions of BCP 78 and BCP 79. 36 Internet-Drafts are working documents of the Internet Engineering 37 Task Force (IETF). Note that other groups may also distribute 38 working documents as Internet-Drafts. The list of current Internet- 39 Drafts is at http://datatracker.ietf.org/drafts/current/. 41 Internet-Drafts are draft documents valid for a maximum of six months 42 and may be updated, replaced, or obsoleted by other documents at any 43 time. It is inappropriate to use Internet-Drafts as reference 44 material or to cite them other than as "work in progress." 46 This Internet-Draft will expire on September 14, 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 (http://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. DWDM line system . . . . . . . . . . . . . . . . . . . . . . 3 67 3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 4 68 4. Extensions to LMP-WDM Protocol . . . . . . . . . . . . . . . 4 69 5. Multi carrier Transceiver . . . . . . . . . . . . . . . . . . 5 70 6. Security Considerations . . . . . . . . . . . . . . . . . . . 6 71 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 72 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 7 73 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 74 9.1. Normative References . . . . . . . . . . . . . . . . . . 7 75 9.2. Informative References . . . . . . . . . . . . . . . . . 8 76 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 78 1. Introduction 80 This experimental extension addresses the use cases described by 81 "draft-kdkgall-ccamp-dwdm-if-mng-ctrl-fwk-00" to the Spectrum 82 Switched Optical Network applications. LMP [RFC4902] provides link 83 property correlation capabilities that can be used between a 84 transceiver device and an Optical Line System (OLS) device. Link 85 property correlation is a procedure by which, intrinsic parameters 86 and capabilities are exchanged between two ends of a link. Link 87 property correlation as defined in RFC3591 allows either end of the 88 link to supervise the received signal and operate within a commonly 89 understood parameter window. Here the term 'link' refers in 90 particular to the attachment link between OXC and OLS (see Figure 1). 91 The relevant novelty is the interface configuration having a multiple 92 carrier where the client signal is spread on. The parameters 93 parameters are not yet fully defined by ITU-T do this document can 94 jast be seen as an experimental proposal not binding operators and 95 vendors to require and implement them 97 2. DWDM line system 99 Figure 1 shows a set of reference points (Rs and Ss), for a single- 100 channel connection between transmitter (Tx) and receiver (Rx) 101 devices. Here the DWDM network elements in between those devices 102 include an Optical Multiplexer (OM) and an Optical Demultiplexer 103 (OD). In addition it may include one or more Optical Amplifiers (OA) 104 and one or more Optical Add-Drop Multiplexers (OADM). 106 +-------------------------------------------------+ 107 Ss | DWDM Network Elements | Rs 108 +--+ | | | \ / | | | +--+ 109 Tx L1--|->| \ +------+ +------+ / |--|-->Rx L1 110 +---+ | | | | | +------+ | | | | | +--+ 111 +---+ | | FX | | | | FLEX | | | | FX | | +--+ 112 Tx L2--|->| OM |-->|------|->| OADM |--|------|->| OD |--|-->Rx L2 113 +---+ | | | | | | | | | | | | +--+ 114 +---+ | | | | | +------+ | | | | | +--+ 115 Tx L3--|->| / | DWDM | | ^ | DWDM | \ |--|-->Rx L3 116 +---+ | | / | Link +----|--|----+ Link | \ | | +--+ 117 +-----------+ | | +----------+ 118 +--+ +--+ 119 | | 120 Rs v | Ss 121 +-----+ +-----+ 122 |RxLx | |TxLx | 123 +-----+ +-----+ 125 Ss = Sender reference point at the DWDM network element 126 tributary output, this can be a set of multiple transceivers 127 carrying the same client payload. 128 Rs = Receiver reference point at the DWDM network element 129 tributary input this can be a set of multiple transceivers 130 carrying the same client payload. 132 FX OM = Flex-Spectrum Optical Mux 133 FX OD = Flex-Spectrum Optical Demux 134 Flex OADM = Flex-Spectrum Optical Add Drop Mux 136 extending Fig. 5.1/G.698.2 138 Figure 1: Linear Single Channel approach 140 Figure 2 Extended LMP Model ( from [RFC4209] ) 142 +------+ Ss +------+ +------+ Rs +------+ 143 | | ----- | | | | ----- | | 144 | OXC1 | ----- | OLS1 | ===== | OLS2 | ----- | OXC2 | 145 | | ----- | | | | ----- | | 146 +------+ +------+ +------+ +------+ 147 ^ ^ ^ ^ ^ ^ 148 | | | | | | 149 | +-----LMP-----+ +-----LMP-----+ | 150 | | 151 +----------------------LMP-----------------------+ 153 OXC : is an entity that contains Multiple carriers transponders 154 OLS : generic Flex-Spectrum optical system, it can be - 155 Optical Mux, Optical Demux, Optical Add 156 Drop Mux, Amplifier etc. 157 OLS to OLS: represents the Optical Multiplex section 158 159 Rs/Ss : reference points in between the OXC and the OLS 161 Figure 2: Extended LMP Model 163 3. Use Cases 165 The set of paramentes exchanged between is to support the Spectrum 166 Switched Optical Network in therms of Number of Sub-carriers 167 available at the transceiver , their characteristics to provide the 168 SSON control plane all the information suitable to calculate the 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]. IYU-T working group are working to detail 189 most of parameters and an update of the TLV may be required. 191 The general parameters are 192 1. Modulation identifier: indicates the Transceiver capabilities 193 to support a single or multiple modulation format like: 194 BPSK (1), DC-DP-BSPSK, QPSK, DP-QPSK, QAM16, DP-QAM16, 195 DC-DP-QAM16 196 2. FEC: indicates the FEC types the transceiver can support 197 3. baud rate: number of symbols rate, besically this identify the 198 channel frequency 199 4. Num Carriers: number of subcarriers the trasceiver can support 200 and can be "mapped" in a Mediachannel 201 5. Bits/symbol: number of bit per simbol (aka spectral efficiency) 202 6. Subcarrier band (minimum distance between subcarriers) in GHz 203 7. Guard band (required guard band at the side of media channel) 204 8. Sub-carrier Power: output optical power the transceiver can 205 provide 206 9. Sub-carrier OSNR robustness 208 Figure 3: The format of the this sub-object (Type = TBA, Length = 209 TBA) is as follows: 211 0 1 2 3 212 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 213 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 214 | Type | Length | (Reserved) | 215 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 216 |S|I| Modulation ID | FEC | 217 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 218 | baud rate (Symbol Rate) | 219 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 220 | Number of subcarriers | Bit/Symbol | 221 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 222 | subcarried band | guard band | 223 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 224 | sub-carrier power | 225 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 226 | sub-carrier OSNR | 227 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 229 - S: standardized format; 230 - I: input / output (1 / 0) 231 - Modulation IDs: BPSK (1), DC DP BSPSK, QPSK, DP QPSK, 8QAM 232 16QAM, 64QAM 233 - FEC 234 - baud rate: Symbol Rate IEEE float in bauds/s 235 - Num Carriers 236 - Bits/symbol 237 - Subcarrier band (minimum distance between subcarriers) 238 - Guard band (required guard band at the side of media channel) 239 - Sub-carrier Power 240 - Sub-carrier OSNR robustness 242 Figure 3: Multi carrier Transceiver 244 6. Security Considerations 246 LMP message security uses IPsec, as described in [RFC4204]. This 247 document only defines new LMP objects that are carried in existing 248 LMP messages, similar to the LMP objects in [RFC:4209]. This 249 document does not introduce new security considerations. 251 7. IANA Considerations 253 LMP defines the following name spaces and 254 the ways in which IANA can make assignments to these namespaces: 256 - LMP Message Type 257 - LMP Object Class 258 - LMP Object Class type (C-Type) unique within the Object Class 259 - LMP Sub-object Class type (Type) unique within the Object Class 260 This memo introduces the following new assignments: 262 LMP Sub-Object Class names: 264 under DATA_LINK Class name (as defined in ) 265 - Multi carrier Transceiver (sub-object Type = TBA) 267 8. Contributors 269 Zafar Ali 270 Cisco 271 3000 Innovation Drive 272 KANATA 273 ONTARIO K2K 3E8 274 zali@cisco.com 276 9. References 278 9.1. Normative References 280 [RFC4204] Lang, J., Ed., "Link Management Protocol (LMP)", RFC 4204, 281 DOI 10.17487/RFC4204, October 2005, 282 . 284 [RFC4209] Fredette, A., Ed. and J. Lang, Ed., "Link Management 285 Protocol (LMP) for Dense Wavelength Division Multiplexing 286 (DWDM) Optical Line Systems", RFC 4209, 287 DOI 10.17487/RFC4209, October 2005, 288 . 290 [RFC6205] Otani, T., Ed. and D. Li, Ed., "Generalized Labels for 291 Lambda-Switch-Capable (LSC) Label Switching Routers", 292 RFC 6205, DOI 10.17487/RFC6205, March 2011, 293 . 295 [RFC4054] Strand, J., Ed. and A. Chiu, Ed., "Impairments and Other 296 Constraints on Optical Layer Routing", RFC 4054, 297 DOI 10.17487/RFC4054, May 2005, 298 . 300 [I-D.kdkgall-ccamp-dwdm-if-mng-ctrl-fwk] 301 Kunze, R., Grammel, G., Beller, D., and G. Galimberti, "A 302 framework for Management and Control of G.698.2 optical 303 interface parameters", draft-kdkgall-ccamp-dwdm-if-mng- 304 ctrl-fwk-00 (work in progress), October 2015. 306 [ITU.G698.2] 307 International Telecommunications Union, "Amplified 308 multichannel dense wavelength division multiplexing 309 applications with single channel optical interfaces", 310 ITU-T Recommendation G.698.2, November 2009. 312 [ITU.G694.1] 313 International Telecommunications Union, ""Spectral grids 314 for WDM applications: DWDM frequency grid"", 315 ITU-T Recommendation G.698.2, February 2012. 317 [ITU.G709] 318 International Telecommunications Union, "Interface for the 319 Optical Transport Network (OTN)", ITU-T Recommendation 320 G.709, February 2012. 322 [ITU.G872] 323 International Telecommunications Union, "Architecture of 324 optical transport networks", ITU-T Recommendation G.872, 325 October 2012. 327 [ITU.G874.1] 328 International Telecommunications Union, "Optical transport 329 network (OTN): Protocol-neutral management information 330 model for the network element view", ITU-T Recommendation 331 G.874.1, October 2012. 333 9.2. Informative References 335 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 336 "Introduction and Applicability Statements for Internet- 337 Standard Management Framework", RFC 3410, 338 DOI 10.17487/RFC3410, December 2002, 339 . 341 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 342 DOI 10.17487/RFC2629, June 1999, 343 . 345 [RFC4181] Heard, C., Ed., "Guidelines for Authors and Reviewers of 346 MIB Documents", BCP 111, RFC 4181, DOI 10.17487/RFC4181, 347 September 2005, . 349 Authors' Addresses 351 Dharini Hiremagalur (editor) 352 Juniper 353 1194 N Mathilda Avenue 354 Sunnyvale - 94089 California 355 USA 357 Phone: +1408 358 Email: dharinih@juniper.net 360 Gert Grammel (editor) 361 Juniper 362 Oskar-Schlemmer Str. 15 363 80807 Muenchen 364 Germany 366 Phone: +49 1725186386 367 Email: ggrammel@juniper.net 369 Gabriele Galimberti (editor) 370 Cisco 371 Via S. Maria Molgora, 48 372 20871 - Vimercate 373 Italy 375 Phone: +390392091462 376 Email: ggalimbe@cisco.com 378 Ruediger Kunze 379 Deutsche Telekom 380 Dddd, xx 381 Berlin 382 Germany 384 Phone: +49xxxxxxxxxx 385 Email: RKunze@telekom.de 386 Dieter Beller 387 Nokia 388 Lorenzstrasse, 10 389 70435 Stuttgart 390 Germany 392 Phone: +4971182143125 393 Email: Dieter.Beller@nokia.com