idnits 2.17.1
draft-dharinigert-ccamp-g-698-2-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.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 (July 15, 2013) is 3937 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 135, but not defined
== Missing Reference: 'G.694.1' is mentioned on line 144, but not defined
== Unused Reference: 'RFC4054' is defined on line 293, but no explicit
reference was found in the text
== Unused Reference: 'ITU.G709' is defined on line 307, but no explicit
reference was found in the text
== Unused Reference: 'ITU.G872' is defined on line 312, but no explicit
reference was found in the text
== Unused Reference: 'I-D.kunze-g-698-2-management-control-framework' is
defined on line 319, but no explicit reference was found in the text
== Unused Reference: 'I-D.galimbe-kunze-g-698-2-snmp-mib' is defined on
line 325, 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 14, 2013 Juniper
6 G. Galimberti, Ed.
7 Z. Ali, Ed.
8 Cisco
9 R. Kunze, Ed.
10 Deutsche Telekom
11 July 15, 2013
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-03
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 14, 2013.
49 Copyright Notice
51 Copyright (c) 2013 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 - BL_Ss . . . . . . . . . . . . . . . . . . . . . 5
71 6. Black Link - BL_Rs . . . . . . . . . . . . . . . . . . . . . 5
72 7. Security Considerations . . . . . . . . . . . . . . . . . . . 6
73 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
74 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
75 9.1. Normative References . . . . . . . . . . . . . . . . . . 7
76 9.2. Informative References . . . . . . . . . . . . . . . . . 8
77 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
79 1. Introduction
81 This extension is based on "draft-galikunze-ccamp-g-698-2-snmp-
82 mib-03" and "draft-kunze-g-698-2-management-control-framework-02",
83 for the relevant interface optical parameters described in
84 recommendations like ITU-T G.698.2 [ITU.G698.2]. The LMP Model from
85 RFC4902 is extended to provide link property correlation between a
86 client and an OLS device. By using LMP, the capabilities of either
87 end of this link are exchanged where the term 'link' refers to the
88 attachment link between OXC and OLS (see Figure 1). By performing
89 link property correlation, both ends of the link can agree on a
90 common parameter window that can be supported and supervised by each
91 device. The actual selection of a specific parameter value whithin
92 the parameter window is outside the scope of LMP. In GMPLS the
93 parameter selection (e.g. wavelength) is performed by RSVP-TE and
94 Wavelength routing by IGP.
96 Figure 1 Extended LMP Model ( from [RFC4209] )
98 +------+ Ss +------+ +------+ Rs +------+
99 | | ----- | | | | ----- | |
100 | OXC1 | ----- | OLS1 | ===== | OLS2 | ----- | OXC2 |
101 | | ----- | | | | ----- | |
102 +------+ +------+ +------+ +------+
103 ^ ^ ^ ^ ^ ^
104 | | | | | |
105 | +-----LMP-----+ +-----LMP-----+ |
106 | |
107 +----------------------LMP-----------------------+
109 OXC : is an entity that contains transponders
110 OLS : generic optical system, it can be -
111 Optical mux, Optical demux, Optical Add
112 Drop Mux, etc
113 OLS to OLS : represents the black-Link itself
114 Rs/Ss : inbetween the OXC and the OLS
116 Figure 1: Extended LMP Model
118 2. Extensions to LMP-WDM Protocol
120 This document defines extensions to [RFC4209] to allow the Black Link
121 (BL) parameters of G.698.2, as described in the draft draft-
122 kunze-g-698-2-management-control-framework-02, to be exchanged
123 between a router or optical switch and the optical line system to
124 which it is attached. In particular, this document defines
125 additional Data Link sub-objects to be carried in the LinkSummary
126 message defined in [RFC4204] and [RFC6205]. The OXC and OLS systems
127 may be managed by different Network management systems and hence may
128 not know the capability and status of their peer. The intent of this
129 draft is to enable the OXC and OLS systems to exchange this
130 information. These messages and their usage are defined in
131 subsequent sections of this document.
133 The following new messages are defined for the WDM extension for
134 ITU-T G.698.2 [ITU.G698.2]/ITU-T G.698.1 [ITU.G698.1]/
135 ITU-T G.959.1 [ITU.G959.1]
136 - BL_General (sub-object Type = TBA)
137 - BL_ApplicationCode (sub-object Type = TBA)
138 - BL_Ss (sub-object Type = TBA)
139 - BL_Rs (sub-object Type = TBA)
141 3. Black Link General Parameters - BL_General
143 These are the general parameters as described in [G698.2] and
144 [G.694.1]. Please refer to the "draft-galikunze-ccamp-g-698-2-snmp-
145 mib-03" for more details about these parameters and the [RFC6205] for
146 the wavelength definition.
148 The general parameters are
149 1. Bit-Rate/line coding of optical tributary signals
150 2. Wavelength - (Tera Hertz) 4 bytes (see RFC6205 sec.3.2)
152 Figure 2: The format of the this sub-object (Type = TBA, Length =
153 TBA) is as follows:
155 0 1 2 3
156 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
157 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
158 | Type | Length | (Reserved) |
159 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
160 | Bit-Rate/Line coding |
161 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
162 | Wavelength |
163 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
165 Figure 2: BL_General
167 4. Black Link ApplicationCode - BL_ApplicationCode
169 These are the general parameters as described in [G698.2]. Please
170 refer to the "draft-galikunze-ccamp-g-698-2-snmp-mib-03". for more
171 details about these parameters.
173 The general parameters are
174 1. Single-channel application codes -- 32 bytes
175 (from [G698.1]/[G698.2]/[G959.1]
177 Figure 3: The format of the this sub-object (Type = TBA, Length =
178 TBA) is as follows:
180 0 1 2 3
181 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
182 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
183 | Type | Length | (Reserved) |
184 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
185 | Single-channel Application Code |
186 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
187 // .... //
188 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
190 Figure 3: BL_ApplicationCode
192 5. Black Link - BL_Ss
194 These are the G.698.2 parameters at the Source(Ss reference points).
195 Please refer to "draft-galikunze-ccamp-g-698-2-snmp-mib-03" for more
196 details about these parameters.
198 1. Minimum Mean Channel Output Power -(0.1 dbm) 4 bytes
199 2. Maximum Mean Channel Output Power -(0.1 dbm) 4 bytes
201 Figure 4: The format of the Black link 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 | Minimum Mean Channel Output Power |
210 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
211 | Maximum Mean Channel Output Power |
212 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
214 Figure 4: Black Link - BL_Ss
216 6. Black Link - BL_Rs
218 These are the G.698.2 parameters at the Sink (Rs reference points).
219 Please refer to the "draft-galikunze-ccamp-g-698-2-snmp-mib-02" for
220 more details about these parameters.
222 1. Minimum Mean Input Power - (0.1dbm) 4bytes
223 2. Maximum Mean Input Power - (0.1dbm) 4bytes
224 3. Minimum OSNR - (0.1dB) 4bytes
225 4. OSNR Tolerance - (0.1dB) 4bytes
226 5. Current Input Power - (0.1dbm) 4bytes
228 Figure 5: The format of the Black link sub-object (Type = TBA, Length
229 = TBA) is as follows:
231 The format of the Black Link/OLS Sink sub-object (Type = TBA,
232 Length = TBA) is as follows:
234 0 1 2 3
235 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
236 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
237 | Type | Length | (Reserved) |
238 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
239 | Minimum Mean Input Power |
240 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
241 | Maximum Mean Input Power |
242 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
243 | Minimum OSNR |
244 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
245 | OSNR Tolerance |
246 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
247 | Current Input Power |
248 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
250 Figure 5: Black Link - BL_Rs
252 7. Security Considerations
254 LMP message security uses IPsec, as described in [RFC4204]. This
255 document only defines new LMP objects that are carried in existing
256 LMP messages, similar to the LMP objects in [RFC:4209]. This
257 document does not introduce new security considerations.
259 8. IANA Considerations
261 LMP defines the following name spaces and
262 the ways in which IANA can make assignments to these namespaces:
264 - LMP Message Type
265 - LMP Object Class
266 - LMP Object Class type (C-Type) unique within the Object Class
267 - LMP Sub-object Class type (Type) unique within the Object Class
268 This memo introduces the following new assignments:
270 LMP Sub-Object Class names:
272 under DATA_LINK Class name (as defined in )
273 - BL_General (sub-object Type = TBA)
274 - BL_Applicationcode (sub-object Type = TBA)
275 - BL_Ss (sub-object Type = TBA)
276 - BL_Rs (sub-object Type = TBA)
278 9. References
280 9.1. Normative References
282 [RFC4204] Lang, J., "Link Management Protocol (LMP)", RFC 4204,
283 October 2005.
285 [RFC4209] Fredette, A. and J. Lang, "Link Management Protocol (LMP)
286 for Dense Wavelength Division Multiplexing (DWDM) Optical
287 Line Systems", RFC 4209, October 2005.
289 [RFC6205] Otani, T. and D. Li, "Generalized Labels for Lambda-
290 Switch-Capable (LSC) Label Switching Routers", RFC 6205,
291 March 2011.
293 [RFC4054] Strand, J. and A. Chiu, "Impairments and Other Constraints
294 on Optical Layer Routing", RFC 4054, May 2005.
296 [ITU.G698.2]
297 International Telecommunications Union, "Amplified
298 multichannel dense wavelength division multiplexing
299 applications with single channel optical interfaces ",
300 ITU-T Recommendation G.698.2, November 2009.
302 [ITU.G694.1]
303 International Telecommunications Union, ""Spectral grids
304 for WDM applications: DWDM frequency grid" ", ITU-T
305 Recommendation G.698.2, February 2012.
307 [ITU.G709]
308 International Telecommunications Union, "Interface for the
309 Optical Transport Network (OTN) ", ITU-T Recommendation
310 G.709, March 2003.
312 [ITU.G872]
313 International Telecommunications Union, "Architecture of
314 optical transport networks ", ITU-T Recommendation G.872,
315 November 2001.
317 9.2. Informative References
319 [I-D.kunze-g-698-2-management-control-framework]
320 Kunze, R., "A framework for Management and Control of
321 optical interfaces supporting G.698.2", draft-
322 kunze-g-698-2-management-control-framework-00 (work in
323 progress), July 2011.
325 [I-D.galimbe-kunze-g-698-2-snmp-mib]
326 Kunze, R. and D. Hiremagalur, "A SNMP MIB to manage black-
327 link optical interface parameters of DWDM applications",
328 draft-galimbe-kunze-g-698-2-snmp-mib-02 (work in
329 progress), March 2012.
331 Authors' Addresses
333 Dharini Hiremagalur (editor)
334 Juniper
335 1194 N Mathilda Avenue
336 Sunnyvale - 94089 California
337 USA
339 Phone: +1408
340 Email: dharinih@juniper.net
342 Gert Grammel (editor)
343 Juniper
344 1194 N Mathilda Avenue
345 Sunnyvale - 94089 California
346 USA
348 Phone: +1408
349 Email: ggrammel@juniper.net
351 John E. Drake (editor)
352 Juniper
353 1194 N Mathilda Avenue
354 HW-US,Pennsylvania
355 USA
357 Phone: +1408
358 Email: jdrake@juniper.net
359 Gabriele Galimberti (editor)
360 Cisco
361 Via Philips,12
362 20052 - Monza
363 Italy
365 Phone: +390392091462
366 Email: ggalimbe@cisco.com
368 Zafar Ali (editor)
369 Cisco
370 3000 Innovation Drive
371 KANATA
372 ONTARIO K2K 3E8
374 Email: zali@cisco.com
376 Ruediger Kunze (editor)
377 Deutsche Telekom
378 Dddd, xx
379 Berlin
380 Germany
382 Phone: +49xxxxxxxxxx
383 Email: RKunze@telekom.de