COMS Architecture
draft-geng-coms-architecture-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2018-01-30
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: August 3, 2018                                           Huawei
                                                            Jose. Lucena
                                                         Oscar. Hinojosa
                                                           P. Ameigeiras
                                                   University of Granada
                                                                D. Lopez
                                                           Luis. Murillo
                                                              Telefonica
                                                        January 30, 2018

                            COMS Architecture
                    draft-geng-coms-architecture-00

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 August 3, 2018.

Copyright Notice

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

Geng, et al.             Expires August 3, 2018                 [Page 1]

Internet-Draft               Network slicing                January 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 . . . . . . . . . . . . . . . . . . .  11
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  11
   9.  Informative References  . . . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   Deploying network slices on a common infrastructure logically
   requires at least three steps as shown in Figure 1:

   Step 1: Slice physical/logical resources including connectivity,
   storage, computing resources from the infrastructure.  The sliced
   resources couldn't be used directly, just as people is unable to use
   a computer with only hardware resources.

   Step 2: Install protocols and make some necessary configurations to
   make the sliced resources usable.  Following up the former example,
   this step is to install an operating system on the computer.  Just as
   there are kinds of operating systems (e.g., Linux, Windows, MacOS,
   etc.) could be selected, there are a variety of technologies (e.g.,
   VPN, SFC, Flex-E, etc.) could be used to support the network slicing.

   Step 3: Implement services on slice, just like installing
   applications on the operating system.  This is really a slice in the
   eyes of customer until this step.

Geng, et al.             Expires August 3, 2018                 [Page 2]

Internet-Draft               Network slicing                January 2018

           +------------------+
          /                  /
         /   Service Slice  /  ===> Implement services
        /                  /
Show full document text