Gateway Function for Network Slicing
draft-homma-rtgwg-slice-gateway-00

Document Type Active Internet-Draft (individual)
Last updated 2019-07-08
Replaces draft-homma-nfvrg-slice-gateway
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)
rtgwg                                                           S. Homma
Internet-Draft                                                       NTT
Intended status: Informational                                 X. de Foy
Expires: January 8, 2020                               InterDigital Inc.
                                                                A. Galis
                                               University College London
                                                    L. Contreras-Murillo
                                                          Telefonica I+D
                                                            July 7, 2019

                  Gateway Function for Network Slicing
                   draft-homma-rtgwg-slice-gateway-00

Abstract

   This document describes the roles and requirements for a slice
   gateway that is a function or function group for handling data plane
   traffic, such as connecting/disconnecting and compose/decompose
   network slice subnet instances and providing network slices from end
   to end.  The interworkings between management and control elements at
   the management and control planes with the gateway function for
   controlling and orchestrating end-to-end network slices are also
   presented in this document.

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 8, 2020.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Homma, et al.            Expires January 8, 2020                [Page 1]
Internet-Draft       draft-homma-rtgwg-slice-gateway           July 2019

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Definition of Terms . . . . . . . . . . . . . . . . . . . . .   4
   3.  Motivations and Roles of SLG  . . . . . . . . . . . . . . . .   6
   4.  Architecture of Network Slicing System  . . . . . . . . . . .   8
     4.1.  Network Slice Management System Architecture  . . . . . .   8
   5.  Requirements for SLG  . . . . . . . . . . . . . . . . . . . .  10
     5.1.  Management of NS as Infrastructure  . . . . . . . . . . .  10
       5.1.1.  Data Plane Aspect . . . . . . . . . . . . . . . . . .  10
         5.1.1.1.  Identification/Classification . . . . . . . . . .  11
         5.1.1.2.  Transporting/Forwarding . . . . . . . . . . . . .  11
         5.1.1.3.  Isolation among NSs . . . . . . . . . . . . . . .  12
         5.1.1.4.  Service Chaining as Infrastructural
                   Mechanism(*Optional)  . . . . . . . . . . . . . .  13
       5.1.2.  Control/Management Planes Aspects . . . . . . . . . .  13
         5.1.2.1.  Interfaces to Controllers or Operation Systems  .  13
         5.1.2.2.  Address Resolution/Routing  . . . . . . . . . . .  13
         5.1.2.3.  Authentication Authorization Accounting (AAA) . .  13
         5.1.2.4.  Operation Administration and Maintenance(OAM) . .  14
         5.1.2.5.  Traffic Monitoring  . . . . . . . . . . . . . . .  14
     5.2.  Management of Services on NS (*Optional)  . . . . . . . .  14
       5.2.1.  Data Plane Aspect . . . . . . . . . . . . . . . . . .  14
         5.2.1.1.  Identification/Classification . . . . . . . . . .  14
         5.2.1.2.  QoS Control . . . . . . . . . . . . . . . . . . .  14
         5.2.1.3.  Steering/Service Chaining(Cooperation with VNFs)   15
       5.2.2.  Control/Management Planes Aspects . . . . . . . . . .  15
         5.2.2.1.  Interfaces to Service Management Systems  . . . .  15
         5.2.2.2.  Collection of Telemetry information . . . . . . .  15
   6.  Deployment of SLG . . . . . . . . . . . . . . . . . . . . . .  15
Show full document text