Problem Statement of Network Slicing in IP/MPLS Networks
draft-dong-network-slicing-problem-statement-00

Document Type Active Internet-Draft (individual)
Last updated 2016-10-31
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)
Network Working Group                                            J. Dong
Internet-Draft                                                 S. Bryant
Intended status: Informational                       Huawei Technologies
Expires: May 4, 2017                                    October 31, 2016

        Problem Statement of Network Slicing in IP/MPLS Networks
            draft-dong-network-slicing-problem-statement-00

Abstract

   The research and standardization of IMT-2020 (a.k.a. 5G) are in
   progress in several industry communities and standard organizations.
   The goal of 5G is to integrate various services, each of which has a
   set of unique requirements, into a single network, such that each
   service has a customized network suited to its needs.  The concept
   "Network Slicing" is widely discussed and considered as the key
   mechanism to meet the diverse service requirements concurrently with
   the same physical network infrastructure.  This document provides an
   overview of the concept "network slicing" in the current IMT-2020
   (a.k.a. 5G) related works, and discusses the corresponding
   requirements on IP/MPLS network, which will be used as the mobile
   transport network for 5G.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

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 May 4, 2017.

Dong & Bryant              Expires May 4, 2017                  [Page 1]
Internet-Draft      Network Slicing Problem Statement       October 2016

Copyright Notice

   Copyright (c) 2016 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.  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.  Network Slicing Problem Statement . . . . . . . . . . . . . .   3
     2.1.  Isolation and Separation  . . . . . . . . . . . . . . . .   3
     2.2.  Customization of the Topology . . . . . . . . . . . . . .   5
     2.3.  Flexibility of the Topology . . . . . . . . . . . . . . .   7
     2.4.  Guaranteed Quality of Service . . . . . . . . . . . . . .   7
     2.5.  Management Considerations . . . . . . . . . . . . . . . .   8
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   6.  Informative References  . . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   The research and standardization of IMT-2020 (a.k.a. 5G) are in
   progress in several industry communities and standard organizations.
   The goal of 5G is to integrate various services, each of which has a
   set of unique requirements, into a single network, such that each
   service has a customized network suited to its needs.  The concept
   "Network Slicing" is widely discussed and considered as the key
   mechanism to meet diverse service requirements concurrently with the
   same physical network infrastructure.

   The Next Generation Mobile Networks (NGMN) gives the definition of
   network slice in [Network-Slicing-Concept]:

   "Network Slice Instance: a set of network functions, and resources to
   run these network functions, forming a complete instantiated logical
Show full document text