IPv6-based SDN and NFV; Deployment of IPv6-based SDN and NFV

DGR/IP6-0010

General Information

Status
Published
Publication Date
21-Dec-2017
Technical Committee
Current Stage
12 - Completion
Due Date
04-Jan-2018
Completion Date
22-Dec-2017
Ref Project

Buy Standard

Standard
ETSI GR IP6 010 V1.1.1 (2017-12) - IPv6-based SDN and NFV; Deployment of IPv6-based SDN and NFV
English language
13 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

ETSI GR IP6 010 V1.1.1 (2017-12)






GROUP REPORT
IPv6-based SDN and NFV;
Deployment of IPv6-based SDN and NFV
Disclaimer
The present document has been produced and approved by the IPv6 Integration (IP6) ETSI Industry Specification Group (ISG)
and represents the views of those members who participated in this ISG.
It does not necessarily represent the views of the entire ETSI membership.

---------------------- Page: 1 ----------------------
2 ETSI GR IP6 010 V1.1.1 (2017-12)



Reference
DGR/IP6-0010
Keywords
IPv6, NFV

ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2017.
All rights reserved.

TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members.
GSM® and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3 ETSI GR IP6 010 V1.1.1 (2017-12)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 5
3 Abbreviations . 5
4 IPv6-based SDN & NFV Deployment . 6
4.1 Introduction . 6
4.2 Unified Openv6 Use case . 6
4.2.1 Evolve from one Scenario to Another. 6
4.2.2 Multiple Transition Mechanisms Co-Exist . 7
4.2.3 Scattered Address Pool Management . 7
4.2.4 Extensibility . 7
4.3 Open IPv6 Architecture: Powered by SDN . 8
4.3.1 Overall Architecture . 8
4.3.2 How Open IPv6 works . 9
4.3.3 Processing Flow-Based Services . 9
4.4 vTransition for IPv6: powered by NFV . 10
4.5 NFV and SDN = Programmability . 10
4.6 Management = Programmability . 11
4.7 Conclusion . 11
Annex A: Authors & contributors . 12
History . 13


ETSI

---------------------- Page: 3 ----------------------
4 ETSI GR IP6 010 V1.1.1 (2017-12)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Foreword
This Group Report (GR) has been produced by ETSI Industry Specification Group (ISG) IPv6 Integration (IP6).
Modal verbs terminology
In the present document "should", "should not", "may", "need not", "will", "will not", "can" and "cannot" are to be
interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.

ETSI

---------------------- Page: 4 ----------------------
5 ETSI GR IP6 010 V1.1.1 (2017-12)
1 Scope
The present document outlines the motivation for the deployment of IPv6-based Cloud Computing, the objectives, the
technology guidelines, the step-by-step process, the benefits, the risks, the challenges and the milestones.
2 References
2.1 Normative references
Normative references are not applicable in the present document.
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] IETF RFC 6333: ''Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion'', A.
Durand, R. Droms, J. Woodyatt et al., August 2011.
[i.2] IETF RFC 6877: "464XLAT: Combination of Stateful and Stateless Translation", M. Mawatari,
M. Kawashima, C. Byrne, April 2013.
[i.3] IETF RFC 6535: "Dual-Stack Hosts Using "Bump-in-the-Host" (BIH), B. Huang, H. Deng, T.
Savolainen, February 2012.
[i.4] IETF RFC 6146: "Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients
to IPv4 Servers", M. Bagnulo, P. Matthews, I. van Beijnum, April 2011.
3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ALG Application Layer Gateway
API Application Programming Interface
CAPEX Capital Expenditure
CGN Carrier-Grade NAT
DS-Lite Dual Stack Lite
IPv4 Internet Protocol version 4
IPv6 Internet Protocol version 6
ISP Internet Service Provider
lw4over6 lightweight IPv4 over IPv6
MAP Mapping of Address and Port
NAT Network Address Translation
NAT44 Network Address Translation IPv4 to IPv4
NAT64 Network Address Translation IPv6 to IPv4
NFV Network Functions Virtualisation
NFVI Network Functions Virtualisation Infrastructure
OPEX Operations Expenditure
OSS Operations Support System
ETSI

---------------------- Page: 5 ----------------------
6 ETSI GR IP6 010 V1.1.1 (2017-12)
QoS Quality of Service
SDN Software Defined Networking
SUPA Simplified Use of Policy Abstraction
TDP Transition Data Plane
4 IPv6-based SDN & NFV Deployment
4.1 Introduction
The exhaustion of the IPv4 address space has been a practical problem that providers are facing today. The migration to
IPv6 is ongoing and picking up steam throughout the world.
Depending on the amount of technology debt and legacy present in the existing infrastructure, the IPv6 transition might
require significant upgrades and different approaches to the roll-out in order to maintain efficiency. Instrumentation and
operational tools, back-end systems and processes will also need to be updated for the new protocol. Therefore,
operators might have to upgrade network devices to support different transition strategies but more importantly to
support different visions of the future infrastructure. The transition will increase the OPEX and CAPEX needs during
the transition. The increase will be determined by the specifics of the provider and particularly by the speed with which
the provider chooses or is forced to execute the transition.
One option is to consider managing the transition by using SDN/NFV concepts and technologies. A unified Transition
Data Plane (TDP) enables DevOps in IT environment by providing extensibility via programmability, by integrating
deployment and operation into the implementation, and by streamlining OSS. The IPv6 transition can be viewed as
another service enablement exercise managed by TDP. In a TDP enabled environment, an IPv6 transition powered by
SDN could lower the deployment and operational costs by decoupling the data plane and control plane, and by
providing unified data plane devices. It also nurtures the development of native IPv6 services through the availability of
open Northbound APIs. An Open IPv6 can reduce the operational complexity and risk via the unified data plane which
adapts to different transition scenarios.
4.2 Unified Openv6 Use case
4.2.1 Evolve from one Scenario to Another
During the IPv6 transition period, the network will go through three stages: IPv4-only network, dual-stack network and
IPv6-only network. The network should support both IPv4 services and IPv6 services at each stage.
There are multiple IPv6 transition technologies for different network scenarios (e.g. IPv4 network for IPv4/IPv6 user
access, IPv6 network for IPv4/IPv6 user access, IPv4 servers for IPv6 visitors, etc.). Different network scenarios will
c
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.