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

"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Fri, 14 February 2014 18:28 UTC

From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "aeon@ietf.org" <aeon@ietf.org>
Thread-Topic: New Version Notification for draft-eckel-aeon-problem-statement-00.txt
Thread-Index: AQHPKbEyL0Nuw1EqrEWTXJNJ3jCsYJq08EaA
Date: Fri, 14 Feb 2014 18:28:47 +0000
Message-ID: <CF239EE3.1EDB1%eckelcu@cisco.com>
References: <20140214181840.14035.86856.idtracker@ietfa.amsl.com>
In-Reply-To: <20140214181840.14035.86856.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.3.9.131030
Content-Type: text/plain; charset="us-ascii"
Content-ID: <07BF0C6B711968419A199F8ADB3BBF5E@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/aeon/-78v4ZiJQsFGn6JKNaghl9WDj9M
Subject: [Aeon] FW: New Version Notification for draft-eckel-aeon-problem-statement-00.txt
Precedence: list

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, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
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] FW: New Version Notification for draft-eck… Charles Eckel (eckelcu)