Transport Slice Intent
draft-contreras-nmrg-transport-slice-intent-03

Document Type Active Internet-Draft (individual)
Last updated 2020-07-26
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) 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)
NMRG                                                       LM. Contreras
Internet-Draft                                                Telefonica
Intended status: Informational                            P. Demestichas
Expires: January 27, 2021                                          WINGS
                                                             J. Tantsura
                                                            Apstra, Inc.
                                                           July 26, 2020

                         Transport Slice Intent
             draft-contreras-nmrg-transport-slice-intent-03

Abstract

   Slicing at the transport network is expected to be offered as part of
   end-to-end network slices, fostered by the introduction of new
   services such as 5G.  This document explores the usage of intent
   technologies for requesting transport slices.

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 January 27, 2021.

Copyright Notice

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

Contreras, et al.       Expires January 27, 2021                [Page 1]
Internet-Draft           Transport Slice Intent                July 2020

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Transport slice intent  . . . . . . . . . . . . . . . . . . .   3
   3.  Foundation of transport slice intents . . . . . . . . . . . .   3
   4.  Mechanisms for translating transport slice intents  . . . . .   4
     4.1.  Translation approaches and interaction with the upper
           systems . . . . . . . . . . . . . . . . . . . . . . . . .   4
     4.2.  Intent-based system suite . . . . . . . . . . . . . . . .   5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .   6
   Contributors  . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   Network slicing is emerging as the future model for service offering
   in telecom operator networks.  Conceptually, network slicing provides
   a customer with an apparent dedicated network built on top of logical
   (i.e. virtual) and/or physical functions and resources supported by a
   shared infrastructure, provided by one or more telecom operators.

   The concept of network slicing has been largely fostered by the
   advent of 5G services that are expected to be deployed on top of
   different kind of slices, each built to support specific
   characteristics (extreme low latency, high bandwidth, etc).

   As part of an end-to-end network slice it is expected to have a
   number of transport network slices providing the necessary
   connectivity to the rest of components of the end-to-end slice, e.g.,
   mobile packet core slice.

   For a definition of a transport slice refer to
   [I-D.nsdt-teas-transport-slice-definition].  The following paragraph
   is directly taken from it: "A transport slice is built based on a
   request from a higher operations system.  The interface to higher
   operations systems should express the needed connectivity in a
   technology-agnostic way, and slice customers do not need to recognize
   concrete configurations based on the technologies (e.g being more
   declarative than imperative).  The request to instantiate a transport
   slice is represented with some indicators such as SLO, and
   technologies are selected and managed accordingly."

Contreras, et al.       Expires January 27, 2021                [Page 2]
Show full document text