Name of Use Case: 

SD-WAN (Software Defined Wide Area Network)

Use Case Authors:

Netcracker

Presentation Materials:

ONAP SD-WAN Proposal Use Case v0.5.pptx

Description:

• SD-WAN is an emerging VPN technology for Large Enterprises with highly distributed locations, where each location can have one or several connections to internet from different Network Infrastructure Providers with Best Effort quality, rather then expensive MPLS, Dedicated Optical lines or Satellite services.
• SD-WAN currently under standardization in different SDOs, like MEF, ONF, BBF, but several vendors already exist on the market, offering proprietary SD-WAN solutions.
• To be Open, ONAP SD-WAN Use Case will refer to following standards:
  1. MEF LSO API, SD-WAN Use Cases
  2. BBF: WT-328
  3. IETF: draft-ietf-netconf-zerotouch
• ONAP SD-WAN Use Case will be divided on series of Sud-Use Cases ranged by complexity, providing more and more capabilities and features for every next Sud-Use Case, based on top the previous:

...

ZTP - Zero Touch Provisioning

ISP -  Internet Service Provider

vBG - virtual Businness Gateway, BBF WT-328

pBG - phisycal Businness Gateway, BBF WT-328

SFC - Service Function Chaining

Users and Benefit:

• From the User perspective, SD-WAN solution is an overlay technology, which allow refuse expensive dedicated MPLS lines from Network Providers.
• From the Network Providers perspective, SD-WAN is a solution to be not just a “pipe” for OTT providers, but also take role of “Network Service Provider” and chance to earn money on additional services for the Customers.
• From the ONAP perspective, SD-WAN Use Case is demonstrate Orchestration capabilities for Distributed VNFs, Configuration Management for VNF and PNF, Policy Enforcement for Overlay Traffic, Standard ZTP and APIs.

Sub-Use Case #1.

Acthitecture:

1. Before initial VPN service will be provided, ONAP will demonstrate initial device configuration (ZTP, Zero Touch Provisioning), based on a IETF I-D: https://datatracker.ietf.org/doc/html/draft-ietf-netconf-zerotouch.
2. Configuration Management on the Edges as a simplest scenario for VPN Service creation.

ZTP Flow Diagram:

• Preconditions steps described in draft-ietf-netconf-zerotouch, Chapter 6.1 and 6.2
• “Power” button is on. See draft-ietf-netconf-zerotouch, Chapter 6.3:

1. 1. 1. 1. Upon power being applied, the device's bootstrapping logic first checks to see if it is running in its factory default state. If it is in a modified state, then the bootstrapping logic exits and none of the following interactions occur.
         2. For each source of bootstrapping data the device supports, preferably in order of closeness to the device (e.g., removable storage before Internet based servers), the device checks to see if there is any bootstrapping data for it there.
         3. If onboarding information is found, the device initializes itself accordingly (e.g., installing a boot-image and committing an initial configuration). If the source is a bootstrap server, and the bootstrap server can be trusted (i.e., TLS-level authentication), the device also sends progress notifications to the bootstrap server.
         4. Otherwise, if redirect information is found, the device iterates through the list of specified bootstrap servers, checking to see if there is any bootstrapping data for it on them. If the bootstrap server returns more redirect information, then the device processes it recursively. Otherwise, if the bootstrap server returns onboarding information, the device processes it following the description provided in (3) above.
         5. After having tried all supported sources of bootstrapping data, the device MAY retry again all the sources and/or provide manageability interfaces for manual configuration (e.g., CLI, HTTP, NETCONF, etc.). If manual configuration is allowed, and such configuration is provided, the device MUST immediately cease trying to obtain bootstrapping data, as it would then no longer be in running its factory default configuration.

Configuration Management Flow Diagram:

Virtual Network Function: [TDB]

ONAP Flows: [TDB]

Project Impact: [TDB]