idnits 2.17.1
draft-ggalimbe-ccamp-flex-if-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 :
----------------------------------------------------------------------------
No issues found here.
Miscellaneous warnings:
----------------------------------------------------------------------------
== The copyright year in the IETF Trust and authors Copyright Line does not
match the current year
-- The document date (March 11, 2019) is 1866 days in the past. Is this
intentional?
Checking references for intended status: Experimental
----------------------------------------------------------------------------
== Missing Reference: 'RFC4902' is mentioned on line 80, but not defined
== Missing Reference: 'G.694.1' is mentioned on line 187, but not defined
== Unused Reference: 'I-D.ietf-ccamp-dwdm-if-mng-ctrl-fwk' is defined on
line 311, but no explicit reference was found in the text
== Unused Reference: 'ITU.G694.1' is defined on line 317, but no explicit
reference was found in the text
== Unused Reference: 'ITU.G698.2' is defined on line 322, but no explicit
reference was found in the text
== Unused Reference: 'ITU.G709' is defined on line 328, but no explicit
reference was found in the text
== Unused Reference: 'ITU.G872' is defined on line 333, but no explicit
reference was found in the text
== Unused Reference: 'ITU.G874.1' is defined on line 338, but no explicit
reference was found in the text
== Unused Reference: 'RFC4054' is defined on line 344, but no explicit
reference was found in the text
== Unused Reference: 'RFC2629' is defined on line 366, but no explicit
reference was found in the text
== Unused Reference: 'RFC3410' is defined on line 370, but no explicit
reference was found in the text
== Unused Reference: 'RFC4181' is defined on line 376, but no explicit
reference was found in the text
== Outdated reference: A later version (-13) exists of
draft-ietf-ccamp-dwdm-if-mng-ctrl-fwk-11
-- Obsolete informational reference (is this intentional?): RFC 2629
(Obsoleted by RFC 7749)
Summary: 0 errors (**), 0 flaws (~~), 14 warnings (==), 2 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: Experimental Juniper
5 Expires: September 12, 2019 G. Galimberti, Ed.
6 Cisco
7 R. Kunze, Ed.
8 Deutsche Telekom
9 March 11, 2019
11 Extension to the Link Management Protocol (LMP/DWDM -rfc4209) for Dense
12 Wavelength Division Multiplexing (DWDM) Optical Line Systems to manage
13 the application code of optical interface parameters in DWDM application
14 draft-ggalimbe-ccamp-flex-if-lmp-07
16 Abstract
18 This experimental memo defines extensions to LMP(rfc4209) for
19 managing Optical parameters associated with Wavelength Division
20 Multiplexing (WDM) adding a set of parameters related to multicarrier
21 DWDM interfaces to be used in Spectrum Switched Optical Networks
22 (sson).
24 Copyright Notice
26 Copyright (c) 2011 IETF Trust and the persons identified as the
27 document authors. All rights reserved.
29 Status of This Memo
31 This Internet-Draft is submitted in full conformance with the
32 provisions of BCP 78 and BCP 79.
34 Internet-Drafts are working documents of the Internet Engineering
35 Task Force (IETF). Note that other groups may also distribute
36 working documents as Internet-Drafts. The list of current Internet-
37 Drafts is at https://datatracker.ietf.org/drafts/current/.
39 Internet-Drafts are draft documents valid for a maximum of six months
40 and may be updated, replaced, or obsoleted by other documents at any
41 time. It is inappropriate to use Internet-Drafts as reference
42 material or to cite them other than as "work in progress."
44 This Internet-Draft will expire on September 12, 2019.
46 Copyright Notice
48 Copyright (c) 2019 IETF Trust and the persons identified as the
49 document authors. All rights reserved.
51 This document is subject to BCP 78 and the IETF Trust's Legal
52 Provisions Relating to IETF Documents
53 (https://trustee.ietf.org/license-info) in effect on the date of
54 publication of this document. Please review these documents
55 carefully, as they describe your rights and restrictions with respect
56 to this document. Code Components extracted from this document must
57 include Simplified BSD License text as described in Section 4.e of
58 the Trust Legal Provisions and are provided without warranty as
59 described in the Simplified BSD License.
61 Table of Contents
63 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
64 2. DWDM line system . . . . . . . . . . . . . . . . . . . . . . 3
65 3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 4
66 4. Extensions to LMP-WDM Protocol . . . . . . . . . . . . . . . 4
67 5. Multi carrier Transceiver . . . . . . . . . . . . . . . . . . 5
68 6. Security Considerations . . . . . . . . . . . . . . . . . . . 6
69 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
70 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 7
71 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
72 9.1. Normative References . . . . . . . . . . . . . . . . . . 7
73 9.2. Informative References . . . . . . . . . . . . . . . . . 8
74 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
76 1. Introduction
78 This experimental extension addresses the use cases described by
79 "draft-ietf-ccamp-dwdm-if-mng-ctrl-fwk" to the Spectrum Switched
80 Optical Network applications. LMP [RFC4902] provides link property
81 correlation capabilities that can be used between a transceiver
82 device and an Optical Line System (OLS) device. Link property
83 correlation is a procedure by which, intrinsic parameters and
84 capabilities are exchanged between two ends of a link. Link property
85 correlation as defined in RFC4204 allows either end of the link to
86 supervise the received signal and operate within a commonly
87 understood parameter window. Here the term 'link' refers in
88 particular to the attachment link between OXC and OLS (see Figure 1).
89 The relevant novelty is the interface configuration having a multiple
90 carrier where the client signal is spread on. The parameters are not
91 yet fully defined by ITU-, so this document can jast be seen as an
92 experimental proposal not binding operators and vendors to comply and
93 implement them
95 2. DWDM line system
97 Figure 1 shows a set of reference points (Rs and Ss), for a single-
98 channel connection between transmitter (Tx) and receiver (Rx)
99 devices. Here the DWDM network elements in between those devices
100 include an Optical Multiplexer (OM) and an Optical Demultiplexer
101 (OD). In addition it may include one or more Optical Amplifiers (OA)
102 and one or more Optical Add-Drop Multiplexers (OADM).
104 +-------------------------------------------------+
105 Ss | DWDM Network Elements | Rs
106 +--+ | | | \ / | | | +--+
107 Tx L1--|->| \ +------+ +------+ / |--|-->Rx L1
108 +---+ | | | | | +------+ | | | | | +--+
109 +---+ | | FX | | | | FLEX | | | | FX | | +--+
110 Tx L2--|->| OM |-->|------|->|ROADM |--|------|->| OD |--|-->Rx L2
111 +---+ | | | | | | | | | | | | +--+
112 +---+ | | | | | +------+ | | | | | +--+
113 Tx L3--|->| / | DWDM | | ^ | DWDM | \ |--|-->Rx L3
114 +---+ | | / | Link +----|--|----+ Link | \ | | +--+
115 +-----------+ | | +----------+
116 +--+ +--+
117 | |
118 Rs v | Ss
119 +-----+ +-----+
120 |RxLx | |TxLx |
121 +-----+ +-----+
123 Ss = Sender reference point at the DWDM network element
124 tributary output, this can be a set of multiple transceivers
125 carrying the same client payload.
126 Rs = Receiver reference point at the DWDM network element
127 tributary input this can be a set of multiple transceivers
128 carrying the same client payload.
130 FX OM = Flex-Spectrum Optical Mux
131 FX OD = Flex-Spectrum Optical Demux
132 Flex ROADM = Flex-Spectrum Optical Add Drop Mux (reconfigurable)
134 extending Fig. 5.1/G.698.2
136 Figure 1: Linear Single Channel approach
138 Figure 2 Extended LMP Model ( from [RFC4209] )
140 +------+ Ss +------+ +------+ Rs +------+
141 | | ----- | | | | ----- | |
142 | OXC1 | ----- | OLS1 | ===== | OLS2 | ----- | OXC2 |
143 | | ----- | | | | ----- | |
144 +------+ +------+ +------+ +------+
145 ^ ^ ^ ^ ^ ^
146 | | | | | |
147 | +-----LMP-----+ +-----LMP-----+ |
148 | |
149 +----------------------LMP-----------------------+
151 OXC : is an entity that contains Multiple carriers transponders
152 OLS : generic Flex-Spectrum optical system, it can be -
153 Optical Mux, Optical Demux, Optical Add
154 Drop Mux, Amplifier etc.
155 OLS to OLS: represents the Optical Multiplex section
156
157 Rs/Ss : reference points in between the OXC and the OLS
159 Figure 2: Extended LMP Model
161 3. Use Cases
163 The set of paramentes exchanged between OXC and OLS is to support the
164 Spectrum Switched Optical Network in therms of Number of Sub-carriers
165 available at the transceiver and their characteristics to provide the
166 SSON control plane all the information suitable to calculate the path
167 and the optical feasibility
169 4. Extensions to LMP-WDM Protocol
171 This document defines extensions to [RFC4209] to allow a set of
172 characteristic parameters, to be exchanged between a router or
173 optical switch and the optical line system to which it is attached.
174 In particular, this document defines additional Data Link sub-objects
175 to be carried in the LinkSummary message defined in [RFC4204] and
176 [RFC6205]. The OXC and OLS systems may be managed by different
177 Network management systems and hence may not know the capability and
178 status of their peer. These messages and their usage are defined in
179 subsequent sections of this document.
181 The following new messages are defined for the SSON extension
182 - Multi carrier Transceiver (sub-object Type = TBA)
184 5. Multi carrier Transceiver
186 These are a set of general parameters extending the description in
187 [G698.2] and [G.694.1]. ITU-T working groups are working to detail
188 most of parameters and an update of the TLV may be required.
190 Other than the Application Identifier described in [G698.2] and
191 draft-dharinigert-ccamp-dwdm-if-lmp the parameters to describe a
192 multicarrier transceiver are describes as follows:
194 1. Modulation format: indicates the Transceiver capabilities
195 to support a single or multiple modulation format like:
196 BPSK, DC-DP-BSPSK, QPSK, DP-QPSK, QAM16, DP-QAM16,
197 DC-DP-QAM16, 64QAM.
198 2. FEC: indicates the FEC types the transceiver can support
199 3. baud rate: symbols rate, basically this identify the
200 channel symbols number per second
201 4. Num Carriers: number of (sub)carriers the trasceiver can support
202 and can be "mapped" in a Mediachannel
203 5. Bits/symbol: number of bit per simbol (aka spectral efficiency)
204 6. Subcarrier band (minimum distance between subcarriers) in GHz
205 7. Guard band (required guard band at the side of media channel)
206 8. Sub-carrier TX Power: output optical power the transceiver can
207 provide
208 9. Sub-carrier RX Power: Input optical power Range the transceiver
209 can support, this is known also as Sensitivity
210 10 Max-pol-power-difference: max power difference between the
211 polarised components
212 11 Max-pol-skew-difference: maw Skew between polarised signal and
213 subcarriers supported by the transceiver
214 12. Sub-carrier OSNR robustness
216 Figure 3: The format of the this sub-object (Type = TBA, Length =
217 TBA) is as follows:
219 0 1 2 3
220 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
221 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
222 | Type | Length | (Reserved) |
223 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
224 |S|I| Modulation ID | FEC |
225 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
226 | baud rate (Symbol Rate) |
227 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
228 | Number of subcarriers | Bit/Symbol |
229 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
230 | subcarrier band | guard band |
231 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
232 | sub-carrier TX power |
233 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
234 | sub-carrier RX power HIGH |
235 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
236 | sub-carrier RX power LOW |
237 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
238 | Max-pol-power-difference |
239 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
240 | Max-pol-skew-difference |
241 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
242 | sub-carrier OSNR |
243 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
245 - S: standardized format;
246 - I: input / output (1 / 0)
247 - Modulation Format: is the modulation type:
248 BPSK, DC DP BSPSK, QPSK, DP QPSK, 8QAM, 16QAM, 64QAM,
249 Hybrid, etc.
250 - (ITU-T reference)
251 - value > 32768 (first bit is 1): custom defined values
252 Value 0 is reserved to be used if no value is defined
253 - FEC: the signal Forward Error Corrections type (16-bit
254 unsigned integer), the defined values are:
255 - (ITU-T reference)
256 - 32768 (first bit is 1): custom defined values
257 Value 0 is reserved to be used if no value is defined
258 - Baud Rate: the signal symbol rate (IEEE 32-bit float,
259 in bauds/s)
260 Value 0 is reserved to be used if no value is defined
261 - Num Carriers
262 - Bits/symbol
263 - Subcarrier band (minimum distance between subcarriers)
264 - Guard band (required guard band at the side of media channel)
265 - Sub-carrier Transmit Power
266 - Sub-carrier Receive HIGH Power range (Sensitivity)
267 - Sub-carrier Receive LOW Power range (Sensitivity)
268 - Sub-carrier OSNR robustness
269 - Max-pol-power-difference
270 - Max-pol-skew-difference
271 - Sub-carrier OSNR
273 Figure 3: Multi carrier Transceiver
275 6. Security Considerations
277 LMP message security uses IPsec, as described in [RFC4204]. This
278 document only defines new LMP objects that are carried in existing
279 LMP messages, similar to the LMP objects in [RFC:4209]. This
280 document does not introduce new security considerations.
282 7. IANA Considerations
284 LMP defines the following name spaces and
285 the ways in which IANA can make assignments to these namespaces:
287 - LMP Message Type
288 - LMP Object Class
289 - LMP Object Class type (C-Type) unique within the Object Class
290 - LMP Sub-object Class type (Type) unique within the Object Class
291 This memo introduces the following new assignments:
293 LMP Sub-Object Class names:
295 under DATA_LINK Class name (as defined in )
296 - Multi carrier Transceiver (sub-object Type = TBA)
298 8. Contributors
300 Zafar Ali
301 Cisco
302 3000 Innovation Drive
303 KANATA
304 ONTARIO K2K 3E8
305 zali@cisco.com
307 9. References
309 9.1. Normative References
311 [I-D.ietf-ccamp-dwdm-if-mng-ctrl-fwk]
312 Kunze, R., Grammel, G., Beller, D., Galimberti, G., and J.
313 Meuric, "A framework for Management and Control of DWDM
314 optical interface parameters", draft-ietf-ccamp-dwdm-if-
315 mng-ctrl-fwk-11 (work in progress), June 2018.
317 [ITU.G694.1]
318 International Telecommunications Union, ""Spectral grids
319 for WDM applications: DWDM frequency grid"",
320 ITU-T Recommendation G.698.2, February 2012.
322 [ITU.G698.2]
323 International Telecommunications Union, "Amplified
324 multichannel dense wavelength division multiplexing
325 applications with single channel optical interfaces",
326 ITU-T Recommendation G.698.2, November 2009.
328 [ITU.G709]
329 International Telecommunications Union, "Interface for the
330 Optical Transport Network (OTN)", ITU-T Recommendation
331 G.709, June 2016.
333 [ITU.G872]
334 International Telecommunications Union, "Architecture of
335 optical transport networks", ITU-T Recommendation G.872,
336 January 2017.
338 [ITU.G874.1]
339 International Telecommunications Union, "Optical transport
340 network (OTN): Protocol-neutral management information
341 model for the network element view", ITU-T Recommendation
342 G.874.1, November 2016.
344 [RFC4054] Strand, J., Ed. and A. Chiu, Ed., "Impairments and Other
345 Constraints on Optical Layer Routing", RFC 4054,
346 DOI 10.17487/RFC4054, May 2005,
347 .
349 [RFC4204] Lang, J., Ed., "Link Management Protocol (LMP)", RFC 4204,
350 DOI 10.17487/RFC4204, October 2005,
351 .
353 [RFC4209] Fredette, A., Ed. and J. Lang, Ed., "Link Management
354 Protocol (LMP) for Dense Wavelength Division Multiplexing
355 (DWDM) Optical Line Systems", RFC 4209,
356 DOI 10.17487/RFC4209, October 2005,
357 .
359 [RFC6205] Otani, T., Ed. and D. Li, Ed., "Generalized Labels for
360 Lambda-Switch-Capable (LSC) Label Switching Routers",
361 RFC 6205, DOI 10.17487/RFC6205, March 2011,
362 .
364 9.2. Informative References
366 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
367 DOI 10.17487/RFC2629, June 1999,
368 .
370 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
371 "Introduction and Applicability Statements for Internet-
372 Standard Management Framework", RFC 3410,
373 DOI 10.17487/RFC3410, December 2002,
374 .
376 [RFC4181] Heard, C., Ed., "Guidelines for Authors and Reviewers of
377 MIB Documents", BCP 111, RFC 4181, DOI 10.17487/RFC4181,
378 September 2005, .
380 Authors' Addresses
382 Dharini Hiremagalur (editor)
383 Juniper
384 1194 N Mathilda Avenue
385 Sunnyvale - 94089 California
386 USA
388 Phone: +1408
389 Email: dharinih@juniper.net
391 Gert Grammel (editor)
392 Juniper
393 Oskar-Schlemmer Str. 15
394 80807 Muenchen
395 Germany
397 Phone: +49 1725186386
398 Email: ggrammel@juniper.net
400 Gabriele Galimberti (editor)
401 Cisco
402 Via S. Maria Molgora, 48 c
403 20871 - Vimercate
404 Italy
406 Phone: +390392091462
407 Email: ggalimbe@cisco.com
408 Ruediger Kunze (editor)
409 Deutsche Telekom
410 Winterfeldtstr. 21-27
411 10781 Berlin
412 Germany
414 Phone: +491702275321
415 Email: RKunze@telekom.de