WebTransport Working Group - Activity in 2024
No matches.
GitHub
w3c/webtransport
-
3 issues opened.
-
Handshake is not defined in terms of Fetch w3c/webtransport#625, by @annevk.
-
Consider removing wt.datagrams.writable w3c/webtransport#624, by @jan-ivar.
-
Consider removing serverCertificateHashes w3c/webtransport#623, by @annevk.
-
-
5 issues received 36 new comments.
-
Consider removing serverCertificateHashes w3c/webtransport#623 (17 comments by @annevk, @jan-ivar, @martenrichter, @martinthomson, @mozfreddyb, @vasilvv, @youennf)
-
Do we want to allow web developers to add headers of the CONNECT request? w3c/webtransport#263 (10 comments by @annevk, @jan-ivar, @vasilvv, @wilaw)
-
Consider removing wt.datagrams.writable w3c/webtransport#624 (4 comments by @jan-ivar, @martenrichter, @vasilvv)
-
WPT tests are needed for serverCertificateHash feature w3c/webtransport#589 (3 comments by @javifernandez, @martenrichter)
-
-
1 pull request closed.
-
Add sendGroup.weight and datagramsWritable.weight w3c/webtransport#621.
-
-
3 pull requests received 4 new comments.
-
Rename "Data Recvd" to "all data committed" w3c/webtransport#580 (2 comments by @jan-ivar, @nidhijaju)
-
GitHub
w3c/webtransport
-
1 issue opened.
-
Test suite for user agents w3c/webtransport#622, by @martenrichter.
-
-
2 issues received 5 new comments.
-
Relative prioritization of streams and datagrams w3c/webtransport#610 (3 comments by @jan-ivar, @wilaw)
-
Do we want to allow web developers to add headers of the CONNECT request? w3c/webtransport#263 (2 comments by @annevk, @jan-ivar)
-
-
1 pull request received 1 new comment.
GitHub
w3c/webtransport
-
2 issues closed.
-
When should a client initiated unidirectional stream be available on the server side? w3c/webtransport#618.
-
Quality of a bandwidth estimate w3c/webtransport#559.
-
-
7 issues received 19 new comments.
-
Relative prioritization of streams and datagrams w3c/webtransport#610 (6 comments by @afrind, @jan-ivar, @vasilvv)
-
When should a client initiated unidirectional stream be available on the server side? w3c/webtransport#618 (4 comments by @jan-ivar, @martenrichter, @martinthomson)
-
expose a TLS Keying Material Exporter / unique value for the TLS session w3c/webtransport#411 (3 comments by @jan-ivar)
-
Do we want to allow web developers to add headers of the CONNECT request? w3c/webtransport#263 (1 comment by @FZambia)
-
w3c/webtransport#59 (1 comment by @jan-ivar)
-
-
3 pull requests opened.
-
Add sendGroup.weight and datagramsWritable.weight w3c/webtransport#621, by @jan-ivar.
-
Add datagrams.createWritable() w3c/webtransport#620, by @jan-ivar.
-
Add notes on receiver-side stream availability w3c/webtransport#619, by @wilaw.
-
-
3 pull requests merged.
-
Add notes on receiver-side stream availability w3c/webtransport#619.
-
Add stats.atSendCapacity w3c/webtransport#603.
-
Remove some junk from a heading w3c/webtransport#617.
-
-
3 pull requests received 6 new comments.
Lifecycle
-
1 charter started.
-
Chartered until 31 December 2025.
-
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
Jason Thomas (Datadog) joined.
-
-
1 participant left.
-
Dragana Damjanovic (Mozilla Foundation) left.
-
GitHub
w3c/webtransport
-
4 issues opened.
-
When should a client initiated unidirectional stream be available on the server side? w3c/webtransport#618, by @martenrichter.
-
Reference overview doc instead of HTTP3 doc in two places w3c/webtransport#616, by @jan-ivar.
-
Expose MTU via stats w3c/webtransport#615, by @vasilvv.
-
Specify keep-alive and idle timeouts w3c/webtransport#614, by @MOZGIII.
-
-
2 issues closed.
-
Reconsider whether we need sub-protocol negotiation w3c/webtransport#536.
-
Client initiated drain w3c/webtransport#436.
-
-
8 issues received 26 new comments.
-
Detect support for waitUntilAvailable=true? w3c/webtransport#613 (9 comments by @jan-ivar, @martenrichter, @vasilvv)
-
Do we want to allow web developers to add headers of the CONNECT request? w3c/webtransport#263 (5 comments by @annevk, @MarcoPolo, @mnot, @ricea, @vasilvv)
-
Relative prioritization of streams and datagrams w3c/webtransport#610 (4 comments by @afrind, @jan-ivar, @martinthomson)
-
When should a client initiated unidirectional stream be available on the server side? w3c/webtransport#618 (2 comments by @martenrichter, @martinthomson)
-
expose a TLS Keying Material Exporter / unique value for the TLS session w3c/webtransport#411 (2 comments by @vasilvv, @wilaw)
-
Reference overview doc instead of HTTP3 doc in two places w3c/webtransport#616 (1 comment by @ekinnear)
-
-
1 pull request opened.
-
Remove some junk from a heading w3c/webtransport#617, by @martinthomson.
-
-
1 pull request merged.
-
Add protocols constructor argument to WebTransport + protocol read arg w3c/webtransport#598.
-
-
2 pull requests received 20 new comments.
-
Add protocols constructor argument to WebTransport + protocol read arg w3c/webtransport#598 (15 comments by @jan-ivar, @nidhijaju)
-
GitHub
w3c/webtransport
-
1 issue opened.
-
Detect support for waitUntilAvailable=true? w3c/webtransport#613, by @martenrichter.
-
-
2 issues closed.
-
API handling of redirects w3c/webtransport#499.
-
Detect support for waitUntilAvailable=true? w3c/webtransport#613.
-
-
2 issues received 10 new comments.
-
Relative prioritization of streams and datagrams w3c/webtransport#610 (7 comments by @afrind, @jan-ivar, @vasilvv, @wilaw)
-
Detect support for waitUntilAvailable=true? w3c/webtransport#613 (3 comments by @jan-ivar, @martenrichter)
-
-
1 pull request merged.
-
Redirection treated as a network error w3c/webtransport#612.
-
-
2 pull requests received 2 new comments.
-
Add protocols constructor argument to WebTransport + protocol read arg w3c/webtransport#598 (1 comment by @wilaw)
Participants
-
2 participants joined.
-
Hu Liu (Jiangsu TPBlock Technology Co., Ltd. （江苏第三极区块链科技有限公司）) joined.
-
Jasper Hugo (Datadog) joined.
-
-
2 organizations joined.
-
Jiangsu TPBlock Technology Co., Ltd. （江苏第三极区块链科技有限公司） joined.
-
Datadog joined.
-
GitHub
w3c/webtransport
-
3 issues opened.
-
Relative prioritization of streams and datagrams w3c/webtransport#610, by @afrind.
-
What are the initial values of the RTT stats? w3c/webtransport#608, by @jan-ivar.
-
Clarify stats members are required w3c/webtransport#607, by @jan-ivar.
-
-
3 issues closed.
-
Connection sharing/pooling w3c/webtransport#128.
-
Clarify stats members are required w3c/webtransport#607.
-
What are the initial values of the RTT stats? w3c/webtransport#608.
-
-
7 issues received 13 new comments.
-
expose a TLS Keying Material Exporter / unique value for the TLS session w3c/webtransport#411 (3 comments by @jan-ivar, @vasilvv)
-
What are the initial values of the RTT stats? w3c/webtransport#608 (2 comments by @jan-ivar, @vasilvv)
-
w3c/webtransport#59 (1 comment by @jan-ivar)
-
w3c/webtransport#128 (1 comment by @jan-ivar)
-
-
3 pull requests opened.
-
Redirection treated as a network error w3c/webtransport#612, by @wilaw.
-
Update WebTransport Echo in samples directory with HEVC, display glass to glass delay w3c/webtransport#611, by @aboba.
-
Add required or =0 in WebIDL to document stats SHALL be present (except RTT ones) w3c/webtransport#609, by @jan-ivar.
-
-
2 pull requests merged.
-
Update WebTransport Echo in samples directory with HEVC, display glass to glass delay w3c/webtransport#611.
-
Add required or =0 in WebIDL to document stats SHALL be present (except RTT ones) w3c/webtransport#609.
-
-
1 pull request closed.
-
Add support for client initiated drain w3c/webtransport#606.
-
-
4 pull requests received 14 new comments.
-
Add protocols constructor argument to WebTransport + protocol read arg w3c/webtransport#598 (2 comments by @jan-ivar)
Lifecycle
-
1 charter extension.
-
Charter extended until 31 August 2024.
-
Participants
-
1 participant joined.
-
Luca Barbato (Luminem) joined.
-
-
1 organization joined.
-
Luminem joined.
-
GitHub
w3c/webtransport
-
2 issues closed.
-
Should the constructor take http3Only or something more transport agnostic? w3c/webtransport#561.
-
Relative send priority between datagrams and streams w3c/webtransport#451.
-
-
4 issues received 9 new comments.
-
Client initiated drain w3c/webtransport#436 (5 comments by @aboba, @ekinnear, @jan-ivar, @martinthomson)
-
w3c/webtransport#59 (2 comments by @jan-ivar)
-
Do we want to allow web developers to add headers of the CONNECT request? w3c/webtransport#263 (1 comment by @matthewp)
-
expose a TLS Keying Material Exporter / unique value for the TLS session w3c/webtransport#411 (1 comment by @jan-ivar)
-
-
3 pull requests opened.
-
Add support for client initiated drain w3c/webtransport#606, by @nidhijaju.
-
s/http3Only/requireUnreliable/ w3c/webtransport#605, by @jan-ivar.
-
Give datagrams priority over streams but don't starve them w3c/webtransport#604, by @jan-ivar.
-
-
2 pull requests merged.
-
s/http3Only/requireUnreliable/ w3c/webtransport#605.
-
Give datagrams priority over streams but don't starve them w3c/webtransport#604.
-
-
3 pull requests received 4 new comments.
-
Add protocols constructor argument to WebTransport + protocol read arg w3c/webtransport#598 (2 comments by @jan-ivar, @wilaw)
-
Give datagrams priority over streams but don't starve them w3c/webtransport#604 (1 comment by @jan-ivar)
-
TR publications
-
1 document published.
-
WebTransport published as a Working Draft. History of WebTransport
-
GitHub
w3c/webtransport
-
1 issue opened.
-
wt.ready and wt.closed trigger unhandled rejections w3c/webtransport#601, by @jan-ivar.
-
-
5 issues closed.
-
wt.ready and wt.closed trigger unhandled rejections w3c/webtransport#601.
-
Spec should define how the feature interacts with blocking tools (filterlists etc.) w3c/webtransport#96.
-
Listening to event by event name w3c/webtransport#597.
-
Keep connection on tab switch w3c/webtransport#600.
-
Expose [[State]] internal slot w3c/webtransport#539.
-
-
8 issues received 19 new comments.
-
Expose [[State]] internal slot w3c/webtransport#539 (7 comments by @achingbrain, @jan-ivar, @saschanaz, @wilaw)
-
expose a TLS Keying Material Exporter / unique value for the TLS session w3c/webtransport#411 (1 comment by @wilaw)
-
Should the constructor take http3Only or something more transport agnostic? w3c/webtransport#561 (1 comment by @annevk)
-
-
2 pull requests opened.
-
Add stats.atSendCapacity w3c/webtransport#603, by @jan-ivar.
-
Set [[PromiseIsHandled]] on wt.ready and wt.closed. w3c/webtransport#602, by @jan-ivar.
-
-
1 pull request merged.
-
Set [[PromiseIsHandled]] on wt.ready and wt.closed. w3c/webtransport#602.
-
-
1 pull request received 1 new comment.
GitHub
w3c/webtransport
-
1 issue opened.
-
Keep connection on tab switch w3c/webtransport#600, by @nuzzles.
-
-
1 issue closed.
-
Relative URL in WebTransport constructor w3c/webtransport#596.
-
-
1 issue reopened.
-
Should the constructor take http3Only or something more transport agnostic? w3c/webtransport#561, by @jan-ivar.
-
-
8 issues received 24 new comments.
-
Keep connection on tab switch w3c/webtransport#600 (8 comments by @jan-ivar, @martinthomson, @MOZGIII, @nuzzles, @ricea, @wilaw)
-
Listening to event by event name w3c/webtransport#597 (5 comments by @jan-ivar, @LPardue, @MuratovBektur)
-
Relative send priority between datagrams and streams w3c/webtransport#451 (3 comments by @jan-ivar, @wilaw)
-
w3c/webtransport#59 (1 comment by @jan-ivar)
-
Should the constructor take http3Only or something more transport agnostic? w3c/webtransport#561 (1 comment by @annevk)
-
-
2 pull requests opened.
-
Support relative URLs. w3c/webtransport#599, by @jan-ivar.
-
Add protocols constructor argument to WebTransport + protocol read arg w3c/webtransport#598, by @jan-ivar.
-
-
1 pull request merged.
-
Support relative URLs. w3c/webtransport#599.
-
-
1 pull request received 10 new comments.
-
Add protocols constructor argument to WebTransport + protocol read arg w3c/webtransport#598 (10 comments by @jan-ivar, @martinthomson, @nidhijaju)
-
GitHub
w3c/webtransport
-
2 issues opened.
-
Listening to event by event name w3c/webtransport#597, by @MuratovBektur.
-
Relative URL in WebTransport constructor w3c/webtransport#596, by @devsnek.
-
-
2 issues closed.
-
WebTransport API and ManagedMediaSource API w3c/webtransport#522.
-
Retransmissions and send order w3c/webtransport#523.
-
-
7 issues received 9 new comments.
-
Should the constructor take http3Only or something more transport agnostic? w3c/webtransport#561 (1 comment by @jan-ivar)
-
WPT tests are needed for serverCertificateHash feature w3c/webtransport#589 (1 comment by @jan-ivar)
-
expose a TLS Keying Material Exporter / unique value for the TLS session w3c/webtransport#411 (1 comment by @wilaw)
-
1 pull request opened.
-
Add note about retransmissions and send order w3c/webtransport#595, by @nidhijaju.
-
-
2 pull requests merged.
-
Add note about retransmissions and send order w3c/webtransport#595.
-
Update normative RFC references w3c/webtransport#594.
-
-
1 pull request received 4 new comments.
-
Add note about retransmissions and send order w3c/webtransport#595 (4 comments by @jan-ivar, @vasilvv)
-
GitHub
w3c/webtransport
-
2 issues opened.
-
Working with servers behind a NAT or on a local network (aka "p2p") w3c/webtransport#590, by @pthatcher.
-
WPT tests are needed for serverCertificateHash feature w3c/webtransport#589, by @javifernandez.
-
-
6 issues closed.
-
Provide flow control minimums from the browser side w3c/webtransport#541.
-
Confirm behaviour of server certificates. w3c/webtransport#508.
-
Define datagram w3c/webtransport#542.
-
Allow more aggressive garbage collection w3c/webtransport#560.
-
Allow users to find how prioritization is done easily? w3c/webtransport#532.
-
-
12 issues received 30 new comments.
-
WebTransport API and ManagedMediaSource API w3c/webtransport#522 (7 comments by @aboba, @jan-ivar, @jyavenard, @wilaw)
-
Should the constructor take http3Only or something more transport agnostic? w3c/webtransport#561 (3 comments by @aboba, @jan-ivar)
-
w3c/webtransport#59 (2 comments by @jan-ivar)
-
Working with servers behind a NAT or on a local network (aka "p2p") w3c/webtransport#590 (2 comments by @jan-ivar)
-
expose a TLS Keying Material Exporter / unique value for the TLS session w3c/webtransport#411 (2 comments by @hlandau, @jan-ivar)
-
WPT tests are needed for serverCertificateHash feature w3c/webtransport#589 (1 comment by @javifernandez)
-
4 pull requests opened.
-
Update normative RFC references w3c/webtransport#594, by @wilaw.
-
Default to allow the server to create >= 100 uni and >=100 bidi streams. w3c/webtransport#593, by @jan-ivar.
-
Add example for server certificate hashes w3c/webtransport#592, by @nidhijaju.
-
Add spec reference for datagrams definition w3c/webtransport#591, by @nidhijaju.
-
-
5 pull requests merged.
-
Default to allow the server to create >= 100 uni and >=100 bidi streams. w3c/webtransport#593.
-
Add example for server certificate hashes w3c/webtransport#592.
-
Add anticipatedConcurrentIncoming[Bi/Uni]directionalStreams attributes & constructor arg w3c/webtransport#574.
-
Add spec reference for datagrams definition w3c/webtransport#591.
-
Add more conditions for garbage collection w3c/webtransport#587.
-
-
3 pull requests received 14 new comments.
-
Add more conditions for garbage collection w3c/webtransport#587 (9 comments by @jan-ivar, @nidhijaju, @saschanaz)
-
Default to allow the server to create >= 100 uni and >=100 bidi streams. w3c/webtransport#593 (4 comments by @jan-ivar)
-
Lifecycle
-
1 charter extension.
-
Charter extended until 31 May 2024.
-
Participants
-
1 participant joined.
-
Javier Fernandez (Igalia) joined.
-
-
1 organization joined.
-
Igalia joined.
-
GitHub
w3c/webtransport
-
3 issues opened.
-
What are "first-strong heuristics"? w3c/webtransport#583, by @martinthomson.
-
Remove dependency on "Data Recvd" state w3c/webtransport#581, by @martinthomson.
-
serverCertificateHashes really only allow if not pooled? w3c/webtransport#579, by @martenrichter.
-
-
11 issues closed.
-
How should the WebTransport constructor handles timeouts? w3c/webtransport#578.
-
Possible new wording for the implementation / testing criteria w3c/webtransport#444.
-
Zero copy support via BYOB (add an example) w3c/webtransport#131.
-
serverCertificateHashes really only allow if not pooled? w3c/webtransport#579.
-
What are "first-strong heuristics"? w3c/webtransport#583.
-
Should all fields in WebTransportConnectionStats be nullable? w3c/webtransport#567.
-
Add expiredIncoming to stats w3c/webtransport#553.
-
Remove dependency on "Data Recvd" state w3c/webtransport#581.
-
When flow control is blocked w3c/webtransport#426.
-
Does sendRate drop if I stop sending? w3c/webtransport#476.
-
Block source (incoming) ports w3c/webtransport#376.
-
-
1 issue reopened.
-
expose a TLS Keying Material Exporter / unique value for the TLS session w3c/webtransport#411, by @vasilvv.
-
-
14 issues received 39 new comments.
-
serverCertificateHashes really only allow if not pooled? w3c/webtransport#579 (10 comments by @jan-ivar, @martenrichter, @valenting, @vasilvv)
-
How should the WebTransport constructor handles timeouts? w3c/webtransport#578 (4 comments by @jan-ivar, @martenrichter)
-
Remove dependency on "Data Recvd" state w3c/webtransport#581 (3 comments by @martenrichter, @martinthomson)
-
Provide flow control minimums from the browser side w3c/webtransport#541 (3 comments by @jan-ivar, @vasilvv)
-
Node.js support for WebTransport w3c/webtransport#511 (3 comments by @endel, @jasnell, @martenrichter)
-
Should the constructor take http3Only or something more transport agnostic? w3c/webtransport#561 (2 comments by @ekinnear, @jan-ivar)
-
expose a TLS Keying Material Exporter / unique value for the TLS session w3c/webtransport#411 (2 comments by @sukunrt, @wilaw)
-
Possible new wording for the implementation / testing criteria w3c/webtransport#444 (1 comment by @wilaw)
-
-
7 pull requests opened.
-
Add reference for "first-strong" w3c/webtransport#588, by @nidhijaju.
-
Add more conditions for garbage collection w3c/webtransport#587, by @nidhijaju.
-
Add note about unavailability of stats w3c/webtransport#586, by @nidhijaju.
-
Add expiredIncoming w3c/webtransport#585, by @nidhijaju.
-
Add examples for reading with BYOB readers w3c/webtransport#584, by @nidhijaju.
-
Remove dependency on Data Recvd signals in cleanup w3c/webtransport#582, by @martinthomson.
-
Rename "Data Recvd" to "all data committed" w3c/webtransport#580, by @martinthomson.
-
-
6 pull requests merged.
-
Add examples for reading with BYOB readers w3c/webtransport#584.
-
Add reference for "first-strong" w3c/webtransport#588.
-
Add note about unavailability of stats w3c/webtransport#586.
-
Add expiredIncoming w3c/webtransport#585.
-
Remove dependency on Data Recvd signals in cleanup w3c/webtransport#582.
-
Add writer.atomicWrite() method. w3c/webtransport#551.
-
-
5 pull requests received 32 new comments.
-
Add writer.atomicWrite() method. w3c/webtransport#551 (15 comments by @jan-ivar, @martinthomson, @nidhijaju)
-
Add anticipatedConcurrentIncoming[Bi/Uni]directionalStreams attributes & constructor arg w3c/webtransport#574 (12 comments by @jan-ivar, @wilaw)
-
Rename "Data Recvd" to "all data committed" w3c/webtransport#580 (2 comments by @jan-ivar, @vasilvv)
-
Remove dependency on Data Recvd signals in cleanup w3c/webtransport#582 (2 comments by @jan-ivar, @martinthomson)
-