Re: [tsvwg] Agenda request for the TSVWG meeting in Prague

"qinxiaowei@cnnic.cn" <qinxiaowei@cnnic.cn> Fri, 19 June 2015 07:23 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 15E3C1A6FFF for <tsvwg@ietfa.amsl.com>; Fri, 19 Jun 2015 00:23:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.61
X-Spam-Level:
X-Spam-Status: No, score=-0.61 tagged_above=-999 required=5 tests=[BAYES_50=0.8, GB_I_LETTER=-2, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_55=0.6, 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 PWC9uD7BbotK for <tsvwg@ietfa.amsl.com>; Fri, 19 Jun 2015 00:23:02 -0700 (PDT)
Received: from cnnic.cn (smtp13.cnnic.cn [218.241.118.13]) by ietfa.amsl.com (Postfix) with ESMTP id AF6871A6F10 for <tsvwg@ietf.org>; Fri, 19 Jun 2015 00:23:00 -0700 (PDT)
Received: from CNNIC-PC (unknown [218.241.103.131]) by ocmail02.zx.nicx.cn (Coremail) with SMTP id AQAAf0DJ0ZVBw4NVCqxzBw--.4305S2; Fri, 19 Jun 2015 15:22:41 +0800 (CST)
Date: Fri, 19 Jun 2015 15:22:34 +0800
From: "qinxiaowei@cnnic.cn" <qinxiaowei@cnnic.cn>
To: "david.black" <david.black@emc.com>
References: <2015061609380655266421@cnnic.cn>, <CE03DB3D7B45C245BCA0D243277949360B3796CF@MX104CL02.corp.emc.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 5, 136[cn]
Mime-Version: 1.0
Message-ID: <2015061915223473892022@cnnic.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart217547876082_=----"
X-CM-TRANSID: AQAAf0DJ0ZVBw4NVCqxzBw--.4305S2
X-Coremail-Antispam: 1UD129KBjvJXoWxZrW5WryxGFWfGryxAF1xGrg_yoWrury3pa yFgFZxKF4kJa97Xw1kJw1xJryS9393Kw43Ja15tryDA398KF1IkF17Jr1UXr98Cr1rXF1Y qryqvan8Ga4vyrJanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUULCb7Iv0xC_Kw4lb4IE77IF4wAFF20E14v26r1j6r4UM7CY07I2 0VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rw A2F7IY1VAKz4vEj48ve4kI8wA2z4x0Y4vE2Ix0cI8IcVAFwI0_Xr0_Ar1l84ACjcxK6xII jxv20xvEc7CjxVAFwI0_Cr0_Gr1UM28EF7xvwVC2z280aVAFwI0_Cr1j6rxdM28EF7xvwV C2z280aVCY1x0267AKxVW0oVCq3wAS0I0E0xvYzxvE52x082IY62kv0487Mc02F40Eb7x2 x7xS6ryj6rWUMc02F40En4AKxVAvwIkv4cxYr24l5I8CrVAqjxCE14ACF2xKxwAqx4xG64 kEw2xG04xIwI0_Jr0_Gr1l5I8CrVCF0I0E4I0vr24l5I8CrVC2j2CEjI02ccxYII8I67AE r4CY67k08wAv7VC0I7IYx2IY67AKxVWUJVWUGwAv7VC2z280aVAFwI0_Jr0_Gr1lOx8S6x CaFVCjc4AY6r1j6r4UM4x0Y48IcxkI7VAKI48JM4xvF2IEb7IF0Fy264kE64k0F24lFcxC 0VAYjxAxZF0Ex2IqxwCjr7xvwVCIw2I0I7xG6c02F41lc2xSY4AK67AK6r4xMxAIw28Icx kI7VAKI48JMxC20s026xCaFVCjc4AY6r1j6r4UMI8I3I0E5I8CrVAFwI0_JrI_JrWlx2Iq xVCjr7xvwVAFwI0_JrI_JrWlx4CE17CEb7AF67AKxVWUAVWUtwCIc40Y0x0EwIxGrwCI42 IY6xIIjxv20xvE14v26r1j6r1xMIIF0xvE2Ix0cI8IcVCY1x0267AKxVWUJVW8JwCI42IY 6xAIw20EY4v20xvaj40_WFyUJVCq3wCI42IY6I8E87Iv67AKxVWUJVW8JwCI42IY6I8E87 Iv6xkF7I0E14v26r1j6r4UMVCEFcxC0VAYjxAxZFUvcSsGvfC2KfnxnUUI43ZEXa7IU5Wy I5UUUUU==
X-CM-SenderInfo: xtlq5x5drzvxw6fq0xffof0/
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/S5xEK6iuwMr-H5J8sOxbmLmvwKw>
Cc: gorry <gorry@erg.abdn.ac.uk>, tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] Agenda request for the TSVWG meeting in Prague
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: Fri, 19 Jun 2015 07:23:09 -0000

Dear David ,
Thanks for you letter.

Perhaps UATN is an new ideas, so has not attracted people's concerns up to now. IMO, as mobile devices developing, however, the UATN will be used widely in the future.

>  We’re unclear on what protocol or other specification work the draft is suggesting that the IETF (and specifically TSVWG) undertake, as Section 4 says:
> 4.  New Protocol Considerations
 > This document does not call for changes or additions: any new session, transport or network protocols; new protocols for delivering content from a UATN to an End User/User agent; 
> new protocols for ingestion of content between a UATN and a USP.

- Many existing Upload Service Providers(USPs) have deployed or are deploying their own upload acceleration networks, or are scaling up their data servers infrastructure to expand upstream throughput to improve user experience. However, no standards or open specifications currently exist to facilitate such acceleration approach.  IMO, IETF may need to give a "framework" document providing a description of the Upload Acceleration Transport Network(UATN) and how it works. So that end users can use the UATN regardless of that End User's location or attachment network. 
- There already exists transport protocols between end user and data center, so, IMO , UATN can use the existing transport protocols to avoid defining new protocols. However, it needs to point out which transport protocol/ protocols can be used.
-Especially, in existing CDNs, content is moved to Edge Servers ahead of time or scheduled time, and the data transmission service is "from one server to many end users". The uploading of end users is unexpected and the data transmission is "from many end users to one data server". So, UATN itself may need a new transport protocol for moving content over the long-haul Internet with high reliability and performance.

best wishes
Xiaowei Qin 
From: Black, David
Date: 2015-06-17 04:53
To: qinxiaowei@cnnic.cn
CC: tsvwg; gorry; Black, David
Subject: RE: Re:[tsvwg] Agenda request for the TSVWG meeting in Prague
Dear Xiaowei,
 
First of all, we (WG chairs) want to thank you for setting a good example
of how to go about bringing ideas for new work to the IETF.  The -00
UATN draft was submitted well before the 2-week pre-meeting cutoff,
the submission was announced to the relevant mailing lists, and there’s
been some discussion on the lists.
 
All of those steps are appreciated, and are much better than the
alternative approach of submitting a -00 draft right at the 2-week
pre-meeting cutoff and then immediately asking for agenda time.  The
WG chairs usually turn down the latter sort of request, as we want to
see some level of interest in the proposed activity based on list
discussion.
 
Turning to the UATN draft itself, we (WG chairs) have a few concerns:
 
- We’re not sure whether this draft belongs in the TSV Area vs. the ART
      Area.  As a CDN-related draft, it may belong over in ART, at that’s
the IETF Area into which the CDNI WG was recently moved.
- We haven’t seen any interest expressed in this work from people other
      than the authors either here or on the apps-discuss list (in ART).
We’ll continue to watch the mailing lists.
- We’re unclear on what protocol or other specification work the draft
is suggesting that the IETF (and specifically TSVWG) undertake,
as Section 4 says:
 
4.  New Protocol Considerations
 
   This document does not call for changes or additions: any new
   session, transport or network protocols; new protocols for delivering
   content from a UATN to an End User/User agent; new protocols for
   ingestion of content between a UATN and a USP.
 
      (https://tools.ietf.org/html/draft-qin-tsvwg-uatnut-00#section-4)
 
We’d appreciate some clarification on the latter concern, and we’ll
continue to watch mailing list discussion, but it’s not appropriate to
put the UATN draft on the tsvwg agenda at this time.  The agenda will
evolve between now and the Prague meeting, so there may be an opportunity
to add time for the draft later on.
 
Thanks,
--David and Gorry (tsvwg chairs)
 
From: qinxiaowei@cnnic.cn [mailto:qinxiaowei@cnnic.cn] 
Sent: Monday, June 15, 2015 9:38 PM
To: Black, David; gorry
Cc: tsvwg
Subject: Re:[tsvwg] Agenda request for the TSVWG meeting in Prague
 
Dear Gorry & David, 


I would like to have a 15-minute time slot  to present the UATN to our folks in the Prague IETF meeting. 
  I have already proposed an approach to Upload Acceleration Transport Network(UATN) for upstream traffics, and the drafts was submitted.  
   This is the link, https://datatracker.ietf.org/doc/draft-qin-tsvwg-uatnut/
 
Regards,
Xiaowei Qin
 
 
 
It is time to start building the TSVWG meeting agenda for the Prague IETFmeeting.• As usual, if you edit a WG draft, please contact the chairs and let usknow whether we should expect a short update or whether you think youcould benefit from a longer slot to discuss issues.• If you would like to present other work in tsvwg, please send an emailto the Chairs asap - so things can be discussed on the list prior to themeeting.Note: please be sure to embed "tsvwg"in the filename of all newdrafts.Please send requests as soon as possible.Thanks!Gorry & David(tsvwg Co-Chairs)