network virtualization and service awareness properties of fns in itu-t q.21/sg13
DESCRIPTION
Joint ITU-T SG 13 and ISO/JTC1/SC 6 Workshop on “Future Networks Standardization” (Geneva, Switzerland, 11 June 2012). Network Virtualization and Service Awareness Properties of FNs in ITU-T Q.21/SG13. Myung-Ki Shin, ETRI Co- Rapporteur of Q.21/13. 1. Geneva, Switzerland, 11 June 2012. - PowerPoint PPT PresentationTRANSCRIPT
1
Network Virtualization and Network Virtualization and Service Awareness Properties Service Awareness Properties
of FNsof FNsin ITU-T Q.21/SG13 in ITU-T Q.21/SG13
Myung-Ki Shin, ETRI Co-Rapporteur of Q.21/13
Joint ITU-T SG 13 and ISO/JTC1/SC 6 Workshop on
“Future Networks Standardization”(Geneva, Switzerland, 11 June 2012)
Geneva, Switzerland, 11 June 2012
Talk Outline Motivation and background Network virtualization
Y.3011- Framework of Network Virtualization Software-defined networking (SDN)
Y.FNsdn - Framework of Software-defined networking
Conclusion and next steps
Motivation and background
Objectives and motivationFNs are recommended to provide services whose functions
are designed to be appropriate to the needs of applications and users [Y.3001]
Promising technologies for this, include Network virtualization [Y.3011] and Software-defined networking [Y.FNsdn], That enables network operators to control their networks in
unified, programmable manner, and as a result of that realizes multiple isolated and flexible networks in order to support a broad range of network architectures, services, and users that do not interfere with others.
Work items of this area
Y.3001(published)
FN VisionY.3011
(published) Framework
Y.FNsdn
Network virtualizationY.FNvirtr
eqRequirements
Y.FNvirtarch
Architecture(next step)
Framework
Software-defined networking (SDN)
Long-term perspective
Short/mid-term perspective
Service Awareness Properties
Y.FNsdn-fm
Requirements of Formal Specification
5
Recommendation Y.3011Recommendation Y.3011(Framework of Network (Framework of Network
Virtualization)Virtualization)
Scope of Y.3011 Scope of this Recommendation
Definition, overview and motivation Problem spaces Design goals Applicability of network virtualization Use cases
Why this Recommendation ? Key functional features for realizing FNs
objective, Service awareness Key technology for FNs design goals;
service diversity, functional flexibility, virtualization of resources
Y.3011- Problem statement:Why network virtualization is necessary? The current network architecture is under serious
reconsideration and people started thinking about alternatives Redefining network architecture requires many challenges Difficult to drastically change the basic architecture of large scale
networks Enormous amount of resources are required to build, operate, and maintain them
It is difficult to foresee all the user demands that may arise in the long term future
It’s necessary to support a variety of the new different architectures to accommodate the heterogeneity of future networks Network architecture should be designed to flexibly adapt the
continuous changing requirements about networks
Network virtualization definition
A technology that enables the creation of logically isolated network partitions (LINP) over shared physical networks so that heterogeneous collection of multiple virtual networks can simultaneously coexist over the shared networks. This includes the aggregation of multiple resources in a provider and appearing as a single resource.
Network virtualization is required to be capable of providing multiple virtual infrastructures those are isolated each other.
The virtualized infrastructures may be created over the single physical infrastructure
Each virtual network is isolated each other and is programmable to satisfy the user’s demand on the functionality and amount
User’s demand is conveyed to LINP manager which is required to coordinate infrastructures so that appropriate network resource is provided to the user
LINP
3 Manager
Physical Resources(Router, Switch,
Hosts, etc.)
Virtual Networks
Various Services
LINP1 LINP2
LINP
2 Manager
Virtual R
esources M
anager
LINP
1 Manager
LINP3
Physical NW 1
Physical NW 2
Physical NW 3
Physical NW 4
Physical N
W 4
Manager
Physical N
W 3
Manager
Physical N
W 2
Manager
Physical N
W 1
Manager
VirtualResources
Concept of network virtualization(LINP: Logically Isolated Network Partition)
Key properties of LINP Partitioning: each resource can be used
concurrently by multiple LINP instances Isolation: the clear isolation of any LINP
from all others Abstraction: in which a given virtual
resource need not directly correspond to its component resources
Aggregation: aggregate multiple instances to obtain increased capabilities
8 Design goals (1/2) Isolation: isolation among the LINPs
Security isolation, performance isolation, etc. Network abstraction : allows hiding the underlying
characteristics of network resources from the way in which other network resources, applications, or users interact with the network resources and establishing simplified interfaces for accessing the network resources Allows selective exposure of key network functionalities in
networks by defining of abstraction level Topology awareness and quick reconfigurability: update
of LINP's capability needs to be done dynamically and without interrupting the operation of the current LINP
8 Design goals (2/2) Performance: how to reduce the performance degradation
caused by virtualization layer or adaptation layer Programmability: programmable control plane and data
plane so that users can use customized protocols, forwarding or routing functions in the LINP (flexibility)
Management: how to provide independent management functions for each LINP Manage both virtual and physical resources, interaction,…
Mobility: movement of virtual resources including users and services
Wireless: consider some unique characteristics such as limited resource usage, signal interference
Next steps of Y.3011 Y.3011 – Published Has already started Y.FNvirtreq as a next work
Title - Requirements of Network Virtualization Virtual resource management Service mobility Wireless virtualization … (will be described more)
Architecture doc (Y.Y.FNvirtarch) will be also developed, (hopefully), when FNvirtreq is stable
14
Draft Recommendation Draft Recommendation Y.FNsdnY.FNsdn
(Framework of software-defined (Framework of software-defined networking)networking)
Scope of Y.FNsdn Scope of this draft
Definition and overview of software-defined networking;
Key properties of software-defined networking;Framework of software-defined networking,
including; programmable control plane, data forwarding plane abstraction, and how to map into virtualization of the underlying network
infrastructureUse cases of software-defined networking
Network operators’ perspectives will be covered and discussed
15
SDN definition and concept
Definition A technology to networking which allows
centralized, programmable control planes so that network operators can control and manage directly their own virtualized networks
Basic concept (1) separation of control and data planes, (2) centralized, programmable control planes
of network equipment, and (3) support of multiple, isolated virtual
networks16
Basic SDN concept
17
Data Plane(Specialized Hardware)
Control Plane
Data Plane(Forwarding Abstraction)
Control Plane
Network OS
Controller(NetworkOS)
Separation
a.3 single physical network
b.3 Multiple, isolated, virtual networks
Network OS
Client
ClientServer
Server
Mobiltye.g., Content Routing
Energy efficient forwarding
SDNLanguages
a.1 control and data planes tightly-coupled b.1 control and data planes separated
a.2 distributedcontrol of network equipments
SDNApps
b.2 centralized, programmable control of network equipments
a. Current networking technology b. SDN networking technology
Framework of SDN (1/2)
18
Data Plane(ForwardingHardware)
ProgrammableControl Plane
Control and Data Planes Separation
Network OS
Data Plane(ForwardingHardware)
Data Plane(ForwardingHardware)
Data Plane(Forwarding Hardware)
ProgrammableControl PlaneNetwork OS
Southbound Interface
Northbound Interface East-west Interface
SDN Services,Apps
App APIs
Carriers’ InfrastructureInformation
SDN Language
Framework of SDN (2/2) Programmable control plane
It is recommended that SDN has three open interfaces, including southbound, northbound, and east-west bound interfaces for control planes.
SDN languages and formal specification [Y.FNsdn-fm] It is recommended that SDN has formal specification
method and languages for application/service development.
Data plane abstraction It is recommend that SDN has well-defined, common
data plane models, rather than using of specific hardwares
Virtualization of the underlying network19
Next steps of Y.FNsdn Initial drafts are well revised at this week
Y.FNsdn and Y.FNsdn-fm Network operators’ perspectives will be
covered and discussed Collaboration with other relevant SDOs
To propagate SDN to wider telecom community Terminologies, framework, use cases, etc.
Future plan of Q.21 NEW Question X/13 – “Service awareness
properties of FNs” is being proposed and discussed for new SG13 study period (2013-2016)
This new Q will cover the following tasks - Network virtualization (i.e., Y.FNvirtreq …)SDN (i.e., Y.FNsdn, Y.FNsdn-fm, …)and other service awareness properties of FNs
22
Thank you !Thank you !Any questions ?Any questions ?