draft-ietf-ccamp-dwdm-if-mng-ctrl-fwk-02.txt   draft-ietf-ccamp-dwdm-if-mng-ctrl-fwk-03.txt 
Internet Engineering Task Force R. Kunze, Ed. Internet Engineering Task Force R. Kunze, Ed.
Internet-Draft Deutsche Telekom Internet-Draft Deutsche Telekom
Intended status: Informational G. Grammel, Ed. Intended status: Informational G. Grammel, Ed.
Expires: January 9, 2017 Juniper Expires: May 4, 2017 Juniper
D. Beller, Ed. D. Beller
Nokia Nokia
G. Galimberti, Ed. G. Galimberti, Ed.
Cisco Cisco
July 8, 2016 October 31, 2016
A framework for Management and Control of DWDM optical interface A framework for Management and Control of DWDM optical interface
parameters parameters
draft-ietf-ccamp-dwdm-if-mng-ctrl-fwk-02 draft-ietf-ccamp-dwdm-if-mng-ctrl-fwk-03
Abstract Abstract
To ensure an efficient data transport, meeting the requirements To ensure an efficient data transport, meeting the requirements
requested by today's IP-services the control and management of DWDM requested by today's IP-services the control and management of DWDM
interfaces is a precondition for enhanced multilayer networking and interfaces is a precondition for enhanced multilayer networking and
for an further automation of network provisioning and operation. for an further automation of network provisioning and operation.
This document describes use cases and requirements for the control This document describes use cases and requirements for the control
and management of optical interfaces parameters according to and management of optical interfaces parameters according to
different types of single channel DWDM interfaces. The focus is on different types of single channel DWDM interfaces. The focus is on
skipping to change at page 1, line 48 skipping to change at page 1, line 48
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 9, 2017. This Internet-Draft will expire on May 4, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 8, line 40 skipping to change at page 8, line 40
Tx L3---|->| / | DWDM | | ^ | DWDM | \ |--|-->Rx L3 Tx L3---|->| / | DWDM | | ^ | DWDM | \ |--|-->Rx L3
+---+ | | / | Link +----|--|----+ Link | \ | | +---+ +---+ | | / | Link +----|--|----+ Link | \ | | +---+
+-----------+ | | +----------+ +-----------+ | | +----------+
+--+ +--+ +--+ +--+
| | | |
v | v |
+---+ +---+ +---+ +---+
RxLx TxLx RxLx TxLx
+---+ +---+ +---+ +---+
Ss = Reference point at the DWDM network element tributary output Ss = Reference point at the DWDM network element tributary output
Rs = Reference point at the DWDM network element tributary input Rs = Reference point at the DWDM network element tributary input
Lx = Lambda x Lx = Lambda x
OM = Optical Mux OM = Optical Mux
OD = Optical Demux OD = Optical Demux
OADM = Optical Add Drop Mux OADM = Optical Add Drop Mux
Linear DWDM network as per ITU-T G.698.2 Linear DWDM network as per ITU-T G.698.2
Figure 2: Linear Black Link Figure 2: Linear Black Link
As shown in Figure 2, the administrative domain may consists of As shown in Figure 2, the administrative domain may consists of
several vendor domains. Even a in that case a common north bound several vendor domains. Even a in that case a common north bound
management interface is required to ensure a consistent management of management interface is required to ensure a consistent management of
the entire connection. the entire connection.
skipping to change at page 20, line 4 skipping to change at page 20, line 4
An alarm shall be raised if P(in) or P(Rx) drops below a An alarm shall be raised if P(in) or P(Rx) drops below a
configured threshold (t [dB]): configured threshold (t [dB]):
- P(in) < P(Tx) - a(Tx) - t (Tx direction) - P(in) < P(Tx) - a(Tx) - t (Tx direction)
- P(Rx) < P(out) - a(Rx) - t (Rx direction) - P(Rx) < P(out) - a(Rx) - t (Rx direction)
- a(Tx) =| a(Rx) - a(Tx) =| a(Rx)
Figure 5: Extended LMP Model Figure 5: Extended LMP Model
5.2.1. Pure Access Link (AL) Monitoring Use Case 5.2.1. Pure Access Link (AL) Monitoring Use Case
Figure 6 illustrates the access link monitoring use case and the Figure 6 illustrates the access link monitoring use case and the
different physical properties involved that are defined below: different physical properties involved that are defined below:
- Ss, Rs: Single Channel reference points - Ss, Rs: Single Channel reference points
- P(Tx): current optical output power of transmitter Tx - P(Tx): current optical output power of transmitter Tx
- a(Tx): access link attenuation in Tx direction (external - a(Tx): access link attenuation in Tx direction (external
transponder point of view) transponder point of view)
- P(in): measured current optical input power at the input port - P(in): measured current optical input power at the input port
of border DWDM NE of border DWDM NE
- t: user defined threshold (tolerance) - t: user defined threshold (tolerance)
- P(out): measured current optical output power at the output port - P(out): measured current optical output power at the output port
of border DWDM NE of border DWDM NE
- a(Rx): access link attenuation in Rx direction (external - a(Rx): access link attenuation in Rx direction (external
transponder point of view) transponder point of view)
- P(Rx): current optical input power of receiver Rx - P(Rx): current optical input power of receiver Rx
Description: Description:
- The access link attenuation in both directions (a(Tx), a(Rx)) - The access link attenuation in both directions (a(Tx), a(Rx))
is known or can be determined as part of the commissioning is known or can be determined as part of the commissioning
process. Typically, both values are the same. process. Typically, both values are the same.
- A threshold value t has been configured by the operator. This - A threshold value t has been configured by the operator. This
should also be done during commissioning. should also be done during commissioning.
- A control plane protocol (e.g. this draft) is in place that allows - A control plane protocol (e.g. this draft) is in place that allows
to periodically send the optical power values P(Tx) and P(Rx) to periodically send the optical power values P(Tx) and P(Rx)
to the control plane protocol instance on the DWDM border NE. to the control plane protocol instance on the DWDM border NE.
This is llustrated in Figure 3. This is illustrated in Figure 3.
- The DWDM border NE is capable to periodically measure the optical - The DWDM border NE is capable to periodically measure the optical
power Pin and Pout as defined in G.697 by power monitoring points power Pin and Pout as defined in G.697 by power monitoring points
depicted as yellow triangles in the figures below. depicted as yellow triangles in the figures below.
Access Link monitoring process: Access Link monitoring process:
- Tx direction: the measured optical input power Pin is compared - Tx direction: the measured optical input power Pin is compared
with the expected optical input power P(Tx) - a(Tx). If the with the expected optical input power P(Tx) - a(Tx). If the
measured optical input power P(in) drops below the value measured optical input power P(in) drops below the value
(P(Tx) - a(Tx) - t) a low power alarm shall be raised indicating (P(Tx) - a(Tx) - t) a low power alarm shall be raised indicating
that the access link attenuation has exceeded a(Tx) + t. that the access link attenuation has exceeded a(Tx) + t.
- Rx direction: the measured optical input power P(Rx) is - Rx direction: the measured optical input power P(Rx) is
compared with the expected optical input power P(out) - a(Rx). compared with the expected optical input power P(out) - a(Rx).
If the measured optical input power P(Rx) drops below the value If the measured optical input power P(Rx) drops below the value
(P(out) - a(Rx) - t) a (P(out) - a(Rx) - t) a
low power alarm shall be raised indicating that the access link low power alarm shall be raised indicating that the access link
attenuation has exceeded a(Rx) + t. attenuation has exceeded a(Rx) + t.
-to avoid toggling errors, the low power alarm threshold shall be - to avoid toggling errors, the low power alarm threshold shall be
lower than the alarm clear threshold. lower than the alarm clear threshold.
Figure 6 Use case 1: Access Link monitoring Figure 6 Use case 1: Access Link monitoring
+----------+ +--------------------------+ +----------+ +--------------------------+
| +------+ | P(Tx), P(Rx) | +-------+ | | +------+ | P(Tx), P(Rx) | +-------+ |
| | | | =================> | | | | | | | | =================> | | | |
| | LMP | | P(in), P(out) | | LMP | | | | LMP | | P(in), P(out) | | LMP | |
| | | | <================= | | | | | | | | <================= | | | |
| +------+ | | +-------+ | | +------+ | | +-------+ |
| | | | | | | |
skipping to change at page 24, line 29 skipping to change at page 24, line 29
The following requirements are focusing on the usage of standardised The following requirements are focusing on the usage of standardised
integrated single channel interfaces but also valid in other integrated single channel interfaces but also valid in other
environments. environments.
1 To ensure a lean management and provisioning process of single 1 To ensure a lean management and provisioning process of single
channel interfaces management and control plane of the client channel interfaces management and control plane of the client
and DWDM network must be aware of the parameters of the and DWDM network must be aware of the parameters of the
interfaces and the optical network to properly setup the optical interfaces and the optical network to properly setup the optical
connection. connection.
2 A standardized northbound API (to network management system)must 2 A standardized northbound API (to network management system)
be supported based on SNMP and Netconf. based on Netconf must be supported, alternatively SNMP should
be supported too.
3 A standardized data model for single channel interfaces must be 3 A standardized data model for single channel interfaces must be
supported to exchange optical parameters with control/ management supported to exchange optical parameters with control/management
plane. plane.
4..Netconf should be used also for configuration of the single 4..Netconf should be used also for configuration of the single
channel interfaces including the setting of the power. channel interfaces including the setting of the power.
5 LMP should be extended and used in cases where optical 5 LMP should be extended and used in cases where optical
parameters need to be exchanged between peer nodes to correlate parameters need to be exchanged between peer nodes to correlate
link characteristics and adopt the working mode of the single link characteristics and adopt the working mode of the single
channel interface. channel interface.
6 Legacy operational models should be supported (parameters must 6 Legacy operational models should be supported (parameters must
be exchanged with the DWDM transport EMS to manage the be exchanged with the DWDM transport EMS to manage the
configuration and the transmission of alarms and other FCAPS configuration and the transmission of alarms and other FCAPS
messages. messages.
7 LMP should be used to adjust the output power of the single 7 LMP should be used to adjust the output power of the single
channel DWDM interface to ensure that the interface works in channel DWDM interface to ensure that the interface works in
the right range defined by the application code. the right range defined by the application code.
8 Parameters e.g. PRE-FEC BER could be used to trigger a FRR 8 Parameters e.g. PRE-FEC BER should be used to trigger a FRR
mechanism on the IP control plane to reroute traffic before mechanism on the IP control plane to reroute traffic before
the link breaks. the link breaks.
9 LMP should be used to automate the end to end connection 9 LMP should be used to automate the end to end connection
setup of the optical connection. setup of the optical connection.
10 Power monitoring functions at both ends of the DWDM connection 10 Power monitoring functions at both ends of the DWDM connection
should be implemented to further automate the setup and should be implemented to further automate the setup and
shoutdown process of the optical interfaces. shoutdown process of the optical interfaces.
11 A standardized procedure to setup an optical connection must be 11 A standardized procedure to setup an optical connection should
defined and implemented in DWDM and client devices (containing be defined and implemented in DWDM and client devices
the single channel optical interface).LMP should be used to (containing the single channel optical interface).LMP should be
ensure that the process follows the right order. used to ensure that the process follows the right order.
12 Pre-tested and configured backup paths should be stored in so 12 Pre-tested and configured backup paths should be stored in so
called backup profiles. In fault cases this wavelength routes called backup profiles. In fault cases this wavelength routes
can be used to recover the service. can be used to recover the service.
13 LMP should be used to monitor and observe the access link. 13 LMP should be used to monitor and observe the access link.
7. Acknowledgements 7. Acknowledgements
The authors would like to thank all who supported the work with The authors would like to thank all who supported the work with
skipping to change at page 29, line 22 skipping to change at page 29, line 22
Gert Grammel (editor) Gert Grammel (editor)
Juniper Juniper
Oskar-Schlemmer Str. 15 Oskar-Schlemmer Str. 15
80807 Muenchen 80807 Muenchen
Germany Germany
Phone: +49 1725186386 Phone: +49 1725186386
Email: ggrammel@juniper.net Email: ggrammel@juniper.net
Dieter Beller (editor) Dieter Beller
Nokia Nokia
Lorenzstrasse, 10 Lorenzstrasse, 10
70435 Stuttgart 70435 Stuttgart
Germany Germany
Phone: +4971182143125 Phone: +4971182143125
Email: Dieter.Beller@nokia.com Email: Dieter.Beller@nokia.com
Gabriele Galimberti (editor) Gabriele Galimberti (editor)
Cisco Cisco
 End of changes. 14 change blocks. 
61 lines changed or deleted 62 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/