General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Dave Täht" <dave@taht.net>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] BoF @IETF-95 'Ultra-Low Queuing Delay for All' (L4S, DualQ Coupled AQM, TCP Prague)
Date: Wed, 6 Apr 2016 19:26:05 -0700	[thread overview]
Message-ID: <5705C53D.4030002@taht.net> (raw)
In-Reply-To: <57059F43.1050406@bobbriscoe.net>

[-- Attachment #1: Type: text/plain, Size: 5318 bytes --]

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
>> <spencerdawkins.ietf@gmail.com> wrote:
>>
>>     Just to try to be helpful ...
>>
>>     On Mon, Feb 22, 2016 at 2:54 AM, Bob Briscoe
>>     <ietf@bobbriscoe.net> wrote:
>>
>>         John,
>>
>>         On 19/02/16 18:23, John Leslie wrote:
>>
>>             Bob Briscoe <ietf@bobbriscoe.net
>>             <mailto:ietf@bobbriscoe.net>> 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 <<mailto:john@jlc.net>john@jlc.net>
>>
>>             _______________________________________________
>>             tcpPrague mailing list
>>             tcpPrague@ietf.org <mailto:tcpPrague@ietf.org>
>>             https://www.ietf.org/mailman/listinfo/tcpprague
>>
>>
>>         -- 
>>         ________________________________________________________________
>>         Bob Briscoe                               http://bobbriscoe.net/
>>
>>
>>
>>     _______________________________________________
>>     tcpm mailing list
>>     tcpm@ietf.org <mailto: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/



[-- Attachment #2: Attached Message Part --]
[-- Type: text/plain, Size: 121 bytes --]

_______________________________________________
aqm mailing list
aqm@ietf.org
https://www.ietf.org/mailman/listinfo/aqm


           reply	other threads:[~2016-04-07  2:21 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <57059F43.1050406@bobbriscoe.net>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5705C53D.4030002@taht.net \
    --to=dave@taht.net \
    --cc=bloat@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox