Re: [tcpm] [tsvwg] Agenda requests for TSVWG@IETF101
Gorry Fairhurst <gorry@erg.abdn.ac.uk> Tue, 13 March 2018 12:23 UTC
Return-Path: <gorry@erg.abdn.ac.uk>
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 4799012D892; Tue, 13 Mar 2018 05:23:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 Rk-ZHOkvaQtL; Tue, 13 Mar 2018 05:23:28 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:241:204::f0f0]) by ietfa.amsl.com (Postfix) with ESMTP id 1C5BA1241F5; Tue, 13 Mar 2018 05:23:28 -0700 (PDT)
Received: from Gs-MacBook-Pro.local (at-zeroshell-1.erg.abdn.ac.uk [139.133.217.68]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id C80361B0012A; Tue, 13 Mar 2018 12:22:51 +0000 (GMT)
Message-ID: <5AA7C29B.50809@erg.abdn.ac.uk>
Date: Tue, 13 Mar 2018 12:22:51 +0000
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Reply-To: gorry@erg.abdn.ac.uk
Organization: University of Aberdeen
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: David Ros <dros@simula.no>
CC: Michael Welzl <michawe@ifi.uio.no>, "tcpm-chairs@ietf.org" <tcpm@ietf.org>, "tsvwg-chairs@ietf.org" <tsvwg-chairs@ietf.org>, Jana Iyengar <jri@google.com>
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> <430A7C48-DA1D-4D73-AB40-F2B30A8E8580@lurchi.franken.de> <5AA7A614.3050706@erg.abdn.ac.uk> <AM5PR0701MB254730C89ECA7272AE9288EC93D20@AM5PR0701MB2547.eurprd07.prod.outlook.com> <5AA7BB41.4070507@erg.abdn.ac.uk> <FF54A053-F7ED-4B94-B229-62C03339316F@ifi.uio.no> <12981CEA-7472-4AF8-92A3-49775FD92613@simula.no>
In-Reply-To: <12981CEA-7472-4AF8-92A3-49775FD92613@simula.no>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/G2srxdVMH9AxNsKMYodvOVmPZ1o>
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 12:23:30 -0000
David: You need to prune youself from the tracker mail exploder lists - or get your co-chairs to ask the secretariat this ;-) ... Otherwise you'll still feel compelled to read this. Gorry On 13/03/2018, 12:15, David Ros wrote: > Hi, > > Erm, this former ICCRG chair is also getting all these messages, and > hadn’t noticed until now that he was being bcc’ed… is this a bug or a > feature? :) > > Cheers, > > David > >> On 13 Mar 2018, at 13:11, Michael Welzl <michawe@ifi.uio.no >> <mailto:michawe@ifi.uio.no>> wrote: >> >> Hi folks! >> >> I am puzzled as to why I receive this - has someone put me in bcc? >> AFAIK, I’m not in tcpm-chairs, not in tsvwg-chairs, and I’m also >> happy to remind people that I’m *not* chairing ICCRG anymore! :-) >> >> Anyway, to me, this also sounds like ICCRG material - but I haven’t >> read the draft and so I probably shouldn’t even comment. >> But FWIW, I’d enjoy seeing this in ICCRG. I might even ask something >> at the mic, just to see how that feels. >> >> I’m cc’ing the ICCRG chair, Jana, because it seems that this should >> have reached him. >> >> Jana - I actually even can’t fully figure out what these folks here >> are talking about: either this draft: >> https://datatracker.ietf.org/doc/draft-han-tsvwg-cc >> or that draft: >> https://tools.ietf.org/html/draft-lochin-ietf-tsvwg-gtfrc-02 >> >> I think it’s the upper one. >> >> Cheers, >> Michael >> >> >>> On Mar 13, 2018, at 12:51 PM, Gorry Fairhurst <gorry@erg.abdn.ac.uk >>> <mailto:gorry@erg.abdn.ac.uk>> wrote: >>> >>> On 13/03/2018, 11:23, Scharf, Michael (Nokia - DE/Stuttgart) wrote: >>>>> As for TSVWG, we have had quite a long discussion with the authors >>>>> at the >>>>> meeting and after. The TSV chairs encouraged them to take the CC >>>>> aspects >>>>> separately and explain why this method is better and detail what >>>>> this benefit >>>>> is and what is required in the router to allow this. We suggested >>>>> an initial talk >>>>> in ICCRG to present results and show *why* this is attractive. As >>>>> far as I know >>>>> they requested time to do this. >>>> ICCRG is the right home for this. And the TCPM charter explicitly >>>> allows us to move topics there... >>>> >>>> I have written a PhD thesis on exactly this topic; we had a network >>>> processor implementation of Quick-Start, and our use cases was >>>> actually augmented/virtual reality... And I run into tons of >>>> fundamental issues 10 years ago, which are not easy to solve and >>>> not even mentioned in the I-Ds. So I somehow feel qualified to give >>>> feedback on what they have to look at more in detail 😉 >>>> >>>>> They also requested time in TSVWG - but there's (as yet) been >>>>> little discssion >>>>> on the list, so we curently advise them to prepare a slide to show >>>>> to say why >>>>> people should read the draft. We have not decided (yet) to give >>>>> time to this >>>>> new framework. >>>> I personally believe that for new ideas the IETF should give a >>>> presentation slot *once*. For a second presentation the bar should >>>> be higher. If the framework draft has been presented already in >>>> TSVWG, IMHO further discussion on that belongs now on the list. >>>> >>>>> They have now also requested time in TCPM. >>>> The draft is very specific about TCP congestion control, so in >>>> principle it belongs into TCPM. In general, I think TCPM should be >>>> open to new ideas. But my own thinking is that this can be at best >>>> a "if time permits" presentation in TCPM. >>>> >>>>> I don't know whethere this time they are also requesting slots >>>>> some other >>>>> places to discuss other aspects. >>>>> >>>>> I also suggested (informally) that they should try making a great >>>>> short >>>>> presentation of how this is a new opportunity and whar has changed >>>>> since >>>>> we last saw schemes proposed. I do see that there are significant >>>>> advances in >>>>> router forwarding hardware - and I suspect there could be similar >>>>> ideas in >>>>> cisco, etc.Would other vendors (or operators) be interested in >>>>> standardising >>>>> this? I think such a talk could be put to TSVAREA. >>>> I am only at the IETF on Sunday evening and Monday morning. >>>> Unfortunately, I may not be in TSVAREA as I have to go back to the >>>> airport. >>>> >>>> I doubt that other people who are familiar with RTG and OPS area >>>> will show up in TSVAREA (but I may be wrong). It is pointless to >>>> discuss traffic engineering and OAM in router hardware without RTG >>>> area input. In RTG and OPS area, the level of multi-vendor support >>>> of a document can typically be seen in the author list. >>>> >>>> Michael >>>> >>> I suspect it is far too late to use TSVAREA for this at the coming IETF. >>> >>> Actually, to be more clear --- I am **NOT** against some sort of >>> evolution in the network, and figuring out how best transports >>> interact with this. >>> >>> I still have people working on this, I see newer router designs as >>> more inviting, I still see appetite to do this. But like you, I >>> **KNOW** there some big obtsacles and pitfalls. I am wondering how >>> best to bring this sort of work to the IETF and get good perspective >>> on the problems and solutions. After PLUS was short down by Privacy, >>> I'd hate the next new thing to be shot down for the wrong reason. >>> >>> Gorry >>> >>> _______________________________________________ >>> tcpm mailing list >>> tcpm@ietf.org <mailto:tcpm@ietf.org> >>> https://www.ietf.org/mailman/listinfo/tcpm >> >> _______________________________________________ >> tcpm mailing list >> tcpm@ietf.org <mailto:tcpm@ietf.org> >> https://www.ietf.org/mailman/listinfo/tcpm >
- Re: [tcpm] Agenda requests for TSVWG@IETF101 Scharf, Michael (Nokia - DE/Stuttgart)
- Re: [tcpm] Agenda requests for TSVWG@IETF101 Gorry Fairhurst
- Re: [tcpm] [tsvwg] Agenda requests for TSVWG@IETF… Yingzhen Qu
- Re: [tcpm] [tsvwg] Agenda requests for TSVWG@IETF… Scharf, Michael (Nokia - DE/Stuttgart)
- [tcpm] draft-han-tsvwg-cc (was: Re: [tsvwg] Agend… Toerless Eckert
- Re: [tcpm] draft-han-tsvwg-cc (was: Re: [tsvwg] A… Toerless Eckert
- Re: [tcpm] [tsvwg] Agenda requests for TSVWG@IETF… Yingzhen Qu
- Re: [tcpm] [tsvwg] Agenda requests for TSVWG@IETF… Gorry Fairhurst
- Re: [tcpm] [tsvwg] Agenda requests for TSVWG@IETF… Michael Tuexen
- Re: [tcpm] [tsvwg] Agenda requests for TSVWG@IETF… Gorry Fairhurst
- Re: [tcpm] [tsvwg] Agenda requests for TSVWG@IETF… Scharf, Michael (Nokia - DE/Stuttgart)
- Re: [tcpm] [tsvwg] Agenda requests for TSVWG@IETF… Gorry Fairhurst
- Re: [tcpm] [tsvwg] Agenda requests for TSVWG@IETF… Scharf, Michael (Nokia - DE/Stuttgart)
- Re: [tcpm] [tsvwg] Agenda requests for TSVWG@IETF… Michael Welzl
- Re: [tcpm] [tsvwg] Agenda requests for TSVWG@IETF… David Ros
- Re: [tcpm] [tsvwg] Agenda requests for TSVWG@IETF… Gorry Fairhurst
- Re: [tcpm] inband signaling (was: Re: [tsvwg] Age… Toerless Eckert
- Re: [tcpm] [tsvwg] Agenda requests for TSVWG@IETF… Spencer Dawkins at IETF
- Re: [tcpm] [tsvwg] inband signaling (was: Re: Age… Lin Han
- Re: [tcpm] [tsvwg] inband signaling (was: Re: Age… Toerless Eckert
- Re: [tcpm] [tsvwg] inband signaling (was: Re: Age… Lin Han
- Re: [tcpm] [tsvwg] inband signaling (was: Re: Age… Ingemar Johansson S
- Re: [tcpm] [tsvwg] inband signaling (was: Re: Age… Smith, Kevin, (R&D) Vodafone Group
- Re: [tcpm] [tsvwg] Agenda requests for TSVWG@IETF… Yingzhen Qu
- Re: [tcpm] [tsvwg] Agenda requests for TSVWG@IETF… Michael Tuexen
- Re: [tcpm] Agenda requests for TSVWG@IETF101 Pat Thaler
- Re: [tcpm] Agenda requests for TSVWG@IETF101 Yingzhen Qu
- Re: [tcpm] [tsvwg] Agenda requests for TSVWG@IETF… Brian E Carpenter
- Re: [tcpm] [tsvwg] inband signaling (was: Re: Age… Lin Han
- Re: [tcpm] [tsvwg] Agenda requests for TSVWG@IETF… Toerless Eckert
- Re: [tcpm] [tsvwg] inband signaling (was: Re: Age… Ingemar Johansson S
- Re: [tcpm] [tsvwg] inband signaling Brian E Carpenter
- Re: [tcpm] draft-han-tsvwg-cc (was: Re: [tsvwg] A… Scharf, Michael (Nokia - DE/Stuttgart)
- Re: [tcpm] [tsvwg] Agenda requests for TSVWG@IETF… Scharf, Michael (Nokia - DE/Stuttgart)
- Re: [tcpm] [tsvwg] inband signaling (was: Re: Age… Lin Han
- Re: [tcpm] inband signaling (was: Re: [tsvwg] Age… Scharf, Michael (Nokia - DE/Stuttgart)
- Re: [tcpm] [tsvwg] inband signaling (was: Re: Age… Lin Han
- Re: [tcpm] [tsvwg] inband signaling (was: Re: Age… Scharf, Michael (Nokia - DE/Stuttgart)
- Re: [tcpm] [tsvwg] inband signaling (was: Re: Age… Lin Han
- Re: [tcpm] [tsvwg] inband signaling Brian E Carpenter
- Re: [tcpm] [tsvwg] inband signaling (was: Re: Age… Scharf, Michael (Nokia - DE/Stuttgart)
- Re: [tcpm] [tsvwg] inband signaling (was: Re: Age… Tom Herbert
- Re: [tcpm] [tsvwg] inband signaling (was: Re: Age… Toerless Eckert
- Re: [tcpm] [tsvwg] inband signaling (was: Re: Age… Spencer Dawkins at IETF
- Re: [tcpm] [tsvwg] inband signaling (was: Re: Age… Toerless Eckert
- Re: [tcpm] [tsvwg] inband signaling (was: Re: Age… Ingemar Johansson S
- Re: [tcpm] [tsvwg] inband signaling (was: Re: Age… Lin Han