Re: [Aeon] Collaborative network proposal

"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Mon, 24 March 2014 19:19 UTC

Return-Path: <eckelcu@cisco.com>
X-Original-To: aeon@ietfa.amsl.com
Delivered-To: aeon@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEF3F1A02AC for <aeon@ietfa.amsl.com>; Mon, 24 Mar 2014 12:19:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xntYMNSa8y7N for <aeon@ietfa.amsl.com>; Mon, 24 Mar 2014 12:19:45 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 6F3971A029A for <aeon@ietf.org>; Mon, 24 Mar 2014 12:19:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=23325; q=dns/txt; s=iport; t=1395688785; x=1396898385; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=uE5NUjGn7AaEM4EmO2Xjj1yY0+u4e+u+QPIxN3Vo4/Q=; b=UwXTj1FQVi2IwAmjGcHeuv7e6EmMC6S9sGp/iUj3EG14cziQoRm7p6w5 laeqTQXw5y20d/xd174+G0cw+9gw7nq7W/2mlHI41uRxVrve5SQ0Q5jbw a6p2NcknfgWtyBJXnk4sYx9Bt/PARHadVHgVuwE4YYnghBoE7qQ6wCB73 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlUFALiEMFOtJV2Z/2dsb2JhbABPCoJCRDtXuXuBP4c1gR8WdIIlAQEBBAEBASpBBAcQAgEIEQMBAQEhBwchBgsUCQgBAQQBDQUJEodKAxABDcd1DYcyF4xdgUE4Ew0EBgEChDYEll2BbYEyizaFSYMtgis
X-IronPort-AV: E=Sophos; i="4.97,722,1389744000"; d="scan'208,217"; a="312481295"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-2.cisco.com with ESMTP; 24 Mar 2014 19:19:43 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s2OJJhFq000642 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 24 Mar 2014 19:19:43 GMT
Received: from xmb-aln-x08.cisco.com ([169.254.3.148]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.03.0123.003; Mon, 24 Mar 2014 14:19:43 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Fan, Peng" <fanpeng@chinamobile.com>, Hui Deng <denghui02@gmail.com>
Thread-Topic: [Aeon] Collaborative network proposal
Thread-Index: Ac9E/e2F9LxhCAqLRE6sXsjuwdf/NwAEpNIAAA8j8YAAjgsoAA==
Date: Mon, 24 Mar 2014 19:19:42 +0000
Message-ID: <CF55D20F.23767%eckelcu@cisco.com>
References: <913383AAA69FF945B8F946018B75898A242D9B09@xmb-rcd-x10.cisco.com> <CF51B2E4.234F4%eckelcu@cisco.com> <6CFE8000-610F-403B-A361-60D996CD62F9@ericsson.com>
In-Reply-To: <6CFE8000-610F-403B-A361-60D996CD62F9@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.9.131030
x-originating-ip: [171.68.20.27]
Content-Type: multipart/alternative; boundary="_000_CF55D20F23767eckelcuciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/aeon/8Nq4HO9poAVY4GGg5D3wACr8Reo
Cc: Anton Smith <anton.smith@ericsson.com>, "aeon@ietf.org" <aeon@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>, "Tirumaleswar Reddy \(tireddy\)" <tireddy@cisco.com>
Subject: Re: [Aeon] Collaborative network proposal
X-BeenThere: aeon@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Application Enabled Open Networking \(AEON\)" <aeon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aeon>, <mailto:aeon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aeon/>
List-Post: <mailto:aeon@ietf.org>
List-Help: <mailto:aeon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aeon>, <mailto:aeon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Mar 2014 19:19:50 -0000

Hui and Peng,

Your draft fits very well with the problem statement and use cases discussed within AEON. It provides valuable insights into the ISP/ICP relationship and how it can be improved. In addition to those mentioned previously in this thread, limitations AEON aims to address include:
1) Lack of ability for end user or application to express the relative priority of this applications traffic or with respect to other applications or other traffic within this same application (e.g. one video stream more important than another) .
2) Lack of ability for network to provide explicit feedback to application regarding network conditions such as congestion, pre-configured limitations, etc. For example, the network drops packets arbitrarily rather than telling the application the network conditions and enabling the application to adapt its traffic accordingly.
Do you agree these limitations exist currently within ISP networks, and do you see it being within the scope of AEON to address these limitations as well?

Cheers,
Charles

From: Anton Smith <anton.smith@ericsson.com<mailto:anton.smith@ericsson.com>>
Date: Friday, March 21, 2014 at 9:32 AM
To: Charles Eckel <eckelcu@cisco.com<mailto:eckelcu@cisco.com>>
Cc: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com<mailto:tireddy@cisco.com>>, "Fan, Peng" <fanpeng@chinamobile.com<mailto:fanpeng@chinamobile.com>>, Hui Deng <denghui02@gmail.com<mailto:denghui02@gmail.com>>, "aeon@ietf.org<mailto:aeon@ietf.org>" <aeon@ietf.org<mailto:aeon@ietf.org>>, Ted Lemon <Ted.Lemon@nominum.com<mailto:Ted.Lemon@nominum.com>>
Subject: Re: [Aeon] Collaborative network proposal

Hi all,

I've been lurking but another consideration of course is that DPI doesn't scale in terms of bps/forwarding.

Regards
Anton

Sent from my iPhone

On 21 mar 2014, at 17:19, "Charles Eckel (eckelcu)" <eckelcu@cisco.com<mailto:eckelcu@cisco.com>> wrote:

I agree. Network operators need ways to categorize and provide differentiated services for traffic, but relying on DPI is error prone, cumbersome, and potentially done at the expense of user privacy and application security (e.g. shared keys made available to DPI enabled middle boxes or HTTP proxies ). In the end, much more information about the user and the application are revealed than was actually needed by the network operator to achieve their goals. By eliminating reliance on DPI we reduce the incentive and justification for such practices.

Cheers,
Charles

From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com<mailto:tireddy@cisco.com>>
Date: Friday, March 21, 2014 at 5:06 AM
To: "Fan, Peng" <fanpeng@chinamobile.com<mailto:fanpeng@chinamobile.com>>, 'Hui Deng' <denghui02@gmail.com<mailto:denghui02@gmail.com>>, "aeon@ietf.org<mailto:aeon@ietf.org>" <aeon@ietf.org<mailto:aeon@ietf.org>>, 'Ted Lemon' <Ted.Lemon@nominum.com<mailto:Ted.Lemon@nominum.com>>
Subject: Re: [Aeon] Collaborative network proposal

Hi Peng,

I think DPI should be retired. In addition to the below problems you had mentioned in the draft, it’s the same problem with WebRTC where DPI would fail for signaling traffic. WebRTC framework allows any proprietary signaling to be used, so DPI/ALG will not be able to understand the control traffic (Even if middle boxes somehow magically figure to act as TLS proxy).  Both home and access network will not be able to identify and prioritize the media streams.

Cheers,
-Tiru

From: Fan, Peng [mailto:fanpeng@chinamobile.com]
Sent: Thursday, March 20, 2014 5:20 PM
To: Tirumaleswar Reddy (tireddy); 'Hui Deng'; aeon@ietf.org<mailto:aeon@ietf.org>; 'Ted Lemon'
Subject: RE: [Aeon] Collaborative network proposal

Hi Tiru,

Yes, encrypted traffic is another supporting point. I guess it is time we consider finding a way to retire or simplify DPI functions.

Regards,
Peng

From: Aeon [mailto:aeon-bounces@ietf.org] On Behalf Of Tirumaleswar Reddy (tireddy)
Sent: Thursday, March 20, 2014 3:03 PM
To: Hui Deng; aeon@ietf.org<mailto:aeon@ietf.org>; Ted Lemon
Subject: Re: [Aeon] Collaborative network proposal

Hi Hui,

The other problem is that when content providers and clients move to TLS for privacy reasons, the current DPI mechanisms used by middle boxes will fail.
You may want to look into http://tools.ietf.org/html/draft-eckel-aeon-use-cases-00#section-2.5.1 which discusses similar problems with CDN and possible solutions.

Thanks and Regards,
-Tiru

From: Aeon [mailto:aeon-bounces@ietf.org] On Behalf Of Hui Deng
Sent: Thursday, March 20, 2014 7:09 AM
To: aeon@ietf.org<mailto:aeon@ietf.org>; Ted Lemon
Subject: [Aeon] Collaborative network proposal

Hello all.

We just submitted a draft to propose the concept of the collaborative network as below link:
http://www.ietf.org/id/draft-fan-intarea-conet-ps-uc-00.txt

Our basic ideal is that there are many similar use cases as AEON, so we post here to seek for more comments whether we could work together

Here we cc to Int Area AD Ted.

Thanks a lot

-Hui
_______________________________________________
Aeon mailing list
Aeon@ietf.org<mailto:Aeon@ietf.org>
https://www.ietf.org/mailman/listinfo/aeon