Re: [tsvwg] I-D Action: draft-qin-tsvwg-uatnut-00.txt

"qinxiaowei@cnnic.cn" <qinxiaowei@cnnic.cn> Mon, 15 June 2015 07:47 UTC

Return-Path: <qinxiaowei@cnnic.cn>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2FCF1B2AD9; Mon, 15 Jun 2015 00:47:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.79
X-Spam-Level:
X-Spam-Status: No, score=0.79 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 XzwF2xLGB6-h; Mon, 15 Jun 2015 00:47:08 -0700 (PDT)
Received: from cnnic.cn (smtp13.cnnic.cn [218.241.118.13]) by ietfa.amsl.com (Postfix) with ESMTP id 432761A1AC1; Mon, 15 Jun 2015 00:47:03 -0700 (PDT)
Received: from CNNIC-PC (unknown [218.241.119.111]) by ocmail02.zx.nicx.cn (Coremail) with SMTP id AQAAf0BpcZXxgn5Vk0ZvBw--.4027S2; Mon, 15 Jun 2015 15:46:57 +0800 (CST)
Date: Mon, 15 Jun 2015 15:46:51 +0800
From: "qinxiaowei@cnnic.cn" <qinxiaowei@cnnic.cn>
To: Linlin Zhou <nucent@gmail.com>
References: <201506041134264013761@cnnic.cn>, <CAN1WL5pFOnvQh3L3z3jR=3=cyJdjQD=MFXtykYU7n-iA8eyWsg@mail.gmail.com>, <CAN1WL5odXiLTvR_r1VGw5-9XRg8310ZJ1AH-+CmsxPGNACEw5A@mail.gmail.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 5, 136[cn]
Mime-Version: 1.0
Message-ID: <2015061515465115580522@cnnic.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart312232570750_=----"
X-CM-TRANSID: AQAAf0BpcZXxgn5Vk0ZvBw--.4027S2
X-Coremail-Antispam: 1UD129KBjvJXoWxGF47Gw4fJFW8GrWUGr4fGrg_yoWrXr47pa yUXr95KrWUA3Wftw1kZ3WrXr95u3ykW3y3KFn8Gr1Uu398CFyIgr17KrWFya47XrnIgFs0 vr4Uuw1Ykws5ZrJanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUdmb7Iv0xC_Cr1lb4IE77IF4wAFF20E14v26r1j6r4UM7CY07I2 0VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rw A2F7IY1VAKz4vEj48ve4kI8wA2z4x0Y4vE2Ix0cI8IcVAFwI0_Xr0_Ar1l84ACjcxK6xII jxv20xvEc7CjxVAFwI0_Cr0_Gr1UM28EF7xvwVC2z280aVAFwI0_GcCE3s1l84ACjcxK6I 8E87Iv6xkF7I0E14v26rxl6s0DM2AIxVAIcxkEcVAq07x20xvEncxIr21l5I8CrVAaz4v2 6cxKscIFY7kG0wAqx4xG6xAIxVCFxsxG0wAqx4xG6I80eVA0xI0YY7vIx2IE14AGzxvEb7 x7Mc02F40Ex2IqxVA2YxCjr7Iv64kEw24lYx0E2Ix0cI8IcVAFwI0_Jr0_Jr4lYx0Ex4A2 jsIE14v26r1j6r4UMcvjeVCFs4IE7xkEbVWUJVW8JwACjcxG0xvY0x0EwIxGrwACY4xI67 k04243AVAKzVAKj4xxM4xvF2IEb7IF0Fy26I8I3I1l7480Y4vEI4kI2Ix0rVAqx4xJMxkI ecxEwVAFwVW8CwCF04k20xvY0x0EwIxGrwCFx2IqxVCFs4IE7xkEbVWUJVW8JwC20s026c 02F40E14v26r106r1rMI8I3I0E7480Y4vE14v26r106r1rMI8E67AF67kF1VAFwI0_Jrv_ JF1lIxkGc2Ij64vIr41lIxAIcVC0I7IYx2IY67AKxVWUJVWUCwCI42IY6xIIjxv20xvEc7 CjxVAFwI0_Jr0_Gr1lIxAIcVCF04k26cxKx2IYs7xG6rW3Jr0E3s1lIxAIcVC2z280aVAF wI0_Jr0_Gr1lIxAIcVC2z280aVCY1x0267AKxVWUJVW8JwCE64xvF2IEb7IF0Fy7YxBIda VFxhVjvjDU0xZFpf9x07j79N3UUUUU=
X-CM-SenderInfo: xtlq5x5drzvxw6fq0xffof0/
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/NlYKeSZKyUd35NsCwp1tkqOpYMc>
Cc: tsv-area <tsv-area@ietf.org>, tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] I-D Action: draft-qin-tsvwg-uatnut-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jun 2015 07:47:11 -0000

hi, Linlin
Thanks again for you review and suggestion.

>I think the numbers you listed are not enough to prove the conclusion. 
>Do you have more detailed examples?

The test is only for mobile devices, and the the report comes from: 
http://testmyiphone.com/stats.

This is the latest stats:
Download:
Download tests taken 3,140,257 
Average speed 3585.44 kbps
Upload:
Upload tests taken 708,158
Average speed 630.56 kbps

In order to validate the analysis described above, I have also take a practical measurement in China Mobile Labs (located in Beijing) which is the department of the China Mobile Limited. A data server deployed in Shenzhen, situated immediately north of Hong Kong (about 2500 kilometers away from Beijing) is used to continuously wait for packets from mobile devices. 
The mobile devices is connected to Internet via TD-LTE, and content generated by mobile devices is directly uploaded to the receiver without any acceleration processing. The average upstream throughput is about 180 kbps. 
I also deploy a data server in Beijing,  the average upstream throughput can be up to 860 kbps. 
Therefore, "moving content closer to end users results in greater network efficiency, increased robustness of delivery, and lower latency.

>Regardless of the UATN approach you mentioned in the document, I
>feel like this is something like a reverse CDN. So I am wondering why
>CDN providers do not have motivation to to this work? Is it technical
>issues or not a problem at all.

The existing CDN is used to distribute content to end users, however, may not directly receive the content generated by end users.  For example, in downloading,when the user types a URL into his/her browser, the request will be redirected to the CDN through “CNAME” by the DNS.
However, in uploading, a "mechanism" is needed to redirect the requests of end users to UATN.  That is to say, the request of uploading content to data center will be redirected to an appropriate Edge Server to serve this uploading.

Regards,
Xiaowei Qin
 



 
From: Linlin Zhou
Date: 2015-06-12 14:11
To: qinxiaowei
CC: tsvwg; tsv-area
Subject: Re: Fw: Fw: I-D Action: draft-qin-tsvwg-uatnut-00.txt
Hi Xiaowei,
 
- Regardless of the UATN approach you mentioned in the document, I
feel like this is something like a reverse CDN. So I am wondering why
CDN providers do not have motivation to to this work? Is it technical
issues or not a problem at all.
 
- According to the report in [1], throughput measurements
   from over 1.5 million mobile devices have shown that compared with an
   average downstream throughput of over 1860 Kbps, the average upstream
   throughput is only about 430 Kbps.  This is because of the adoption
   of cache techniques such as CDNs to acelerate downloading large
   content that moves the "content" closer to end users.
 
I think the numbers you listed are not enough to prove the conclusion.
Do you have more detailed examples?
 
- typo in Figure 5
No arrow III is indicated in the paragraph.
 
> From: qinxiaowei@cnnic.cn
> Date: 2015-05-29 11:47
> To: tsvwg; tsv-area
> Subject: Fw: Fw: I-D Action: draft-qin-tsvwg-uatnut-00.txt
> Dear all,
> I proposed an approach to upload acceleration transport network for upstream
> traffics, and the drafts was submitted.
>
> This is the link, http://datatracker.ietf.org/doc/draft-qin-tsvwg-uatnut/
>
> Any comments are welcome.
>
> Regards,
>
> Xiaowei Qin
>
>
> From: internet-drafts
> Date: 2015-05-29 11:16
> To: i-d-announce@ietf.org
> Subject: I-D Action: draft-qin-tsvwg-uatnut-00.txt
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>   Title           : Upload Acceleration Transport Network for Upstream
> Traffics
> Authors         : Xiaowei Qin
>                           Ning Kong
>                           Xiaodong Lee
> Filename        : draft-qin-tsvwg-uatnut-00.txt
> Pages           : 12
> Date            : 2015-05-28
>
> Abstract:
>    Photos, videos and other upstream traffics generated by end users are
>    rapidly increasing these days and expected to continue doing so in
>    the future.  A lot of factors, such as long round-trip-time (RTT),
>    low robustness of delivery, and transport bottlenecks, etc., lead to
>    low upload rate, which cause poor user experiences.  This draft
>    discusses an Upload Acceleration Transport Network(UATN) for upstream
>    traffics that use distributed cache servers and separates the upload
>    transaction into two parts for greater network efficiency.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-qin-tsvwg-uatnut/
>
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-qin-tsvwg-uatnut-00
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt