WebTransport Working Group - Activity in 2025
No matches.
TR publications
-
2 documents published.
-
WebTransport published twice as a Working Draft. History of WebTransport
-
Participants
-
1 participant joined.
-
Le Zhang (ByteDance) joined.
-
GitHub
w3c/webtransport
-
2 issues opened.
-
More flexible send orders w3c/webtransport#712, by @vasilvv.
-
Update Charter w3c/webtransport#710, by @wilaw.
-
-
6 issues closed.
-
Is DatagramsReadableMode necessary and should it use byob as its default value? w3c/webtransport#706.
-
More stats w3c/webtransport#674.
-
createWritable should throw if the send group is from the wrong Transport object w3c/webtransport#700.
-
Tighten up serverCertificateHashes API for fetch w3c/webtransport#705.
-
Specify what to do with a certificate chain w3c/webtransport#692.
-
getStats() unclear w3c/webtransport#691.
-
-
3 issues received 13 new comments.
-
More flexible send orders w3c/webtransport#712 (9 comments by @afrind, @jan-ivar, @martinduke, @martinthomson, @vasilvv, @wilaw)
-
Is DatagramsReadableMode necessary and should it use byob as its default value? w3c/webtransport#706 (3 comments by @jan-ivar, @martinthomson)
-
-
5 pull requests opened.
-
Add headers constructor option and readonly response wt.responseHeaders attribute w3c/webtransport#713, by @jan-ivar.
-
Rely on request's WebTransport-hash list for CSP & cert verification w3c/webtransport#711, by @jan-ivar.
-
s/datagramsReadableMode/datagramsReadableType/ and beef up note w3c/webtransport#709, by @jan-ivar.
-
throw InvalidStateError on invalid sendGroups w3c/webtransport#708, by @jan-ivar.
-
Make WebTransportHash members required w3c/webtransport#707, by @jan-ivar.
-
-
8 pull requests merged.
-
s/datagramsReadableMode/datagramsReadableType/ and beef up note w3c/webtransport#709.
-
Remove framing overhead from bytesSent. Add bytesAcknowledged and bytesSentOverhead w3c/webtransport#702.
-
throw InvalidStateError on invalid sendGroups w3c/webtransport#708.
-
Make WebTransportHash members required w3c/webtransport#707.
-
Export two defs: "custom certificate requirements" and "verify a certificate hash" w3c/webtransport#704.
-
Update terminology for certificate verification process w3c/webtransport#703.
-
Describe the CONNECT request using fetch. w3c/webtransport#701.
-
Revert #609 and add more detailed getStats algorithms. w3c/webtransport#699.
-
-
3 pull requests received 17 new comments.
-
Add headers constructor option and readonly response wt.responseHeaders attribute w3c/webtransport#713 (11 comments by @annevk, @jan-ivar, @wilaw)
-
Make WebTransportHash members required w3c/webtransport#707 (4 comments by @ekinnear, @martinthomson)
-
Remove framing overhead from bytesSent. Add bytesAcknowledged and bytesSentOverhead w3c/webtransport#702 (2 comments by @jan-ivar)
-
TR publications
-
1 document published.
-
WebTransport published as a Working Draft. History of WebTransport
-
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
dheeraj pannala (Microsoft Corporation) joined.
-
GitHub
w3c/webtransport
-
3 issues opened.
-
Is DatagramsReadableMode necessary and should it use byob as its default value? w3c/webtransport#706, by @youennf.
-
Tighten up serverCertificateHashes API for fetch w3c/webtransport#705, by @jan-ivar.
-
createWritable should throw if the send group is from the wrong Transport object w3c/webtransport#700, by @achristensen07.
-
-
1 issue closed.
-
Handshake is not defined in terms of Fetch w3c/webtransport#625.
-
-
3 issues received 3 new comments.
-
createWritable should throw if the send group is from the wrong Transport object w3c/webtransport#700 (1 comment by @jan-ivar)
-
5 pull requests opened.
-
Export two defs: "custom certificate requirements" and "verify a certificate hash" w3c/webtransport#704, by @jan-ivar.
-
Update terminology for certificate verification process w3c/webtransport#703, by @wilaw.
-
Remove framing overhead from bytesSent. Add bytesAcknowledged and bytesSentOverhead w3c/webtransport#702, by @jan-ivar.
-
Describe the CONNECT request using fetch. w3c/webtransport#701, by @jan-ivar.
-
Revert #609 and add more detailed getStats algorithms. w3c/webtransport#699, by @jan-ivar.
-
-
1 pull request merged.
-
Integrate with fetch w3c/webtransport#697.
-
-
1 pull request closed.
-
Add connection stats bytesAcknowledged & applicationBytes(Sent|Acknowledged) w3c/webtransport#689.
-
-
4 pull requests received 25 new comments.
-
Describe the CONNECT request using fetch. w3c/webtransport#701 (9 comments by @annevk, @jan-ivar, @martinthomson)
-
Revert #609 and add more detailed getStats algorithms. w3c/webtransport#699 (5 comments by @annevk, @jan-ivar, @vasilvv)
-
Add connection stats bytesAcknowledged & applicationBytes(Sent|Acknowledged) w3c/webtransport#689 (2 comments by @jan-ivar, @nidhijaju)
-
TR publications
-
2 documents published.
-
WebTransport published twice as a Working Draft. History of WebTransport
-
GitHub
w3c/webtransport
-
4 issues opened.
-
Update explainer to cover recent features w3c/webtransport#694, by @jan-ivar.
-
Add protocol negotiation to explainer w3c/webtransport#693, by @jan-ivar.
-
Specify what to do with a certificate chain w3c/webtransport#692, by @achristensen07.
-
getStats() unclear w3c/webtransport#691, by @annevk.
-
-
3 issues closed.
-
Keying exporter algorithm should reference overview doc w3c/webtransport#682.
-
Add protocol negotiation to explainer w3c/webtransport#693.
-
Document WebTransport's interaction with non-active documents w3c/webtransport#690.
-
-
5 issues received 18 new comments.
-
Document WebTransport's interaction with non-active documents w3c/webtransport#690 (7 comments by @fergald, @jan-ivar, @nidhijaju, @rakina)
-
Specify what to do with a certificate chain w3c/webtransport#692 (2 comments by @jan-ivar, @vasilvv)
-
-
4 pull requests opened.
-
Fix tbd reference to Keying Exporter in Overview Doc w3c/webtransport#698, by @wilaw.
-
Integrate with fetch w3c/webtransport#697, by @jan-ivar.
-
Indent note to fix numbering order regressed by #487 w3c/webtransport#696, by @jan-ivar.
-
Add an explainer for subprotocol negotiation w3c/webtransport#695, by @vasilvv.
-
-
3 pull requests merged.
-
Fix tbd reference to Keying Exporter in Overview Doc w3c/webtransport#698.
-
Indent note to fix numbering order regressed by #487 w3c/webtransport#696.
-
Add an explainer for subprotocol negotiation w3c/webtransport#695.
-
-
3 pull requests received 9 new comments.
-
Add an explainer for subprotocol negotiation w3c/webtransport#695 (6 comments by @martinthomson, @nidhijaju, @vasilvv, @wilaw)
-
Add connection stats bytesAcknowledged & applicationBytes(Sent|Acknowledged) w3c/webtransport#689 (1 comment by @jan-ivar)
-
GitHub
w3c/webtransport
-
1 issue opened.
-
Document WebTransport's interaction with non-active documents w3c/webtransport#690, by @fergald.
-
-
5 issues closed.
-
Scrub spec of IETF Webtrans HTTP/3 references as much as possible w3c/webtransport#681.
-
Specify keep-alive and idle timeouts w3c/webtransport#614.
-
Client-side certificate (mTLS) in WebTransport options w3c/webtransport#684.
-
WebTransportError.isInitiatedByClient w3c/webtransport#317.
-
Duplicate CRYPTO data error w3c/webtransport#687.
-
-
8 issues received 9 new comments.
-
Document WebTransport's interaction with non-active documents w3c/webtransport#690 (2 comments by @nidhijaju, @wilaw)
-
Do we want to allow web developers to add headers of the CONNECT request? w3c/webtransport#263 (1 comment by @Hebilicious)
-
Client-side certificate (mTLS) in WebTransport options w3c/webtransport#684 (1 comment by @jan-ivar)
-
-
1 pull request opened.
-
Add connection stats bytesAcknowledged & applicationBytes(Sent|Acknowledged) w3c/webtransport#689, by @jan-ivar.
-
-
1 pull request merged.
-
Updating references to IETF Webtrans Overview doc w3c/webtransport#688.
-
-
1 pull request closed.
-
Add wt.idleTimeout read-only attribute w3c/webtransport#685.
-
-
2 pull requests received 15 new comments.
-
Add connection stats bytesAcknowledged & applicationBytes(Sent|Acknowledged) w3c/webtransport#689 (12 comments by @jan-ivar, @martinthomson, @wilaw)
-
GitHub
w3c/webtransport
-
3 issues opened.
-
Duplicate CRYPTO data error w3c/webtransport#687, by @jinbei09.
-
Client-side certificate (mTLS) in WebTransport options w3c/webtransport#684, by @max-au.
-
RTT definitions are per path, not per conneciotn w3c/webtransport#683, by @marten-seemann.
-
-
1 issue closed.
-
RTT definitions are per path, not per conneciotn w3c/webtransport#683.
-
-
9 issues received 22 new comments.
-
Client-side certificate (mTLS) in WebTransport options w3c/webtransport#684 (6 comments by @jan-ivar, @LPardue, @martinthomson, @max-au, @vasilvv)
-
RTT definitions are per path, not per conneciotn w3c/webtransport#683 (5 comments by @alvestrand, @jan-ivar, @martinthomson, @wilaw)
-
Scrub spec of IETF Webtrans HTTP/3 references as much as possible w3c/webtransport#681 (1 comment by @wilaw)
-
Working with servers behind a NAT or on a local network (aka "p2p") w3c/webtransport#590 (1 comment by @wilaw)
-
-
3 pull requests opened.
-
Updating references to IETF Webtrans Overview doc w3c/webtransport#688, by @wilaw.
-
Adding RFC link to minRTT definition w3c/webtransport#686, by @wilaw.
-
Add wt.idleTimeout read-only attribute w3c/webtransport#685, by @jan-ivar.
-
-
1 pull request merged.
-
Adding RFC link to minRTT definition w3c/webtransport#686.
-
-
2 pull requests received 8 new comments.
-
Add wt.idleTimeout read-only attribute w3c/webtransport#685 (7 comments by @martinthomson, @MOZGIII, @nidhijaju)
-
TR publications
-
1 document published.
-
WebTransport published as a Working Draft. History of WebTransport
-
GitHub
w3c/webtransport
-
8 issues opened.
-
Keying exporter algorithm should reference overview doc w3c/webtransport#682, by @wilaw.
-
Scrub spec of IETF Webtrans HTTP/3 references as much as possible w3c/webtransport#681, by @wilaw.
-
Reliable Reset is transport specific? w3c/webtransport#680, by @nidhijaju.
-
DatagramsReadableMode has one value but two states w3c/webtransport#679, by @tidoust.
-
Improved congestion control for real-time use cases w3c/webtransport#676, by @jan-ivar.
-
Basic Echo Fails on Firefox Windows 11 (Chicago and Amsterdam) w3c/webtransport#675, by @ValorZard.
-
More stats w3c/webtransport#674, by @vasilvv.
-
Add support for negotiating and receiving custom QUIC frame data w3c/webtransport#672, by @wilaw.
-
-
8 issues closed.
-
DatagramsReadableMode has one value but two states w3c/webtransport#679.
-
Capsule and frame names in the spec w3c/webtransport#647.
-
Writing zero length Uint8Array to stream, what is the expected behavior? w3c/webtransport#643.
-
Basic Echo Fails on Firefox Windows 11 (Chicago and Amsterdam) w3c/webtransport#675.
-
Add support for negotiating and receiving custom QUIC frame data w3c/webtransport#672.
-
Audit threading model of send datagrams algorithm. w3c/webtransport#236.
-
Add reliable reset stream to the API w3c/webtransport#654.
-
Server replying with the protocol selection is optional w3c/webtransport#653.
-
-
10 issues received 27 new comments.
-
Specify keep-alive and idle timeouts w3c/webtransport#614 (7 comments by @jan-ivar, @martinthomson, @MOZGIII)
-
Do we want to allow web developers to add headers of the CONNECT request? w3c/webtransport#263 (3 comments by @kixelated, @petrroll, @randomstuff)
-
Improved congestion control for real-time use cases w3c/webtransport#676 (3 comments by @alvestrand, @jan-ivar, @wilaw)
-
Working with servers behind a NAT or on a local network (aka "p2p") w3c/webtransport#590 (3 comments by @jan-ivar, @marten-seemann)
-
DatagramsReadableMode has one value but two states w3c/webtransport#679 (2 comments by @jan-ivar, @tidoust)
-
Basic Echo Fails on Firefox Windows 11 (Chicago and Amsterdam) w3c/webtransport#675 (2 comments by @jan-ivar, @ValorZard)
-
Add support for negotiating and receiving custom QUIC frame data w3c/webtransport#672 (2 comments by @LPardue, @wilaw)
-
-
5 pull requests opened.
-
Fix bikeshed warnings w3c/webtransport#678, by @jan-ivar.
-
Fix link to {{WebTransportDatagramsWritable/[[OutgoingDatagramsQueue]]}} w3c/webtransport#677, by @jan-ivar.
-
[editorial] <acronym> is deprecated, use <abbr> instead w3c/webtransport#673, by @ylafon.
-
Add datagramsReadableMode to constructor options w3c/webtransport#671, by @nidhijaju.
-
Fix threading model of send datagrams algorithm w3c/webtransport#670, by @jan-ivar.
-
-
8 pull requests merged.
-
Update frame and signal names to reference the overview w3c/webtransport#669.
-
Add datagramsReadableMode to constructor options w3c/webtransport#671.
-
Fix bikeshed warnings w3c/webtransport#678.
-
Fix link to {{WebTransportDatagramsWritable/[[OutgoingDatagramsQueue]]}} w3c/webtransport#677.
-
[editorial] <acronym> is deprecated, use <abbr> instead w3c/webtransport#673.
-
Fix threading model of send datagrams algorithm w3c/webtransport#670.
-
API for Reliable Resets w3c/webtransport#667.
-
Updating expected behavior around application protocols w3c/webtransport#668.
-
-
5 pull requests received 20 new comments.
-
Update frame and signal names to reference the overview w3c/webtransport#669 (7 comments by @jan-ivar, @nidhijaju)
-
Add datagramsReadableMode to constructor options w3c/webtransport#671 (4 comments by @jan-ivar, @nidhijaju)
-
Fix link to {{WebTransportDatagramsWritable/[[OutgoingDatagramsQueue]]}} w3c/webtransport#677 (1 comment by @jan-ivar)
-
Participants
-
1 participant joined.
-
Philip Eliasson (Google LLC) joined.
-
GitHub
w3c/webtransport
-
1 issue opened.
-
Remove references to GOAWAY and replace with the "draining" concept w3c/webtransport#664, by @ekinnear.
-
-
3 issues closed.
-
Remove references to GOAWAY and replace with the "draining" concept w3c/webtransport#664.
-
maxDatagramSize what happens, if proxies are involved w3c/webtransport#642.
-
Idle energy consumption compared to WebSockets/SSE? w3c/webtransport#636.
-
-
1 issue reopened.
-
Idle energy consumption compared to WebSockets/SSE? w3c/webtransport#636, by @jan-ivar.
-
-
4 issues received 36 new comments.
-
Specify keep-alive and idle timeouts w3c/webtransport#614 (21 comments by @jan-ivar, @LPardue, @martinthomson, @MOZGIII, @wilaw)
-
Writing zero length Uint8Array to stream, what is the expected behavior? w3c/webtransport#643 (7 comments by @jan-ivar, @martenrichter, @martinthomson)
-
-
5 pull requests opened.
-
Update frame and signal names to reference the overview w3c/webtransport#669, by @nidhijaju.
-
Updating expected behavior around application protocols w3c/webtransport#668, by @wilaw.
-
API for Reliable Resets w3c/webtransport#667, by @martinthomson.
-
Remove GOAWAY and update drain w3c/webtransport#666, by @nidhijaju.
-
Clean up webcodecs-echo sample to work in Safari using spec MSTP/VTG w3c/webtransport#665, by @jan-ivar.
-
-
4 pull requests merged.
-
Remove GOAWAY and update drain w3c/webtransport#666.
-
Clean up webcodecs-echo sample to work in Safari using spec MSTP/VTG w3c/webtransport#665.
-
Add some guidance on how to pick maxDatagramSize w3c/webtransport#648.
-
More robust camera selection in webcodecs-echo sample w3c/webtransport#663.
-
-
3 pull requests received 9 new comments.
-
More robust camera selection in webcodecs-echo sample w3c/webtransport#663 (3 comments by @jan-ivar)
-
Add some guidance on how to pick maxDatagramSize w3c/webtransport#648 (2 comments by @martinthomson, @wilaw)
GitHub
w3c/webtransport
-
5 issues opened.
-
Missing tasks in parallel steps in WebTransport w3c/webtransport#659, by @dontcallmedom-bot.
-
Broken links in WebTransport w3c/webtransport#658, by @dontcallmedom-bot.
-
Add reliable reset stream to the API w3c/webtransport#654, by @afrind.
-
Server replying with the protocol selection is optional w3c/webtransport#653, by @vasilvv.
-
Session information w3c/webtransport#652, by @martenrichter.
-
-
8 issues closed.
-
Missing tasks in parallel steps in WebTransport w3c/webtransport#659.
-
Broken links in WebTransport w3c/webtransport#658.
-
Official Examples have expired certificates w3c/webtransport#646.
-
Exposing headers of the CONNECT response w3c/webtransport#264.
-
Sample basic echo: Handshake failure w3c/webtransport#639.
-
expose a TLS Keying Material Exporter / unique value for the TLS session w3c/webtransport#411.
-
Consider removing serverCertificateHashes w3c/webtransport#623.
-
Session information w3c/webtransport#652.
-
-
14 issues received 56 new comments.
-
Writing zero length Uint8Array to stream, what is the expected behavior? w3c/webtransport#643 (16 comments by @alvestrand, @jan-ivar, @LPardue, @martenrichter, @martinthomson)
-
Consider removing serverCertificateHashes w3c/webtransport#623 (6 comments by @alvestrand, @bergstroem, @ekinnear, @jan-ivar)
-
Add reliable reset stream to the API w3c/webtransport#654 (5 comments by @afrind, @jan-ivar, @wilaw)
-
Server replying with the protocol selection is optional w3c/webtransport#653 (4 comments by @jan-ivar)
-
Sample basic echo: Handshake failure w3c/webtransport#639 (3 comments by @martinthomson, @vkrot-cell, @wilaw)
-
Do we want to allow web developers to add headers of the CONNECT request? w3c/webtransport#263 (2 comments by @jan-ivar, @wilaw)
-
expose a TLS Keying Material Exporter / unique value for the TLS session w3c/webtransport#411 (2 comments by @jan-ivar, @Neustradamus)
-
w3c/webtransport#59 (1 comment by @jan-ivar)
-
-
9 pull requests opened.
-
More robust camera selection in webcodecs-echo sample w3c/webtransport#663, by @jan-ivar.
-
Queue a task to resolve exportKeyingMaterial() promise w3c/webtransport#662, by @jan-ivar.
-
Fix link to privacy-principles dfn-cross-site-recognition w3c/webtransport#661, by @jan-ivar.
-
Updating hosted samples in readme w3c/webtransport#660, by @wilaw.
-
Revert "Mark serverCertificateHashes as at risk" w3c/webtransport#657, by @jan-ivar.
-
Fix link to [=cross-site recognition=] w3c/webtransport#656, by @jan-ivar.
-
Update to new echo-server (also polyfill MSTP+MSTG) w3c/webtransport#655, by @jan-ivar.
-
Don't send and ignore reception of zero-byte datagrams w3c/webtransport#651, by @jan-ivar.
-
Explain that chunk boundaries are not preserved on reception w3c/webtransport#650, by @jan-ivar.
-
-
8 pull requests merged.
-
Queue a task to resolve exportKeyingMaterial() promise w3c/webtransport#662.
-
Fix link to privacy-principles dfn-cross-site-recognition w3c/webtransport#661.
-
Updating hosted samples in readme w3c/webtransport#660.
-
Revert "Mark serverCertificateHashes as at risk" w3c/webtransport#657.
-
Update to new echo-server (also polyfill MSTP+MSTG) w3c/webtransport#655.
-
Explain that chunk boundaries are not preserved on reception w3c/webtransport#650.
-
Fix link to [=cross-site recognition=] w3c/webtransport#656.
-
Add exportKeyingMaterial method w3c/webtransport#644.
-
-
1 pull request closed.
-
Don't send and ignore reception of zero-byte datagrams w3c/webtransport#651.
-
-
7 pull requests received 18 new comments.
-
Don't send and ignore reception of zero-byte datagrams w3c/webtransport#651 (7 comments by @alvestrand, @jan-ivar, @martinthomson)
-
Add exportKeyingMaterial method w3c/webtransport#644 (4 comments by @jan-ivar, @martenrichter, @Neustradamus, @nidhijaju)
-
Update to new echo-server (also polyfill MSTP+MSTG) w3c/webtransport#655 (2 comments by @jan-ivar, @wilaw)
-
Explain that chunk boundaries are not preserved on reception w3c/webtransport#650 (1 comment by @jan-ivar)
-
Participants
-
1 participant left.
-
Lucas Pardue (Cloudflare) left.
-
-
1 organization left.
-
Cloudflare left.
-
GitHub
w3c/webtransport
-
5 issues opened.
-
Update our WPTs (meta) w3c/webtransport#649, by @jan-ivar.
-
Capsule and frame names in the spec w3c/webtransport#647, by @nidhijaju.
-
Official Examples have expired certificates w3c/webtransport#646, by @ValorZard.
-
Writing zero length Uint8Array to stream, what is the expected behavior? w3c/webtransport#643, by @martenrichter.
-
maxDatagramSize what happens, if proxies are involved w3c/webtransport#642, by @martenrichter.
-
-
3 issues closed.
-
Is CORS preflight necessary for WebTransport if we add Header support? w3c/webtransport#637.
-
Reference overview doc instead of HTTP3 doc in two places w3c/webtransport#616.
-
Consider removing wt.datagrams.writable w3c/webtransport#624.
-
-
7 issues received 48 new comments.
-
maxDatagramSize what happens, if proxies are involved w3c/webtransport#642 (12 comments by @jan-ivar, @LPardue, @martenrichter, @martinthomson)
-
Writing zero length Uint8Array to stream, what is the expected behavior? w3c/webtransport#643 (11 comments by @jan-ivar, @martenrichter, @martinthomson, @wilaw)
-
Consider removing serverCertificateHashes w3c/webtransport#623 (10 comments by @annevk, @jan-ivar, @kixelated, @marten-seemann, @martenrichter, @vasilvv)
-
Is CORS preflight necessary for WebTransport if we add Header support? w3c/webtransport#637 (4 comments by @annevk, @jan-ivar, @martinthomson, @wilaw)
-
expose a TLS Keying Material Exporter / unique value for the TLS session w3c/webtransport#411 (3 comments by @martinthomson, @vasilvv)
-
-
4 pull requests opened.
-
Add some guidance on how to pick maxDatagramSize w3c/webtransport#648, by @martinthomson.
-
Replaces references of HTTP/3 spec with Overview w3c/webtransport#645, by @nidhijaju.
-
Add exportKeyingMaterial method w3c/webtransport#644, by @nidhijaju.
-
Mark serverCertificateHashes as at risk w3c/webtransport#641, by @jan-ivar.
-
-
4 pull requests merged.
-
Replaces references of HTTP/3 spec with Overview w3c/webtransport#645.
-
Remove wt.datagrams.writable and fix cleanup. w3c/webtransport#638.
-
Mark serverCertificateHashes as at risk w3c/webtransport#641.
-
Reference overview doc for protocol negotiation w3c/webtransport#640.
-
-
2 pull requests received 7 new comments.
-
Add exportKeyingMaterial method w3c/webtransport#644 (4 comments by @martinthomson, @nidhijaju, @vasilvv)
-
Replaces references of HTTP/3 spec with Overview w3c/webtransport#645 (3 comments by @jan-ivar, @wilaw)
-
GitHub
w3c/webtransport
-
3 issues opened.
-
Sample basic echo: Handshake failure w3c/webtransport#639, by @vkrot-cell.
-
Is CORS preflight necessary for WebTransport if we add Header support? w3c/webtransport#637, by @jan-ivar.
-
Idle energy consumption compared to WebSockets/SSE? w3c/webtransport#636, by @Symbitic.
-
-
1 issue closed.
-
Relative prioritization of streams and datagrams w3c/webtransport#610.
-
-
9 issues received 36 new comments.
-
Exposing headers of the CONNECT response w3c/webtransport#264 (10 comments by @LPardue, @martinthomson, @vasilvv, @wilaw)
-
Sample basic echo: Handshake failure w3c/webtransport#639 (7 comments by @jan-ivar, @martinthomson, @vkrot-cell, @wilaw)
-
Is CORS preflight necessary for WebTransport if we add Header support? w3c/webtransport#637 (7 comments by @jan-ivar, @KershawChang, @martenrichter)
-
Consider removing serverCertificateHashes w3c/webtransport#623 (4 comments by @alvestrand, @ekinnear, @martenrichter, @martinthomson)
-
Idle energy consumption compared to WebSockets/SSE? w3c/webtransport#636 (4 comments by @LPardue, @martinthomson, @Symbitic, @vasilvv)
-
expose a TLS Keying Material Exporter / unique value for the TLS session w3c/webtransport#411 (1 comment by @wilaw)
-
Reference overview doc instead of HTTP3 doc in two places w3c/webtransport#616 (1 comment by @jan-ivar)
-
Do we want to allow web developers to add headers of the CONNECT request? w3c/webtransport#263 (1 comment by @jan-ivar)
-
-
2 pull requests opened.
-
Reference overview doc for protocol negotiation w3c/webtransport#640, by @jan-ivar.
-
Remove wt.datagrams.writable and fix cleanup. w3c/webtransport#638, by @jan-ivar.
-
-
1 pull request merged.
-
Add datagrams.createWritable({sendGroup, sendOrder}) w3c/webtransport#629.
-
-
1 pull request received 2 new comments.
-
Reference overview doc for protocol negotiation w3c/webtransport#640 (2 comments by @jan-ivar, @vasilvv)
-
TR publications
-
1 document published.
-
WebTransport published as a Working Draft. History of WebTransport
-
Participants
-
2 participants left.
-
Luca Barbato (Luminem) left.
-
Bernard Aboba (Microsoft Corporation) left.
-
-
1 organization left.
-
Luminem left.
-
GitHub
w3c/webtransport
-
2 issues opened.
-
Prayag transport w3c/webtransport#635, by @SachinMishra-1234.
-
Not really an issue w3c/webtransport#633, by @rayj00.
-
-
4 issues closed.
-
Not really an issue w3c/webtransport#633.
-
Prayag transport w3c/webtransport#635.
-
Missing tasks in parallel steps in WebTransport w3c/webtransport#626.
-
Expose MTU via stats w3c/webtransport#615.
-
-
6 issues received 14 new comments.
-
Consider removing serverCertificateHashes w3c/webtransport#623 (7 comments by @annevk, @jan-ivar, @mozfreddyb, @wilaw)
-
Do we want to allow web developers to add headers of the CONNECT request? w3c/webtransport#263 (1 comment by @petrroll)
-
-
7 pull requests opened.
-
Add missing tasks in parallel steps w3c/webtransport#634, by @jan-ivar.
-
Adjust estimatedSendRate definition to exclude framing overhead w3c/webtransport#632, by @wilaw.
-
Update editors to include JIB w3c/webtransport#631, by @wilaw.
-
Updating editors w3c/webtransport#630, by @wilaw.
-
Add datagrams.createWritable({sendGroup, sendOrder}) w3c/webtransport#629, by @jan-ivar.
-
Add datagrams.createWritable({sendGroup, sendOrder}) w3c/webtransport#628, by @jan-ivar.
-
Fix some bikeshed errors w3c/webtransport#627, by @jan-ivar.
-
-
5 pull requests merged.
-
Add missing tasks in parallel steps w3c/webtransport#634.
-
Adjust estimatedSendRate definition to exclude framing overhead w3c/webtransport#632.
-
Update editors to include JIB w3c/webtransport#631.
-
Updating editors w3c/webtransport#630.
-
Fix some bikeshed errors w3c/webtransport#627.
-
-
2 pull requests closed.
-
Add datagrams.createWritable() w3c/webtransport#620.
-
Add datagrams.createWritable({sendGroup, sendOrder}) w3c/webtransport#628.
-
-
5 pull requests received 11 new comments.
-
Add datagrams.createWritable({sendGroup, sendOrder}) w3c/webtransport#629 (5 comments by @jan-ivar, @wilaw)
-
Participants
-
5 participants left.
-
xianyang zhang (Agora.io) left.
-
yang lee (Agora.io) left.
-
Zeyu Guo (Agora.io) left.
-
Xiao Fu (Agora.io) left.
-
Chun Gao (Agora.io) left.
-
-
1 organization left.
-
Agora.io left.
-
GitHub
w3c/webtransport
-
1 issue opened.
-
Missing tasks in parallel steps in WebTransport w3c/webtransport#626, by @dontcallmedom-bot.
-
-
5 issues received 28 new comments.
-
Handshake is not defined in terms of Fetch w3c/webtransport#625 (14 comments by @annevk, @jan-ivar, @KershawChang, @vasilvv)
-
Consider removing serverCertificateHashes w3c/webtransport#623 (6 comments by @jan-ivar, @kixelated, @marten-seemann, @martenrichter, @vasilvv)
-
Do we want to allow web developers to add headers of the CONNECT request? w3c/webtransport#263 (5 comments by @annevk, @jan-ivar, @repulsio, @wilaw)
-
-
1 pull request merged.
-
Rename "Data Recvd" to "all data committed" w3c/webtransport#580.
-
-
2 pull requests received 3 new comments.