From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.taht.net (mail.taht.net [176.58.107.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id D36943B337 for ; Wed, 6 Apr 2016 22:21:06 -0400 (EDT) Received: from dair-1494.gw.taht.net (c-73-252-201-217.hsd1.ca.comcast.net [73.252.201.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.taht.net (Postfix) with ESMTPSA id 4C4112130D for ; Thu, 7 Apr 2016 02:21:05 +0000 (UTC) References: <57059F43.1050406@bobbriscoe.net> To: bloat@lists.bufferbloat.net From: =?UTF-8?Q?Dave_T=c3=a4ht?= X-Forwarded-Message-Id: <57059F43.1050406@bobbriscoe.net> Message-ID: <5705C53D.4030002@taht.net> Date: Wed, 6 Apr 2016 19:26:05 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 In-Reply-To: <57059F43.1050406@bobbriscoe.net> Content-Type: multipart/mixed; boundary="------------000803070407070605000400" Subject: [Bloat] BoF @IETF-95 'Ultra-Low Queuing Delay for All' (L4S, DualQ Coupled AQM, TCP Prague) X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Apr 2016 02:21:07 -0000 This is a multi-part message in MIME format. --------------000803070407070605000400 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit There are devils in the details, probably. -------- Forwarded Message -------- Folks, Reminder, agenda & supporting materials below for the Bar BoF on L4S / DualQ Coupled AQM / TCP Prague *Event details** *Date/time: 09:00 - 10:00 local time (ART = 12-13:00 UTC) Thu 7 Apr 2016 Room: Quebracho B *Supporting materials / background:** *https://riteproject.eu/dctth/ To use the time effectively, it will be assumed that people have a working knowledge of what the technology is, and a rough idea of how it works. For those wanting an introduction, a useful 2-pager in the IETF Journal is linked from the above, plus videos of the demos etc.b Or chat with us afterwards *Proposed Agenda:** ***09:00 * Note Well, Agenda Bashing [Bob] * Introduction/Background (very brief) [Bob] * Clarification Questions 09:15 * Status updates [Koen to lead], e.g.: - what people are doing on parts of the problem: - planned work - evaluation work - interest in implementing - willingness to review 09:40 * Build a standardisation roadmap [Bob to lead] * Build a BoF for the Berlin time-frame - should it be non-WG forming? - volunteers to help with organisation / writing problem statement, etc. - which mailing list? - what name? * Discussion / Q&A 09:55 end Most time will be allowed for people to talk from the floor. Cheers Bob & Koen On 05/04/16 13:02, Bob Briscoe wrote: > Folks, > > We have a time and room for this Bar BoF: > Date/time: 09:00 - 10:00 ART (= 12-13:00 UTC) Thu 7 Apr 2016 > Room: Quebracho B > > We have the regular IETF remote attendance facilities in that room. > The room is not being used for the following session, so we don't have > to vacate early. > > Sorry for delay setting this up. My fault. > I've bcc'd a few people who have been asking about this specifically. > > > Bob > > On 30/03/16 21:13, Aaron Falk wrote: >> Did this get scheduled? >> >> --aaron >> >> On Mon, Feb 22, 2016 at 12:21 PM, Spencer Dawkins at IETF >> wrote: >> >> Just to try to be helpful ... >> >> On Mon, Feb 22, 2016 at 2:54 AM, Bob Briscoe >> wrote: >> >> John, >> >> On 19/02/16 18:23, John Leslie wrote: >> >> Bob Briscoe > > wrote: >> >> I'm cross-posting 'cos this impacts 3 IETF WGs and >> interested implementers. >> >> We would like to propose a Bar BoF at the Buenos >> Aires IETF, about L4S, >> DualQ and solutions to the TCP Prague Requirements. >> >> This feels like it belongs as a non-WG-forming formal >> BoF. >> >> It describes work spanning at least three WGs; and >> could benefit from >> formal scheduling to avoid conflicts with those WGs and >> others. >> >> OTOH, it really isn't to the point where a WG charter >> can reasonably >> be drafted. First we must decide whether the work _can_ >> be split among >> existing WGs. >> >> However this may turn out, I wish to participate >> remotely. >> >> OK, we'll see if the secretariat can help us with that. >> >> >> I believe that happens at http://www.ietf.org/meeting/amreq.html. >> If you put "TSV" in as "type of meeting", your happy TSV ADs >> would see the request. >> >> Thanks, >> >> Spencer >> >> >> Unfortunately we ran out of time for the formal BoF deadline >> on Friday. >> >> >> Bob >> >> >> -- >> John Leslie <john@jlc.net> >> >> _______________________________________________ >> tcpPrague mailing list >> tcpPrague@ietf.org >> https://www.ietf.org/mailman/listinfo/tcpprague >> >> >> -- >> ________________________________________________________________ >> Bob Briscoe http://bobbriscoe.net/ >> >> >> >> _______________________________________________ >> tcpm mailing list >> tcpm@ietf.org >> https://www.ietf.org/mailman/listinfo/tcpm >> >> >> >> >> _______________________________________________ >> aqm mailing list >> aqm@ietf.org >> https://www.ietf.org/mailman/listinfo/aqm > > -- > ________________________________________________________________ > Bob Briscoe http://bobbriscoe.net/ > > -- > ________________________________________________________________ > Bob Briscoe http://bobbriscoe.net/ > -- > ________________________________________________________________ > Bob Briscoe http://bobbriscoe.net/ > -- > ________________________________________________________________ > Bob Briscoe http://bobbriscoe.net/ > -- > ________________________________________________________________ > Bob Briscoe http://bobbriscoe.net/ > -- > ________________________________________________________________ > Bob Briscoe http://bobbriscoe.net/ --------------000803070407070605000400 Content-Type: text/plain; charset=UTF-8; name="Attached Message Part" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="Attached Message Part" _______________________________________________ aqm mailing list aqm@ietf.org https://www.ietf.org/mailman/listinfo/aqm --------------000803070407070605000400--