IETF Logo Mail Archive

Re: [Aeon] Collaborative network proposal

"Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com> Fri, 21 March 2014 12:06 UTC

Return-Path: <tireddy@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 E00031A096C for <aeon@ietfa.amsl.com>; Fri, 21 Mar 2014 05:06:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.047
X-Spam-Level:
X-Spam-Status: No, score=-10.047 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, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001, 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 tZ8RxPvbpp16 for <aeon@ietfa.amsl.com>; Fri, 21 Mar 2014 05:06:48 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) by ietfa.amsl.com (Postfix) with ESMTP id 3DA561A072C for <aeon@ietf.org>; Fri, 21 Mar 2014 05:06:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15377; q=dns/txt; s=iport; t=1395403599; x=1396613199; h=from:to:subject:date:message-id:mime-version; bh=kDMvnDNJF0QfonMVMMebZo87yMBPG+/WjGt8EuPRzlM=; b=hh/XsT1+5uQqR+iInmTAbrMkgEElWf0bxaX8EpoyzrPhkYAh4Ke1SAS+ sDwZyxVLTcCJXgaymadegEZqBC+39GaoAiLHRnhH8deXIWBX8upeHvAs1 j5QI4qdW/QkyKiPP1nW7tU7GFxOrJs5TwAmBf/bSrCbYgqvYDWoB1DlLW k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Al4FAFQqLFOtJXHB/2dsb2JhbABPCoJCRDtXuWiIcYEWFnSCJQEBAQQtXgEIEQQBAQsdORQJCQEEARIIARKHXg3PWxeODis3gyWBFASZe5B/gy2CKw
X-IronPort-AV: E=Sophos; i="4.97,703,1389744000"; d="scan'208,217"; a="29285975"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by alln-iport-2.cisco.com with ESMTP; 21 Mar 2014 12:06:38 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id s2LC6coZ002664 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 21 Mar 2014 12:06:38 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.233]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.03.0123.003; Fri, 21 Mar 2014 07:06:38 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: "Fan, Peng" <fanpeng@chinamobile.com>, "'Hui Deng'" <denghui02@gmail.com>, "aeon@ietf.org" <aeon@ietf.org>, "'Ted Lemon'" <Ted.Lemon@nominum.com>
Thread-Topic: [Aeon] Collaborative network proposal
Thread-Index: Ac9E/e2FwCfU9vrUT9acrKqmZrxP7w==
Date: Fri, 21 Mar 2014 12:06:37 +0000
Message-ID: <913383AAA69FF945B8F946018B75898A242D9B09@xmb-rcd-x10.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [173.39.67.67]
Content-Type: multipart/alternative; boundary="_000_913383AAA69FF945B8F946018B75898A242D9B09xmbrcdx10ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/aeon/AIsryV3AXJtJCRgXtgzilQKXdE4
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: Fri, 21 Mar 2014 12:06:51 -0000

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; '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

v2.8.7 | Report a Bug | By Email