Technology Independent Information Model for Network Slicing
draft-qiang-coms-netslicing-information-model-02
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2018-01-25
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
|
Additional URLs |
|
|
| 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. Qiang
Internet-Draft Huawei
Intended status: Informational A. Galis
Expires: July 30, 2018 University College London
L. Geng
China Mobile
K. Makhijani
Huawei
P. Martinez-Julia
NICT
H. Flinck
Nokia
X. de Foy
InterDigital Inc.
January 26, 2018
Technology Independent Information Model for Network Slicing
draft-qiang-coms-netslicing-information-model-02
Abstract
This document provides a technology independent information model for
transport network slicing.
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 July 30, 2018.
Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved.
Qiang, et al. Expires July 30, 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 . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Network Slice Tree Structure . . . . . . . . . . . . . . . . 4
3.1. resources . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1.1. nodes . . . . . . . . . . . . . . . . . . . . . . . . 6
3.1.2. links . . . . . . . . . . . . . . . . . . . . . . . . 7
3.1.3. storage-units . . . . . . . . . . . . . . . . . . . . 8
3.1.4. compute-units . . . . . . . . . . . . . . . . . . . . 9
3.2. generalized-function-block . . . . . . . . . . . . . . . 9
3.3. slice-level-attributes . . . . . . . . . . . . . . . . . 10
4. Operations . . . . . . . . . . . . . . . . . . . . . . . . . 13
5. Yang Module . . . . . . . . . . . . . . . . . . . . . . . . . 14
6. Security Considerations . . . . . . . . . . . . . . . . . . . 27
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 27
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 27
9.1. Normative References . . . . . . . . . . . . . . . . . . 27
9.2. Informative References . . . . . . . . . . . . . . . . . 27
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27
1. Introduction
Network slicing is a tool to share network resources and to offer
customized network architectures for diverse use cases that share the
same underlying infrastructure [NGMN-NS-Framework]. Customers may
not be familiar with underlying networking technologies, and
therefore may prefer to interface with network slices in a
technology-agnostic way. On the other hand, service providers may
have multiple candidate technologies for supporting network slicing.
As shown in Figure 1, there is a gap between technology-agnostic
network slicing service requirements and specific implementation
technologies, that needs to be filled by a technology independent
Show full document text