IETF Logo Mail Archive

Re: [Aeon] Comments and next step proposal

Linda Dunbar <linda.dunbar@huawei.com> Thu, 24 April 2014 22:42 UTC

Return-Path: <linda.dunbar@huawei.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 D03941A040D for <aeon@ietfa.amsl.com>; Thu, 24 Apr 2014 15:42:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.472
X-Spam-Level:
X-Spam-Status: No, score=-4.472 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] 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 W2Kjmpj2qRnk for <aeon@ietfa.amsl.com>; Thu, 24 Apr 2014 15:42:42 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 055D51A03FD for <aeon@ietf.org>; Thu, 24 Apr 2014 15:42:40 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BGB17911; Thu, 24 Apr 2014 22:42:34 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 24 Apr 2014 23:41:33 +0100
Received: from DFWEML703-CHM.china.huawei.com (10.193.5.130) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 24 Apr 2014 23:42:33 +0100
Received: from DFWEML701-CHM.china.huawei.com ([169.254.1.127]) by dfweml703-chm.china.huawei.com ([169.254.5.104]) with mapi id 14.03.0158.001; Thu, 24 Apr 2014 15:42:26 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: "Fan, Peng" <fanpeng@chinamobile.com>, "pierrick.seite@orange.com" <pierrick.seite@orange.com>, "aeon@ietf.org" <aeon@ietf.org>
Thread-Topic: [Aeon] Comments and next step proposal
Thread-Index: Ac9eHbq9rtqo/E0OR+qe+zafwgUmEgAhdSyAADtjrPAAF1LJgAAH8RJw
Date: Thu, 24 Apr 2014 22:42:26 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F645CFD20F@dfweml701-chm.china.huawei.com>
References: <00a301cf5e20$ab403530$01c09f90$@chinamobile.com> <5D36713D8A4E7348A7E10DF7437A4B923AE3D6C6@nkgeml512-mbx.china.huawei.com> <21425_1398328888_5358CE38_21425_1410_1_81C77F07008CA24F9783A98CFD706F711422ED0D@PEXCVZYM12.corporate.adroot.infra.ftgroup> <007a01cf5fb3$bd975530$38c5ff90$@chinamobile.com>
In-Reply-To: <007a01cf5fb3$bd975530$38c5ff90$@chinamobile.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.150.240]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F645CFD20Fdfweml701chmchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/aeon/ZAwsafeaY6V4TW7qJHA3iLlm3uM
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: Thu, 24 Apr 2014 22:42:46 -0000

Peng,

Questions inserted below:

From: Aeon [mailto:aeon-bounces@ietf.org] On Behalf Of Fan, Peng


Content based charging is already deployed in China. For example, Alibaba has the cooperation with China Mobile and China Unicom for the charge of its traffic.

[Linda] is the charging based on total traffic volume? Or is it based on specific applications? Will Alibaba agree to attach some identifier of their specific application to their data packets?

Thanks,
Linda

v2.8.7 | Report a Bug | By Email