Software Defined Networks Use Case for Virtual Connection and Network on Demand

Document Type Expired Internet-Draft (individual)
Last updated 2013-07-29 (latest revision 2013-01-15)
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


Software Defined Networks (SDN) provide a way to virtualize and abstract the network and presents the virtual/abstract resources to the third-party applications/software. The applications/software can, by the programmable interface or Northbound API, request, manipulate and monitor the services that the network provided. With this SDN capability, more innovative services can be introduced and rapidly deployed. Additionally, existing services can be deployed and managed in a much more simple way. This document outlines two use cases that leverage the SDN architecture/model to implement a kind of "self-help" and automated set of network services: Virtual Connection on Demand (VCoD) and Virtual Network on Demand (VNoD).


Mach Chen (
Mike McBride (
Liang Ou (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)