Skip to main content

Application Enabled Collaborative Networking: Problem Statement
draft-conet-aeon-problem-statement-01

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Peng Fan , DENG Hui , Mohamed Boucadair , Tirumaleswar Reddy.K , Charles Eckel , Brandon Williams
Last updated 2015-01-04 (Latest revision 2014-07-03)
Replaces draft-fan-intarea-conet-ps-uc, draft-eckel-aeon-problem-statement
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

Identification and treatment of application flows are important to many application providers and network operators. They often rely on these capabilities to deploy and/or support a wide range of applications. These applications generate flows that may have specific connectivity requirements that can be met if made known to the network. Historically, this functionality has been implemented to the extent possible using heuristics, which inspect and infer flow characteristics. Heuristics may be based on port ranges, network separation (e.g. subnets or VLANs, Deep Flow Inspection (DFI), or Deep Packet Inspection (DPI). 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.

Authors

Peng Fan
DENG Hui
Mohamed Boucadair
Tirumaleswar Reddy.K
Charles Eckel
Brandon Williams

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