Considerations for defining a Transport Slice NBI
draft-contreras-teas-slice-nbi-00

Document Type Active Internet-Draft (individual)
Last updated 2019-11-04
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized 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)
TEAS Working Group                                         LM. Contreras
Internet-Draft                                                Telefonica
Intended status: Informational                                  S. Homma
Expires: May 7, 2020                                                 NTT
                                                       J. Ordonez-Lucena
                                                              Telefonica
                                                        November 4, 2019

           Considerations for defining a Transport Slice NBI
                   draft-contreras-teas-slice-nbi-00

Abstract

   The transport network is an essential component in the end-to-end
   delivery of services and, consequently, with the advent of network
   slicing it is necessary to understand what could be the way in which
   the transport network is consumed as a slice.  This document analyses
   the needs of potential transport slice consumers in order to identify
   the functionality required on the North Bound Interface (NBI) of a
   transport slice producer for satisfying such transport slcie
   requests.

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 https://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 May 7, 2020.

Copyright Notice

   Copyright (c) 2019 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

Contreras, et al.          Expires May 7, 2020                  [Page 1]
Internet-Draft     Considerations Transport Slice NBI      November 2019

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions used in this document . . . . . . . . . . . . . .   3
   3.  Northbound interface for transport slices . . . . . . . . . .   3
   4.  Transport slice use cases . . . . . . . . . . . . . . . . . .   4
     4.1.  5G Services . . . . . . . . . . . . . . . . . . . . . . .   4
       4.1.1.  Generic Slice Template  . . . . . . . . . . . . . . .   5
       4.1.2.  Categorization of GST attributes  . . . . . . . . . .   6
         4.1.2.1.  Attributes with direct impact on the transport
                   slice definition  . . . . . . . . . . . . . . . .   7
         4.1.2.2.  Attributes with indirect impact on the transport
                   slice definition  . . . . . . . . . . . . . . . .   7
         4.1.2.3.  Attributes with no impact on the transport slice
                   definition  . . . . . . . . . . . . . . . . . . .   8
     4.2.  NFV-based services  . . . . . . . . . . . . . . . . . . .   8
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   A number of new technologies, such as 5G, NFV and SDN are not only
   evolving the network from a pure technological perspective but also
   are changing the concept in which new services are offered to the
   customers [I-D.homma-slice-provision-models] by introducing the
   concept of network slicing.

   The transport network is an essential component in the end-to-end
   delivery of services and, consequently, it is necessary to understand
   what could be the way in which the transport network is consumed as a
   slice.

   In this document it is assumed that there exists a (logically)
   centralized component in the transport network, namely Transport
   Slice Producer (TSP) with the responsibilities on the control and
   management of the transport slices invoked for a given service, as
Show full document text