[Aeon] FW: New Version Notification for draft-conet-aeon-problem-statement-00.txt

["Charles Eckel (eckelcu)" <[e-mail]>]

The following draft is the result of merging the CoNET and AEON problem
statement drafts discussed previously on this list. It is intended as a
replacement for both of them, combining important aspects of both and
addressing review comments received to date. Please review and share your
comments.

Cheers,
Charles

On 5/23/14, 4:05 PM, "[e-mail]" <[e-mail]>
wrote:

>
>A new version of I-D, draft-conet-aeon-problem-statement-00.txt
>has been successfully submitted by Charles Eckel and posted to the
>IETF repository.
>
>Name:		draft-conet-aeon-problem-statement
>Revision:	00
>Title:		Application Enabled Collaborative Networking: Problem Statement
>and Requirements
>Document date:	2014-05-21
>Group:		Individual Submission
>Pages:		11
>URL:            
>http://www.ietf.org/internet-drafts/draft-conet-aeon-problem-statement-00.
>txt
>Status:         
>https://datatracker.ietf.org/doc/draft-conet-aeon-problem-statement/
>Htmlized:       
>http://tools.ietf.org/html/draft-conet-aeon-problem-statement-00
>
>
>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, and the packet flows they generate
>   and consume, 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.
>
>                  
>        
>
>
>Please note that it may take a couple of minutes from the time of
>submission
>until the htmlized version and diff are available at tools.ietf.org.
>
>The IETF Secretariat
>