idnits 2.17.1
draft-dharinigert-ccamp-g-698-2-lmp-06.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 (February 8, 2014) is 3730 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 136, but not defined
== Missing Reference: 'G.694.1' is mentioned on line 146, but not defined
== Unused Reference: 'RFC4054' is defined on line 336, but no explicit
reference was found in the text
== Unused Reference: 'ITU.G709' is defined on line 350, but no explicit
reference was found in the text
== Unused Reference: 'ITU.G872' is defined on line 355, but no explicit
reference was found in the text
== Unused Reference: 'I-D.kunze-g-698-2-management-control-framework' is
defined on line 362, but no explicit reference was found in the text
== Unused Reference: 'I-D.galimbe-kunze-g-698-2-snmp-mib' is defined on
line 368, 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'
== Outdated reference: A later version (-02) exists of
draft-kunze-g-698-2-management-control-framework-00
Summary: 2 errors (**), 0 flaws (~~), 9 warnings (==), 5 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: August 12, 2014 Juniper
6 G. Galimberti, Ed.
7 Z. Ali, Ed.
8 Cisco
9 R. Kunze, Ed.
10 Deutsche Telekom
11 February 8, 2014
13 Extension to the Link Management Protocol (LMP/DWDM -rfc4209) for Dense
14 Wavelength Division Multiplexing (DWDM) Optical Line Systems to manage
15 application code of optical interface parameters in DWDM application
16 draft-dharinigert-ccamp-g-698-2-lmp-06
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 extendsions./>
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 August 12, 2014.
49 Copyright Notice
51 Copyright (c) 2014 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. Black Link General Parameters - BL_General . . . . . . . . . 4
69 4. Black Link ApplicationCode - BL_ApplicationCode . . . . . . . 4
70 5. Black Link Vendor Transceiver Class - BL_ApplicationCode . . 5
71 6. Black Link - BL_Ss . . . . . . . . . . . . . . . . . . . . . 6
72 7. Black Link - BL_Rs . . . . . . . . . . . . . . . . . . . . . 7
73 8. Security Considerations . . . . . . . . . . . . . . . . . . . 7
74 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
75 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
76 10.1. Normative References . . . . . . . . . . . . . . . . . . 8
77 10.2. Informative References . . . . . . . . . . . . . . . . . 9
78 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
80 1. Introduction
82 This extension is based on "draft-galikunze-ccamp-g-698-2-snmp-
83 mib-03" and "draft-kunze-g-698-2-management-control-framework-02",
84 for the relevant interface optical parameters described in
85 recommendations like ITU-T G.698.2 [ITU.G698.2]. The LMP Model from
86 RFC4902 is extended to provide link property correlation between a
87 client and an OLS device. By using LMP, the capabilities of either
88 end of this link are exchanged where the term 'link' refers to the
89 attachment link between OXC and OLS (see Figure 1). By performing
90 link property correlation, both ends of the link can agree on a
91 common parameter window that can be supported and supervised by each
92 device. The actual selection of a specific parameter value whithin
93 the parameter window is outside the scope of LMP. In GMPLS the
94 parameter selection (e.g. wavelength) is performed by RSVP-TE and
95 Wavelength routing by IGP.
97 Figure 1 Extended LMP Model ( from [RFC4209] )
99 +------+ Ss +------+ +------+ Rs +------+
100 | | ----- | | | | ----- | |
101 | OXC1 | ----- | OLS1 | ===== | OLS2 | ----- | OXC2 |
102 | | ----- | | | | ----- | |
103 +------+ +------+ +------+ +------+
104 ^ ^ ^ ^ ^ ^
105 | | | | | |
106 | +-----LMP-----+ +-----LMP-----+ |
107 | |
108 +----------------------LMP-----------------------+
110 OXC : is an entity that contains transponders
111 OLS : generic optical system, it can be -
112 Optical mux, Optical demux, Optical Add
113 Drop Mux, etc
114 OLS to OLS : represents the black-Link itself
115 Rs/Ss : inbetween the OXC and the OLS
117 Figure 1: Extended LMP Model
119 2. Extensions to LMP-WDM Protocol
121 This document defines extensions to [RFC4209] to allow the Black Link
122 (BL) parameters of G.698.2, as described in the draft draft-
123 kunze-g-698-2-management-control-framework-02, to be exchanged
124 between a router or optical switch and the optical line system to
125 which it is attached. In particular, this document defines
126 additional Data Link sub-objects to be carried in the LinkSummary
127 message defined in [RFC4204] and [RFC6205]. The OXC and OLS systems
128 may be managed by different Network management systems and hence may
129 not know the capability and status of their peer. The intent of this
130 draft is to enable the OXC and OLS systems to exchange this
131 information. These messages and their usage are defined in
132 subsequent sections of this document.
134 The following new messages are defined for the WDM extension for
135 ITU-T G.698.2 [ITU.G698.2]/ITU-T G.698.1 [ITU.G698.1]/
136 ITU-T G.959.1 [ITU.G959.1]
137 - BL_General (sub-object Type = TBA)
138 - BL_ApplicationCode (sub-object Type = TBA)
139 - BL_VendorTransceiverClass (sub-object Type = TBA)
140 - BL_Ss (sub-object Type = TBA)
141 - BL_Rs (sub-object Type = TBA)
143 3. Black Link General Parameters - BL_General
145 These are the general parameters as described in [G698.2] and
146 [G.694.1]. Please refer to the "draft-galikunze-ccamp-g-698-2-snmp-
147 mib-04" for more details about these parameters and the [RFC6205] for
148 the wavelength definition.
150 The general parameters are
151 1. Bit-Rate/line coding of optical tributary signals
152 2. Wavelength - (Tera Hertz) 4 bytes (see RFC6205 sec.3.2)
153 3. Number of Application Codes Supported
154 4. Number of Vendor Transceiver Classes Supported
155 5. Identifier of Application code to/in use
156 6. Identifier Vendor transceiver Application code to/in use
158 Figure 2: The format of the this sub-object (Type = TBA, Length =
159 TBA) is as follows:
161 0 1 2 3
162 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
163 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
164 | Type | Length | (Reserved) |
165 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
166 | Wavelength |
167 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
168 | Number of application codes | Number of vendor transceiver |
169 | Supported | classes Supported |
170 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
171 | Identifier of Application code to/in use |
172 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
173 | Identifier Vendor transceiver Application code to/in use |
174 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
176 Figure 2: BL_General
178 4. Black Link ApplicationCode - BL_ApplicationCode
180 This message is to exchange the application code supported as
181 described in [G698.2]. Please refer to the "draft-galikunze-
182 ccamp-g-698-2-snmp-mib-04". for more details about these parameters.
183 There can be more than one Application Code supported by the OXC/OLS.
184 The number of application codes supported is exchanged in the
185 "BL_General" message. (from [G698.1]/[G698.2]/[G959.1]
186 The parameters are
187 1. Single-channel application code identifire - 8 bits
189 2. Single-channel application codes -- 32 bytes
190 (from [G698.1]/[G698.2]/[G959.1] - this parameter can have
191 multiple instances as the transceiver can support multiple
192 application codes.
194 Figure 3: The format of the this sub-object (Type = TBA, Length =
195 TBA) is as follows:
197 0 1 2 3
198 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
199 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
200 | Type | Length | (Reserved) |
201 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
202 | Single-channel| (Reserved) |
203 | Application| |
204 | CodeIdentifier| |
205 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
206 | Single-channel Application Code |
207 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
208 // .... //
209 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
211 Figure 3: BL_ApplicationCode
213 5. Black Link Vendor Transceiver Class - BL_ApplicationCode
215 This message is to exchange the application code supported as
216 described in [G698.2]. Please refer to the "draft-galikunze-
217 ccamp-g-698-2-snmp-mib-04". for more details about these parameters.
218 There can be more than one Vendor Transceiver Class supported by the
219 OXC/OLS. The number of Vendor Transceiver Classes supported is
220 exchanged in the "BL_General" message. (from [G698.1]/[G698.2]/
221 [G959.1]
222 The parameters are
223 1. Single-channel Transceiver Class identifier - 8 bits
225 2. Vendor Transceiver Class -- 32 bytes
226 (from [G698.1]/[G698.2]/[G959.1] - this parameter can have
227 multiple instances as the transceiver can support multiple
228 application codes.
230 Figure 4: The format of the this sub-object (Type = TBA, Length =
231 TBA) is as follows:
233 0 1 2 3
234 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
235 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
236 | Type | Length | (Reserved) |
237 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
238 | Single-channel| (Reserved) |
239 |Transceiver | |
240 |ClassIdentifier| |
241 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
242 | Single-channel Vendor Transceiver Class |
243 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
244 // .... //
245 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
247 Figure 4: BL_VendorTransceiverClass
249 6. Black Link - BL_Ss
251 These are the G.698.2 parameters at the Source(Ss reference points).
252 Please refer to "draft-galikunze-ccamp-g-698-2-snmp-mib-03" for more
253 details about these parameters.
255 1. Output power
257 Figure 5: The format of the Black link sub-object (Type = TBA, Length
258 = TBA) is as follows:
260 0 1 2 3
261 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
262 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
263 | Type | Length | (Reserved) |
264 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
265 | Output Power |
266 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
268 Figure 5: Black Link - BL_Ss
270 7. Black Link - BL_Rs
272 These are the G.698.2 parameters at the Sink (Rs reference points).
273 Please refer to the "draft-galikunze-ccamp-g-698-2-snmp-mib-02" for
274 more details about these parameters.
276 1. Current Input Power - (0.1dbm) 4bytes
278 Figure 6: The format of the Black link sub-object (Type = TBA, Length
279 = TBA) is as follows:
281 The format of the Black Link/OLS Sink sub-object (Type = TBA,
282 Length = TBA) is as follows:
284 0 1 2 3
285 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
286 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
287 | Type | Length | (Reserved) |
288 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
289 | Current Input Power |
290 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
292 Figure 6: Black Link - BL_Rs
294 8. Security Considerations
296 LMP message security uses IPsec, as described in [RFC4204]. This
297 document only defines new LMP objects that are carried in existing
298 LMP messages, similar to the LMP objects in [RFC:4209]. This
299 document does not introduce new security considerations.
301 9. IANA Considerations
303 LMP defines the following name spaces and
304 the ways in which IANA can make assignments to these namespaces:
306 - LMP Message Type
307 - LMP Object Class
308 - LMP Object Class type (C-Type) unique within the Object Class
309 - LMP Sub-object Class type (Type) unique within the Object Class
310 This memo introduces the following new assignments:
312 LMP Sub-Object Class names:
314 under DATA_LINK Class name (as defined in )
315 - BL_General (sub-object Type = TBA)
316 - BL_ApplicationCode (sub-object Type = TBA)
317 - BL_VendorTransceiverClass (sub-object Type = TBA)
318 - BL_Ss (sub-object Type = TBA)
319 - BL_Rs (sub-object Type = TBA)
321 10. References
323 10.1. Normative References
325 [RFC4204] Lang, J., "Link Management Protocol (LMP)", RFC 4204,
326 October 2005.
328 [RFC4209] Fredette, A. and J. Lang, "Link Management Protocol (LMP)
329 for Dense Wavelength Division Multiplexing (DWDM) Optical
330 Line Systems", RFC 4209, October 2005.
332 [RFC6205] Otani, T. and D. Li, "Generalized Labels for Lambda-
333 Switch-Capable (LSC) Label Switching Routers", RFC 6205,
334 March 2011.
336 [RFC4054] Strand, J. and A. Chiu, "Impairments and Other Constraints
337 on Optical Layer Routing", RFC 4054, May 2005.
339 [ITU.G698.2]
340 International Telecommunications Union, "Amplified
341 multichannel dense wavelength division multiplexing
342 applications with single channel optical interfaces",
343 ITU-T Recommendation G.698.2, November 2009.
345 [ITU.G694.1]
346 International Telecommunications Union, ""Spectral grids
347 for WDM applications: DWDM frequency grid"", ITU-T
348 Recommendation G.698.2, February 2012.
350 [ITU.G709]
351 International Telecommunications Union, "Interface for the
352 Optical Transport Network (OTN)", ITU-T Recommendation
353 G.709, March 2003.
355 [ITU.G872]
356 International Telecommunications Union, "Architecture of
357 optical transport networks", ITU-T Recommendation G.872,
358 November 2001.
360 10.2. Informative References
362 [I-D.kunze-g-698-2-management-control-framework]
363 Kunze, R., "A framework for Management and Control of
364 optical interfaces supporting G.698.2", draft-
365 kunze-g-698-2-management-control-framework-00 (work in
366 progress), July 2011.
368 [I-D.galimbe-kunze-g-698-2-snmp-mib]
369 Kunze, R. and D. Hiremagalur, "A SNMP MIB to manage black-
370 link optical interface parameters of DWDM applications",
371 draft-galimbe-kunze-g-698-2-snmp-mib-02 (work in
372 progress), March 2012.
374 Authors' Addresses
376 Dharini Hiremagalur (editor)
377 Juniper
378 1194 N Mathilda Avenue
379 Sunnyvale - 94089 California
380 USA
382 Phone: +1408
383 Email: dharinih@juniper.net
384 Gert Grammel (editor)
385 Juniper
386 1194 N Mathilda Avenue
387 Sunnyvale - 94089 California
388 USA
390 Phone: +1408
391 Email: ggrammel@juniper.net
393 John E. Drake (editor)
394 Juniper
395 1194 N Mathilda Avenue
396 HW-US,Pennsylvania
397 USA
399 Phone: +1408
400 Email: jdrake@juniper.net
402 Gabriele Galimberti (editor)
403 Cisco
404 Via Philips,12
405 20052 - Monza
406 Italy
408 Phone: +390392091462
409 Email: ggalimbe@cisco.com
411 Zafar Ali (editor)
412 Cisco
413 3000 Innovation Drive
414 KANATA
415 ONTARIO K2K 3E8
417 Email: zali@cisco.com
419 Ruediger Kunze (editor)
420 Deutsche Telekom
421 Dddd, xx
422 Berlin
423 Germany
425 Phone: +49xxxxxxxxxx
426 Email: RKunze@telekom.de