WebTransport Working Group - Activity in 2023
No matches.
TR publications
-
1 document published.
-
WebTransport published as a Working Draft. History of WebTransport
-
Participants
-
1 participant left.
-
Jack J (Google LLC) left.
-
GitHub
w3c/webtransport
-
1 issue opened.
-
How should the WebTransport constructor handles timeouts? w3c/webtransport#578, by @martenrichter.
-
-
7 issues closed.
-
WebTransport new features w3c/webtransport#506.
-
Make create(Uni|Bi)directionalStream() synchronous? w3c/webtransport#529.
-
Busy requestAnimationFrame Causes WebTransport Send Queue Starvation w3c/webtransport#543.
-
Clarify what sending "completed" means e.g. wrt. flow control w3c/webtransport#571.
-
WebTransport http2 idea's suggestions w3c/webtransport#518.
-
No write requests are being rejected on in-flight error w3c/webtransport#565.
-
Rewrite the text of the specification to be independent of the underlying transport w3c/webtransport#408.
-
-
16 issues received 30 new comments.
-
Quality of a bandwidth estimate w3c/webtransport#559 (5 comments by @ianswett, @jan-ivar, @martinthomson)
-
Provide flow control minimums from the browser side w3c/webtransport#541 (4 comments by @jan-ivar, @vasilvv)
-
Reconsider whether we need sub-protocol negotiation w3c/webtransport#536 (2 comments by @jan-ivar, @vasilvv)
-
expose a TLS Keying Material Exporter / unique value for the TLS session w3c/webtransport#411 (2 comments by @jan-ivar, @vasilvv)
-
Relative send priority between datagrams and streams w3c/webtransport#451 (2 comments by @jan-ivar, @wilaw)
-
Clarify what sending "completed" means e.g. wrt. flow control w3c/webtransport#571 (2 comments by @aboba, @jan-ivar)
-
How should the WebTransport constructor handles timeouts? w3c/webtransport#578 (1 comment by @martenrichter)
-
Do we want to allow web developers to add headers of the CONNECT request? w3c/webtransport#263 (1 comment by @randomstuff)
-
Allow users to find how prioritization is done easily? w3c/webtransport#532 (1 comment by @jan-ivar)
-
Busy requestAnimationFrame Causes WebTransport Send Queue Starvation w3c/webtransport#543 (1 comment by @wilaw)
-
-
3 pull requests opened.
-
s/An send order/A send order/ w3c/webtransport#577, by @jan-ivar.
-
Update reference from RFC6125 to RFC9525. w3c/webtransport#576, by @jan-ivar.
-
Add WebTransport.supportsReliableOnly boolean. w3c/webtransport#575, by @jan-ivar.
-
-
4 pull requests merged.
-
s/An send order/A send order/ w3c/webtransport#577.
-
Add WebTransport.supportsReliableOnly boolean. w3c/webtransport#575.
-
Reject in-flight write promise on network error. w3c/webtransport#566.
-
Update spec with transport agnostic language w3c/webtransport#562.
-
-
2 pull requests closed.
-
Update reference from RFC6125 to RFC9525. w3c/webtransport#576.
-
Add feature-detection of HTTP/2 fallback. w3c/webtransport#568.
-
-
7 pull requests received 19 new comments.
-
Add writer.atomicWrite() method. w3c/webtransport#551 (9 comments by @jan-ivar, @martinthomson, @nidhijaju, @ricea)
-
Add anticipatedConcurrentIncoming[Bi/Uni]directionalStreams attributes & constructor arg w3c/webtransport#574 (1 comment by @jan-ivar)
-
Participants
-
1 participant left.
-
shuai zhao (Intel Corporation) left.
-
GitHub
w3c/webtransport
-
5 issues opened.
-
Clarify what sending "completed" means e.g. wrt. flow control w3c/webtransport#571, by @jan-ivar.
-
Send algos contains normative MAY and SHOULD in non-normative notes w3c/webtransport#569, by @jan-ivar.
-
Should all fields in WebTransportConnectionStats be nullable? w3c/webtransport#567, by @vasilvv.
-
No write requests are being rejected on in-flight error w3c/webtransport#565, by @jan-ivar.
-
WebTransportSendStream's abortSignal algorithm doesn't make sense w3c/webtransport#563, by @jan-ivar.
-
-
5 issues closed.
-
estimatedSendRate absent vs null w3c/webtransport#554.
-
Send algos contains normative MAY and SHOULD in non-normative notes w3c/webtransport#569.
-
WebTransportSendStream's abortSignal algorithm doesn't make sense w3c/webtransport#563.
-
getStats() being rejected w3c/webtransport#557.
-
-
10 issues received 27 new comments.
-
WebTransport http2 idea's suggestions w3c/webtransport#518 (9 comments by @jan-ivar, @martenrichter)
-
Improve Server→Client Stream Performance by Allowing Customizable Concurrency Limits in WebTransport w3c/webtransport#544 (3 comments by @jan-ivar, @wilaw)
-
Reconsider whether we need sub-protocol negotiation w3c/webtransport#536 (2 comments by @ekinnear, @jan-ivar)
-
Should the constructor take http3Only or something more transport agnostic? w3c/webtransport#561 (2 comments by @jan-ivar)
-
Should all fields in WebTransportConnectionStats be nullable? w3c/webtransport#567 (2 comments by @jan-ivar)
-
No write requests are being rejected on in-flight error w3c/webtransport#565 (2 comments by @jan-ivar)
-
expose a TLS Keying Material Exporter / unique value for the TLS session w3c/webtransport#411 (1 comment by @Neustradamus)
-
Busy requestAnimationFrame Causes WebTransport Send Queue Starvation w3c/webtransport#543 (1 comment by @cybersoulK)
-
-
7 pull requests opened.
-
Add anticipatedConcurrentIncoming[Bi/Uni]directionalStreams attributes & constructor arg w3c/webtransport#574, by @jan-ivar.
-
Make estimatedSendRate be `null` instead of `undefined` w3c/webtransport#573, by @vasilvv.
-
Add a `waitUntilAvailable` option to stream creation w3c/webtransport#572, by @vasilvv.
-
Move normative prose in send algortithms out of notes. w3c/webtransport#570, by @jan-ivar.
-
Add feature-detection of HTTP/2 fallback. w3c/webtransport#568, by @jan-ivar.
-
Reject in-flight write promise on network error. w3c/webtransport#566, by @jan-ivar.
-
Fix missing |promise| reference in abortSignal algorithm. w3c/webtransport#564, by @jan-ivar.
-
-
5 pull requests merged.
-
Make estimatedSendRate be `null` instead of `undefined` w3c/webtransport#573.
-
Add a `waitUntilAvailable` option to stream creation w3c/webtransport#572.
-
Move normative prose in send algortithms out of notes. w3c/webtransport#570.
-
Fix missing |promise| reference in abortSignal algorithm. w3c/webtransport#564.
-
Reject getStats() promise when the connection is closed/failed. w3c/webtransport#558.
-
-
6 pull requests received 17 new comments.
-
Move normative prose in send algortithms out of notes. w3c/webtransport#570 (2 comments by @jan-ivar, @vasilvv)
-
Make estimatedSendRate be `null` instead of `undefined` w3c/webtransport#573 (1 comment by @jan-ivar)
GitHub
w3c/webtransport
-
6 issues opened.
-
Should the constructor take http3Only or something more transport agnostic? w3c/webtransport#561, by @ekinnear.
-
Allow more aggressive garbage collection w3c/webtransport#560, by @jan-ivar.
-
Quality of a bandwidth estimate w3c/webtransport#559, by @vasilvv.
-
getStats() being rejected w3c/webtransport#557, by @vasilvv.
-
estimatedSendRate absent vs null w3c/webtransport#554, by @vasilvv.
-
Add expiredIncoming to stats w3c/webtransport#553, by @vasilvv.
-
-
3 issues closed.
-
Accept ∞ for incoming/outgoingHighWaterMark and incoming/outgoingMaxAge for consistency w3c/webtransport#463.
-
Timestamp in the Stats object w3c/webtransport#550.
-
Priority groups w3c/webtransport#515.
-
-
1 issue reopened.
-
Accept ∞ for incoming/outgoingHighWaterMark and incoming/outgoingMaxAge for consistency w3c/webtransport#463, by @vasilvv.
-
-
12 issues received 25 new comments.
-
Improve Server→Client Stream Performance by Allowing Customizable Concurrency Limits in WebTransport w3c/webtransport#544 (6 comments by @jan-ivar, @martinthomson)
-
WebTransport http2 idea's suggestions w3c/webtransport#518 (4 comments by @jan-ivar, @martenrichter)
-
MAX_STREAM limit (Client→Server) (still need an event when stream ids become available again) w3c/webtransport#446 (2 comments by @jan-ivar)
-
Accept ∞ for incoming/outgoingHighWaterMark and incoming/outgoingMaxAge for consistency w3c/webtransport#463 (2 comments by @jan-ivar, @vasilvv)
-
Rewrite the text of the specification to be independent of the underlying transport w3c/webtransport#408 (1 comment by @nidhijaju)
-
w3c/webtransport#59 (1 comment by @nidhijaju)
-
-
6 pull requests opened.
-
Update spec with transport agnostic language w3c/webtransport#562, by @nidhijaju.
-
Reject getStats() promise when the connection is closed/failed. w3c/webtransport#558, by @vasilvv.
-
Fix wrong internal slot in a note about the datagrams queue. w3c/webtransport#556, by @jan-ivar.
-
Make incomingMaxAge and outgoingMaxAge nullable again. w3c/webtransport#555, by @jan-ivar.
-
Remove timestamp from all stats objects w3c/webtransport#552, by @vasilvv.
-
Add writer.atomicWrite() method. w3c/webtransport#551, by @jan-ivar.
-
-
5 pull requests merged.
-
Fix wrong internal slot in a note about the datagrams queue. w3c/webtransport#556.
-
Make incomingMaxAge and outgoingMaxAge nullable again. w3c/webtransport#555.
-
Remove timestamp from all stats objects w3c/webtransport#552.
-
Add SendGroup, and make sendOrder no longer nullable. w3c/webtransport#548.
-
Set optimizeForLatency in decoder configuration w3c/webtransport#549.
-
-
1 pull request closed.
-
Add getAtomicWriter() API. w3c/webtransport#502.
-
-
4 pull requests received 12 new comments.
-
Reject getStats() promise when the connection is closed/failed. w3c/webtransport#558 (2 comments by @jan-ivar)
Past meetings
-
1 meeting.
GitHub
w3c/webtransport
-
3 issues opened.
-
Timestamp in the Stats object w3c/webtransport#550, by @vasilvv.
-
Busy requestAnimationFrame Causes WebTransport Send Queue Starvation w3c/webtransport#543, by @cybersoulK.
-
-
1 issue closed.
-
Clarify the semantics of stats and their relationship to QUIC connection w3c/webtransport#537.
-
-
1 issue reopened.
-
MAX_STREAM limit (Client→Server) (still need an event when stream ids become available again) w3c/webtransport#446, by @vasilvv.
-
-
8 issues received 20 new comments.
-
Improve Server→Client Stream Performance by Allowing Customizable Concurrency Limits in WebTransport w3c/webtransport#544 (7 comments by @aboba, @cybersoulK, @martinthomson)
-
Busy requestAnimationFrame Causes WebTransport Send Queue Starvation w3c/webtransport#543 (2 comments by @jan-ivar, @wilaw)
-
MAX_STREAM limit (Client→Server) (still need an event when stream ids become available again) w3c/webtransport#446 (2 comments by @vasilvv, @wilaw)
-
Clarify the semantics of stats and their relationship to QUIC connection w3c/webtransport#537 (1 comment by @wilaw)
-
-
5 pull requests opened.
-
Set optimizeForLatency in decoder configuration w3c/webtransport#549, by @aboba.
-
Add SendGroup, and make sendOrder no longer nullable. w3c/webtransport#548, by @jan-ivar.
-
Define [=underlying connection=] for connection-level stats. w3c/webtransport#547, by @jan-ivar.
-
Add stat bytesLost w3c/webtransport#546, by @jan-ivar.
-
Remove stats numOutgoingStreamsCreated & numIncomingStreamsCreated w3c/webtransport#545, by @jan-ivar.
-
-
4 pull requests merged.
-
Define [=underlying connection=] for connection-level stats. w3c/webtransport#547.
-
Add stat bytesLost w3c/webtransport#546.
-
Remove stats numOutgoingStreamsCreated & numIncomingStreamsCreated w3c/webtransport#545.
-
Reject create(Uni|Bi)directionalStream() on stream ID exhaustion. w3c/webtransport#528.
-
-
5 pull requests received 12 new comments.
-
Add SendGroup, and make sendOrder no longer nullable. w3c/webtransport#548 (5 comments by @jan-ivar, @martinthomson)
-
Define [=underlying connection=] for connection-level stats. w3c/webtransport#547 (4 comments by @nidhijaju)
-
GitHub
w3c/webtransport
-
7 issues opened.
-
Define datagram w3c/webtransport#542, by @achristensen07.
-
Provide flow control minimums from the browser side w3c/webtransport#541, by @vasilvv.
-
Expose [[State]] internal slot w3c/webtransport#539, by @achingbrain.
-
Clarify the semantics of stats and their relationship to QUIC connection w3c/webtransport#537, by @vasilvv.
-
Reconsider whether we need sub-protocol negotiation w3c/webtransport#536, by @vasilvv.
-
Protocol concepts don't include sending on streams w3c/webtransport#533, by @martinthomson.
-
Allow users to find how prioritization is done easily? w3c/webtransport#532, by @MarcWeber.
-
-
2 issues closed.
-
Protocol concepts don't include sending on streams w3c/webtransport#533.
-
IncomingStreams pullUnidirectionStream algorithm w3c/webtransport#452.
-
-
14 issues received 24 new comments.
-
Reconsider whether we need sub-protocol negotiation w3c/webtransport#536 (3 comments by @jan-ivar, @LPardue, @martinthomson)
-
Clarify the semantics of stats and their relationship to QUIC connection w3c/webtransport#537 (2 comments by @jan-ivar)
-
WebTransport http2 idea's suggestions w3c/webtransport#518 (2 comments by @ekinnear, @martenrichter)
-
Protocol concepts don't include sending on streams w3c/webtransport#533 (2 comments by @jan-ivar, @nidhijaju)
-
MAX_STREAM limit (Client→Server) (still need an event when stream ids become available again) w3c/webtransport#446 (1 comment by @jan-ivar)
-
Allow users to find how prioritization is done easily? w3c/webtransport#532 (1 comment by @jan-ivar)
-
w3c/webtransport#127 (1 comment by @FZambia)
-
4 pull requests opened.
-
Use plotly graphing library instead of Google Graphs in samples w3c/webtransport#540, by @aboba.
-
Add introduction to Section 3 w3c/webtransport#538, by @nidhijaju.
-
Clarify Protocol concepts section (Section 3) w3c/webtransport#535, by @nidhijaju.
-
Reject promise if state is not "connected" in pull(Uni|Bi)directionalStream w3c/webtransport#534, by @nidhijaju.
-
-
4 pull requests merged.
-
Use plotly graphing library instead of Google Graphs in samples w3c/webtransport#540.
-
Add introduction to Section 3 w3c/webtransport#538.
-
Clarify Protocol concepts section (Section 3) w3c/webtransport#535.
-
Reject promise if state is not "connected" in pull(Uni|Bi)directionalStream w3c/webtransport#534.
-
-
1 pull request closed.
-
1 pull request received 2 new comments.
-
Clarify Protocol concepts section (Section 3) w3c/webtransport#535 (2 comments by @martinthomson, @nidhijaju)
-
TR publications
-
1 document published.
-
WebTransport published as a Working Draft. History of WebTransport
-
GitHub
w3c/webtransport
-
3 issues opened.
-
Support for CLOSE_FRAME w3c/webtransport#531, by @aboba.
-
Make create(Uni|Bi)directionalStream() synchronous? w3c/webtransport#529, by @jan-ivar.
-
Clarification about reverse proxies and WebTransport w3c/webtransport#525, by @FZambia.
-
-
2 issues closed.
-
cleanup does not specify what to do with the datagrams streams w3c/webtransport#524.
-
Clarification about reverse proxies and WebTransport w3c/webtransport#525.
-
-
5 issues received 16 new comments.
-
Make create(Uni|Bi)directionalStream() synchronous? w3c/webtransport#529 (5 comments by @jan-ivar, @vasilvv)
-
Clarification about reverse proxies and WebTransport w3c/webtransport#525 (4 comments by @FZambia, @LPardue)
-
-
4 pull requests opened.
-
Remove potential race condition from encode and decode transform streams (WebCodecs Echo Sample) w3c/webtransport#530, by @aboba.
-
Reject create(Uni|Bi)directionalStream() on stream ID exhaustion. w3c/webtransport#528, by @jan-ivar.
-
Update ranges of streamErrorCode w3c/webtransport#527, by @bashi.
-
Cleanup Datagram Streams w3c/webtransport#526, by @nidhijaju.
-
-
3 pull requests merged.
-
Update ranges of streamErrorCode w3c/webtransport#527.
-
Cleanup Datagram Streams w3c/webtransport#526.
-
Add automated glass-glass latency calculation via RVFC w3c/webtransport#519.
-
-
4 pull requests received 8 new comments.
-
Reject create(Uni|Bi)directionalStream() on stream ID exhaustion. w3c/webtransport#528 (3 comments by @jan-ivar, @ricea, @vasilvv)
-
Add automated glass-glass latency calculation via RVFC w3c/webtransport#519 (1 comment by @jan-ivar)
-
Participants
-
1 participant left.
-
Dag-Inge Aas (Daily, Co) left.
-
-
1 organization left.
-
Loongson Technology Corporation Limited left.
-
GitHub
w3c/webtransport
-
5 issues opened.
-
cleanup does not specify what to do with the datagrams streams w3c/webtransport#524, by @rvadhavk.
-
Retransmissions and send order w3c/webtransport#523, by @vasilvv.
-
WebTransport API and ManagedMediaSource API w3c/webtransport#522, by @aboba.
-
Do we need to say something about default priority and fairness? w3c/webtransport#520, by @jan-ivar.
-
WebTransport http2 idea's suggestions w3c/webtransport#518, by @martenrichter.
-
-
2 issues closed.
-
Do we need to say something about default priority and fairness? w3c/webtransport#520.
-
Sorry for the interruption w3c/webtransport#517.
-
-
5 issues received 12 new comments.
-
Retransmissions and send order w3c/webtransport#523 (5 comments by @aboba, @kixelated, @LPardue, @martinthomson)
-
Do we need to say something about default priority and fairness? w3c/webtransport#520 (2 comments by @jan-ivar, @LPardue)
-
-
2 pull requests opened.
-
UA SHOULD divide bandwidth fairly between all streams that aren’t starved w3c/webtransport#521, by @jan-ivar.
-
Add automated glass-glass latency calculation via RVFC w3c/webtransport#519, by @aboba.
-
-
1 pull request merged.
-
UA SHOULD divide bandwidth fairly between all streams that aren’t starved w3c/webtransport#521.
-
-
3 pull requests received 16 new comments.
-
Add automated glass-glass latency calculation via RVFC w3c/webtransport#519 (7 comments by @aboba, @alvestrand, @jan-ivar)
-
UA SHOULD divide bandwidth fairly between all streams that aren’t starved w3c/webtransport#521 (1 comment by @jan-ivar)
GitHub
w3c/webtransport
-
6 issues opened.
-
Sorry for the interruption w3c/webtransport#517, by @lemanschik.
-
WPT tests are needed for sendOrder w3c/webtransport#516, by @jesup.
-
Priority groups w3c/webtransport#515, by @vasilvv.
-
Node.js support for WebTransport w3c/webtransport#511, by @wilaw.
-
Confirm behaviour of server certificates. w3c/webtransport#508, by @hamishwillee.
-
Should incomingUni/BidirectionalStreams be "owning"? w3c/webtransport#507, by @jan-ivar.
-
-
9 issues closed.
-
Can we multiplex more than one session per connection in the same browser tab? w3c/webtransport#449.
-
serverCertificateHashes w3c/webtransport#456.
-
Support sendRateEstimate for pooled connections w3c/webtransport#497.
-
Human readable error message without language info w3c/webtransport#414.
-
Normative key words w3c/webtransport#505.
-
Allow updating send order for streams w3c/webtransport#492.
-
Define default send order w3c/webtransport#493.
-
Clarify whether spec supports BYOB readers for Datagrams w3c/webtransport#480.
-
-
12 issues received 32 new comments.
-
Node.js support for WebTransport w3c/webtransport#511 (6 comments by @aboba, @jasnell, @martenrichter, @vasilvv, @wilaw)
-
Confirm behaviour of server certificates. w3c/webtransport#508 (6 comments by @hamishwillee, @martinthomson, @vasilvv)
-
MAX_STREAM limit (Client→Server) (still need an event when stream ids become available again) w3c/webtransport#446 (2 comments by @jan-ivar)
-
Should incomingUni/BidirectionalStreams be "owning"? w3c/webtransport#507 (2 comments by @jan-ivar, @ricea)
-
Can we multiplex more than one session per connection in the same browser tab? w3c/webtransport#449 (1 comment by @jan-ivar)
-
w3c/webtransport#131 (1 comment by @jan-ivar)
-
5 pull requests opened.
-
Removing language that indicates the sendRate estimate must be absent when pooled. w3c/webtransport#514, by @wilaw.
-
Provide guidance on displaying a human readable error message without language info w3c/webtransport#513, by @wilaw.
-
Update normative key words w3c/webtransport#512, by @wilaw.
-
Add sendStream.sendOrder = n attribute. w3c/webtransport#510, by @jan-ivar.
-
Make streamErrorCode 32-bit long w3c/webtransport#509, by @vasilvv.
-
-
9 pull requests merged.
-
Throwing serverCertificateHashes related errors w3c/webtransport#489.
-
Removing language that indicates the sendRate estimate must be absent when pooled. w3c/webtransport#514.
-
Provide guidance on displaying a human readable error message without language info w3c/webtransport#513.
-
Update normative key words w3c/webtransport#512.
-
Add sendStream.sendOrder = n attribute. w3c/webtransport#510.
-
Make streamErrorCode 32-bit long w3c/webtransport#509.
-
Update BFCache interaction w3c/webtransport#503.
-
Support BYOB Readers for Datagrams w3c/webtransport#487.
-
Add .gitignore to remove index.html w3c/webtransport#504.
-
-
6 pull requests received 11 new comments.
-
Throwing serverCertificateHashes related errors w3c/webtransport#489 (2 comments by @ekinnear, @vasilvv)
-
Provide guidance on displaying a human readable error message without language info w3c/webtransport#513 (2 comments by @jan-ivar)
TR publications
-
1 document published.
-
WebTransport published as a Working Draft. History of WebTransport
-
GitHub
w3c/webtransport
-
6 issues opened.
-
WebTransport new features w3c/webtransport#506, by @MuratovBektur.
-
Normative key words w3c/webtransport#505, by @LPardue.
-
API handling of redirects w3c/webtransport#499, by @vasilvv.
-
Redirect Handling w3c/webtransport#498, by @aboba.
-
Support sendRateEstimate for pooled connections w3c/webtransport#497, by @jan-ivar.
-
Should there be any way to send capsules on the WebTransport session CONNECT stream? w3c/webtransport#496, by @LPardue.
-
-
8 issues closed.
-
Rate control privacy considerations w3c/webtransport#478.
-
More thorough state persistence treatment w3c/webtransport#332.
-
Determine interaction with back forward cache w3c/webtransport#326.
-
Should there be any way to send capsules on the WebTransport session CONNECT stream? w3c/webtransport#496.
-
Opening WebTransport streams before the WebTransport session is established w3c/webtransport#409.
-
Redirect Handling w3c/webtransport#498.
-
Question: Partial Reliability w3c/webtransport#422.
-
Add sendRateEstimate to getStats() w3c/webtransport#484.
-
-
1 issue reopened.
-
Define default send order w3c/webtransport#493, by @vasilvv.
-
-
12 issues received 37 new comments.
-
Determine interaction with back forward cache w3c/webtransport#326 (10 comments by @fergald, @jan-ivar, @jesup, @ricea)
-
Should there be any way to send capsules on the WebTransport session CONNECT stream? w3c/webtransport#496 (5 comments by @jan-ivar, @LPardue, @wilaw)
-
Support sendRateEstimate for pooled connections w3c/webtransport#497 (2 comments by @martinthomson, @wilaw)
-
Opening WebTransport streams before the WebTransport session is established w3c/webtransport#409 (1 comment by @aboba)
-
expose a TLS Keying Material Exporter / unique value for the TLS session w3c/webtransport#411 (1 comment by @vasilvv)
-
MAX_STREAM limit (Client→Server) (still need an event when stream ids become available again) w3c/webtransport#446 (1 comment by @jan-ivar)
-
5 pull requests opened.
-
Add .gitignore to remove index.html w3c/webtransport#504, by @nidhijaju.
-
Update BFCache interaction w3c/webtransport#503, by @nidhijaju.
-
Add getAtomicWriter() API. w3c/webtransport#502, by @jan-ivar.
-
State persistence w3c/webtransport#501, by @aboba.
-
Specify BFCache interaction w3c/webtransport#500, by @nidhijaju.
-
-
5 pull requests merged.
-
Networking privacy considerations w3c/webtransport#485.
-
State persistence w3c/webtransport#501.
-
Specify BFCache interaction w3c/webtransport#500.
-
RESET_STREAM handling w3c/webtransport#491.
-
Add estimatedSendRate to stats. w3c/webtransport#494.
-
-
8 pull requests received 60 new comments.
-
Throwing serverCertificateHashes related errors w3c/webtransport#489 (20 comments by @jan-ivar, @martinthomson, @nidhijaju, @vasilvv)
-
Support BYOB Readers for Datagrams w3c/webtransport#487 (16 comments by @domenic, @jan-ivar, @nidhijaju, @ricea, @saschanaz)
-
Add estimatedSendRate to stats. w3c/webtransport#494 (7 comments by @jan-ivar, @martinthomson, @pthatcher)
-
Networking privacy considerations w3c/webtransport#485 (6 comments by @jan-ivar, @martinthomson, @vasilvv)
-
Participants
-
1 participant joined.
-
shuai zhao (Intel Corporation) joined.
-
GitHub
w3c/webtransport
-
5 issues opened.
-
Please use RFC 9000 style message formats isntead of misleading octet graphs w3c/webtransport#495, by @huitema.
-
Define default send order w3c/webtransport#493, by @vasilvv.
-
Allow updating send order for streams w3c/webtransport#492, by @vasilvv.
-
Add sendRateEstimate to getStats() w3c/webtransport#484, by @jan-ivar.
-
Revert ratecontrol PR based on conclusion to put it in getStats() w3c/webtransport#483, by @jan-ivar.
-
-
12 issues closed.
-
Please use RFC 9000 style message formats isntead of misleading octet graphs w3c/webtransport#495.
-
Review Framework for Accessibility in the Specification of Technologies (FAST) checklist w3c/webtransport#405.
-
Draining WebTransport connections w3c/webtransport#432.
-
Handling of negative values and 0 for incomingMaxAge w3c/webtransport#450.
-
Revert ratecontrol PR based on conclusion to put it in getStats() w3c/webtransport#483.
-
rateControlFeedbackMinInterval is unused w3c/webtransport#475.
-
[[sendRate]] is uninitialized w3c/webtransport#477.
-
HTTP/2 might be reliable(-only), but datagrams aren't w3c/webtransport#479.
-
Final API shape of rate control feedback w3c/webtransport#481.
-
API behavior when opening a new stream is blocked w3c/webtransport#469.
-
Reliability is always supports-unreliable w3c/webtransport#472.
-
-
17 issues received 32 new comments.
-
Add sendRateEstimate to getStats() w3c/webtransport#484 (5 comments by @jan-ivar, @pthatcher, @wilaw)
-
Final API shape of rate control feedback w3c/webtransport#481 (4 comments by @jan-ivar, @martinthomson, @wilaw)
-
Review Framework for Accessibility in the Specification of Technologies (FAST) checklist w3c/webtransport#405 (2 comments by @ruoxiran, @wilaw)
-
MAX_STREAM limit (Client→Server) (still need an event when stream ids become available again) w3c/webtransport#446 (2 comments by @jan-ivar, @marten-seemann)
-
Please use RFC 9000 style message formats isntead of misleading octet graphs w3c/webtransport#495 (1 comment by @huitema)
-
-
8 pull requests opened.
-
Add estimatedSendRate to stats. w3c/webtransport#494, by @pthatcher.
-
RESET_STREAM handling w3c/webtransport#491, by @aboba.
-
RESET_STREAM handling w3c/webtransport#490, by @aboba.
-
Throwing serverCertificateHashes related errors w3c/webtransport#489, by @nidhijaju.
-
Revert #421. w3c/webtransport#488, by @jan-ivar.
-
Support BYOB Readers for Datagrams w3c/webtransport#487, by @nidhijaju.
-
Editorial reference updates w3c/webtransport#486, by @ekinnear.
-
Networking privacy considerations w3c/webtransport#485, by @martinthomson.
-
-
5 pull requests merged.
-
Editorial reference updates w3c/webtransport#486.
-
Receiving a GOAWAY frame or DRAIN_WEBTRANSPORT_SESSION capsule w3c/webtransport#482.
-
Revert #421. w3c/webtransport#488.
-
Use nested steps for steps run in parallel w3c/webtransport#468.
-
Supporting "reliable-only" w3c/webtransport#474.
-
-
3 pull requests closed.
-
RESET_STREAM handling w3c/webtransport#490.
-
Congestion control event with no sub-object w3c/webtransport#471.
-
Congestion control event with everything in WebTranspsort.rateControlFeedback. w3c/webtransport#470.
-
-
9 pull requests received 27 new comments.
-
Support BYOB Readers for Datagrams w3c/webtransport#487 (8 comments by @jan-ivar, @nidhijaju, @ricea, @saschanaz)
-
Receiving a GOAWAY frame or DRAIN_WEBTRANSPORT_SESSION capsule w3c/webtransport#482 (6 comments by @ekinnear, @jan-ivar, @martinthomson)
-
Throwing serverCertificateHashes related errors w3c/webtransport#489 (2 comments by @jan-ivar, @ricea)
-
Congestion control event with everything in WebTranspsort.rateControlFeedback. w3c/webtransport#470 (1 comment by @jan-ivar)
-
GitHub
w3c/webtransport
-
10 issues opened.
-
Final API shape of rate control feedback w3c/webtransport#481, by @jan-ivar.
-
Clarify whether spec supports BYOB readers for Datagrams w3c/webtransport#480, by @jesup.
-
HTTP/2 might be reliable(-only), but datagrams aren't w3c/webtransport#479, by @martinthomson.
-
Rate control privacy considerations w3c/webtransport#478, by @martinthomson.
-
[[sendRate]] is uninitialized w3c/webtransport#477, by @jan-ivar.
-
Does sendRate drop if I stop sending? w3c/webtransport#476, by @jan-ivar.
-
rateControlFeedbackMinInterval is unused w3c/webtransport#475, by @jan-ivar.
-
Reliability is always supports-unreliable w3c/webtransport#472, by @jesup.
-
API behavior when opening a new stream is blocked w3c/webtransport#469, by @vasilvv.
-
Use nested steps instead of "Return promise and run the remaining steps in parallel" pattern w3c/webtransport#466, by @saschanaz.
-
-
8 issues closed.
-
WebTransportError & DOMExceptions w3c/webtransport#459.
-
WebTransportError setup algorithm incorrectly calls DOMException constructor w3c/webtransport#458.
-
Stats for congestion control and bandwidth estimation w3c/webtransport#21.
-
hole punching support w3c/webtransport#429.
-
"QUIC Protocol Action" in #protocol-mapping is misleading w3c/webtransport#410.
-
"if it exists, and * otherwise" should be replaced by the IDL dictionary default value w3c/webtransport#457.
-
Consider aligning WebTransportError with upcoming guidance w3c/webtransport#425.
-
Samples w3c/webtransport#416.
-
-
12 issues received 29 new comments.
-
Clarify whether spec supports BYOB readers for Datagrams w3c/webtransport#480 (7 comments by @jan-ivar, @LPardue, @martinthomson, @ricea)
-
API behavior when opening a new stream is blocked w3c/webtransport#469 (7 comments by @aboba, @ekinnear, @jesup, @martinthomson, @ricea, @wilaw)
-
MAX_STREAM limit (Client→Server) (still need an event when stream ids become available again) w3c/webtransport#446 (3 comments by @jan-ivar, @LPardue, @wilaw)
-
Use nested steps instead of "Return promise and run the remaining steps in parallel" pattern w3c/webtransport#466 (2 comments by @nidhijaju, @saschanaz)
-
expose a TLS Keying Material Exporter / unique value for the TLS session w3c/webtransport#411 (1 comment by @jan-ivar)
-
Review Framework for Accessibility in the Specification of Technologies (FAST) checklist w3c/webtransport#405 (1 comment by @ruoxiran)
-
-
8 pull requests opened.
-
Receiving a GOAWAY frame or DRAIN_WEBTRANSPORT_SESSION capsule w3c/webtransport#482, by @aboba.
-
Supporting "reliable-only" w3c/webtransport#474, by @aboba.
-
Linkify "fire an event" concept to clarify steps and interface w3c/webtransport#473, by @tidoust.
-
Congestion control event with no sub-object w3c/webtransport#471, by @pthatcher.
-
Congestion control event with everything in WebTranspsort.rateControlFeedback. w3c/webtransport#470, by @pthatcher.
-
Use nested steps for steps run in parallel w3c/webtransport#468, by @nidhijaju.
-
Update protocol mapping table w3c/webtransport#467, by @nidhijaju.
-
Add name to Editors list w3c/webtransport#465, by @nidhijaju.
-
-
9 pull requests merged.
-
Linkify "fire an event" concept to clarify steps and interface w3c/webtransport#473.
-
Add rate control event w3c/webtransport#421.
-
Update protocol mapping table w3c/webtransport#467.
-
Add name to Editors list w3c/webtransport#465.
-
Allow ∞ for incoming/outgoingHighWaterMark and incoming/outgoingMaxAge. w3c/webtransport#464.
-
Rely on allowPooling's default value. w3c/webtransport#462.
-
function name mismatch in sample snippet w3c/webtransport#461.
-
Add WebCodecs-Echo to the samples directory w3c/webtransport#430.
-
Align WebTransportError with guidance. w3c/webtransport#460.
-
-
1 pull request closed.
-
Receiving a DRAIN_WEBTRANSPORT_SESSION capsule w3c/webtransport#437.
-
-
6 pull requests received 22 new comments.
Lifecycle
-
1 charter started.
-
Chartered until 31 December 2023.
-
TR publications
-
1 document published.
-
WebTransport published as a Working Draft. History of WebTransport
-
Participants
-
4 participants joined.
-
Dag-Inge Aas (Daily, Co) joined.
-
Colin Bendell (Shopify) joined.
-
Ilya Grigorik (Shopify) joined.
-
Kenichi Ishibashi (Google LLC) joined.
-
-
1 organization joined.
-
Shopify joined.
-
GitHub
w3c/webtransport
-
7 issues opened.
-
Accept ∞ for incoming/outgoingHighWaterMark and incoming/outgoingMaxAge for consistency w3c/webtransport#463, by @jan-ivar.
-
WebTransportError & DOMExceptions w3c/webtransport#459, by @jesup.
-
WebTransportError setup algorithm incorrectly calls DOMException constructor w3c/webtransport#458, by @saschanaz.
-
"if it exists, and * otherwise" should be replaced by the IDL dictionary default value w3c/webtransport#457, by @saschanaz.
-
serverCertificateHashes w3c/webtransport#456, by @jesup.
-
The cleanup procedure is onconsistent with regards to arguments (closeInfo...) w3c/webtransport#454, by @jesup.
-
IncomingStreams pullUnidirectionStream algorithm w3c/webtransport#452, by @jesup.
-
-
6 issues closed.
-
WebTransport/WebCodecs interaction (copies) w3c/webtransport#231.
-
Complete W3C Internationalization (i18n) review checklist w3c/webtransport#404.
-
The cleanup procedure is onconsistent with regards to arguments (closeInfo...) w3c/webtransport#454.
-
Clarify DOMString comparison method in dictionaly WebTransportHash w3c/webtransport#413.
-
Datagram vs stream & relative stream prioritization w3c/webtransport#62.
-
Weighted flows of datagrams and short-lived streams w3c/webtransport#419.
-
-
17 issues received 30 new comments.
-
The cleanup procedure is onconsistent with regards to arguments (closeInfo...) w3c/webtransport#454 (4 comments by @jan-ivar, @jesup)
-
Relative send priority between datagrams and streams w3c/webtransport#451 (4 comments by @bdrtc, @jan-ivar, @wilaw)
-
Human readable error message without language info w3c/webtransport#414 (2 comments by @jan-ivar, @wilaw)
-
Review Framework for Accessibility in the Specification of Technologies (FAST) checklist w3c/webtransport#405 (2 comments by @wilaw)
-
IncomingStreams pullUnidirectionStream algorithm w3c/webtransport#452 (2 comments by @jan-ivar, @jesup)
-
MAX_STREAM limit (Client→Server) (still need an event when stream ids become available again) w3c/webtransport#446 (2 comments by @jan-ivar, @martinthomson)
-
Complete W3C Internationalization (i18n) review checklist w3c/webtransport#404 (1 comment by @wilaw)
-
WebTransportError setup algorithm incorrectly calls DOMException constructor w3c/webtransport#458 (1 comment by @wilaw)
-
Consider aligning WebTransportError with upcoming guidance w3c/webtransport#425 (1 comment by @jan-ivar)
-
w3c/webtransport#62 (1 comment by @jan-ivar)
-
-
6 pull requests opened.
-
Allow ∞ for incoming/outgoingHighWaterMark and incoming/outgoingMaxAge. w3c/webtransport#464, by @jan-ivar.
-
Rely on allowPooling's default value. w3c/webtransport#462, by @jan-ivar.
-
function name mismatch in sample snippet w3c/webtransport#461, by @netizen-ais.
-
Align WebTransportError with guidance. w3c/webtransport#460, by @jan-ivar.
-
Restore #380 after merge accident. w3c/webtransport#455, by @jan-ivar.
-
Update index.bs to clarify DOMString comparison method w3c/webtransport#453, by @wilaw.
-
-
2 pull requests merged.
-
Restore #380 after merge accident. w3c/webtransport#455.
-
Update index.bs to clarify DOMString comparison method w3c/webtransport#453.
-
-
6 pull requests received 32 new comments.
-
Align WebTransportError with guidance. w3c/webtransport#460 (5 comments by @domenic, @jan-ivar, @ricea, @saschanaz)
-
Update index.bs to clarify DOMString comparison method w3c/webtransport#453 (2 comments by @jan-ivar, @wilaw)