Application Enabled SDN (A-SDN)
draft-penno-pcp-asdn-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Reinaldo Penno , Tirumaleswar Reddy.K , Mohamed Boucadair , Dan Wing , Suresh Vinapamula | ||
| Last updated | 2014-04-02 (Latest revision 2013-09-29) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
To allow traversal of firewalls or provide additional network services such as QoS or supplemental bandwidth, it is necessary to deploy application-aware network elements. Such network elements are costly to create, deploy, and are unable to adequately cope with changes to the application itself, stifling innovation. This document describes a different approach, where the application explicitly signals its needs to the network.
Authors
Reinaldo Penno
Tirumaleswar Reddy.K
Mohamed Boucadair
Dan Wing
Suresh Vinapamula
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)