Application Enabled Collaborative Networking Requirements
draft-conet-aeon-requirements-00

Document Type Expired Internet-Draft (individual)
Last updated 2015-01-04 (latest revision 2014-07-03)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf 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
https://www.ietf.org/archive/id/draft-conet-aeon-requirements-00.txt

Abstract

Identification and treatment of application flows are important to many application providers and network operators. Historically, this functionality has been implemented to the extent possible using heuristics, which inspect and infer flow characteristics. But many application flows in current usages are dynamic, adaptive, time- bound, encrypted, peer-to-peer, asymmetric, used on multipurpose devices, and have different priorities depending on direction of flow, user preferences, and other factors. Any combination of these properties renders heuristic based techniques less effective and may result in compromises to application security or user privacy. The document states requirements for a solution that enables identification and treatment of application flows without suffering the limitations that plague existing solutions.

Authors

Peng Fan (fanpeng@chinamobile.com)
Mohamed Boucadair (mohamed.boucadair@orange.com)
Brandon Williams (brandon.williams@akamai.com)
Tirumaleswar Reddy.K (tireddy@cisco.com)
Charles Eckel (eckelcu@cisco.com)

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