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

From: "Tirumaleswar Reddy (tireddy)" <[email-masked]>
Date: Fri, 4 Jul 2014 03:41:38 +0000

Revised http://tools.ietf.org/html/draft-conet-aeon-problem-statement-01 has been published. Further comments and suggestions are welcome.

Thanks and Regards,
-Authors

-----Original Message-----
From: [email-masked] [mailto:[email-masked]] 
Sent: Friday, July 04, 2014 8:52 AM
To: Peng Fan; Charles Eckel (eckelcu); Tirumaleswar Reddy (tireddy); Hui Deng; Charles Eckel (eckelcu); Peng Fan; Mohamed Boucadair; Brandon Williams; Hui Deng; Mohamed Boucadair; Tirumaleswar Reddy (tireddy); Brandon Williams
Subject: New Version Notification for draft-conet-aeon-problem-statement-01.txt

A new version of I-D, draft-conet-aeon-problem-statement-01.txt
has been successfully submitted by Tirumaleswar Reddy and posted to the
IETF repository.

Name:		draft-conet-aeon-problem-statement
Revision:	01
Title:		Application Enabled Collaborative Networking: Problem Statement
Document date:	2014-07-03
Group:		Individual Submission
Pages:		11
URL:            http://www.ietf.org/internet-drafts/draft-conet-aeon-problem-statement-01.txt
Status:         https://datatracker.ietf.org/doc/draft-conet-aeon-problem-statement/
Htmlized:       http://tools.ietf.org/html/draft-conet-aeon-problem-statement-01
Diff:           http://www.ietf.org/rfcdiff?url2=draft-conet-aeon-problem-statement-01

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.

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