Transport Northbound Interface Applicability Statement and Use Cases
draft-ietf-ccamp-transport-nbi-use-cases-01

Document Type Active Internet-Draft (ccamp WG)
Last updated 2017-10-30
Replaces draft-tnbidt-ccamp-transport-nbi-use-cases
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
CCAMP Working Group                                      I. Busi (Ed.)
Internet Draft                                                 Huawei
Intended status: Informational                                D. King
                                                  Lancaster University

Expires: April 2018                                   October 30, 2017

    Transport Northbound Interface Applicability Statement and Use Cases
                draft-ietf-ccamp-transport-nbi-use-cases-01

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), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

   This Internet-Draft will expire on April 30, 2018.

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
   (https://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.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Busi & King, et al.    Expires April 30, 2018                 [Page 1]
Internet-Draft         Transport NBI Use Cases            October 2017

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 to be
   used as the basis for applicability statements analyzing how IETF
   data models can be used for transport network control and
   management.

Table of Contents

   1. Introduction ................................................ 3
      1.1. Scope of this document                                   4
   2. Terminology ................................................. 4
   3. Conventions used in this document                             4
      3.1. Topology and traffic flow processing ................... 4
   4. Use Case 1: Single-domain with single-layer ................. 5
      4.1. Reference Network ...................................... 5
         4.1.1. Single Transport Domain - OTN Network ............. 5
      4.2. Topology Abstractions .................................. 8
      4.3. Service Configuration .................................. 9
         4.3.1. ODU Transit ....................................... 9
         4.3.2. EPL over ODU ..................................... 10
         4.3.3. Other OTN Client Services ........................ 10
         4.3.4. EVPL over ODU .................................... 11
         4.3.5. EVPLAN and EVPTree Services ...................... 12
      4.4. Multi-functional Access Links ......................... 13
      4.5. Protection Requirements ............................... 14
         4.5.1. Linear Protection ................................ 15
   5. Use Case 2: Single-domain with multi-layer ................. 15
      5.1. Reference Network ..................................... 15
      5.2. Topology Abstractions ................................. 16
      5.3. Service Configuration ................................. 16
   6. Use Case 3: Multi-domain with single-layer ................. 16
      6.1. Reference Network ..................................... 16
      6.2. Topology Abstractions ................................. 19

Busi & King, et al.    Expires April 30, 2018                 [Page 2]
Show full document text