Subject: [tram] FW: New Version Notification for draft-eckel-aeon-problem-statement-00.txt

From: "Tirumaleswar Reddy (tireddy)" <[email-masked]>
Date: Mon, 17 Feb 2014 14:15:44 +0000

This draft may be of interest to the WG. It discusses the problems of application identification using heuristics like DPI.  

-Tiru

-----Original Message-----
From: Aeon [mailto:[email-masked]] On Behalf Of Charles Eckel (eckelcu)
Sent: Friday, February 14, 2014 11:59 PM
To: [email-masked]
Subject: [Aeon] FW: New Version Notification for draft-eckel-aeon-problem-statement-00.txt

This draft has been submitted in an attempt to focus on the problem statement without jumping to a specific solution. Instead, a section at the end captures some high level requirements of any such solution. Please have a look and share your comments.

Cheers,
Charles

On 2/14/14 10:18 AM, "[email-masked]" <[email-masked]>
wrote:

>
>A new version of I-D, draft-eckel-aeon-problem-statement-00.txt
>has been successfully submitted by Charles Eckel and posted to the IETF 
>repository.
>
>Name:		draft-eckel-aeon-problem-statement
>Revision:	00
>Title:		Application Enabled Open Networking: Problem Statement and
>Requirements
>Document date:	2014-02-14
>Group:		Individual Submission
>Pages:		6
>URL:            
>http://www.ietf.org/internet-drafts/draft-eckel-aeon-problem-statement-00.
>txt
>Status:         
>https://datatracker.ietf.org/doc/draft-eckel-aeon-problem-statement/
>Htmlized:       
>http://tools.ietf.org/html/draft-eckel-aeon-problem-statement-00
>
>
>Abstract:
>   Identification and treatment of application flows are critical for
>   the successful deployment and operation of applications.
>   Historically, this functionality has been accomplished to the extent
>   possible using heuristics, which inspect and infer flow
>   characteristics.  Heuristics may be based on port ranges, network
>   separation, or deep packet inspection (DPI).  But many application
>   flows in current usages are dynamic, time-bound (short lived for some
>   of them), possibly encrypted (TLS for signaling), peer-to-peer,
>   possibly asymmetric, and used on non-dedicated devices, any
>   combination of which renders such techniques less effective or
>   results 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
>

_______________________________________________
Aeon mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/aeon