idnits 2.17.1
draft-dharinigert-ccamp-g-698-2-lmp-07.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 (June 18, 2014) is 3593 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 139, but not defined
== Missing Reference: 'G.694.1' is mentioned on line 149, but not defined
== Unused Reference: 'RFC4054' is defined on line 341, but no explicit
reference was found in the text
== Unused Reference: 'ITU.G709' is defined on line 355, but no explicit
reference was found in the text
== Unused Reference: 'ITU.G872' is defined on line 360, but no explicit
reference was found in the text
== Unused Reference: 'I-D.kunze-g-698-2-management-control-framework' is
defined on line 367, but no explicit reference was found in the text
== Unused Reference: 'I-D.galimbe-kunze-g-698-2-snmp-mib' is defined on
line 373, 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: December 20, 2014 Juniper
6 G. Galimberti, Ed.
7 Z. Ali, Ed.
8 Cisco
9 R. Kunze, Ed.
10 Deutsche Telekom
11 June 18, 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-07
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 December 20, 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 . . . . . . . 5
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-mib-
83 06" and "draft-kunze-g-698-2-management-control-framework-02", for
84 the relevant interface optical parameters described in
85 recommendations like ITU-T G.698.2 [ITU.G698.2]. The LMP Model from
86 RFC4902 provides link property correlation between a client and an
87 OLS device. LMP link property correlation, exchanges the
88 capabilities of either end of the link where the term 'link' refers
89 to the attachment link between OXC and OLS (see Figure 1). By
90 performing link property correlation, both ends of the link exchange
91 link properties, such as standard and proprietary application codes.
92 This allows either end to operate within a commonly understood
93 parameter window. Based on known parameter limits, each device can
94 supervise the received signal for conformance using mechanisms
95 defined in RFC3591. The actual route selection of a specific
96 wavelength within the allowed set is outside the scope of LMP. In
97 GMPLS, the parameter selection (e.g. wavelength) is performed by
98 RSVP-TE and Wavelength routing by IGP.
100 Figure 1 Extended LMP Model ( from [RFC4209] )
102 +------+ Ss +------+ +------+ Rs +------+
103 | | ----- | | | | ----- | |
104 | OXC1 | ----- | OLS1 | ===== | OLS2 | ----- | OXC2 |
105 | | ----- | | | | ----- | |
106 +------+ +------+ +------+ +------+
107 ^ ^ ^ ^ ^ ^
108 | | | | | |
109 | +-----LMP-----+ +-----LMP-----+ |
110 | |
111 +----------------------LMP-----------------------+
113 OXC : is an entity that contains transponders
114 OLS : generic optical system, it can be -
115 Optical mux, Optical demux, Optical Add
116 Drop Mux, etc
117 OLS to OLS : represents the black-Link itself
118 Rs/Ss : inbetween the OXC and the OLS
120 Figure 1: Extended LMP Model
122 2. Extensions to LMP-WDM Protocol
124 This document defines extensions to [RFC4209] to allow the Black Link
125 (BL) parameters of G.698.2, as described in the draft draft-kunze-
126 g-698-2-management-control-framework-02, to be exchanged between a
127 router or optical switch and the optical line system to which it is
128 attached. In particular, this document defines additional Data Link
129 sub-objects to be carried in the LinkSummary message defined in
130 [RFC4204] and [RFC6205]. The OXC and OLS systems may be managed by
131 different Network management systems and hence may not know the
132 capability and status of their peer. The intent of this draft is to
133 enable the OXC and OLS systems to exchange this information. These
134 messages and their usage are defined in subsequent sections of this
135 document.
137 The following new messages are defined for the WDM extension for
138 ITU-T G.698.2 [ITU.G698.2]/ITU-T G.698.1 [ITU.G698.1]/
139 ITU-T G.959.1 [ITU.G959.1]
140 - BL_General (sub-object Type = TBA)
141 - BL_ApplicationCode (sub-object Type = TBA)
142 - BL_VendorTransceiverClass (sub-object Type = TBA)
143 - BL_Ss (sub-object Type = TBA)
144 - BL_Rs (sub-object Type = TBA)
146 3. Black Link General Parameters - BL_General
148 These are the general parameters as described in [G698.2] and
149 [G.694.1]. Please refer to the "draft-galikunze-ccamp-g-698-2-snmp-
150 mib-04" for more details about these parameters and the [RFC6205] for
151 the wavelength definition.
153 The general parameters are
154 1. Bit-Rate/line coding of optical tributary signals
155 2. Wavelength - (Tera Hertz) 4 bytes (see RFC6205 sec.3.2)
156 3. Number of Application Codes Supported
157 4. Number of Vendor Transceiver Classes Supported
158 5. Identifier of Application code to/in use
159 6. Identifier Vendor transceiver Application code to/in use
161 Figure 2: The format of the this sub-object (Type = TBA, Length =
162 TBA) is as follows:
164 0 1 2 3
165 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
166 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
167 | Type | Length | (Reserved) |
168 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
169 | Wavelength |
170 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
171 | Number of application codes | Number of vendor transceiver |
172 | Supported | classes Supported |
173 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
174 | Identifier of Application code to/in use |
175 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
176 | Identifier Vendor transceiver Application code to/in use |
177 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
179 Figure 2: BL_General
181 4. Black Link ApplicationCode - BL_ApplicationCode
183 This message is to exchange the application code supported as
184 described in [G698.2]. Please refer to the "draft-galikunze-ccamp-
185 g-698-2-snmp-mib-04". for more details about these parameters.
186 There can be more than one Application Code supported by the OXC/OLS.
187 The number of application codes supported is exchanged in the
188 "BL_General" message. (from [G698.1]/[G698.2]/[G959.1]
190 The parameters are
191 1. Single-channel application code identifire - 8 bits
193 2. Single-channel application codes -- 32 bytes
194 (from [G698.1]/[G698.2]/[G959.1] - this parameter can have
195 multiple instances as the transceiver can support multiple
196 application codes.
198 Figure 3: The format of the this sub-object (Type = TBA, Length =
199 TBA) is as follows:
201 0 1 2 3
202 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
203 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
204 | Type | Length | (Reserved) |
205 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
206 | Single-channel| (Reserved) |
207 | Application| |
208 | CodeIdentifier| |
209 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
210 | Single-channel Application Code |
211 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
212 // .... //
213 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
215 Figure 3: BL_ApplicationCode
217 5. Black Link Vendor Transceiver Class - BL_ApplicationCode
219 This message is to exchange the application code supported as
220 described in [G698.2]. Please refer to the "draft-galikunze-ccamp-
221 g-698-2-snmp-mib-04". for more details about these parameters.
222 There can be more than one Vendor Transceiver Class supported by the
223 OXC/OLS. The number of Vendor Transceiver Classes supported is
224 exchanged in the "BL_General" message. (from
225 [G698.1]/[G698.2]/[G959.1]
227 The parameters are
228 1. Single-channel Transceiver Class identifier - 8 bits
230 2. Vendor Transceiver Class -- 32 bytes
231 (from [G698.1]/[G698.2]/[G959.1] - this parameter can have
232 multiple instances as the transceiver can support multiple
233 application codes.
235 Figure 4: The format of the this sub-object (Type = TBA, Length =
236 TBA) is as follows:
238 0 1 2 3
239 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
240 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
241 | Type | Length | (Reserved) |
242 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
243 | Single-channel| (Reserved) |
244 |Transceiver | |
245 |ClassIdentifier| |
246 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
247 | Single-channel Vendor Transceiver Class |
248 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
249 // .... //
250 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
252 Figure 4: BL_VendorTransceiverClass
254 6. Black Link - BL_Ss
256 These are the G.698.2 parameters at the Source(Ss reference points).
257 Please refer to "draft-galikunze-ccamp-g-698-2-snmp-mib-03" for more
258 details about these parameters.
260 1. Output power
262 Figure 5: The format of the Black link sub-object (Type = TBA, Length
263 = TBA) is as follows:
265 0 1 2 3
266 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
267 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
268 | Type | Length | (Reserved) |
269 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
270 | Output Power |
271 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
273 Figure 5: Black Link - BL_Ss
275 7. Black Link - BL_Rs
277 These are the G.698.2 parameters at the Sink (Rs reference points).
278 Please refer to the "draft-galikunze-ccamp-g-698-2-snmp-mib-02" for
279 more details about these parameters.
281 1. Current Input Power - (0.1dbm) 4bytes
283 Figure 6: The format of the Black link sub-object (Type = TBA, Length
284 = TBA) is as follows:
286 The format of the Black Link/OLS Sink sub-object (Type = TBA,
287 Length = 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 | Current Input Power |
295 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
297 Figure 6: Black Link - BL_Rs
299 8. Security Considerations
301 LMP message security uses IPsec, as described in [RFC4204]. This
302 document only defines new LMP objects that are carried in existing
303 LMP messages, similar to the LMP objects in [RFC:4209]. This
304 document does not introduce new security considerations.
306 9. IANA Considerations
308 LMP defines the following name spaces and
309 the ways in which IANA can make assignments to these namespaces:
311 - LMP Message Type
312 - LMP Object Class
313 - LMP Object Class type (C-Type) unique within the Object Class
314 - LMP Sub-object Class type (Type) unique within the Object Class
315 This memo introduces the following new assignments:
317 LMP Sub-Object Class names:
319 under DATA_LINK Class name (as defined in )
320 - BL_General (sub-object Type = TBA)
321 - BL_ApplicationCode (sub-object Type = TBA)
322 - BL_VendorTransceiverClass (sub-object Type = TBA)
323 - BL_Ss (sub-object Type = TBA)
324 - BL_Rs (sub-object Type = TBA)
326 10. References
328 10.1. Normative References
330 [RFC4204] Lang, J., "Link Management Protocol (LMP)", RFC 4204,
331 October 2005.
333 [RFC4209] Fredette, A. and J. Lang, "Link Management Protocol (LMP)
334 for Dense Wavelength Division Multiplexing (DWDM) Optical
335 Line Systems", RFC 4209, October 2005.
337 [RFC6205] Otani, T. and D. Li, "Generalized Labels for Lambda-
338 Switch-Capable (LSC) Label Switching Routers", RFC 6205,
339 March 2011.
341 [RFC4054] Strand, J. and A. Chiu, "Impairments and Other Constraints
342 on Optical Layer Routing", RFC 4054, May 2005.
344 [ITU.G698.2]
345 International Telecommunications Union, "Amplified
346 multichannel dense wavelength division multiplexing
347 applications with single channel optical interfaces",
348 ITU-T Recommendation G.698.2, November 2009.
350 [ITU.G694.1]
351 International Telecommunications Union, ""Spectral grids
352 for WDM applications: DWDM frequency grid"", ITU-T
353 Recommendation G.698.2, February 2012.
355 [ITU.G709]
356 International Telecommunications Union, "Interface for the
357 Optical Transport Network (OTN)", ITU-T Recommendation
358 G.709, March 2003.
360 [ITU.G872]
361 International Telecommunications Union, "Architecture of
362 optical transport networks", ITU-T Recommendation G.872,
363 November 2001.
365 10.2. Informative References
367 [I-D.kunze-g-698-2-management-control-framework]
368 Kunze, R., "A framework for Management and Control of
369 optical interfaces supporting G.698.2", draft-kunze-
370 g-698-2-management-control-framework-00 (work in
371 progress), July 2011.
373 [I-D.galimbe-kunze-g-698-2-snmp-mib]
374 Kunze, R. and D. Hiremagalur, "A SNMP MIB to manage black-
375 link optical interface parameters of DWDM applications",
376 draft-galimbe-kunze-g-698-2-snmp-mib-02 (work in
377 progress), March 2012.
379 Authors' Addresses
381 Dharini Hiremagalur (editor)
382 Juniper
383 1194 N Mathilda Avenue
384 Sunnyvale - 94089 California
385 USA
387 Phone: +1408
388 Email: dharinih@juniper.net
389 Gert Grammel (editor)
390 Juniper
391 1194 N Mathilda Avenue
392 Sunnyvale - 94089 California
393 USA
395 Phone: +1408
396 Email: ggrammel@juniper.net
398 John E. Drake (editor)
399 Juniper
400 1194 N Mathilda Avenue
401 HW-US,Pennsylvania
402 USA
404 Phone: +1408
405 Email: jdrake@juniper.net
407 Gabriele Galimberti (editor)
408 Cisco
409 Via Philips,12
410 20052 - Monza
411 Italy
413 Phone: +390392091462
414 Email: ggalimbe@cisco.com
416 Zafar Ali (editor)
417 Cisco
418 3000 Innovation Drive
419 KANATA
420 ONTARIO K2K 3E8
422 Email: zali@cisco.com
424 Ruediger Kunze (editor)
425 Deutsche Telekom
426 Dddd, xx
427 Berlin
428 Germany
430 Phone: +49xxxxxxxxxx
431 Email: RKunze@telekom.de