COMS Architecture
draft-geng-coms-architecture-02

Document Type Active Internet-Draft (individual)
Last updated 2018-03-05
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)
none                                                             L. Geng
Internet-Draft                                              China Mobile
Intended status: Informational                                  L. Qiang
Expires: September 6, 2018                                        Huawei
                                                              J. Ordonez
                                                      O. Adamuz-Hinojosa
                                                           P. Ameigeiras
                                                   University of Granada
                                                                D. Lopez
                                                          Telefonica I+D
                                                            L. Contreras
                                                              Telefonica
                                                           March 5, 2018

                           COMS Architecture
                    draft-geng-coms-architecture-02

Abstract

   This document defines the overall architecture of a COMS based
   network slicing system.  COMS works on the top level network slice
   orchestrator which directly communicates with the network slice
   provider and enables the technology-independent network slice
   management.

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 September 6, 2018.

Copyright Notice

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

Geng, et al.            Expires September 6, 2018               [Page 1]
Internet-Draft               Network slicing                  March 2018

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Overall Architecture  . . . . . . . . . . . . . . . . . . . .   3
   4.  Advanced Architecture . . . . . . . . . . . . . . . . . . . .   4
   5.  Integration with NFV  . . . . . . . . . . . . . . . . . . . .   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   9.  Informative References  . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   Network slicing itself is a new concept triggered by vertical
   industry, but that doesn't mean new forwarding technology is needed.
   As an example given by [draft-arkko-arch-virtualization] shows, there
   are multiple existing technologies could be used for network slicing
   - VLAN tags are used in an ethernet segment, MPLS or VPNs across the
   domain.  If the storage and computing resources are considered, there
   will be more available technologies (e.g., SFC).

   Let's follow IETF's routine and image what will happen from the
   bottom-up view.  At first, existing technologies evolve toward
   network slicing at forwarding plane in their own scopes.  Then slice
   management related functions will be patched at management/control
   planes.  When a network slice is going to be deployed inside a
   domain, one of implementation technology will be selected, and the NS
   provider directly operates on the management plane of this selected
   technology.  For example, If VPN is selected as the implementation
   technology, then a network slice is a VPN for the NS provider in this
   domain.  While if SFC is selected in other domain, then a network
   slice is a SFC for NS provider.  What will happen if a network slice
   across both VPN and SFC domains?  There is no uniform management
Show full document text