<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.conet-aeon-problem-statement" target="https://datatracker.ietf.org/doc/html/draft-conet-aeon-problem-statement-01">
   <front>
      <title>Application Enabled Collaborative Networking: Problem Statement</title>
      <author initials="P." surname="Fan" fullname="Peng Fan">
         <organization>China Mobile</organization>
      </author>
      <author initials="H." surname="Deng" fullname="DENG Hui">
         <organization>China Mobile</organization>
      </author>
      <author initials="M." surname="Boucadair" fullname="Mohamed Boucadair">
         <organization>France Telecom</organization>
      </author>
      <author initials="T." surname="Reddy.K" fullname="Tirumaleswar Reddy.K">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="C." surname="Eckel" fullname="Charles Eckel">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="B." surname="Williams" fullname="Brandon Williams">
         <organization>Akamai, Inc.</organization>
      </author>
      <date month="July" day="3" year="2014" />
      <abstract>
	 <t>   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.

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