1. ONOS Drake Release
September 2015

2. Themes Open source project integration and distributions Security
Device configuration
Infrastructure support

3. Open Source Distributions
Upstream inclusion
ONF Atrium
OPNFV November release
Cloudrouter
Integration
OpenStack - Neutron layer 2

4. Security Constrain app to part of the network GUI login
CLI (public/private keys)
REST interfaces
TLS support for internode communication (east-west)
Security mode ONOS (SRI, KAIST collaboration)
Constrain app to part of the network
Constrain app to header space
Applications permissions in a “manifest” (similar to cellular)
OSGi / Java 2 Security - allows code to be authenticated (apps, bundles)
KAIST Korea Advanced Institute of Science and Technology

5. Device Configuration
New configuration subsystem - all ONOS apps can get their config from a central repository (used to be separate files)
Apps ported to use it (like SDN-IP)
Netconf/Yang model for ACLs at southbound
OVSDB plug-in

6. Other infrastructure Adaptive flow statistics subsystem
PCEP southbound plug-in
VXLAN tunnel setup
DHCP server app
Metrics collection subsystem
OpenFlow meter support
Multicast improvements to IGMP snooping, PIM-SSM
GUI topology overlays and better link highlighting
AFS - It enables analyzing and monitoring various types of traffic associated with ONOS. It includes but not limited to the control and management traffic as well as user data traffic between hosts in ONOS networks. Our proposed OPEN-TAM functionality will eventually provide deep operational visibility of ONOS-based networks in real-time.
PCEP - path computation element protocol
The Path Computation Element Communication Protocol (PCEP) is a special set of rules that allows a Path Computation Client (PCC) to request path computations from Path Computation Elements (PCEs). The protocol also lets the PCEs return responses.
Path Computation Element (PCE) is a network component, application or node that can compute sophisticated paths through a network by applying computational constraints in real time. Traditionally, network routes are are calculated and managed off-line as part of a network's traffic engineering. In such a scenario, when a new customer comes online, the customer's traffic requirements are evaluated and superimposed on the current network's topology. Defined by IETF RFC 4655, the Path Computation Element (PCE) has a complete picture of flows and paths in the network at the precise moment derived from other Operational Support Software (OSS) programs so it can calculate in real time the optimal path through the network. This path is then used to automatically update router configurations and the traffic engineering database.
Openflow meter support - a switch element that can measure and control the rate of packets. The meter triggers a meter band if the packet rate or byte rate passing through the meter exceeds a predefined threshold. If the meter band drops the packet, it is called a Rate Limiter. Per-flow meters enable OpenFlow to implement various simple QoS operations, such as rate-limiting, and can be combined with per- port queues (see 5.12) to implement complex QoS frameworks, such as DiffServ.
PIM source specific multicast - Source-Specific Multicast (SSM), defined in RFC 4607, extends this concept to identify a set of multicast hosts not only by group address but also by source.