Transport Northbound Interface Use Cases
draft-tnbidt-ccamp-transport-nbi-use-cases-01
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-03-13
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
CCAMP Working Group I. Busi (Ed.)
Internet-Draft Huawei
Intended status: Informational D. King (Ed.)
Expires: September 14, 2017 Lancaster University
March 13, 2017
Transport Northbound Interface Use Cases
draft-tnbidt-ccamp-transport-nbi-use-cases-01
Abstract
Transport network domains, including Optical Transport Network (OTN)
and Wavelength Division Multiplexing (WDM) networks, are typically
deployed based on a single vendor or technology platforms. They are
often managed using proprietary interfaces to dedicated Element
Management Systems (EMS), Network Management Systems (NMS) and
increasingly Software Defined Network (SDN) controllers.
A well-defined open interface to each domain management system or
controller is required for network operators to facilitate control
automation and orchestrate end-to-end services across multi-domain
networks. These functions may be enabled using standardized data
models (e.g. YANG), and appropriate protocol (e.g., RESTCONF).
This document describes the key use cases and requirements for
transport network control and management. It reviews proposed and
existing IETF transport network data models, their applicability,
and highlights gaps and requirements.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 14, 2017.
King & Busi, et al. Expires September, 2017 [Page 1]
Internet-Draft Transport NBI Use Cases February 2017
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. This document is subject
to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
Documents (http://trustee.ietf.org/license-info) in effect on the
date of publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document.
Table of Contents
1. Introduction.................................................1
2. Conventions used in this document............................3
3. Use Case 1: Single-domain with single-layer..................3
3.1. Reference Network.......................................3
3.1.1. Single Transport Domain - OTN Network..............6
3.1.2. Single Domain - ROADM Network......................6
3.2. Topology Abstractions...................................6
3.3. Service Configuration...................................7
3.3.1. ODU Transit........................................7
3.3.2. EPL over ODU.......................................8
3.3.3. Other OTN Client Services..........................8
3.3.4. EVPL over ODU......................................9
3.3.5. EVPLAN and EVPTree Services........................9
3.3.6. Virtual Network Services...........................9
3.4. Multi-functional Access Links...........................9
4. Use Case 2: Single-domain with multi-layer...................9
5. Use Case 3: Multi-domain with single-layer...................9
6. Use Case 4: Multi-domain and multi-layer.....................9
7. Security Considerations......................................9
8. IANA Considerations..........................................9
9. References...................................................10
9.1. Normative References....................................10
9.2. Informative References..................................10
10. Acknowledgments.............................................10
Authors' Addresses..............................................11
1. Introduction
A common open interface to each domain controller/management system
is pre-requisite for network operators to control multi-vendor and
multi-domain networks and enable also service provisioning
coordination/automation. This can be achieved by using standardized
Show full document text