idnits 2.17.1
draft-dharinigert-ccamp-dwdm-if-lmp-00.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 (October 19, 2015) is 3104 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 181, but not defined
== Missing Reference: 'G.694.1' is mentioned on line 190, but not defined
== Unused Reference: 'RFC4054' is defined on line 464, but no explicit
reference was found in the text
== Unused Reference: 'I-D.kdkgall-ccamp-dwdm-if-mng-ctrl-fwk' is defined on
line 469, but no explicit reference was found in the text
== Unused Reference: 'ITU.G698.2' is defined on line 475, but no explicit
reference was found in the text
== Unused Reference: 'ITU.G709' is defined on line 486, but no explicit
reference was found in the text
== Unused Reference: 'ITU.G872' is defined on line 491, but no explicit
reference was found in the text
== Unused Reference: 'ITU.G874.1' is defined on line 496, but no explicit
reference was found in the text
== Unused Reference: 'RFC3410' is defined on line 504, but no explicit
reference was found in the text
== Unused Reference: 'RFC2629' is defined on line 510, but no explicit
reference was found in the text
== Unused Reference: 'RFC4181' is defined on line 514, 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: April 21, 2016 G. Galimberti, Ed.
6 Z. Ali, Ed.
7 Cisco
8 R. Kunze, Ed.
9 Deutsche Telekom
10 D. Beller, Ed.
11 ALU
12 October 19, 2015
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-00
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 April 21, 2016.
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. 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-00" and "draft-dharini-netmod-ext-xponder-
96 yang-00".
98 2. DWDM line system
100 Figure 1 shows a set of reference points (Rs and Ss), for a single-
101 channel connection between transmitter (Tx) and receiver (Rx)
102 devices. Here the DWDM network elements in between those devices
103 include an Optical Multiplexer (OM) and an Optical Demultiplexer
104 (OD). In addition it may include one or more Optical Amplifiers (OA)
105 and one or more Optical Add-Drop Multiplexers (OADM).
107 +-------------------------------------------------+
108 Ss | DWDM Network Elements | Rs
109 +--+ | | | \ / | | | +--+
110 Tx L1--|->| \ +------+ +------+ / |--|-->Rx L1
111 +---+ | | | | | +------+ | | | | | +--+
112 +---+ | | | | | | | | | | | | +--+
113 Tx L2--|->| OM |-->|------|->| OADM |--|------|->| OD |--|-->Rx L2
114 +---+ | | | | | | | | | | | | +--+
115 +---+ | | | | | +------+ | | | | | +--+
116 Tx L3--|->| / | DWDM | | ^ | DWDM | \ |--|-->Rx L3
117 +---+ | | / | Link +----|--|----+ Link | \ | | +--+
118 +-----------+ | | +----------+
119 +--+ +--+
120 | |
121 Rs v | Ss
122 +-----+ +-----+
123 |RxLx | |TxLx |
124 +-----+ +-----+
126 Ss = Sender reference point at the DWDM network element
127 tributary output
128 Rs = Receiver reference point at the DWDM network element
129 tributary input
130 Lx = Lambda x
131 OM = Optical Mux
132 OD = Optical Demux
133 OADM = Optical Add Drop Mux
135 from Fig. 5.1/G.698.2
137 Figure 1: Linear Single Channel approach
139 Figure 2 Extended LMP Model ( from [RFC4209] )
141 +------+ Ss +------+ +------+ Rs +------+
142 | | ----- | | | | ----- | |
143 | OXC1 | ----- | OLS1 | ===== | OLS2 | ----- | OXC2 |
144 | | ----- | | | | ----- | |
145 +------+ +------+ +------+ +------+
146 ^ ^ ^ ^ ^ ^
147 | | | | | |
148 | +-----LMP-----+ +-----LMP-----+ |
149 | |
150 +----------------------LMP-----------------------+
152 OXC : is an entity that contains transponders
153 OLS : generic optical system, it can be -
154 Optical Mux, Optical Demux, Optical Add
155 Drop Mux, Amplifier etc.
156 OLS to OLS : represents the Optical Multiplex section
157
158 Rs/Ss : reference points in between the OXC and the OLS
160 Figure 2: Extended LMP Model
162 3. Use Cases
164 The use cases are described in draft-kdkgall-ccamp-dwdm-if-mng-ctrl-
165 fwk
167 4. Extensions to LMP-WDM Protocol
169 This document defines extensions to [RFC4209] to allow a set of
170 characteristic parameters, to be exchanged between a router or
171 optical switch and the optical line system to which it is attached.
172 In particular, this document defines additional Data Link sub-objects
173 to be carried in the LinkSummary message defined in [RFC4204] and
174 [RFC6205]. The OXC and OLS systems may be managed by different
175 Network management systems and hence may not know the capability and
176 status of their peer. These messages and their usage are defined in
177 subsequent sections of this document.
179 The following new messages are defined for the WDM extension for
180 ITU-T G.698.2 [ITU.G698.2]/ITU-T G.698.1 [ITU.G698.1]/
181 ITU-T G.959.1 [ITU.G959.1]
182 - OCh_General (sub-object Type = TBA)
183 - OCh_ApplicationIdentier (sub-object Type = TBA)
184 - OCh_Ss (sub-object Type = TBA)
185 - OCh_Rs (sub-object Type = TBA)
187 5. General Parameters - OCh_General
189 These are a set of general parameters as described in [G698.2] and
190 [G.694.1]. Please refer to the "draft-galikunze-ccamp-g-698-2-snmp-
191 mib-12" and "draft-dharini-netmod-g-698-2-yang-05" for more details
192 about these parameters and the [RFC6205] for the wavelength
193 definition.
195 The general parameters are
196 1. Central Frequency - (Tera Hz) 4 bytes (see RFC6205 sec.3.2)
197 2. Number of Application Identifiers (A.I.) Supported
198 3. Single-channel Application Identifier in use
199 4. Application Identifier Type in use
200 5. Application Identifier in use
202 Figure 3: The format of the this sub-object (Type = TBA, Length =
203 TBA) is as follows:
205 0 1 2 3
206 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
207 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
208 | Type | Length | (Reserved) |
209 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
210 | Central Frequency |
211 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
212 | Number of Application | |
213 | Identifiers Supported | (Reserved) |
214 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
215 | Single-channel| A.I. Type | A.I. length |
216 | Application | in use | |
217 | Identifier | | |
218 | Number in use | | |
219 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
220 | Single-channel Application Identifier in use |
221 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
222 | Single-channel Application Identifier in use |
223 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
224 | Single-channel Application Identifier in use |
225 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
226 A.I. Type in use: STANDARD, PROPRIETARY
228 A.I. Type in use: STANDARD
230 Refer to G.698.2 recommendation : B-DScW-ytz(v)
232 0 1 2 3
233 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
234 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
235 | Single-channel Application Code |
236 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
237 | Single-channel Application Code |
238 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
239 | Single-channel Application Code |
240 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
242 A.I. Type in use: PROPRIETARY
244 Note: if the A.I. type = PROPRIETARY, the first 6 Octets of the
245 Application Identifier in use are six characters of the
246 PrintableString must contain the Hexadecimal representation of
247 an OUI (Organizationally Unique Identifier) assigned to the
248 vendor whose implementation generated the Application
249 Identifier; the remaining octets of the PrintableString are
250 unspecified.
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 | OUI |
256 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
257 | OUI cont. | Vendor value |
258 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
259 | Vendor Value |
260 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
262 Figure 3: OCh_General
264 6. ApplicationIdentifier - OCh_ApplicationIdentifier
266 This message is to exchange the application identifiers supported as
267 described in [G698.2]. There can be more than one Application
268 Identifier supported by the transmitter/receiver in the OXC. The
269 number of application identifiers supported is exchanged in the
270 "OCh_General" message. (from [G698.1]/[G698.2]/[G959.1] and G.874.1
271 )
272 The parameters are
273 1. Number of Application Identifiers (A.I.) Supported
275 2. Single-channel application identifier Number
276 uniquely identifiers this entry - 8 bits
278 3. Application Indentifier Type (A.I.) (STANDARD/PROPRIETARY)
280 4. Single-channel application identifier -- 96 bits
281 (from [G698.1]/[G698.2]/[G959.1]
283 - this parameter can have
284 multiple instances as the transceiver can support multiple
285 application identifiers.
287 Figure 4: The format of the this sub-object (Type = TBA, Length =
288 TBA) is as follows:
290 0 1 2 3
291 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
292 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
293 | Type | Length | (Reserved) |
294 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
295 | Number of Application | |
296 | Identifiers Supported | (Reserved) |
297 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
298 | Single-channel| A.I. Type | A.I. length |
299 | Application | | |
300 | Identifier | | |
301 | Number | | |
302 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
303 | Single-channel Application Identifier |
304 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
305 | Single-channel Application Identifier |
306 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
307 | Single-channel Application Identifier |
308 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
309 // .... //
310 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
311 | Single-channel| | A.I. length |
312 | Application | A.I. Type | |
313 | Identifier | | |
314 | Number | | |
315 | | | |
316 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
317 | Single-channel Application Identifier |
318 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
319 | Single-channel Application Identifier |
320 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
321 | Single-channel Application Identifier |
322 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
324 A.I. Type in use: STANDARD, PROPRIETARY
326 A.I. Type in use: STANDARD
327 Refer to G.698.2 recommendation : B-DScW-ytz(v)
329 0 1 2 3
330 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
331 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
332 | Single-channel Application Code |
333 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
334 | Single-channel Application Code |
335 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
336 | Single-channel Application Code |
337 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
339 A.I. Type in use: PROPRIETARY
341 Note: if the A.I. type = PROPRIETARY, the first 6 Octets of the
342 Application Identifier in use are six characters of the
343 PrintableString must contain the Hexadecimal representation of
344 an OUI (Organizationally Unique Identifier) assigned to the
345 vendor whose implementation generated the Application
346 Identifier; the remaining octets of the PrintableString are
347 unspecified.
349 0 1 2 3
350 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
351 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
352 | OUI |
353 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
354 | OUI cont. | Vendor value |
355 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
356 | Vendor Value |
357 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
359 Figure 4: OCh_ApplicationIdentifier
361 7. OCh_Ss - OCh transmit parameters
363 These are the G.698.2 parameters at the Source(Ss reference points).
364 Please refer to "draft-galikunze-ccamp-g-698-2-snmp-mib-11" for more
365 details about these parameters.
367 1. Output power
369 Figure 5: The format of the OCh sub-object (Type = TBA, Length = TBA)
370 is as follows:
372 0 1 2 3
373 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
374 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
375 | Type | Length | (Reserved) |
376 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
377 | Output Power |
378 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
380 Figure 5: OCh_Ss transmit parameters
382 8. OCh_Rs - receive parameters
384 These are the G.698.2 parameters at the Sink (Rs reference points).
386 1. Current Input Power - (0.1dbm) 4bytes
388 Figure 6: The format of the OCh receive sub-object (Type = TBA,
389 Length = TBA) is as follows:
391 The format of the OCh receive/OLS Sink sub-object (Type = TBA,
392 Length = TBA) is as follows:
394 0 1 2 3
395 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
396 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
397 | Type | Length | (Reserved) |
398 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
399 | Current Input Power |
400 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
402 Figure 6: OCh_Rs receive parameters
404 9. Security Considerations
406 LMP message security uses IPsec, as described in [RFC4204]. This
407 document only defines new LMP objects that are carried in existing
408 LMP messages, similar to the LMP objects in [RFC:4209]. This
409 document does not introduce new security considerations.
411 10. IANA Considerations
413 LMP defines the following name spaces and
414 the ways in which IANA can make assignments to these namespaces:
416 - LMP Message Type
417 - LMP Object Class
418 - LMP Object Class type (C-Type) unique within the Object Class
419 - LMP Sub-object Class type (Type) unique within the Object Class
420 This memo introduces the following new assignments:
422 LMP Sub-Object Class names:
424 under DATA_LINK Class name (as defined in )
425 - OCh_General (sub-object Type = TBA)
426 - OCh_ApplicationIdentifier (sub-object Type = TBA)
427 - OCh_Ss (sub-object Type = TBA)
428 - OCh_Rs (sub-object Type = TBA)
430 11. Contributors
432 Arnold Mattheus
433 Deutsche Telekom
434 Darmstadt
435 Germany
436 email a.mattheus@telekom.de
438 John E. Drake
439 Juniper
440 1194 N Mathilda Avenue
441 HW-US,Pennsylvania
442 USA
443 jdrake@juniper.net
445 12. References
447 12.1. Normative References
449 [RFC4204] Lang, J., Ed., "Link Management Protocol (LMP)", RFC 4204,
450 DOI 10.17487/RFC4204, October 2005,
451 .
453 [RFC4209] Fredette, A., Ed. and J. Lang, Ed., "Link Management
454 Protocol (LMP) for Dense Wavelength Division Multiplexing
455 (DWDM) Optical Line Systems", RFC 4209,
456 DOI 10.17487/RFC4209, October 2005,
457 .
459 [RFC6205] Otani, T., Ed. and D. Li, Ed., "Generalized Labels for
460 Lambda-Switch-Capable (LSC) Label Switching Routers",
461 RFC 6205, DOI 10.17487/RFC6205, March 2011,
462 .
464 [RFC4054] Strand, J., Ed. and A. Chiu, Ed., "Impairments and Other
465 Constraints on Optical Layer Routing", RFC 4054,
466 DOI 10.17487/RFC4054, May 2005,
467 .
469 [I-D.kdkgall-ccamp-dwdm-if-mng-ctrl-fwk]
470 Kunze, R., Grammel, G., Beller, D., and G. Galimberti, "A
471 framework for Management and Control of G.698.2 optical
472 interface parameters", draft-kdkgall-ccamp-dwdm-if-mng-
473 ctrl-fwk-00 (work in progress), October 2015.
475 [ITU.G698.2]
476 International Telecommunications Union, "Amplified
477 multichannel dense wavelength division multiplexing
478 applications with single channel optical interfaces",
479 ITU-T Recommendation G.698.2, November 2009.
481 [ITU.G694.1]
482 International Telecommunications Union, ""Spectral grids
483 for WDM applications: DWDM frequency grid"",
484 ITU-T Recommendation G.698.2, February 2012.
486 [ITU.G709]
487 International Telecommunications Union, "Interface for the
488 Optical Transport Network (OTN)", ITU-T Recommendation
489 G.709, February 2012.
491 [ITU.G872]
492 International Telecommunications Union, "Architecture of
493 optical transport networks", ITU-T Recommendation G.872,
494 October 2012.
496 [ITU.G874.1]
497 International Telecommunications Union, "Optical transport
498 network (OTN): Protocol-neutral management information
499 model for the network element view", ITU-T Recommendation
500 G.874.1, October 2012.
502 12.2. Informative References
504 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
505 "Introduction and Applicability Statements for Internet-
506 Standard Management Framework", RFC 3410,
507 DOI 10.17487/RFC3410, December 2002,
508 .
510 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
511 DOI 10.17487/RFC2629, June 1999,
512 .
514 [RFC4181] Heard, C., Ed., "Guidelines for Authors and Reviewers of
515 MIB Documents", BCP 111, RFC 4181, DOI 10.17487/RFC4181,
516 September 2005, .
518 Authors' Addresses
520 Dharini Hiremagalur (editor)
521 Juniper
522 1194 N Mathilda Avenue
523 Sunnyvale - 94089 California
524 USA
526 Phone: +1408
527 Email: dharinih@juniper.net
529 Gert Grammel (editor)
530 Juniper
531 Oskar-Schlemmer Str. 15
532 80807 Muenchen
533 Germany
535 Phone: +49 1725186386
536 Email: ggrammel@juniper.net
537 Gabriele Galimberti (editor)
538 Cisco
539 Via S. Maria Molgora, 48
540 20871 - Vimercate
541 Italy
543 Phone: +390392091462
544 Email: ggalimbe@cisco.com
546 Zafar Ali (editor)
547 Cisco
548 3000 Innovation Drive
549 KANATA
550 ONTARIO K2K 3E8
552 Email: zali@cisco.com
554 Ruediger Kunze (editor)
555 Deutsche Telekom
556 Dddd, xx
557 Berlin
558 Germany
560 Phone: +49xxxxxxxxxx
561 Email: RKunze@telekom.de
563 Dieter Beller (editor)
564 ALU
565 Lorenzstrasse, 10
566 70435 Stuttgart
567 Germany
569 Phone: +4971182143125
570 Email: Dieter.Beller@alcatel-lucent.com