Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: Dave Taht <dave@taht.net>
To: ecn-sane@lists.bufferbloat.net
Subject: Re: [Ecn-sane] [tsvwg] Transport Area Working Group (tsvwg) WG Virtual Meeting: 2020-02-20
Date: Thu, 30 Jan 2020 14:38:40 -0800	[thread overview]
Message-ID: <87wo98y3gv.fsf@taht.net> (raw)
In-Reply-To: <158014090210.26587.12925021630999725769@ietfa.amsl.com> (IESG Secretary's message of "Mon, 27 Jan 2020 08:01:42 -0800")

IESG Secretary <iesg-secretary@ietf.org> writes:

> The Transport Area Working Group (tsvwg) Working Group will hold
> a virtual interim meeting on 2020-02-20 from 10:00 to 12:00 America/New_York.
>
> Agenda:
> 1. Agenda bashing (chairs - 5 min)
> 2. Update on status and near-term plans for the set of L4S drafts (Bob? - 5 min)
>      - Chair request: Think about adding an explicit "Open Issues / Future Work" type of section in the architecture draft to consolidate a list of things still being worked in the context of TCP Prague and/or caveats and unknowns people should be aware of when deploying this Experimental work.
> 3. Update on L4S & TCP Prague implementation, test, evaluation (Greg/Bob/Koen? - 15 min)
> 4. L4S Issues List Discussion (goal is to see if we can agree on what more needs to be done on each issue to suffice for Experimental/Informational RFCs):
>     4.1 Discuss status on (Bob - ~30 min):
>           #16 on classic ECN interaction
>           #21 CE codepoint semantics (closely related to #16)
>           #20 ECT(1) codepoint usage
>     4.2  Discuss plans forward to address (Bob - ~15 min):
>            #26 on admission control
>            #27 on terminology
>            #22 on deployment feasibility
>             #24 on evaluation & testing results
>      4.3 (We will try to handle the issues below by mailing list prior to the meeting)
>            If needed, discuss close-out of (~15 min):
>            #25 on IPR
>            #18 on loss detection in time-units
>            #23 on implementation status
>            #19 on the single codepoint
>            #17 on FQ interaction  
> 5. SCE Update (Morton/Heist/etc. - ~30 min)
>
>
> Information about remote participation:
> Remote participation information will be obtained at the time of approval.  Plan to use IETF WebEx.

           reply	other threads:[~2020-01-30 22:38 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <158014090210.26587.12925021630999725769@ietfa.amsl.com>]

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/ecn-sane.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=87wo98y3gv.fsf@taht.net \
    --to=dave@taht.net \
    --cc=ecn-sane@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