1. Geneva, Switzerland, 14 November 2014 NaaS and IaaS Functional Requirements Ying Cheng China Unicom chengying10@chinaunicom.cn ITU Workshop on “Cloud Computing Standards – Today and the Future” (Geneva, Switzerland 14 November 2014) Nan Chen China Telecom chenn@gsta.com

2. Geneva, Switzerland, 14 November 2014 2 Contents Part I: Functional Requirements of Network as a Service Based on Recommendation ITU-T Y.3512 (Cloud computing - Functional requirements of Network as a Service) Part II: Functional Requirements of Infrastructure as a Service Based on Recommendation ITU-T Y.3513 (Cloud computing - Functional requirements of Infrastructure as a Service)

3. Geneva, Switzerland, 14 November 2014 3 Contents Part I: Functional Requirements of Network as a Service Based on Recommendation ITU-T Y.3512 (Cloud computing - Functional requirements of Network as a Service)

4. Geneva, Switzerland, 14 November 2014 4 Summary of Y.3512 Scope High level concept of NaaS; Functional requirements of NaaS application, NaaS platform and NaaS connectivity; Typical NaaS use cases of NaaS application, NaaS platform and NaaS connectivity. Statistics 61 contributions from 8 sector members: China Unicom, Orange Polska SA, Orange, ETRI, ZTE, Microsoft, Huawei, Alcatel-Lucent Shanghai Bell 8 meetings: 7 physical meetings and 1 e-meeting 13 use cases: 3 in general and 10 in detail 26 functional reqts: 4 for NaaS application, 5 for NaaS platform, and 17 for NaaS connectivity Editors Ying Cheng (China Unicom) and Emil Kowalczyk (Orange Polska SA)

5. Geneva, Switzerland, 14 November 2014 5 NaaS concept Network as a Service (NaaS) [Y.3500]: cloud service category in which the capability provided to the cloud service customer is transport connectivity and related network capabilities NaaS services are divided into network application service, network platform service, and network connectivity service. In particular, NaaS connectivity service is an “infrastructure capabilities type” service (limited to networking resources). NOTE – NaaS can provide any of the three cloud capabilities types.

6. Geneva, Switzerland, 14 November 2014 6 High level concept of NaaS using the layering framework defined in [ITU-T Y.3502] NaaS concept (2) NaaS Application: application capabilities type of service where NaaS CSC can use network applications provided by CSP. Examples of NaaS applications include virtual router, virtual content delivery network (vCDN), virtualised evolved packet core (vEPC) and virtual firewall (vFW). NaaS Platform: platform capabilities type of service where NaaS CSC can use the network platform provided by NaaS CSP. The NaaS platform offers one or more software execution environments and one or more programming languages to deploy, manage and run customer-created or customer-acquired network applications. NaaS Connectivity: infrastructure capabilities type of service where NaaS CSC can provision and use networking connectivity resources provided by NaaS CSP. This includes for example flexible and extended virtual private network (VPN), bandwidth on demand (BoD), etc. In this category, CSP offers network connections between two or more endpoints, which may include additional network functionalities.

7. Development methodology of NaaS related WIs Considering the standardization methodology and conventional study sequence, the abstractions of functional entities and their mutual interactions are based on the functional requirements and the corresponding use cases analysis, which form a standardization body together. Therefore, it is required to progress NaaS functional requirements and architecture according to the following steps and priorities. Additionally, it is needed to align with the high level requirements of NaaS described in the latest edition of Y.3501 (Cloud computing framework and high-level requirements), whose most recent edition is ITU-T Y.3501 (2013). Source: Appendix I of Y.3512 Use CasesFunctional Requirements Functional Architecture Y.3512 Y.CCNaaS-arch Geneva, Switzerland, 14 November 2014 7

8. Milestones of NaaS related WIs TimelinesMilestones 2012.4First proposal from China Unicom on NaaS related WI – agreed to be kept in living list of Q27/13 2012.6Agreed to launch Y.CCNaaS in study period 2013-2016 2013.2Initial draft Rec of Y.CCNaaS; Use cases and derived reqts on dynamic transport network and flexible and extended VPN; Ying Cheng (China Unicom) and Emil Kowalczyk (Telekomunikacja Polska S.A) are nominated as editors; 2013.6Re-organization of use cases and functional requirements into three types; Use cases and derived reqts on Cloud CDN, Application/platform capabilities types NaaS provision, BoD, Optimized traffic engineering, Performance on demand 2013.11Excluding architecture clause from the scope of Y.CCNaaS; New time plan for Y.CCNaaS consent on Q3 2014; New use cases and derived functional reqts on virtual router and service chain 2014.2Refinement on scope; Modifications on general description including introduction and high level concept of NaaS; 2014.5Addition and modification of detailed functional reqts in clauses 7-9; Editorial supplements and modifications for the whole document 2014.7Consent of Y.3512 (former Y.CCNaaS) ; Launch of NaaS series WI Y.CCNaaS-arch and Ying Cheng (China Unicom), Emil Kowalczyk (Orange Polska SA), and Qian Gu (China Telecom) are nominated as editors 2014.8Publishing of Y.3512 after AAP Geneva, Switzerland, 14 November 2014 8

9. Detailed use caseDerived functional reqts Cloud CDN Monitoring utilization and delivery performance Providing efficient management solution Providing mechanisms allowing for the chaining of NaaS applications Detailed use cases and functional reqts of NaaS application Geneva, Switzerland, 14 November 2014 9

10. Detailed use caseDerived functional reqts Service chain Programmable NaaS platform; Dynamic and flexible network service composition and steering; Isolation of service chains for tenants Platform provision Flexible scaling of NaaS platform Integration of software applications Detailed use cases and functional reqts of NaaS platform Geneva, Switzerland, 14 November 2014 10

11. Detailed use caseDerived functional reqts Dynamic transport network Unified SLA for multiple optimized networks Leveraging transport networks dynamically Unified network control mechanism Flexible and extended VPN Elastic network reconfiguration Bandwidth on demand service Seamless and end-to-end solution of bandwidth allocation Symmetric or asymmetric capacity Optimized traffic engineering Optimized and fine-grained traffic engineering Coexistence with legacy network services and functions Detailed use cases and functional reqts of NaaS connectivity (1) Geneva, Switzerland, 14 November 2014 11

12. Detailed use caseDerived functional reqts Performance on demand CSC limited control to services Centralized control view and abstraction view of resources Virtual Router Logically isolated network partition Overlay network mechanism Private IP addresses and VPNs Overlapped private IP addresses Interworking among different VPN solutions VPN connection in mobile environment Connection to NaaS CSP’s network through public Internet Geneva, Switzerland, 14 November 2014 12 Detailed use cases and functional reqts of NaaS connectivity (2)

13. Geneva, Switzerland, 14 November 2014 13 Contents Part II: Functional Requirements of Infrastructure as a Service Based on Recommendation ITU-T Y.3513 (Cloud computing - Functional requirements of Infrastructure as a Service)

14. Scope of Y.CCIaaS General description of IaaS Functional requirements of IaaS Typical IaaS use cases 41 related contributions from 7 sector members in 9 meetings Editors CHEN Nan (China Telecom) Peter Tomsu (Cisco) Y.CCIaaS in Summary Geneva, Switzerland, 14 November 2014 14

15. Milestones of Y.3513 TimelinesMilestones 2012.4First proposal from China Telecom on IaaS related WI – agreed to be kept in living list of Q27/13 2012.6Agreed to launch Y.CCIaaS in study period 2013-2016 2013.2Initial draft Rec of Y.CCIaaS CHEN Nan (China Telecom) and Orit Levin (Microsoft) are nominated as the editors 2013.6Mr. Peter Tomsu from Cisco is nominated as the co-editor 2014.2Excluding architecture clause from the scope of Y.CCIaaS New time plan for Y.CCIaaS consent on Q3 2014 2014.7Consented Geneva, Switzerland, 14 November 2014 15

16. 16 The definition of IaaS Infrastructure as a Service [ITU-T Y.3500] cloud service category in which the cloud capabilities type provided to the cloud service customer is an infrastructure capabilities type NOTE – The cloud service customer does not manage or control the underlying physical and virtual resources, but does have control over operating systems, storage, and deployed applications that use the physical and virtual resources. The cloud service customer may also have limited ability to control certain networking components (e.g. host firewalls). Geneva, Switzerland, 14 November 2014

17. 17 High level concept of IaaS

18. Geneva, Switzerland, 14 November 2014 18 IaaS service functions computing service functions allow CSC to provision and use processing resources. CSC can perform operations relevant to processing resources including machine (physical or virtual machine) lifecycle operations and functions such as VM migration, backup, snapshot, clone and reservation. storage service functions allow CSC to use storage resources. CSC can perform operations relevant to storage resources including lifecycle operations and functions such as snapshot, backup, I/O performance, load balance and reservation. network service functions allow CSC to use networking resources. CSC can integrate infrastructure resources using network relevant functions such as IP address, network isolation (e.g. VLAN), virtual networking (e.g. virtual switch), load balance and firewall.

19. Geneva, Switzerland, 14 November 2014 19 Computing service functions Computing Service Physical machine Virtual machine migration scaling snapshot clone backup time synchronization reservation image template

20. Geneva, Switzerland, 14 November 2014 20 Storage service functions Storage snapshot Storage backup I/O performance Storage service Storage resource reservation Storage migration

21. Geneva, Switzerland, 14 November 2014 21 Network service functions Network Service Load balance Firewall Gateway Network policy migration Network QoS IP address Network Isolation Virtual networking Network configuration

22. Geneva, Switzerland, 14 November 2014 22 The relationship between IaaS and NaaS Regarding the network connectivity, one important difference between IaaS and NaaS is that IaaS is a cloud service category that is offered in only one flavour of cloud capability type, and that is infrastructure capabilities type [ITU-T Y.3500]. However, NaaS is a cloud service category that can be offered in all three cloud capabilities types.

23. Thanks for your attention ！ Geneva, Switzerland, 14 November 2014 23