Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

We produce a roadmap at the beginning of each release cycle, and then archive it here.

Table of Contents

CORD Platform

  • Micro-CORD – Support right-and-light footprint for CORD
    • Test robustness of remote management (no head nodes)
    • Enable OpenStack-free configuration (container-only)
    • Architect for flexible upstream connectivity (not just vRouter)
    • Streamline for single/partial-rack configuration
  • Reconcile/Extend Models – Unify and generalize core models based on experience
    • Generalize VTN to "splice" arbitrary network types (see Notes)
    • Make Network interconnectivity explicit in Service Graph (see previous)
    • Extend Network model to include Carrier Ethernet (related to E-CORD)
    • Extend synchronizer framework to support richer model dependencies (see Notes)
    • Explore how to leverage YANG in service assembly and composition (see Notes)


  • Trellis: Network Infrastructure
    • Move to OF-DPA 2.0 GA (actually 3.0 EA0) release on switches
    • Add dual homing support for servers, access devices and upstream routers
    • DPDK support with OvS and BESS
    • VXLAN VTEP support in Leaf switches
    • sFlow integration
    • ARP/DHCP delegation
    • More dynamic configuration (switches, links etc.)
    • ISSU
    • Troubleshooting tools
    • Add features (e.g., IPv6, Pseudowires, E-VPN, L3VPN) to vRouter and Fabric (related to E-CORD)
    • Exploratory: P4, Flat network (no overlay/underlay)

Residential CORD

  • Device Inventory – Demonstrate additional wireline devices running in CORD 
    • OLT – Celestica, Fujitsu, TiBiT
    • G.Fast
    • DOCSIS


  • Scale Performance – Optimize for the number of simultaneous residential subscribers

    • Benchmark performance of current configuration
    • Integrate DPDK and evaluate performance (related to Platform)
    • Integrate BESS and evaluate performance (related to Platform)

Enterprise CORD

  • Prepare First Release – Integrate E-CORD proof-of-concept into CORD reference implementation
    • Settle on a target POD Hardware and Service Graph
    • Implement missing service elements: Model, Admin GUI, REST API, TOSCA
    • Integrate into service on-boarding and build/test process
    • Design test plan and integrate into Jenkins


  • L3VPN Service – Provide private IP network across enterprise locations
    • Design end-to-end service graph to site-local service graph refinement process
    • Consider route distribution mechanism options
    • Integration with vRouter and VTN (see Platform)
  • SD-WAN Overlay – Provide cost-effective best-effort service combining broadband connections with LxVPN
    • Design light-weight VNF provisioning on CPE
    • Design gateway feature to manage CPE in a location, where operator does not have point-of-presence
  • Multi-CORD Site Coordination – Provide mechanism for inter-site coordination
    • Global A-CORD view at the orchestration layer (e.g., Aggregated site metrics to the orchestrator, bulk transfer, ...) 
    • Coordinated service instantiation across multiple sites (e.g., WAN Accelerator, encryption)
    • Evaluate nested/layered XOS for multi-site orchestration

CORD Summit 2016 slide

Mobile CORD

A more detailed outline of the M-CORD Roadmap is available here (7.4MB powerpoint).


  • RAN Slicing – Policy-based resource isolation

    • vBBU assigns and manages radio resource blocks to different slices under the control of an ONOS slicing app
    • Slicing app talks to RAN agent (vBBU) through proposed OF-extensions
    • Slicing app acts on UE-based, time-based, location-based, and services-based policies
    • Service classification is implemented by UE and/or BBU using tagging (e.g., network cookies)
    • Build closed control loop to analyze power and channel quality (related to A-CORD)
      • Adjust power
      • Spin up new BBUs
  • Core Slicing – Flexible allocation of resources to EPC components
    • Dynamic assignment of EPC resources (e.g. MME, SGW-C, PGW-C, SGW-D, PGW-D…) to slices
    • Resources can be dedicated or shared between slices
    • Coordinate core with RAN and Fabric slicing (e.g., vBBU gets slice information from slicing app to select appropriate core slice for incoming packets)
    • Build closed control loop to analyze singalling workload (related to A-CORD)
  • Connectionless RAN – Non-GTP based data forwarding model

    • Disaggregate eNB/SGW/PGW components to enable a centralized entity to manage new (non-GTP) data plane

    • vBBU data plane and service gateway data plane are controlled by ONOS apps

    • Get rid of GTP tunnels; replace with proactive OF rules in data path element

  • Edge Services – Demonstrate edge services taking advantage of capabilities

    • CDN – Utilize slicing to provide policy-based quality-of-experience

    • Public Safety – Utilize slicing to steer emergency traffic (e.g., police, fire)

    • AR/VR – Utilize slicing to meet high throughput needs of AR/VR

    • m-Health – Utilize slicing by dedicating resources to critical m-Health applications

Analytics for CORD

A more detailed outline of the A-CORD is available at here (powerpoint)


  • Demonstrate E2E Use Cases – Build Proof-of-Concept Analytics Use cases
    • eSON for Mobile CORD (related to M-CORD)
    • Auto-scaling for disaggregated EPC (related to M-CORD)