Application Enabled SDN (A-SDN)
draft-penno-pcp-asdn-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2014-04-02 (latest revision 2013-09-29) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
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) | ||
https://www.ietf.org/archive/id/draft-penno-pcp-asdn-00.txt
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
(repenno@cisco.com)
Reddy K
(tireddy@cisco.com)
Mohamed Boucadair
(mohamed.boucadair@orange.com)
Dan Wing
(dwing@cisco.com)
Suresh Vinapamula
(sureshk@juniper.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)