ONUG Open SDWAN Exchange OSE API Interworking progress

ONUG Open SDWAN Exchange OSE API Interworking progress

ONUG Is the largest user community of the Global 2000 that speaks with one voice Building Practical Hybrid-Multi Cloud Infrastructure is ONUG’s Focus ● ● ● Open SD-WAN Exchange Software-Defined Security Services Monitoring and Analytics

The Open SD-WAN Exchange (OSE) is an open framework to allow for one vendor SD-WAN solution to federate and communicate with other vendor SD-WAN solutions that utilize different Overlay, Control and Management plane protocols. The “Open SD-WAN Exchange” use cases address marketplace M&A, business partner connectivity, Cloud/Service Provider network connectivity, technology transition and vendor interworking.

OSE Interworking Architecture Framework Other Manager Cy Infrastructure Go Gm Gx SD-WAN Manager SDW-NNI EX-NNI Other Network Domain Nn Cx CTL-IF SD-WAN Transport Network Other Controller Serving SDWAN Manager Cn M-IF Nsw Client Orchestration Layer Gy SD-WAN Controller Cmg Other SD-WAN Domain Policy Nx EX-NNI Gc Orchestrator CL-NNI Visibility Extranet Iaa. S Nc Public Cloud Saa. S UNI Uu SD-WAN Client 4

Open SDWAN Interworking Model Client Orchestration Layer G G Service Context Exch. Vendor 1 SD WAN Manager SD-WAN Controller Authentication Exch. C C SD-WAN Manager SD-WAN Controller Intradomain Orchestration Site B External Networks Interdomain Orchestration Vendor 1 Traffic/Segment Mapping Authenticated Control Plane Traffic/Segment Mapping Vendor 2 Site A SD-WAN N Vendor 2 pp Data Plane Nsw OSE Gateway Elements N External Networks 5

OSE Multiple Area Reference Network Client Orchestration Layer Co-NI NNI … SW-NNI SD-WAN Transport Network SD-WAN Controller M-NI EX-NNI SW-NNI EX-NNI Vendor 2 NNI SD-WAN Manager SD-WAN Controller M-NI Cl-NNI SW-NNI EX-NNI SD-WAN Transport Network Serving SDWAN Manager n Vendor n Co-NI M-NI Vendor 1 SD-WAN Manager SD-WAN Controller NNI SD-WAN Manager Serving SDWAN Manager 2 Cl-NNI Serving SDWAN Manager 1 Visibility/Analytics Policy SD-WAN Transport Network UNI UNI SD-WAN Client Transport Area 1 Transport Area 2 Transport Area n Cl-NNI Infrastructure Orchestration 6

OSE WORK ACTIVITY & TASK FORCES • Task Forces • Active Specification Work 1. Open Authentication Framework –Definition of Open Auth between controllers. 1. OSE Architecture Spec – Reference SDWAN Architecture and interface reference points 2. Service Chaining – propose requirements and objectives for Open SD-WAN 2. OSE Path Management – Access network selection service definition 3. Reachability Exchange via API –proposal for controller-tocontroller direct interface methods. 3. OSE External Gateway Spec – cross-domain reachability and segmentation exchange 4. OSE Hybrid Cloud API - Establish use cases and requirements. OSE requirements for common API services to leading cloud providers. 4. Open API Format – API format and service modelling specification

SD-WAN Work Areas • APIs for Service Management & Provisioning — Access Network (Path) Management Service Definition — SDWAN domain peering and interworking — OSE Gateway NNI • Authentication between domains • Security (Confidentiality/Crypto) • Segmentation — • Standard namespaces (eg. App. ID) Service connection / mapping at peering points — IPSec and Routing interworking specifications • Hybrid Cloud Services Access homologation (v. PC, Saa. S, Iaa. S) • Service Chaining across SDWANs Ensure that traffic is mapped between network segment with same policy intent Service Definitions — Consistent service behaviors across SD-WANs endto-end — Standard metadata exchange for traffic classifier and service policy 8

KEY PROGRESS & RESULTS • SD-WAN Reference Architecture - • First draft of architecture spec published for external review OSE Path Management Service API - First draft API released. Not yet for implementation. - External review and improvement - Yang Service models for: - Predefined and custom SLA definition - Flow classification - Preferred path selection

KEY PROGRESS & RESULTS • SD-WAN Reference Architecture - • First draft of architecture spec published for external review OSE Path Management Service API - First draft API released. Not yet for implementation. - External review and improvement • OSE Gateway Service API - Gateway Service creation, interface configuration - Segmentation instance creation, crossconnect - Yang-based service models • Where to find? - Github: swood 1465 - Repositories: ONUG-OSE, ONUG-OSEDocs

OPEN ITEMS • Service definitions: services available via the API • Close on outstanding Nsw reference point definitions — IPSec definition — API for VPN and control plane configuration across Nsw reference point • API Element/Type definitions and OSE namespace • API Authentication

OSE HYBRID CLOUD USE-CASES v. PC/Iaa. S – SD-WAN edge inside a v. PC 1. Establish an SD-WAN fabric edge in v. PC/Iaa. S facility. • Multiple vendor SD-WAN services can be hosted in a single v. PC. • Common service API definition would be beneficial • SD-WAN Integration to Carrier Neutral Facility (CNF) 2. Similar to use case #1 • Orchestration API definition, NBI interface to CNF services • Public Cloud / Saa. S – SD-WAN user access Saa. S providers (O 365, SFDC, . . ) 3. Access to Saa. S applications via Internet or private WAN (MPLS) providers • SD-WAN access to Saa. S is vendor specific and does not require interoperability • Common service definition and behavior required – path selection, security, app assurance, v. Qo. E •

OSE HYBRID CLOUD TASK FORCE • Step 1: Establish use cases and requirements: • Step 2: Areas of Work/API definition • Translation/Adaptation API to consume CSP VNF orchestration and lifecycle mgmt across multiple CSPs in a common way • Control plane services • Management/Orchestration services • Common set of services? Service homologation? • Building the Hybrid IT Datacenter • Direct Internet Access i. e. split tunnel (Saa. S) • Direct Cloud access i. e. SD-WAN Edge (Iaa. S, Paa. S, Colo) • Branch to hybrid DC connection use cases: Any-any SD WAN ; via Relay-site • Defines types of network services between DCs (SD-WAN or Direct connect/cloud express) Establish VPC connectivity to SDWAN -> configure SDWAN services from vendor controller • Define use cases for Colo - SD-WAN Edge connect to colocated services/Apps Establish connectivity to Cloud/Application Service and Customer DC App servers within CSP • Enumerate the DC-side connectivity options (CP/DP) for each CSP • Enumerate the VNF orchestration API capabilities and methods for each CSP • Trust establishment – User-to-App, Workload-to-Workload, Resources, etc • • • Resiliency requirements Create a proposal to define the details we need to work in the areas above Focus CSPs: AWS, Azure, Google, IBM, Oracle

Discussion