NFV Forum Progression to Launch

Transcription

1 NFV Forum Progression to Launch Laurent Laporte Technology Development Strategist Sprint September 25, 2014

2 Progression to NFV Forum Launch TOPS Council SDN/NFV Focus Group: NFV Landscape Assessment completed, identifying North American priorities SDN/NFV objectives focused on: Two initial use cases on virtual network operator and service roaming Inter-provider aspects of service chaining ATIS Board analysis resulted in the NFV Forum launch on September 25,

3 NFV Landscape Assessment Matrix Category Management / Orchestration Inter-Operator/Domain Intra-Operator/Domain Use Cases & PoCs NFV Infrastructure / Cloud Network Applications (EPC, virtual CPE,...) Interoperability Inter-provider (inter-domain) SDN (in NFV) Service Chaining/ Forwarding Graphs Combined virtual & physical Industry Activity NFV ISG, TMF NFV ISG NFV ISG, 3GPP, BBF NFV ISG ATIS NFV ISG, IETF, BBF NFV ISG, IETF, BBF NFV ISG 3

4 NFV Landscape Assessment Matrix Category Architecture VNFM <-> NFVO VIM / NFVI Telco Grade Performance/Capacity Reliability/Availability Security Industry Activity NFV ISG NFV ISG, OP-NFV, OpenStack NFV ISG NFV ISG NFV ISG 4

5 NFV Landscape ATIS OpenDaylight Open NFV OpenStack TMForum The ETSI NFV ISG has defined the reference architecture and many organizations are contributing. 5

6 NFV Landscape Summary Many SDOs have ongoing efforts to evaluate the impact of NFV on their respective subject matter areas. The landscape team identified that very little ongoing work is addressing the inter-provider NFV use case(s). The ATIS Board noted this opportunity and has chartered a new NFV Forum to address this topic and other applicable work areas. 6

7 NFV Landscape Recommendations Related work will be required in the ATIS Ordering and Billing Forum (OBF) associated with the inter-provider use case(s); OBF engagement on this topic is recommended. Given the broad industry involvement with NFV topics, it is recommended that some mechanism be put in place to provide overall industry coordination. This could be an added role for the ETSI ISG in phase 2. 7

8 NFV Use Cases Use cases were selected for their business relevance in providing requirements for inter-provider NFV. Virtual Network Operator Service Roaming In addition, the cross administrative domain service chaining use case was analyzed because of its connection with the technical problem being addressed. 8

9 Virtualized Network Operator Use Case Virtual network operations provides a lower barrier to market entry for entities that do not have sufficient capital and/or interest available with which to build and operate a network. Businesses wishing to offer network services may instantiate service by virtualizing some or all of the necessary network functions in a tenant domain with the balance being provided by a physical network operator. Overall capex and opex may be substantially lowered by the use of COTS h/w and DevOps tool sets A resultant greater flexibility in service creation and reduction in lifecycle thus promotes ecosystem expansion 9

10 Virtualized Network Operator Use Case A 1 2 OSS OSS 2 1 Orch. Virtualized Network Operator VNF_C VNF_A VNF_D 2 1 VNF Mgr Physical Network Operator VNF_B 2 1 VI. Mgr 10

11 Service Roaming Use Case Virtualization affords the possibility for service providers to offer continuity of value-added data services (e.g., parental controls) when subscribers roam to other networks. Continuity of value-added data services while roaming is currently non-existent and a source of customer dissatisfaction With the advent of virtualization, the home service provider instantiates virtualized network functions in the visited service provider s tenant domain When roaming to the visited service provider s network, the subscriber now experiences service continuity while outside the home network 11

12 Service Roaming Use Case 12

13 Cross-administrative Domains Use Case The IETF Service Function Chaining (sfc) Working Group has a goal of improving the process for inserting functions such as firewalls, load balancers, and proxies into the data-forwarding path. The SDN/NFV-FG progressed the following activities related to service function chaining: Analyze cross-administrative domain service chain use cases, requirements, and existing mechanisms Progress working text to outline recommended approach including best practices for inter-provider interoperability Collaborate with IETF Service Function Chaining (sfc) WG on solution design 13

14 Cross-administrative Domains Use Case Single Domain Service Chaining Enterprise A Site 1 Enterprise A Service Function 1 Enterprise A Service Function 2 Network SP 1 Enterprise domain tunneled (invisible) to Network SP 1 domain SP1 Service Function 1 SP1 Service Function 2 Enterprise A Site 2 Enterprise A Service Function 3 Single Domain Cross Domain Service Chaining Network SP 1 Network SP 2 Network SP 3 SP1 Service Function 1 SP1 Service Function 2 Network SP1 domain tunneled (invisible) to Network SP 2 domain SP1 Service Function 3 SP3 Service Function 4 14

15 Supporting Material

16 ETSI NFV ISG Activities INF WG (Infrastructure) Reference architecture for the NFV infrastructure. SWA WG (Software Architecture) Reference software architecture. REL WG (Reliability and Availability) Framework for resilience of VNFs. PER EG (Performance and Portability Expert Group) Performance limitations of key network functions running in a software-based fashion. MANO (NFV Management and Orchestration) Deployment, instantiation, configuration, and management of network services based on NFV infrastructure. 16

17 ETSI NFV ISG Activities (2) POC - to coordinate and promote public demonstrations of Proofs of Concept (PoC) illustrating key aspects of NFV. Next Steps: The ISG has been re-chartered for 2 more years. New work items proposed, but not yet approved. Proposed NFVI use case work item attracting significant interest from ETSI ISG members. Public NFV ISG drafts/documents are available at 17

18 IETF NFV Related Activities NVO3 - Network Virtualization Overlays Separation of traffic for multi-tenant data centers with Data Center Virtual Private Networks (DCVPN). Chartered for problem statement, requirements, and gap analysis. SFC - Service Function Chaining Chartered for problem statement, architecture, and data plane encapsulation. VNFPool (BoF) redundancy and reliability across pools of VNFs Working towards charter. NFVRG Non working-group mail list. Proposed IRTF research group. 18

19 Broadband Forum NFV Work Status SDN Business Requirements and Framework Long-term evolution. Incremental introduction of SDN. Flexible Service Chaining Guidance on work needed to define service chaining concepts. NFV in Multi-Service Broadband Network Stage 1. Study possible NFV applications in a broadband plus cloud environment. 19

20 Broadband Forum NFV Work Status Migrating to NFV in context of Multi Service Broadband Network Architecture and Nodal Requirements. Address architectural and operational issues of deploying WT- 178 architectures with both VNFs and Physical Network Functions (PNF). Expectation that initial deployments of NFV will be primarily at the service edge. 20

21 Broadband Forum NFV Work Status (2) Network Enhanced Residential Gateway (Virtual CPE) Architecture to move networking and service functions to the provider network. Virtual Business Gateway (Virtual CPE) Migration of Business Gateway functions to provider infrastructure. Architecture and deployment scenarios. 21

22 TM Forum NFV Activities ZOOM Project Define business operations support architecture. Manage physical and virtual resources. Provide flexibility and agility. End-to-end management and rich analytics. Significant cost reduction. 22

23 TM Forum NFV Activities ETSI MANO Contributions Interface mapping and gap analyses. Relations between NFV management and orchestration with. existing OSS/BSS. Information Model (SID). Integration Framework (TIP). Business Process Framework (etom). 23

24 3GPP Impacts NFV impacts on OAM are expected and so a new Study Item in SA5 has been agreed and work will commence in the Fall of NFV impacts on the Core Network (e.g., EPC) are unclear. The 3GPP architecture is logical, and in general independent of deployment technology. New NFV enabled attributes tend to be independent of changes to 3GPP interfaces and entities. Debate in the June 2014 SA Plenary seemed to show a majority favouring minimal work in the Release 13 timeframe, with others preferring more extensive re-architecture work. 24

25 OASIS Contributed the OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC, ( TOSCA works to enhance the portability of applications and services. Enables the interoperable description of applications and services, relationships between parts of the service, and the operational behavior of these services: e.g., to deploy, patch, or shutdown, all in a manner that is independent of the supplier creating the service or any particular hosting technology. Direct link: 25

26 Open Platform for NFV A new organization has been formed called Open Network Function Virtualization (OP-NFV) under the Linux Foundation. This new organization seeks to create integration projects that combine upstream code from projects such as OpenStack, OpenDaylight, and the Linux Kernel and combine them with extensive testing, custom configuration and possibly upstream code patches. These things are based on the ETSI framework and requirements. Open NFV is currently (8/2014) in the formative stages. Source: 26

27 ITU-T Study Group 13 (Future Networks and Cloud) developing requirements for network virtualization and a framework for telecom SDN along with requirements and formal specifications and verification methods for SDN. Cloud computing is an important part of SG13 work and the group develops standards that detail requirements and functional architectures of the cloud computing ecosystem, covering interand intra-cloud computing and technologies supporting XaaS (X as a Service). This work includes infrastructure and networking aspects of cloud computing models, as well as deployment considerations and requirements for interoperability and data portability. 27

28 ITU-T (2) Study Group 11 continues to advance its work on a signaling framework for SDN, the subject of a new Supplement to the Q- series Recommendations based on Recommendation ITU-T Y.3300 Framework of software-defined networking. ITU-T has also established a Joint Coordination Activity on Software-Defined Networking (JCA-SDN) approved in June The role of JCA-SDN is the coordination of the standardization work on SDN and related technical topics within ITU-T, taking into consideration work of relevant other standards development organizations (SDOs), forums and consortia. Scope and Terms of Reference provided here: 28

29 Non-SDO Activities OpenStack NFV Sub-team Use cases and requirements needed for NFV workloads on top of OpenStack. Identify functional gaps, create blueprints, and coordinate patches to relevant OpenStack projects. 29