WebTransport (webtrans) Working Group

CHAIRS: Bernard Aboba
David Schinazi

IETF 119 Agenda
Date: Monday, March 18, 2024
Session: III
Time: 15:30 - 17:00 Brisbane time
Room: M1
Notes: Mo Zanaty

Meeting link: https://meetings.conf.meetecho.com/ietf119/?session=31926

Notes: https://notes.ietf.org/notes-ietf-119-webtrans
Slides:
https://docs.google.com/presentation/d/1zMBF7hpp_taOxF43R4a3a5C5zjTY3m2_xqKOQTk9mmI


  1. Preliminaries (Chairs, 15 min)
    Note Well, Note Takers, Agenda Bashing, Draft status

Contact Marten Seemann to add your implementation to the InteropRunner.

  1. W3C WebTransport Update, Will Law (15 minutes)
    https://w3c.github.io/webtransport/

8 issues open for the Candidate Recommendation milestone.
WebTransport support now in Chrome, Edge, Firefox, Opera. Progress on
Safari.
Added support for TLS Keying Material Exporter
Issues needing IETF feedback are still open but being worked with owners
assigned.

  1. WebTransport over HTTP/2, Eric Kinnear (25 minutes)
    https://datatracker.ietf.org/doc/html/draft-ietf-webtrans-http2

Main update is to starting a WebTransport session.

  1. WebTransport over HTTP/3, Victor Vasiliev (25 minutes)
    https://datatracker.ietf.org/doc/html/draft-ietf-webtrans-http3

Reliable Reset: Please review draft-ietf-quic-reliable-stream-reset
before it's final.

Key Exporters: No objection to merging PR #148.

Flow Control: Marten Seemann gave the problem overview.
Victor Vasiliev said this is not a WebTransport-specifc issue, so don't
block on this issue, handle it incrementally.
Luke Curley said this may not matter in practice.
Martin Thompson +1 to Victor, HOLB is not a problem.
Eric Kennear +1 to Martin, big lift to go from no flow control to
optimal flow control, so don't bother.
Alan Frindell suggests implementation experience to guide this.
Chairs: Can everyone live with this flow control proposal even with a
HOLB problem? Specifically Marten, who just shrugged. Consensus to move
forward with current proposal.

  1. Wrap up and Summary, Chairs & ADs (10 minutes)

Chairs: Need editors to finalize PRs for open issues. Don't need an
interim for now, if editors address open issues with PRs before IETF
120.