idnits 2.17.1 draft-dharinigert-ccamp-g-698-2-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 : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([ITU.G698.2], [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 date (March 6, 2015) is 3332 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'ITU.G959.1' is mentioned on line 142, but not defined == Missing Reference: 'G.694.1' is mentioned on line 151, but not defined == Unused Reference: 'RFC4054' is defined on line 409, but no explicit reference was found in the text == Unused Reference: 'ITU.G709' is defined on line 423, but no explicit reference was found in the text == Unused Reference: 'ITU.G872' is defined on line 428, but no explicit reference was found in the text == Unused Reference: 'ITU.G874.1' is defined on line 433, but no explicit reference was found in the text == Unused Reference: 'I-D.galimbe-kunze-g-698-2-snmp-mib' is defined on line 441, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 4054 -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU.G698.2' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU.G694.1' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU.G709' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU.G872' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU.G874.1' Summary: 2 errors (**), 0 flaws (~~), 8 warnings (==), 6 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: Standards Track J. Drake, Ed. 5 Expires: September 7, 2015 Juniper 6 G. Galimberti, Ed. 7 Z. Ali, Ed. 8 Cisco 9 R. Kunze, Ed. 10 Deutsche Telekom 11 March 6, 2015 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-dharinigert-ccamp-g-698-2-lmp-09 18 Abstract 20 This memo defines extensions to LMP(rfc4209) for managing Optical 21 parameters associated with Wavelength Division Multiplexing (WDM) 22 systems or characterized by the Optical Transport Network (OTN) in 23 accordance with the Interface Application Code approach defined in 24 ITU-T Recommendation G.698.2.[ITU.G698.2], G.694.1.[ITU.G694.1] and 25 its extensions. 27 Copyright Notice 29 Copyright (c) 2011 IETF Trust and the persons identified as the 30 document authors. All rights reserved. 32 Status of This Memo 34 This Internet-Draft is submitted in full conformance with the 35 provisions of BCP 78 and BCP 79. 37 Internet-Drafts are working documents of the Internet Engineering 38 Task Force (IETF). Note that other groups may also distribute 39 working documents as Internet-Drafts. The list of current Internet- 40 Drafts is at http://datatracker.ietf.org/drafts/current/. 42 Internet-Drafts are draft documents valid for a maximum of six months 43 and may be updated, replaced, or obsoleted by other documents at any 44 time. It is inappropriate to use Internet-Drafts as reference 45 material or to cite them other than as "work in progress." 47 This Internet-Draft will expire on September 7, 2015. 49 Copyright Notice 51 Copyright (c) 2015 IETF Trust and the persons identified as the 52 document authors. All rights reserved. 54 This document is subject to BCP 78 and the IETF Trust's Legal 55 Provisions Relating to IETF Documents 56 (http://trustee.ietf.org/license-info) in effect on the date of 57 publication of this document. Please review these documents 58 carefully, as they describe your rights and restrictions with respect 59 to this document. Code Components extracted from this document must 60 include Simplified BSD License text as described in Section 4.e of 61 the Trust Legal Provisions and are provided without warranty as 62 described in the Simplified BSD License. 64 Table of Contents 66 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 67 2. Extensions to LMP-WDM Protocol . . . . . . . . . . . . . . . 3 68 3. General Parameters - OCh_General . . . . . . . . . . . . . . 4 69 4. ApplicationIdentifier - OCh_ApplicationIdentifier . . . . . . 5 70 5. OCh_Ss - OCh transmit parameters . . . . . . . . . . . . . . 8 71 6. OCh_Rs - receive parameters . . . . . . . . . . . . . . . . . 8 72 7. Security Considerations . . . . . . . . . . . . . . . . . . . 9 73 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 74 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 75 9.1. Normative References . . . . . . . . . . . . . . . . . . 10 76 9.2. Informative References . . . . . . . . . . . . . . . . . 11 77 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 79 1. Introduction 81 This extension is based on "draft-galikunze-ccamp-g-698-2-snmp-mib- 82 09", for the relevant interface optical parameters described in 83 recommendations like ITU-T G.698.2 [ITU.G698.2] and 84 G.694.1.[ITU.G694.1]. The LMP Model from RFC4902 provides link 85 property correlation between a client and an OLS device. LMP link 86 property correlation, exchanges the capabilities of either end of the 87 link where the term 'link' refers to the attachment link between OXC 88 and OLS (see Figure 1). By performing link property correlation, 89 both ends of the link exchange link properties, such as application 90 identifiers. This allows either end to operate within a commonly 91 understood parameter window. Based on known parameter limits, each 92 device can supervise the received signal for conformance using 93 mechanisms defined in RFC3591. For example if the Client transmitter 94 power (OXC1) has a value of 0dBm and the ROADM interface measured 95 power (at OLS1) is -6dBm the fiber patch cord connecting the two 96 nodes may be pinched or the connectors are dirty. More, the 97 interface characteristics can be used by the OLS network Control 98 Plane in order to check the Optical Channels feasibility. Finally 99 the OXC1 transceivers parameters (Application Code) can be shared 100 with OXC2 using the LMP protocol to verify the Transceivers 101 compatibility. The actual route selection of a specific wavelength 102 within the allowed set is outside the scope of LMP. In GMPLS, the 103 parameter selection (e.g. central frequency) is performed by RSVP-TE. 105 Figure 1 Extended LMP Model ( from [RFC4209] ) 107 +------+ Ss +------+ +------+ Rs +------+ 108 | | ----- | | | | ----- | | 109 | OXC1 | ----- | OLS1 | ===== | OLS2 | ----- | OXC2 | 110 | | ----- | | | | ----- | | 111 +------+ +------+ +------+ +------+ 112 ^ ^ ^ ^ ^ ^ 113 | | | | | | 114 | +-----LMP-----+ +-----LMP-----+ | 115 | | 116 +----------------------LMP-----------------------+ 118 OXC : is an entity that contains transponders 119 OLS : generic optical system, it can be - 120 Optical Mux, Optical Demux, Optical Add 121 Drop Mux, etc. 122 OLS to OLS : represents the black-Link itself 123 Rs/Ss : in between the OXC and the OLS 125 Figure 1: Extended LMP Model 127 2. Extensions to LMP-WDM Protocol 129 This document defines extensions to [RFC4209] to allow the Black Link 130 (BL) parameters of G.698.2, to be exchanged between a router or 131 optical switch and the optical line system to which it is attached. 132 In particular, this document defines additional Data Link sub-objects 133 to be carried in the LinkSummary message defined in [RFC4204] and 134 [RFC6205]. The OXC and OLS systems may be managed by different 135 Network management systems and hence may not know the capability and 136 status of their peer. The intent of this draft is to enable the OXC 137 and OLS systems to exchange this information. These messages and 138 their usage are defined in subsequent sections of this document. 140 The following new messages are defined for the WDM extension for 141 ITU-T G.698.2 [ITU.G698.2]/ITU-T G.698.1 [ITU.G698.1]/ 142 ITU-T G.959.1 [ITU.G959.1] 143 - OCh_General (sub-object Type = TBA) 144 - OCh_ApplicationIdentier (sub-object Type = TBA) 145 - OCh_Ss (sub-object Type = TBA) 146 - OCh_Rs (sub-object Type = TBA) 148 3. General Parameters - OCh_General 150 These are the general parameters as described in [G698.2] and 151 [G.694.1]. Please refer to the "draft-galikunze-ccamp-g-698-2-snmp- 152 mib-09" for more details about these parameters and the [RFC6205] for 153 the wavelength definition. 155 The general parameters are 156 1. Central Frequency - (Tera Hertz) 4 bytes (see RFC6205 sec.3.2) 157 2. Number of Application Identifiers (A.I.) Supported 158 3. Single-channel Application Identifier in use 159 4. Application Identifier Type in use 160 5. Application Identifier in use 162 Figure 2: The format of the this sub-object (Type = TBA, Length = 163 TBA) is as follows: 165 0 1 2 3 166 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 167 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 168 | Type | Length | (Reserved) | 169 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 170 | Central Frequency | 171 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 172 | Number of Application | | 173 | Identifiers Supported | (Reserved) | 174 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 175 | Single-channel| A.I. Type | A.I. length | 176 | Application | in use | | 177 | Identifier | | | 178 | Number in use | | | 179 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 180 | Single-channel Application Identifier in use | 181 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 182 | Single-channel Application Identifier in use | 183 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 184 | Single-channel Application Identifier in use | 185 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 186 A.I. Type in use: STANDARD, PROPRIETARY 188 A.I. Type in use: STANDARD 190 Refer to G.698.2 recommendation : B-DScW-ytz(v) 192 0 1 2 3 193 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 194 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 195 | Single-channel Application Code | 196 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 197 | Single-channel Application Code | 198 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 199 | Single-channel Application Code | 200 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 202 A.I. Type in use: PROPRIETARY 204 Note: if the A.I. type = PROPRIETARY, the first 6 Octets of the 205 Application Identifier in use are six characters of the 206 PrintableString must contain the Hexadecimal representation of 207 an OUI (Organizationally Unique Identifier) assigned to the 208 vendor whose implementation generated the Application 209 Identifier; the remaining octets of the PrintableString are 210 unspecified. 212 0 1 2 3 213 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 214 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 215 | OUI | 216 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 217 | OUI cont. | Vendor value | 218 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 219 | Vendor Value | 220 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 222 Figure 2: OCh_General 224 4. ApplicationIdentifier - OCh_ApplicationIdentifier 226 This message is to exchange the application identifiers supported as 227 described in [G698.2]. Please refer to the "draft-galikunze-ccamp- 228 g-698-2-snmp-mib-09". For more details about these parameters. 229 There can be more than one Application Identifier supported by the 230 OXC/OLS. The number of application identifiers supported is 231 exchanged in the "OCh_General" message. (from 232 [G698.1]/[G698.2]/[G959.1] and G.874.1 ) 234 The parameters are 235 1. Number of Application Identifiers (A.I.) Supported 237 2. Single-channel application identifier Number 238 uniquely identifiers this entry - 8 bits 240 3. Application Indentifier Type (A.I.) (STANDARD/PROPRIETARY) 242 4. Single-channel application identifier -- 96 bits 243 (from [G698.1]/[G698.2]/[G959.1] 245 - this parameter can have 246 multiple instances as the transceiver can support multiple 247 application identifiers. 249 Figure 3: The format of the this sub-object (Type = TBA, Length = 250 TBA) is as follows: 252 0 1 2 3 253 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 254 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 255 | Type | Length | (Reserved) | 256 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 257 | Number of Application | | 258 | Identifiers Supported | (Reserved) | 259 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 260 | Single-channel| A.I. Type | A.I. length | 261 | Application | | | 262 | Identifier | | | 263 | Number | | | 264 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 265 | Single-channel Application Identifier | 266 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 267 | Single-channel Application Identifier | 268 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 269 | Single-channel Application Identifier | 270 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 271 // .... // 272 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 273 | Single-channel| | A.I. length | 274 | Application | A.I. Type | | 275 | Identifier | | | 276 | Number | | | 277 | | | | 278 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 279 | Single-channel Application Identifier | 280 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 281 | Single-channel Application Identifier | 282 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 283 | Single-channel Application Identifier | 284 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 286 A.I. Type in use: STANDARD, PROPRIETARY 288 A.I. Type in use: STANDARD 289 Refer to G.698.2 recommendation : B-DScW-ytz(v) 291 0 1 2 3 292 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 293 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 294 | Single-channel Application Code | 295 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 296 | Single-channel Application Code | 297 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 298 | Single-channel Application Code | 299 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 301 A.I. Type in use: PROPRIETARY 303 Note: if the A.I. type = PROPRIETARY, the first 6 Octets of the 304 Application Identifier in use are six characters of the 305 PrintableString must contain the Hexadecimal representation of 306 an OUI (Organizationally Unique Identifier) assigned to the 307 vendor whose implementation generated the Application 308 Identifier; the remaining octets of the PrintableString are 309 unspecified. 311 0 1 2 3 312 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 313 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 314 | OUI | 315 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 316 | OUI cont. | Vendor value | 317 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 318 | Vendor Value | 319 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 321 Figure 3: OCh_ApplicationIdentifier 323 5. OCh_Ss - OCh transmit parameters 325 These are the G.698.2 parameters at the Source(Ss reference points). 326 Please refer to "draft-galikunze-ccamp-g-698-2-snmp-mib-09" for more 327 details about these parameters. 329 1. Output power 331 Figure 4: The format of the OCh sub-object (Type = TBA, Length = TBA) 332 is as follows: 334 0 1 2 3 335 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 336 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 337 | Type | Length | (Reserved) | 338 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 339 | Output Power | 340 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 342 Figure 4: OCh_Ss transmit parameters 344 6. OCh_Rs - receive parameters 346 These are the G.698.2 parameters at the Sink (Rs reference points). 347 Please refer to the "draft-galikunze-ccamp-g-698-2-snmp-mib-09" for 348 more details about these parameters. 350 1. Current Input Power - (0.1dbm) 4bytes 352 Figure 5: The format of the OCh receive sub-object (Type = TBA, 353 Length = TBA) is as follows: 355 The format of the OCh receive/OLS Sink sub-object (Type = TBA, 356 Length = TBA) is as follows: 358 0 1 2 3 359 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 360 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 361 | Type | Length | (Reserved) | 362 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 363 | Current Input Power | 364 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 366 Figure 5: OCh_Rs receive parameters 368 7. Security Considerations 370 LMP message security uses IPsec, as described in [RFC4204]. This 371 document only defines new LMP objects that are carried in existing 372 LMP messages, similar to the LMP objects in [RFC:4209]. This 373 document does not introduce new security considerations. 375 8. IANA Considerations 377 LMP defines the following name spaces and 378 the ways in which IANA can make assignments to these namespaces: 380 - LMP Message Type 381 - LMP Object Class 382 - LMP Object Class type (C-Type) unique within the Object Class 383 - LMP Sub-object Class type (Type) unique within the Object Class 384 This memo introduces the following new assignments: 386 LMP Sub-Object Class names: 388 under DATA_LINK Class name (as defined in ) 389 - OCh_General (sub-object Type = TBA) 390 - OCh_ApplicationIdentifier (sub-object Type = TBA) 391 - OCh_Ss (sub-object Type = TBA) 392 - OCh_Rs (sub-object Type = TBA) 394 9. References 396 9.1. Normative References 398 [RFC4204] Lang, J., "Link Management Protocol (LMP)", RFC 4204, 399 October 2005. 401 [RFC4209] Fredette, A. and J. Lang, "Link Management Protocol (LMP) 402 for Dense Wavelength Division Multiplexing (DWDM) Optical 403 Line Systems", RFC 4209, October 2005. 405 [RFC6205] Otani, T. and D. Li, "Generalized Labels for Lambda- 406 Switch-Capable (LSC) Label Switching Routers", RFC 6205, 407 March 2011. 409 [RFC4054] Strand, J. and A. Chiu, "Impairments and Other Constraints 410 on Optical Layer Routing", RFC 4054, May 2005. 412 [ITU.G698.2] 413 International Telecommunications Union, "Amplified 414 multichannel dense wavelength division multiplexing 415 applications with single channel optical interfaces", 416 ITU-T Recommendation G.698.2, November 2009. 418 [ITU.G694.1] 419 International Telecommunications Union, ""Spectral grids 420 for WDM applications: DWDM frequency grid"", ITU-T 421 Recommendation G.698.2, February 2012. 423 [ITU.G709] 424 International Telecommunications Union, "Interface for the 425 Optical Transport Network (OTN)", ITU-T Recommendation 426 G.709, February 2012. 428 [ITU.G872] 429 International Telecommunications Union, "Architecture of 430 optical transport networks", ITU-T Recommendation G.872, 431 October 2012. 433 [ITU.G874.1] 434 International Telecommunications Union, "Optical transport 435 network (OTN): Protocol-neutral management information 436 model for the network element view", ITU-T Recommendation 437 G.874.1, October 2012. 439 9.2. Informative References 441 [I-D.galimbe-kunze-g-698-2-snmp-mib] 442 Kunze, R. and D. Hiremagalur, "A SNMP MIB to manage black- 443 link optical interface parameters of DWDM applications", 444 draft-galimbe-kunze-g-698-2-snmp-mib-02 (work in 445 progress), March 2012. 447 Authors' Addresses 449 Dharini Hiremagalur (editor) 450 Juniper 451 1194 N Mathilda Avenue 452 Sunnyvale - 94089 California 453 USA 455 Phone: +1408 456 Email: dharinih@juniper.net 458 Gert Grammel (editor) 459 Juniper 460 Oskar-Schlemmer Str. 15 461 80807 Muenchen 462 Germany 464 Phone: +49 1725186386 465 Email: ggrammel@juniper.net 467 John E. Drake (editor) 468 Juniper 469 1194 N Mathilda Avenue 470 HW-US,Pennsylvania 471 USA 473 Phone: +1408 474 Email: jdrake@juniper.net 476 Gabriele Galimberti (editor) 477 Cisco 478 Via S. Maria Molgora, 48 479 20871 - Vimercate 480 Italy 482 Phone: +390392091462 483 Email: ggalimbe@cisco.com 484 Zafar Ali (editor) 485 Cisco 486 3000 Innovation Drive 487 KANATA 488 ONTARIO K2K 3E8 490 Email: zali@cisco.com 492 Ruediger Kunze (editor) 493 Deutsche Telekom 494 Dddd, xx 495 Berlin 496 Germany 498 Phone: +49xxxxxxxxxx 499 Email: RKunze@telekom.de