framework for black link management and control draft-kunze-black-link-management-framework-00...

7
Framework for Black Link Management and Control draft-kunze-black-link-management- framework-00 Ruediger Kunze Deutsche Telekom March 2011 80th IETF Prague 1

Upload: christina-jennings

Post on 30-Dec-2015

212 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Framework for Black Link Management and Control draft-kunze-black-link-management-framework-00 Ruediger KunzeDeutsche Telekom March 2011 80th IETF Prague1

Framework for Black Link Management and Control

draft-kunze-black-link-management-framework-00

Ruediger Kunze Deutsche Telekom

March 2011 80th IETF Prague 1

Page 2: Framework for Black Link Management and Control draft-kunze-black-link-management-framework-00 Ruediger KunzeDeutsche Telekom March 2011 80th IETF Prague1

BL Introduction

Black Link: The Black Link approach [ITU-T G.698.2] allows supporting an optical transmitter/receiver pair of one or different vendors to inject a DWDM channel and run it over an optical network composed of amplifiers, filters, add-drop multiplexers from a different vendor. Therefore the standard defines the ingress and egress parameters at the interface Ss and Rs.

Tx (vendor X)

k

SS

Optical path (incl. e.g. OAs,

OADMs) RS

k

Rx (vendor Y)

OD OM

Black- link (vendor A)

Page 3: Framework for Black Link Management and Control draft-kunze-black-link-management-framework-00 Ruediger KunzeDeutsche Telekom March 2011 80th IETF Prague1

Motivation• Black Link (BL) as specified by ITU-T offers carriers an

additional option to deploy optical interfaces in a WDM network

– BL is currently defined for 2,5G and 10G and will be extended by ITU-T for 40G,100G and beyond

• The approach offers some benefits but has also some challenges regarding the operation of the network

– Today it is state-of-the-art to interconnect IP Routers from different vendors and WDM transport systems using short-reach, grey interfaces

– To ensure applicability as in state-of-the-art networks, the BL approach must support a multi-vendor environment

– The traditional approach operating carrier networks today is based on a separation of transport and packet, means different departments with different tools operate and manage network and services.

• Initial requirements discussed on the draft– Interoperable BL solutions– Manageability based on the Status-Quo today

Page 4: Framework for Black Link Management and Control draft-kunze-black-link-management-framework-00 Ruediger KunzeDeutsche Telekom March 2011 80th IETF Prague1

Document Scope

• Focus on solutions for management and control of the optical interfaces:– BL operation scenarios/ uses cases– Black Link Control and Management Solutions– Requirements for BL and FW deployments (could

be further discussed in a separate document)• WSON is complementary

– Focusing on the management and control of the optical interface.

– Dynamic Wavelength switching and assignment is out of scope

Page 5: Framework for Black Link Management and Control draft-kunze-black-link-management-framework-00 Ruediger KunzeDeutsche Telekom March 2011 80th IETF Prague1

Solution initially in scope.

EMS

NMS IP NMS IP

EMS EMS

EMS – Element Management SystemNMS – Network Management System

NMS OD

Tx(vendor X)

k

SS

Optical path(incl. e.g. OAs,

OADMs)RS

k

Terminal # 2

Rx(vendor Y)

ODOM

Black- link (vendor A)

Terminal # 1

Page 6: Framework for Black Link Management and Control draft-kunze-black-link-management-framework-00 Ruediger KunzeDeutsche Telekom March 2011 80th IETF Prague1

Key Requirements• Interoperable BL solutions• Specification of solutions ensuring an

interoperable management of BL deployments for 10G, 40G and beyond.

• Must work with legacy equipment and management components.

Page 7: Framework for Black Link Management and Control draft-kunze-black-link-management-framework-00 Ruediger KunzeDeutsche Telekom March 2011 80th IETF Prague1

Next Steps

• Requesting Working Group feedback• Progressing work on Use Case section and on

Requirements• Extend solution section if there are further

approaches …• Feedback from other operators invited• Corresponding MIB document available