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