idnits 2.17.1
draft-dharinigert-ccamp-dwdm-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 :
----------------------------------------------------------------------------
** The abstract seems to contain references ([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 17, 2016) is 2962 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: 'RFC4902' is mentioned on line 85, but not defined
== Missing Reference: 'ITU.G959.1' is mentioned on line 180, but not defined
== Missing Reference: 'G.694.1' is mentioned on line 189, but not defined
== Unused Reference: 'RFC4054' is defined on line 463, but no explicit
reference was found in the text
== Unused Reference: 'I-D.kdkgall-ccamp-dwdm-if-mng-ctrl-fwk' is defined on
line 468, but no explicit reference was found in the text
== Unused Reference: 'ITU.G698.2' is defined on line 474, but no explicit
reference was found in the text
== Unused Reference: 'ITU.G709' is defined on line 485, but no explicit
reference was found in the text
== Unused Reference: 'ITU.G872' is defined on line 490, but no explicit
reference was found in the text
== Unused Reference: 'ITU.G874.1' is defined on line 495, but no explicit
reference was found in the text
== Unused Reference: 'RFC3410' is defined on line 503, but no explicit
reference was found in the text
== Unused Reference: 'RFC2629' is defined on line 509, but no explicit
reference was found in the text
== Unused Reference: 'RFC4181' is defined on line 513, but no explicit
reference was found in the text
** Downref: Normative reference to an Informational RFC: RFC 4054
== Outdated reference: A later version (-01) exists of
draft-kdkgall-ccamp-dwdm-if-mng-ctrl-fwk-00
** Downref: Normative reference to an Informational draft:
draft-kdkgall-ccamp-dwdm-if-mng-ctrl-fwk (ref.
'I-D.kdkgall-ccamp-dwdm-if-mng-ctrl-fwk')
-- 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'
-- Obsolete informational reference (is this intentional?): RFC 2629
(Obsoleted by RFC 7749)
Summary: 3 errors (**), 0 flaws (~~), 14 warnings (==), 7 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 Juniper
5 Expires: September 18, 2016 G. Galimberti, Ed.
6 Z. Ali, Ed.
7 Cisco
8 R. Kunze, Ed.
9 Deutsche Telekom
10 D. Beller, Ed.
11 ALU
12 March 17, 2016
14 Extension to the Link Management Protocol (LMP/DWDM -rfc4209) for Dense
15 Wavelength Division Multiplexing (DWDM) Optical Line Systems to manage
16 the application code of optical interface parameters in DWDM application
17 draft-dharinigert-ccamp-dwdm-if-lmp-01
19 Abstract
21 This memo defines extensions to LMP(rfc4209) for managing Optical
22 parameters associated with Wavelength Division Multiplexing (WDM)
23 systems in accordance with the Interface Application Identifier
24 approach defined in ITU-T Recommendation G.694.1.[ITU.G694.1] and its
25 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 18, 2016.
49 Copyright Notice
51 Copyright (c) 2016 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. DWDM line system . . . . . . . . . . . . . . . . . . . . . . 3
68 3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 4
69 4. Extensions to LMP-WDM Protocol . . . . . . . . . . . . . . . 4
70 5. General Parameters - OCh_General . . . . . . . . . . . . . . 5
71 6. ApplicationIdentifier - OCh_ApplicationIdentifier . . . . . . 6
72 7. OCh_Ss - OCh transmit parameters . . . . . . . . . . . . . . 9
73 8. OCh_Rs - receive parameters . . . . . . . . . . . . . . . . . 9
74 9. Security Considerations . . . . . . . . . . . . . . . . . . . 10
75 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
76 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 10
77 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
78 12.1. Normative References . . . . . . . . . . . . . . . . . . 11
79 12.2. Informative References . . . . . . . . . . . . . . . . . 12
80 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
82 1. Introduction
84 This extension addresses the use cases described by "draft-kdkgall-
85 ccamp-dwdm-if-mng-ctrl-fwk-00". LMP [RFC4902] provides link property
86 correlation capabilities that can be used between a transceiver
87 device and an Optical Line System (OLS) device. Link property
88 correlation is a procedure by which, intrinsic parameters and
89 capabilities are exchanged between two ends of a link. Link property
90 correlation as defined in RFC3591 allows either end of the link to
91 supervise the received signal and operate within a commonly
92 understood parameter window. Here the term 'link' refers in
93 particular to the attachment link between OXC and OLS (see Figure 1).
94 The relevant interface parameters are in line with "draft-galikunze-
95 ccamp-dwdm-if-snmp-mib-01" and "draft-dharini-ccamp-dwdm-if-yang-00".
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 +---+ | | | | | | | | | | | | +--+
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
127 Rs = Receiver reference point at the DWDM network element
128 tributary input
129 Lx = Lambda x
130 OM = Optical Mux
131 OD = Optical Demux
132 OADM = Optical Add Drop Mux
134 from 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 transponders
152 OLS : generic 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 use cases are described in draft-kdkgall-ccamp-dwdm-if-mng-ctrl-
164 fwk
166 4. Extensions to LMP-WDM Protocol
168 This document defines extensions to [RFC4209] to allow a set of
169 characteristic parameters, to be exchanged between a router or
170 optical switch and the optical line system to which it is attached.
171 In particular, this document defines additional Data Link sub-objects
172 to be carried in the LinkSummary message defined in [RFC4204] and
173 [RFC6205]. The OXC and OLS systems may be managed by different
174 Network management systems and hence may not know the capability and
175 status of their peer. These messages and their usage are defined in
176 subsequent sections of this document.
178 The following new messages are defined for the WDM extension for
179 ITU-T G.698.2 [ITU.G698.2]/ITU-T G.698.1 [ITU.G698.1]/
180 ITU-T G.959.1 [ITU.G959.1]
181 - OCh_General (sub-object Type = TBA)
182 - OCh_ApplicationIdentier (sub-object Type = TBA)
183 - OCh_Ss (sub-object Type = TBA)
184 - OCh_Rs (sub-object Type = TBA)
186 5. General Parameters - OCh_General
188 These are a set of general parameters as described in [G698.2] and
189 [G.694.1]. Please refer to the "draft-galikunze-ccamp-dwdm-if-snmp-
190 mib-01" and "draft-dharini-ccamp-dwdm-if-yang-00" for more details
191 about these parameters and the [RFC6205] for the wavelength
192 definition.
194 The general parameters are
195 1. Central Frequency - (Tera Hz) 4 bytes (see RFC6205 sec.3.2)
196 2. Number of Application Identifiers (A.I.) Supported
197 3. Single-channel Application Identifier in use
198 4. Application Identifier Type in use
199 5. Application Identifier in use
201 Figure 3: The format of the this sub-object (Type = TBA, Length =
202 TBA) is as follows:
204 0 1 2 3
205 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
206 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
207 | Type | Length | (Reserved) |
208 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
209 | Central Frequency |
210 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
211 | Number of Application | |
212 | Identifiers Supported | (Reserved) |
213 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
214 | Single-channel| A.I. Type | A.I. length |
215 | Application | in use | |
216 | Identifier | | |
217 | Number in use | | |
218 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
219 | Single-channel Application Identifier in use |
220 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
221 | Single-channel Application Identifier in use |
222 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
223 | Single-channel Application Identifier in use |
224 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
225 A.I. Type in use: STANDARD, PROPRIETARY
227 A.I. Type in use: STANDARD
229 Refer to G.698.2 recommendation : B-DScW-ytz(v)
231 0 1 2 3
232 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
233 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
234 | Single-channel Application Code |
235 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
236 | Single-channel Application Code |
237 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
238 | Single-channel Application Code |
239 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
241 A.I. Type in use: PROPRIETARY
243 Note: if the A.I. type = PROPRIETARY, the first 6 Octets of the
244 Application Identifier in use are six characters of the
245 PrintableString must contain the Hexadecimal representation of
246 an OUI (Organizationally Unique Identifier) assigned to the
247 vendor whose implementation generated the Application
248 Identifier; the remaining octets of the PrintableString are
249 unspecified.
251 0 1 2 3
252 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
253 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
254 | OUI |
255 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
256 | OUI cont. | Vendor value |
257 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
258 | Vendor Value |
259 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
261 Figure 3: OCh_General
263 6. ApplicationIdentifier - OCh_ApplicationIdentifier
265 This message is to exchange the application identifiers supported as
266 described in [G698.2]. There can be more than one Application
267 Identifier supported by the transmitter/receiver in the OXC. The
268 number of application identifiers supported is exchanged in the
269 "OCh_General" message. (from [G698.1]/[G698.2]/[G959.1] and G.874.1
270 )
271 The parameters are
272 1. Number of Application Identifiers (A.I.) Supported
274 2. Single-channel application identifier Number
275 uniquely identifiers this entry - 8 bits
277 3. Application Indentifier Type (A.I.) (STANDARD/PROPRIETARY)
279 4. Single-channel application identifier -- 96 bits
280 (from [G698.1]/[G698.2]/[G959.1]
282 - this parameter can have
283 multiple instances as the transceiver can support multiple
284 application identifiers.
286 Figure 4: The format of the this sub-object (Type = TBA, Length =
287 TBA) is as follows:
289 0 1 2 3
290 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
291 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
292 | Type | Length | (Reserved) |
293 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
294 | Number of Application | |
295 | Identifiers Supported | (Reserved) |
296 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
297 | Single-channel| A.I. Type | A.I. length |
298 | Application | | |
299 | Identifier | | |
300 | Number | | |
301 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
302 | Single-channel Application Identifier |
303 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
304 | Single-channel Application Identifier |
305 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
306 | Single-channel Application Identifier |
307 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
308 // .... //
309 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
310 | Single-channel| | A.I. length |
311 | Application | A.I. Type | |
312 | Identifier | | |
313 | Number | | |
314 | | | |
315 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
316 | Single-channel Application Identifier |
317 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
318 | Single-channel Application Identifier |
319 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
320 | Single-channel Application Identifier |
321 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
323 A.I. Type in use: STANDARD, PROPRIETARY
325 A.I. Type in use: STANDARD
326 Refer to G.698.2 recommendation : B-DScW-ytz(v)
328 0 1 2 3
329 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
330 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
331 | Single-channel Application Code |
332 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
333 | Single-channel Application Code |
334 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
335 | Single-channel Application Code |
336 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
338 A.I. Type in use: PROPRIETARY
340 Note: if the A.I. type = PROPRIETARY, the first 6 Octets of the
341 Application Identifier in use are six characters of the
342 PrintableString must contain the Hexadecimal representation of
343 an OUI (Organizationally Unique Identifier) assigned to the
344 vendor whose implementation generated the Application
345 Identifier; the remaining octets of the PrintableString are
346 unspecified.
348 0 1 2 3
349 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
350 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
351 | OUI |
352 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
353 | OUI cont. | Vendor value |
354 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
355 | Vendor Value |
356 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
358 Figure 4: OCh_ApplicationIdentifier
360 7. OCh_Ss - OCh transmit parameters
362 These are the G.698.2 parameters at the Source(Ss reference points).
363 Please refer to "draft-galikunze-ccamp-dwdm-if-snmp-mib-01" for more
364 details about these parameters.
366 1. Output power
368 Figure 5: The format of the OCh sub-object (Type = TBA, Length = TBA)
369 is as follows:
371 0 1 2 3
372 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
373 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
374 | Type | Length | (Reserved) |
375 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
376 | Output Power |
377 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
379 Figure 5: OCh_Ss transmit parameters
381 8. OCh_Rs - receive parameters
383 These are the G.698.2 parameters at the Sink (Rs reference points).
385 1. Current Input Power - (0.1dbm) 4bytes
387 Figure 6: The format of the OCh receive sub-object (Type = TBA,
388 Length = TBA) is as follows:
390 The format of the OCh receive/OLS Sink sub-object (Type = TBA,
391 Length = TBA) is as follows:
393 0 1 2 3
394 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
395 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
396 | Type | Length | (Reserved) |
397 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
398 | Current Input Power |
399 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
401 Figure 6: OCh_Rs receive parameters
403 9. Security Considerations
405 LMP message security uses IPsec, as described in [RFC4204]. This
406 document only defines new LMP objects that are carried in existing
407 LMP messages, similar to the LMP objects in [RFC:4209]. This
408 document does not introduce new security considerations.
410 10. IANA Considerations
412 LMP defines the following name spaces and
413 the ways in which IANA can make assignments to these namespaces:
415 - LMP Message Type
416 - LMP Object Class
417 - LMP Object Class type (C-Type) unique within the Object Class
418 - LMP Sub-object Class type (Type) unique within the Object Class
419 This memo introduces the following new assignments:
421 LMP Sub-Object Class names:
423 under DATA_LINK Class name (as defined in )
424 - OCh_General (sub-object Type = TBA)
425 - OCh_ApplicationIdentifier (sub-object Type = TBA)
426 - OCh_Ss (sub-object Type = TBA)
427 - OCh_Rs (sub-object Type = TBA)
429 11. Contributors
431 Arnold Mattheus
432 Deutsche Telekom
433 Darmstadt
434 Germany
435 email a.mattheus@telekom.de
437 John E. Drake
438 Juniper
439 1194 N Mathilda Avenue
440 HW-US,Pennsylvania
441 USA
442 jdrake@juniper.net
444 12. References
446 12.1. Normative References
448 [RFC4204] Lang, J., Ed., "Link Management Protocol (LMP)", RFC 4204,
449 DOI 10.17487/RFC4204, October 2005,
450 .
452 [RFC4209] Fredette, A., Ed. and J. Lang, Ed., "Link Management
453 Protocol (LMP) for Dense Wavelength Division Multiplexing
454 (DWDM) Optical Line Systems", RFC 4209,
455 DOI 10.17487/RFC4209, October 2005,
456 .
458 [RFC6205] Otani, T., Ed. and D. Li, Ed., "Generalized Labels for
459 Lambda-Switch-Capable (LSC) Label Switching Routers",
460 RFC 6205, DOI 10.17487/RFC6205, March 2011,
461 .
463 [RFC4054] Strand, J., Ed. and A. Chiu, Ed., "Impairments and Other
464 Constraints on Optical Layer Routing", RFC 4054,
465 DOI 10.17487/RFC4054, May 2005,
466 .
468 [I-D.kdkgall-ccamp-dwdm-if-mng-ctrl-fwk]
469 Kunze, R., Grammel, G., Beller, D., and G. Galimberti, "A
470 framework for Management and Control of G.698.2 optical
471 interface parameters", draft-kdkgall-ccamp-dwdm-if-mng-
472 ctrl-fwk-00 (work in progress), October 2015.
474 [ITU.G698.2]
475 International Telecommunications Union, "Amplified
476 multichannel dense wavelength division multiplexing
477 applications with single channel optical interfaces",
478 ITU-T Recommendation G.698.2, November 2009.
480 [ITU.G694.1]
481 International Telecommunications Union, ""Spectral grids
482 for WDM applications: DWDM frequency grid"",
483 ITU-T Recommendation G.698.2, February 2012.
485 [ITU.G709]
486 International Telecommunications Union, "Interface for the
487 Optical Transport Network (OTN)", ITU-T Recommendation
488 G.709, February 2012.
490 [ITU.G872]
491 International Telecommunications Union, "Architecture of
492 optical transport networks", ITU-T Recommendation G.872,
493 October 2012.
495 [ITU.G874.1]
496 International Telecommunications Union, "Optical transport
497 network (OTN): Protocol-neutral management information
498 model for the network element view", ITU-T Recommendation
499 G.874.1, October 2012.
501 12.2. Informative References
503 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
504 "Introduction and Applicability Statements for Internet-
505 Standard Management Framework", RFC 3410,
506 DOI 10.17487/RFC3410, December 2002,
507 .
509 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
510 DOI 10.17487/RFC2629, June 1999,
511 .
513 [RFC4181] Heard, C., Ed., "Guidelines for Authors and Reviewers of
514 MIB Documents", BCP 111, RFC 4181, DOI 10.17487/RFC4181,
515 September 2005, .
517 Authors' Addresses
519 Dharini Hiremagalur (editor)
520 Juniper
521 1194 N Mathilda Avenue
522 Sunnyvale - 94089 California
523 USA
525 Phone: +1408
526 Email: dharinih@juniper.net
528 Gert Grammel (editor)
529 Juniper
530 Oskar-Schlemmer Str. 15
531 80807 Muenchen
532 Germany
534 Phone: +49 1725186386
535 Email: ggrammel@juniper.net
536 Gabriele Galimberti (editor)
537 Cisco
538 Via S. Maria Molgora, 48
539 20871 - Vimercate
540 Italy
542 Phone: +390392091462
543 Email: ggalimbe@cisco.com
545 Zafar Ali (editor)
546 Cisco
547 3000 Innovation Drive
548 KANATA
549 ONTARIO K2K 3E8
551 Email: zali@cisco.com
553 Ruediger Kunze (editor)
554 Deutsche Telekom
555 Dddd, xx
556 Berlin
557 Germany
559 Phone: +49xxxxxxxxxx
560 Email: RKunze@telekom.de
562 Dieter Beller (editor)
563 ALU
564 Lorenzstrasse, 10
565 70435 Stuttgart
566 Germany
568 Phone: +4971182143125
569 Email: Dieter.Beller@alcatel-lucent.com