<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.eckel-aeon-problem-statement" target="https://datatracker.ietf.org/doc/html/draft-eckel-aeon-problem-statement-00">
   <front>
      <title>Application Enabled Open Networking: Problem Statement and Requirements</title>
      <author initials="C." surname="Eckel" fullname="Charles Eckel">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="T." surname="Reddy.K" fullname="Tirumaleswar Reddy.K">
         <organization>Cisco Systems</organization>
      </author>
      <date month="February" day="14" year="2014" />
      <abstract>
	 <t>   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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-eckel-aeon-problem-statement-00" />
   
</reference>
