1. +
Timon Sloane VP, Standards & Membership

2. Open Networking Foundation (ONF)
Vision
Strategy
Transform Operator Networks and Business Models with Open Source Solutions for building nimble competitive networks for service delivery
#1 - BUILD IT
Build a viable open source alternative to proprietary solutions for operator networks
Provide complete solutions that are easy to consume
#2 - PROVE IT
Operators put their weight behind it with both:
Up-Front Investment (vision, people, attention and money)
Deployment (& resulting spend), which transforms industry

3. Crossing the Open Tipping Point
This impending Multi-Billion Dollar spend is prompting Industry to develop new business models
Viable Open Source Alternative
Building Solutions Leveraging Disaggregation, White Box and Open Source
Operator PULL: Customize & Deploy
Operator PUSH: Vision & Funding
Inertia due to legacy ways of working

4. Vision: Tiered Cloud Users Commodity Clouds Telco & IX Cloud
Access Edge
For illustration purposes; sizing is done independent of general design.
10GPON also an option (as is Mobile-CORD and Enterprise-CORD).

5. Edge Processing is Vital
Vision: Tiered Cloud
Commodity Clouds
Users
Access Edge
Telco & IX Cloud
Human Reaction time: ms
Latency to Centralized Cloud: – 400ms
Emerging Applications Require Edge Processing
AR visual overlay updates
Autonomous Vehicle Coordination
IoT Battery Life (50-75% improvement)
Edge Processing is Vital
For illustration purposes; sizing is done independent of general design.
10GPON also an option (as is Mobile-CORD and Enterprise-CORD).

6. Centralized Datacenter
WAN
Routers
Switching
Fabric W E
Compute
Storage
For illustration purposes; sizing is done independent of general design.
10GPON also an option (as is Mobile-CORD and Enterprise-CORD).

7. CORD – Edge Optimized Datacenter
Open GPON
48-port, 1RU, I/O Blade
I/O
I/O
ROADM
(Core)
GPON, RAN
(Access)
For illustration purposes; sizing is done independent of general design.
10GPON also an option (as is Mobile-CORD and Enterprise-CORD).

8. Resulting Multi-Tiered Cloud
Commodity Clouds
Users
Access Edge
Azure
Amazon
CORD …
Content Distribution Hub
Internet Exchange
Telco Cloud
Telco & IX Cloud
For illustration purposes; sizing is done independent of general design.
10GPON also an option (as is Mobile-CORD and Enterprise-CORD).

9. Specialized Datacenters with Centralized Orchestration
CORD exposes a set of Composite-VNFs to ONAP
Users
Users
CORD Central Office
Users
CORD Central Office
CORD Edge Datacenter
Telco Cloud (e.g. AT&T AIC)
Edge Service
Composite-VNFs
CORD = Edge Optimized Cloud
– “Peer” of AIC, Amazon, Azure
– Unique Capabilities for the Edge
Subscriber Access
Combination of Micro-Services and Fabric-Services
For illustration purposes; sizing is done independent of general design.
10GPON also an option (as is Mobile-CORD and Enterprise-CORD).

10. Not All Services Should be Run on a Server
CORD Service Building Blocks
Micro-Services - Images that run in containers on servers
Fabric-Services - Flow rules that run in switches
CORD Services are composites of micro-services and fabric-services
Elements run on servers (x86 or ARM)
Elements run in the OpenFlow & P4 enabled dataplane
Different price/performance ratio
CORD Services exposed to northbound controllers as “Composite-VNFs”
Think of CORD as a VNF construction toolkit
As the dataplane becomes more programmable (P4), even more functionality can be moved into networking hardware
Composite-VNF Exposed Northbound
CORD Service
Micro-Service
Fabric-Service
XOS Service Graph

11. CORD Service Architecture
CORD XOS Controller
vOLT
Controller
vSG
vRouter
Residential
Subscribers
vCDN
Controller
OpenStack
Controller
ONOS
Controller
Monitoring
Key
red
= micro-service (runs on a server)
blue
= fabric-service (runs as flow rules on switches)

12. CORD Field Trial Example
Customer Care
Portal
Operator
Portal
CORD Controller
Residential
Subscribers
Controller
Controller
Controller
vRouter
vOLT
vSG
Access the Internet
Stream (Cached) Video
Watch TV
Controller
OpenStack
Controller
Controller
Monitoring
Controller
vCDN
ONOS
Spine-2
Spine-1
Leaf-3
Leaf-1
Compute-1
Compute-3
OLT-1
Leaf-4
Leaf-2
Compute-2
OLT-2
Compute-4
AT&T U-verse
GPON ONT
Laptop
NetGear

13. Residential vOLT, vSG, vRouter, vCDN
Domains of Use
Residential vOLT, vSG, vRouter, vCDN
Mobile vBBU. vMME,
vSGW, vPGW, vCDN
Enterprise
vCarrierEthernet,
vOAM, vWanEx,
vIDS
CORD Controller
ROADM
(Core)
Metro Ethernet
BBUs
PON
OLTs

14. OPNFV CORD Complete Deployable Solution(s)
Compare and Contrast with
Complete Deployable Solution(s)
Testing Framework Upon Which VNFs and Solutions can be Developed
Includes Ready-to-Deploy Services & 3rd Party VNFs & Services Supported
VNFs Out-of-Scope
Differences
Curated Selection of Tightly Integrated Projects
Open Tent Policy All Projects Welcome
Both Leverage Many Common Upstream Open Source Projects
Similarities
Addressing needs of the NFV Space

15. CORD Running on OPNFV Framework
CORD and OPNFV: overlapping use of may upstream projects
OpenStack, ONOS, OVS, DPDK, etc.
CORD Unique Hardware Requirements
OpenFlow (or P4) fabric (fabric-services require nimble switching layer)
Access Hardware (PON, 5G, MetroEther)
What’s Required –
Adding (or simulating) CORD-Required Hardware in OPNFV Labs
Would allow CORD to run on the OPNFV framework

16. CORD and OPNFV – Path Forward
OPNFV to bring CORD into its integration and testing lab as a candidate reference platform
Fosters CORD compatibility with a broader range of projects
E.g., with various OpenStack distributions
Gives OPNFV an opportunity to incorporate:
Different market use cases
Access technologies for the network edge
Blended CORD + ONAP solutions
CORD exposing “Composite-VNFs” to ONAP
ONAP doing end-to-end orchestration
CORD Edge Datacenter
Telco Cloud
OPNFV Framework

17. 70% of Operators Plan to Deploy Cord*
Learn More Join the Ecosystem Get Involved !
Timon Sloane
*IHS Markit Survey, 2017