Re: [Aeon] Comments and next step proposal

"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Wed, 23 April 2014 14:37 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 65D2A1A03D3 for <aeon@ietfa.amsl.com>; Wed, 23 Apr 2014 07:37:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.772
X-Spam-Level:
X-Spam-Status: No, score=-14.772 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, RP_MATCHES_RCVD=-0.272, 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 YN45oryOgklW for <aeon@ietfa.amsl.com>; Wed, 23 Apr 2014 07:37:54 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 11D8F1A03D6 for <aeon@ietf.org>; Wed, 23 Apr 2014 07:37:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=18758; q=dns/txt; s=iport; t=1398263868; x=1399473468; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=p8hQnlIb0omTBwj9ducfgV16r5cpWlRx7VGMcjdKfqs=; b=Wmlxel3Gnwmqs/cOIegCu760R284dB4gEgZT1mJw1ogmmU12dn+CJeHh THpMWb78W6ZdjalpDhzrhxVQoG0GZ+0xJJ0pF7IfOA5Otbsaw+3ET4Gsh bd5EVfFvl2KAb4yb2Xd/yY/5TQrZyJSBjjwj2D1zXJ+taMGKSL9HoiE4N k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnoFAHTPV1OtJV2Y/2dsb2JhbABZgkJET1etKI4RgUCHOoEaFnSCJQEBAQQBAQFoAwsQAgEIDgMBAgEBASgHIQYLFAMGCAIEAQ0FG4gSAxABDcg6DYZtF4xAggcNBAYBhDkElQSCAYFwgTeLS4VTgzGCKw
X-IronPort-AV: E=Sophos; i="4.97,912,1389744000"; d="scan'208,217"; a="319780361"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-8.cisco.com with ESMTP; 23 Apr 2014 14:37:48 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s3NEblUX016073 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 23 Apr 2014 14:37:47 GMT
Received: from xmb-aln-x08.cisco.com ([169.254.3.148]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.03.0123.003; Wed, 23 Apr 2014 09:37:47 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: Rong Zhang <rzhang.ietf@gmail.com>, Sheng Jiang <jiangsheng@huawei.com>
Thread-Topic: [Aeon] Comments and next step proposal
Thread-Index: AQHPXsuWrtqo/E0OR+qe+zafwgUmEpsfJC8A
Date: Wed, 23 Apr 2014 14:37:47 +0000
Message-ID: <CF7D1D3C.26D5A%eckelcu@cisco.com>
References: <CABYVfykV1KfgE2_9F+wtO-=Qqqkqi+9tNwc-J0LanZ8-x6mpNg@mail.gmail.com>
In-Reply-To: <CABYVfykV1KfgE2_9F+wtO-=Qqqkqi+9tNwc-J0LanZ8-x6mpNg@mail.gmail.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.13]
Content-Type: multipart/alternative; boundary="_000_CF7D1D3C26D5Aeckelcuciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/aeon/hJF59HWa2VNgdslgHOqjVa8yX40
Cc: "gr@gsta.com" <gr@gsta.com>, "aeon@ietf.org" <aeon@ietf.org>, "Fan, Peng" <fanpeng@chinamobile.com>
Subject: Re: [Aeon] Comments and next step 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: Wed, 23 Apr 2014 14:37:57 -0000

Hi Rong,

I do not claim to be a 3GPP expert, so please correct me if I have it wrong. The way I see it, the 3GPP Rx interface provides a means for AEON to interact with the existing 3GPP architecture. One problem for 3GPP is how to get the necessary information to be conveyed over the Rx interface. AEON can be used for end applications to communicate this information to the 3GPP network for consumption over the Rx interface. In 3GPP, I do not believe end applications have direct access to the Rx interface. AEON fills that gap.
As for whether the work proceeds in intarea or transport, the original guidance from the ADs of both areas was to start in transport. Once we have the updated drafts in place, we can certainly revisit that decision.

Cheers,
Charles

From: Rong Zhang <rzhang.ietf@gmail.com<mailto:rzhang.ietf@gmail.com>>
Date: Wednesday, April 23, 2014 at 1:11 AM
To: Sheng Jiang <jiangsheng@huawei.com<mailto:jiangsheng@huawei.com>>
Cc: "gr@gsta.com<mailto:gr@gsta.com>" <gr@gsta.com<mailto:gr@gsta.com>>, "aeon@ietf.org<mailto:aeon@ietf.org>" <aeon@ietf.org<mailto:aeon@ietf.org>>, "Fan, Peng" <fanpeng@chinamobile.com<mailto:fanpeng@chinamobile.com>>
Subject: Re: [Aeon] Comments and next step proposal

Hi all,

Speaking as the operator, I do see this trend that OTT are working with operators today which will help to improve the mobile internet user experience dramatically.

I have one basic comment that current documents have n't talked about 3GPP PCRF Rx interface which will allow OTT to work with today's mobile operator, I will work with Sheng to write the gap analysis document by including how IETF work could be a complimentary to 3GPP's specificaiton.

I am planning to attend next IETF meeting, and hope BoF will happen, I personally feel it is more Intarea scope than transport.

Cheers.

-Rong ZHANG


On Wed, Apr 23, 2014 at 11:31 AM, Sheng Jiang <jiangsheng@huawei.com<mailto:jiangsheng@huawei.com>> wrote:
Hi, all,

This is a real requirement from network operation perspective. Both ISPs and ICPs can benefit from this advance collaborative network model.

Rong Zhang and I are working on an gap analysis document, which we hope to share publically early next week.

Best regards,

Sheng

From: Aeon [mailto:aeon-bounces@ietf.org<mailto:aeon-bounces@ietf.org>] On Behalf Of Fan, Peng
Sent: Tuesday, April 22, 2014 7:48 PM
To: aeon@ietf.org<mailto:aeon@ietf.org>
Subject: [Aeon] Comments and next step proposal

Hello all,

Based on our operational experience, we have submitted a draft: http://datatracker.ietf.org/doc/draft-fan-intarea-conet-ps-uc/
The purposes of this draft are to encourage less DPI in the network and propose more cooperation between OTT and Operators. Please kindly help to review the draft and comment here.

I have also reviewed the draft:
http://datatracker.ietf.org/doc/draft-eckel-aeon-problem-statement/,
My comments are:

1)      Shall we consider to split the section 4 into an independent gap analysis document?

2)      For the requirements section, we agree Req. 1, 2, and 7, and just want to clarify:

a)       Req. 3 and 4, do you expect the interaction between network node and host here before the real traffic start?

b)       Req. 5 and 8 are not quite clear to us.

c)        I guess that it not always mandatory to apply Diffserv here, it could be optional?

3)      If you read our draft, we have more experience about the limitation of current DPI/DFI in section 3.

4)      Analysis of other existing solutions like ACL configuration can also be added in section 3.

Also for the draft:
http://datatracker.ietf.org/doc/draft-eckel-aeon-use-cases/
Here I feel that too many use cases are listed here. You may consider narrowing down to a few use cases for which we have strong and specific needs, in order to get work further progressed.

After reading the current work proposed here, we are wondering whether two groups of people could work together to propose a BoF in the coming IETF meeting. To do that, we probably can:

1)      Merge the PS draft into one document.

2)      Write an independent use case document.

3)      Write an gap analysis document.
Once all three documents have finished, we could talk to ADs from both Internet and Transport area about the next step?

Thanks a lot for your consideration.

Best regards,
Peng

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