Re: [tcpm] [tsvwg] Agenda requests for TSVWG@IETF101

Michael Tuexen <michael.tuexen@lurchi.franken.de> Tue, 13 March 2018 09:45 UTC

Return-Path: <michael.tuexen@lurchi.franken.de>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5875F12D7FC; Tue, 13 Mar 2018 02:45:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.609
X-Spam-Level:
X-Spam-Status: No, score=-2.609 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 KRP72oOC8qxc; Tue, 13 Mar 2018 02:45:15 -0700 (PDT)
Received: from drew.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 15E6912D72F; Tue, 13 Mar 2018 02:45:14 -0700 (PDT)
Received: from [IPv6:2003:cd:6bea:8000:6010:e1fa:597e:6ad7] (p200300CD6BEA80006010E1FA597E6AD7.dip0.t-ipconnect.de [IPv6:2003:cd:6bea:8000:6010:e1fa:597e:6ad7]) (Authenticated sender: lurchi) by mail-n.franken.de (Postfix) with ESMTPSA id 00F10721E280C; Tue, 13 Mar 2018 10:45:10 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
From: Michael Tuexen <michael.tuexen@lurchi.franken.de>
In-Reply-To: <CABY-gOMJf-4GKkbmYMJScrafO44NEfy0hoq5KXJ0uVA+QUXGiA@mail.gmail.com>
Date: Tue, 13 Mar 2018 10:45:09 +0100
Cc: "Scharf, Michael (Nokia - DE/Stuttgart)" <michael.scharf@nokia.com>, Thomas Nadeau <tnadeau@lucidvision.com>, "tcpm@ietf.org" <tcpm@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "tsvwg-chairs@ietf.org" <tsvwg-chairs@ietf.org>, Yingzhen Qu <yingzhen.qu@huawei.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <430A7C48-DA1D-4D73-AB40-F2B30A8E8580@lurchi.franken.de>
References: <A1F61D20-1911-4A6E-9F80-A1DF1EF91816@huawei.com> <AM5PR0701MB254755BA63E33173CC7C7BCE93DB0@AM5PR0701MB2547.eurprd07.prod.outlook.com> <5A9BEB65.6010102@erg.abdn.ac.uk> <CABY-gOO8sH3+5qfFj7DV6wh6+uX8CyBfwo4FBLi=9x1RngQDHg@mail.gmail.com> <AM5PR0701MB25474AC4A52E38B43E543FA193DA0@AM5PR0701MB2547.eurprd07.prod.outlook.com> <CABY-gOMJf-4GKkbmYMJScrafO44NEfy0hoq5KXJ0uVA+QUXGiA@mail.gmail.com>
To: Yingzhen Qu <yingzhen.ietf@gmail.com>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/xDhd6yyEs2y-PiynadLqk9gsfT4>
Subject: Re: [tcpm] [tsvwg] Agenda requests for TSVWG@IETF101
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Mar 2018 09:45:18 -0000

> On 13. Mar 2018, at 07:43, Yingzhen Qu <yingzhen.ietf@gmail.com> wrote:
> 
> Hi Michael,
>  
> Sorry for the late response. 
> 
> Thanks for pointing out that we missed this important reference. You're right, Quick-Start and our proposal do have lots of similarities, for example both of them require that end-points and routers to work together. But they are also different in details. For example, in our proposal in-band signaling proposal bandwidth is reserved on routers along the path.
> 
> In next version of this draft, We'll add discussions about RFC 4728 and 6077.
> 
> BTW, can I request a slot to present this draft in TCPM if time allows?
How much time would you need?

Best regards
Michael
> 
> Thanks,
> Yingzhen
> 
> On Mon, Mar 5, 2018 at 12:09 AM, Scharf, Michael (Nokia - DE/Stuttgart) <michael.scharf@nokia.com> wrote:
> I believe that this proposal is similar to QuickStart TCP (RFC 4782), which is not cited in draft-han-tsvwg-cc, and the reference is also missing in draft-han-6man-in-band-signaling-for-transport-qos.
> 
>  
> 
> RFC 6077 explains some of the issues that an in-band signaling mechanism like Quick-Start has to solve. As far as I can tell, the fundamental challenge is neither the protocol specification nor a prototype implementation. For instance, it has been proven that QuickStart TCP can be implemented e.g. in network processors (see http://www.ikr.uni-stuttgart.de/Content/Publications/Archive/Sf_Diss_40112.pdf).
> 
>  
> 
> So, when updating the documents, I suggest to add a discussion of how the open research issues explained in RFC 6077 are addressed.
> 
>  
> 
> Michael
> 
>  
> 
>  
> 
> From: Yingzhen Qu [mailto:yingzhen.ietf@gmail.com] 
> Sent: Sunday, March 04, 2018 9:59 PM
> To: gorry@erg.abdn.ac.uk
> Cc: Scharf, Michael (Nokia - DE/Stuttgart) <michael.scharf@nokia.com>; Thomas Nadeau <tnadeau@lucidvision.com>; tcpm@ietf.org; Yingzhen Qu <yingzhen.qu@huawei.com>; tsvwg@ietf.org; tsvwg-chairs@ietf.org
> Subject: Re: [tsvwg] Agenda requests for TSVWG@IETF101
> 
>  
> 
> Hi Gorry and Michael,
> 
>  
> 
> Thanks for the suggestion, I'll request a presentation in ICCRG. Meanwhile, I think since the in-band signaling draft was presented in TSVWG, if time allows it still makes sense to present this draft in TSVWG. 
> 
>  
> 
> The in-band signaling draft covers lots of aspects, and the required changes include network layer and transport layer. We're working on updating the draft, and may break it into pieces to fit different WGs.
> 
>  
> 
> Your comments and help are very much appreciated.
> 
>  
> 
> Thanks,
> 
> Yingzhen
> 
>  
> 
> On Sun, Mar 4, 2018 at 4:49 AM, Gorry Fairhurst <gorry@erg.abdn.ac.uk> wrote:
> 
> I am unsure yet what the correct group of people world be to explore a "Bandwidth Guaranteed Network". The presentation last IETF looked like the work could imply a need for changes proposed to the network layer (using OAM exchnages) to set the sending rate and make those bandwidth reservations.  In the end, it could result in a protocol quite different to TCP, I think this sort of change may possibly have a home in TSVWG  - but first I'd agree with Michaeland would encourage a presentation of the problem statement in ICCRG to explore the issues.
> 
> Gorry
> 
> On 04/03/2018, 10:34, Scharf, Michael (Nokia - DE/Stuttgart) wrote:
> 
> 
> Hi all,
> 
> >From the abstract: “…This draft proposes a new TCP congestion control algorithm used in bandwidth guaranteed networks.  It is an extension to the current TCP standards.”
> 
> In the IETF, I believe the expertise for this specific document would be in TCPM, which in CC. If the authors are interested in feedback on the proposed mechanism, I would recommend to ask TCPM.
> 
> Alternatively, corresponding research could perhaps be performed in the ICCRG. ICCRG has published RFC 6077 to document some of the open research issues in this space.
> 
> Michael
> 
> *From:*tsvwg [mailto:tsvwg-bounces@ietf.org] *On Behalf Of *Yingzhen Qu
> *Sent:* Sunday, March 04, 2018 6:55 AM
> *To:* tsvwg@ietf.org; tsvwg-chairs@ietf.org
> *Cc:* Thomas Nadeau <tnadeau@lucidvision.com>
> *Subject:* [tsvwg] Agenda requests for TSVWG@IETF101
> 
> Dear Chairs,
> 
> A new draft (The draft was suggested by TSVWG @IETF100) was just submitted, and we’d like to request a time slot to present it @IETF101.
> 
> Title:A New Congestion Control in Bandwidth Guaranteed Network
> 
> Presenter: Yingzhen Qu (Huawei)
> 
> Time required (including Q/A): 10 mins
> 
> Draft: https://datatracker.ietf.org/doc/draft-han-tsvwg-cc/
> 
> If there is any question, please kindly let us know.
> 
> Thanks,
> 
> Yingzhen
> 
>  
> 
>  
> 
> 
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm