WebTransport Working Group - Activity in 2021
No matches.
GitHub
w3c/webtransport
-
2 issues opened.
-
Cap on 1024 bytes in closeInfo.reason risks clipping multi-byte UTF8 sequence w3c/webtransport#382, by @jan-ivar.
-
WPT's echo server not available for webplatform tests run by wpt.live w3c/webtransport#381, by @jan-ivar.
-
-
3 issues closed.
-
Port blocking w3c/webtransport#229.
-
Session closure without close info w3c/webtransport#366.
-
Security considerations still mentions old APIs w3c/webtransport#136.
-
-
6 issues received 12 new comments.
-
Cap on 1024 bytes in closeInfo.reason risks clipping multi-byte UTF8 sequence w3c/webtransport#382 (4 comments by @annevk, @yutakahirano)
-
WPT's echo server not available for webplatform tests run by wpt.live w3c/webtransport#381 (1 comment by @yutakahirano)
-
Figure out how to expose rolling average stats like RTT w3c/webtransport#374 (1 comment by @martinthomson)
-
-
4 pull requests opened.
-
Simplify cleanup steps by avoiding type variance. w3c/webtransport#380, by @jan-ivar.
-
Make code and reason WebTransportCloseInfo non-optional w3c/webtransport#379, by @yutakahirano.
-
Block ports on fetch's bad ports list & use WebTransportError for it and CSP. w3c/webtransport#378, by @jan-ivar.
-
Use AbortSignal's abort reason to abort SendStream w3c/webtransport#377, by @nidhijaju.
-
-
3 pull requests merged.
-
Block ports on fetch's bad ports list & use WebTransportError for it and CSP. w3c/webtransport#378.
-
Make code and reason WebTransportCloseInfo non-optional w3c/webtransport#379.
-
Use AbortSignal's abort reason to abort SendStream w3c/webtransport#377.
-
-
4 pull requests received 37 new comments.
-
Elaborate requirements on custom certificate hashes w3c/webtransport#375 (25 comments by @davidben, @letitz, @martinthomson, @mikewest, @vasilvv)
-
Make code and reason WebTransportCloseInfo non-optional w3c/webtransport#379 (5 comments by @jan-ivar, @martinthomson)
-
Block ports on fetch's bad ports list & use WebTransportError for it and CSP. w3c/webtransport#378 (4 comments by @annevk, @jan-ivar, @yutakahirano)
-
Use AbortSignal's abort reason to abort SendStream w3c/webtransport#377 (3 comments by @nidhijaju, @w3cbot, @yutakahirano)
-
GitHub
w3c/webtransport
-
1 issue opened.
-
Block source (incoming) ports w3c/webtransport#376, by @jan-ivar.
-
-
4 issues closed.
-
Request forgery/cross-protocol attacks w3c/webtransport#175.
-
Add web-platform-tests w3c/webtransport#125.
-
Clarify that we don't support cookies w3c/webtransport#188.
-
Does CONNECT request mean WebTransport should use fetch? w3c/webtransport#272.
-
-
6 issues received 14 new comments.
-
Figure out how to expose rolling average stats like RTT w3c/webtransport#374 (3 comments by @aboba, @jan-ivar, @martinthomson)
-
Does CONNECT request mean WebTransport should use fetch? w3c/webtransport#272 (2 comments by @annevk, @jan-ivar)
-
w3c/webtransport#125 (1 comment by @jan-ivar)
-
1 pull request opened.
-
Elaborate requirements on custom certificate hashes w3c/webtransport#375, by @vasilvv.
-
-
3 pull requests merged.
-
Remove text on request forgery w3c/webtransport#369.
-
Must not provide any credentials via HTTP headers w3c/webtransport#312.
-
Add Content Security Policy check on request w3c/webtransport#367.
-
-
3 pull requests received 13 new comments.
-
Elaborate requirements on custom certificate hashes w3c/webtransport#375 (8 comments by @martinthomson, @vasilvv)
-
TR publications
-
1 document published.
-
WebTransport published as a Working Draft. History of WebTransport
-
Participants
-
1 participant joined.
-
Stefan Pham (Fraunhofer Gesellschaft) joined.
-
-
1 organization joined.
-
Fraunhofer Gesellschaft joined.
-
GitHub
w3c/webtransport
-
6 issues opened.
-
Figure out how to expose rolling average stats like RTT w3c/webtransport#374, by @jan-ivar.
-
Break out stats on retransmits w3c/webtransport#373, by @jan-ivar.
-
Per-stream stats w3c/webtransport#372, by @jan-ivar.
-
Add server-to-client multicast datagrams as a use case w3c/webtransport#371, by @GrumpyOldTroll.
-
Where is the value of the `Origin` header set? w3c/webtransport#368, by @zcorpan.
-
Session closure without close info w3c/webtransport#366, by @yutakahirano.
-
-
2 issues closed.
-
Where is the value of the `Origin` header set? w3c/webtransport#368.
-
Explainer needs to be updated w3c/webtransport#353.
-
-
9 issues received 22 new comments.
-
Pluggable Congestion Control w3c/webtransport#365 (9 comments by @aboba, @jan-ivar, @martinthomson, @murillo128, @vasilvv, @wilaw)
-
Does CONNECT request mean WebTransport should use fetch? w3c/webtransport#272 (4 comments by @annevk, @jan-ivar, @martinthomson)
-
Where is the value of the `Origin` header set? w3c/webtransport#368 (2 comments by @martinthomson, @yutakahirano)
-
serverCertificateFingerprints security properties w3c/webtransport#349 (2 comments by @jan-ivar, @vasilvv)
-
Figure out how to expose rolling average stats like RTT w3c/webtransport#374 (1 comment by @martinthomson)
-
w3c/webtransport#125 (1 comment by @foolip)
-
-
3 pull requests opened.
-
Explicitly provide the "Origin" header on session establishment w3c/webtransport#370, by @yutakahirano.
-
Remove text on request forgery w3c/webtransport#369, by @martinthomson.
-
Add Content Security Policy check on request w3c/webtransport#367, by @yutakahirano.
-
-
3 pull requests merged.
-
Describe BidirectionalStream's attributes w3c/webtransport#364.
-
Explicitly provide the "Origin" header on session establishment w3c/webtransport#370.
-
Update explainer w3c/webtransport#362.
-
-
4 pull requests received 19 new comments.
-
Add Content Security Policy check on request w3c/webtransport#367 (10 comments by @annevk, @antosart, @martinthomson, @yutakahirano)
-
Explicitly provide the "Origin" header on session establishment w3c/webtransport#370 (4 comments by @yutakahirano, @zcorpan)
-
Describe BidirectionalStream's attributes w3c/webtransport#364 (3 comments by @ricea, @yutakahirano)
-
Participants
-
4 participants joined.
-
changqing yan (ByteDance) joined.
-
ting xu (ByteDance) joined.
-
WEI LI (ByteDance) joined.
-
zhi long (ByteDance) joined.
-
-
1 participant left.
-
Alexandre Gouaillard (CoSMo Software Consulting Pte Ltd) left.
-
GitHub
w3c/webtransport
-
12 issues opened.
-
Pluggable Congestion Control w3c/webtransport#365, by @aboba.
-
Examples in explainer need to be updated w3c/webtransport#361, by @foolip.
-
Is notifications a use case? w3c/webtransport#360, by @foolip.
-
"compute a certificate hash" / "verify a certificate hash" should have explicit parameters w3c/webtransport#359, by @yutakahirano.
-
RTCDtlsFingerprint values are strings w3c/webtransport#355, by @martinthomson.
-
Explainer needs to be updated w3c/webtransport#353, by @wilaw.
-
Security questionnaire needs to be completed for TAG review w3c/webtransport#352, by @wilaw.
-
serverCertificateFingerprints bikeshedding w3c/webtransport#350, by @letitz.
-
serverCertificateFingerprints security properties w3c/webtransport#349, by @letitz.
-
Simplify WebTransportError (use NetworkError for "session" errors) w3c/webtransport#345, by @jan-ivar.
-
Use WebTransportError instead of TypeError for connection init failure w3c/webtransport#344, by @jan-ivar.
-
WebTransportCloseInfo.errorCode bikeshedding w3c/webtransport#342, by @yutakahirano.
-
-
16 issues closed.
-
Is notifications a use case? w3c/webtransport#360.
-
Do we need a pathmigration event? w3c/webtransport#314.
-
RTCDtlsFingerprint values are strings w3c/webtransport#355.
-
Examples in explainer need to be updated w3c/webtransport#361.
-
serverCertificateFingerprints bikeshedding w3c/webtransport#350.
-
WebTransportCloseInfo.errorCode bikeshedding w3c/webtransport#342.
-
Security questionnaire needs to be completed for TAG review w3c/webtransport#352.
-
Decide on allowPooling default value w3c/webtransport#228.
-
Tracker for web-platform-tests. w3c/webtransport#341.
-
Simplify WebTransportError (use NetworkError for "session" errors) w3c/webtransport#345.
-
WebTransportError.ApplicationProtocolCode naming w3c/webtransport#328.
-
Use WebTransportError instead of TypeError for connection init failure w3c/webtransport#344.
-
Deal with reason strings for session closure events w3c/webtransport#336.
-
Do we want to store the code and reason for session closure in WebTransportError? w3c/webtransport#338.
-
Create appropriate instances of WebTransportError w3c/webtransport#334.
-
Datagrams readiness w3c/webtransport#302.
-
-
21 issues received 53 new comments.
-
serverCertificateFingerprints security properties w3c/webtransport#349 (10 comments by @davidben, @estark37, @letitz, @martinthomson, @sleevi, @vasilvv)
-
Pluggable Congestion Control w3c/webtransport#365 (9 comments by @aboba, @LPardue, @martinthomson, @murillo128)
-
Does CONNECT request mean WebTransport should use fetch? w3c/webtransport#272 (4 comments by @annevk, @jan-ivar, @yutakahirano)
-
RTCDtlsFingerprint values are strings w3c/webtransport#355 (4 comments by @martinthomson, @vasilvv, @yutakahirano)
-
problem in testing maximum datagram sending speed w3c/webtransport#152 (3 comments by @xujiasci, @yutakahirano)
-
serverCertificateFingerprints bikeshedding w3c/webtransport#350 (3 comments by @jan-ivar, @martinthomson)
-
Simplify WebTransportError (use NetworkError for "session" errors) w3c/webtransport#345 (2 comments by @jan-ivar, @yutakahirano)
-
Deal with reason strings for session closure events w3c/webtransport#336 (1 comment by @yutakahirano)
-
Do we want to store the code and reason for session closure in WebTransportError? w3c/webtransport#338 (1 comment by @yutakahirano)
-
Use WebTransportError instead of TypeError for connection init failure w3c/webtransport#344 (1 comment by @jan-ivar)
-
-
11 pull requests opened.
-
Describe BidirectionalStream's attributes w3c/webtransport#364, by @yutakahirano.
-
Update explainer w3c/webtransport#362, by @yutakahirano.
-
Use BufferSource for the hash value w3c/webtransport#358, by @yutakahirano.
-
Replace "fingerprint" with "hash" in various names w3c/webtransport#357, by @yutakahirano.
-
Rename WebTransportCloseInfo/errorCode to closeCode w3c/webtransport#356, by @yutakahirano.
-
Answer the security questionnaire w3c/webtransport#354, by @yutakahirano.
-
Fetch's obtain a connection changed slightly w3c/webtransport#351, by @annevk.
-
Replace applicationProtocolCode with streamErrorCode w3c/webtransport#348, by @yutakahirano.
-
Fix indentation of notes w3c/webtransport#347, by @yutakahirano.
-
Replace TypeError with WebTransportError w3c/webtransport#346, by @yutakahirano.
-
Deal with the reason string in WebTransport.close() w3c/webtransport#343, by @yutakahirano.
-
-
11 pull requests merged.
-
Use BufferSource for the hash value w3c/webtransport#358.
-
Replace "fingerprint" with "hash" in various names w3c/webtransport#357.
-
Rename WebTransportCloseInfo/errorCode to closeCode w3c/webtransport#356.
-
Answer the security questionnaire w3c/webtransport#354.
-
Fetch's obtain a connection changed slightly w3c/webtransport#351.
-
Deal with the reason string in WebTransport.close() w3c/webtransport#343.
-
Replace applicationProtocolCode with streamErrorCode w3c/webtransport#348.
-
Replace TypeError with WebTransportError w3c/webtransport#346.
-
Define WebTransportError/create w3c/webtransport#335.
-
Fix indentation of notes w3c/webtransport#347.
-
Prioritize outgoing datagrams over stream data w3c/webtransport#340.
-
-
10 pull requests received 49 new comments.
-
Answer the security questionnaire w3c/webtransport#354 (18 comments by @ricea, @vasilvv, @yutakahirano)
-
Use BufferSource for the hash value w3c/webtransport#358 (10 comments by @jan-ivar, @martinthomson, @yutakahirano)
-
Deal with the reason string in WebTransport.close() w3c/webtransport#343 (3 comments by @yutakahirano)
-
Must not provide any credentials via HTTP headers w3c/webtransport#312 (2 comments by @annevk, @yutakahirano)
-
Replace applicationProtocolCode with streamErrorCode w3c/webtransport#348 (1 comment by @yutakahirano)
-
GitHub
w3c/webtransport
-
12 issues opened.
-
Tracker for web-platform-tests. w3c/webtransport#341, by @jan-ivar.
-
Use case: Dropping stale/out-of-order state datagrams w3c/webtransport#339, by @aigarius.
-
Do we want to store the code and reason for session closure in WebTransportError? w3c/webtransport#338, by @yutakahirano.
-
Deal with reason strings for session closure events w3c/webtransport#336, by @yutakahirano.
-
Create appropriate instances of WebTransportError w3c/webtransport#334, by @yutakahirano.
-
Need to specify what happens if sending bytes fails w3c/webtransport#333, by @ricea.
-
More thorough state persistence treatment w3c/webtransport#332, by @martinthomson.
-
Request TAG review w3c/webtransport#331, by @jan-ivar.
-
WebTransportError.ApplicationProtocolCode naming w3c/webtransport#328, by @yutakahirano.
-
Determine interaction with back forward cache w3c/webtransport#326, by @ricea.
-
How to recover datagrams from "errored" state? w3c/webtransport#320, by @jan-ivar.
-
Update explainer.md w3c/webtransport#319, by @jan-ivar.
-
-
18 issues closed.
-
Need to specify what happens if sending bytes fails w3c/webtransport#333.
-
Using WHATWG streams for stream creation w3c/webtransport#40.
-
Use case: Dropping stale/out-of-order state datagrams w3c/webtransport#339.
-
Request TAG review w3c/webtransport#331.
-
Maybe we shouldn't hog overly generic interface names? w3c/webtransport#199.
-
Defining error codes w3c/webtransport#213.
-
Error codes for stream reset and connection close w3c/webtransport#235.
-
Add custom error property for Application Protocol Error Codes? w3c/webtransport#252.
-
SendStream abort reason w3c/webtransport#294.
-
Error codes that don't fit w3c/webtransport#214.
-
WebTransport.maxDatagramSize bikeshedding w3c/webtransport#301.
-
Need the test server to mirror data. w3c/webtransport#212.
-
How to recover datagrams from "errored" state? w3c/webtransport#320.
-
Should WebTransport streams handle Uint8Array or BufferSource? w3c/webtransport#284.
-
Garbage collection w3c/webtransport#225.
-
"verify a certificate fingerprint" algorithm (almost) always returns false w3c/webtransport#117.
-
Agree on wt.datagrams.outgoingMaxAge vs wt.datagrams.writable.maxAge w3c/webtransport#305.
-
Remove SendStream and ReceiveStream w3c/webtransport#306.
-
-
1 issue reopened.
-
Do we need a pathmigration event? w3c/webtransport#314, by @jan-ivar.
-
-
22 issues received 45 new comments.
-
Do we want to store the code and reason for session closure in WebTransportError? w3c/webtransport#338 (7 comments by @jan-ivar, @yutakahirano)
-
Error codes that don't fit w3c/webtransport#214 (7 comments by @jan-ivar, @ricea, @yuki3, @yutakahirano)
-
Determine interaction with back forward cache w3c/webtransport#326 (4 comments by @fergald, @jan-ivar, @rakina)
-
WebTransportError.ApplicationProtocolCode naming w3c/webtransport#328 (4 comments by @jan-ivar, @vasilvv, @yutakahirano)
-
w3c/webtransport#62 (2 comments by @jan-ivar)
-
Need to specify what happens if sending bytes fails w3c/webtransport#333 (2 comments by @yutakahirano)
-
w3c/webtransport#40 (1 comment by @jan-ivar)
-
Maybe we shouldn't hog overly generic interface names? w3c/webtransport#199 (1 comment by @jan-ivar)
-
Should WebTransport streams handle Uint8Array or BufferSource? w3c/webtransport#284 (1 comment by @jan-ivar)
-
Agree on wt.datagrams.outgoingMaxAge vs wt.datagrams.writable.maxAge w3c/webtransport#305 (1 comment by @jan-ivar)
-
-
11 pull requests opened.
-
Prioritize outgoing datagrams over stream data w3c/webtransport#340, by @yutakahirano.
-
Deal with send failures in SendStream/write w3c/webtransport#337, by @yutakahirano.
-
Define WebTransportError/create w3c/webtransport#335, by @yutakahirano.
-
Prefix BidirectionalStream and DatagramDuplexStream with WebTransport w3c/webtransport#330, by @yutakahirano.
-
Introduce WebTransportError/source w3c/webtransport#329, by @yutakahirano.
-
Specify reason handling in abort() and cancel() w3c/webtransport#327, by @yutakahirano.
-
Fixing example script w3c/webtransport#325, by @wilaw.
-
Fix quotes in example script w3c/webtransport#324, by @wilaw.
-
Use [Clamp] for WebTransportErrorInit.applicationProtocolCode w3c/webtransport#323, by @yutakahirano.
-
Allow BufferSources for outgoing bytes w3c/webtransport#322, by @yutakahirano.
-
Active WebTransport must not be collected w3c/webtransport#321, by @yutakahirano.
-
-
13 pull requests merged.
-
Deal with send failures in SendStream/write w3c/webtransport#337.
-
Prefix BidirectionalStream and DatagramDuplexStream with WebTransport w3c/webtransport#330.
-
Introduce WebTransportError/source w3c/webtransport#329.
-
Specify reason handling in abort() and cancel() w3c/webtransport#327.
-
Use [Clamp] for WebTransportErrorInit.applicationProtocolCode w3c/webtransport#323.
-
Define DatagramDuplexStream.maxDatagramSize w3c/webtransport#311.
-
Fixing example script w3c/webtransport#325.
-
Allow BufferSources for outgoing bytes w3c/webtransport#322.
-
Active WebTransport must not be collected w3c/webtransport#321.
-
Update Security Considerations to reflect WebTransport over HTTP better w3c/webtransport#315.
-
Make fingerprint matching case-insensitive. w3c/webtransport#313.
-
Introduce WebTransportError w3c/webtransport#316.
-
Remove "ReceiveStream" Web IDL interface w3c/webtransport#318.
-
-
2 pull requests closed.
-
Fix quotes in example script w3c/webtransport#324.
-
Add WebTransportError interface. w3c/webtransport#288.
-
-
10 pull requests received 47 new comments.
-
Use [Clamp] for WebTransportErrorInit.applicationProtocolCode w3c/webtransport#323 (16 comments by @martinthomson, @ricea, @vasilvv, @yutakahirano)
-
Specify reason handling in abort() and cancel() w3c/webtransport#327 (12 comments by @martinthomson, @ricea, @yutakahirano)
-
Introduce WebTransportError/source w3c/webtransport#329 (7 comments by @jan-ivar, @ricea, @yutakahirano)
-
Must not provide any credentials via HTTP headers w3c/webtransport#312 (4 comments by @martinthomson, @ricea, @vasilvv)
-
Prioritize outgoing datagrams over stream data w3c/webtransport#340 (3 comments by @vasilvv, @yutakahirano)
-
GitHub
w3c/webtransport
-
6 issues opened.
-
WebTransportError.isInitiatedByClient w3c/webtransport#317, by @yutakahirano.
-
Do we need a pathmigration event? w3c/webtransport#314, by @jan-ivar.
-
Remove SendStream and ReceiveStream w3c/webtransport#306, by @yutakahirano.
-
Agree on wt.datagrams.outgoingMaxAge vs wt.datagrams.writable.maxAge w3c/webtransport#305, by @jan-ivar.
-
Datagrams readiness w3c/webtransport#302, by @yutakahirano.
-
WebTransport.maxDatagramSize bikeshedding w3c/webtransport#301, by @yutakahirano.
-
-
10 issues closed.
-
Call the streams algorithms w3c/webtransport#185.
-
Should we expose stream reset codes to JavaScript? w3c/webtransport#123.
-
Discarding stale incoming datagrams w3c/webtransport#221.
-
What to do with SendStreamParameters? w3c/webtransport#277.
-
extends EventTarget w3c/webtransport#116.
-
Deprecate state and onstatechange on WebTransport w3c/webtransport#292.
-
Lossy protocols utilizing datagrams w3c/webtransport#168.
-
Effect of cancel() or abort() for datagrams w3c/webtransport#197.
-
One-way vs two-way reset on the stream w3c/webtransport#95.
-
-
1 issue reopened.
-
Using WHATWG streams for stream creation w3c/webtransport#40, by @jan-ivar.
-
-
27 issues received 60 new comments.
-
WebTransport.maxDatagramSize bikeshedding w3c/webtransport#301 (4 comments by @jan-ivar, @ricea, @yutakahirano)
-
Agree on wt.datagrams.outgoingMaxAge vs wt.datagrams.writable.maxAge w3c/webtransport#305 (4 comments by @jan-ivar, @ricea, @yutakahirano)
-
Does CONNECT request mean WebTransport should use fetch? w3c/webtransport#272 (3 comments by @annevk, @yutakahirano)
-
Should WebTransport streams handle Uint8Array or BufferSource? w3c/webtransport#284 (3 comments by @jan-ivar, @yutakahirano)
-
w3c/webtransport#96 (2 comments by @yutakahirano)
-
w3c/webtransport#33 (1 comment by @LPardue)
-
w3c/webtransport#21 (1 comment by @aboba)
-
w3c/webtransport#62 (1 comment by @yutakahirano)
-
Maybe we shouldn't hog overly generic interface names? w3c/webtransport#199 (1 comment by @yutakahirano)
-
w3c/webtransport#116 (1 comment by @yutakahirano)
-
w3c/webtransport#95 (1 comment by @vasilvv)
-
13 pull requests opened.
-
Remove "ReceiveStream" Web IDL interface w3c/webtransport#318, by @yutakahirano.
-
Introduce WebTransportError w3c/webtransport#316, by @yutakahirano.
-
Update Security Considerations to reflect WebTransport over HTTP better w3c/webtransport#315, by @vasilvv.
-
Make fingerprint matching case-insensitive. w3c/webtransport#313, by @vasilvv.
-
Must not provide any credentials via HTTP headers w3c/webtransport#312, by @vasilvv.
-
Define DatagramDuplexStream.maxDatagramSize w3c/webtransport#311, by @yutakahirano.
-
Remove StreamAbortInfo and a step for remoteCancelled w3c/webtransport#310, by @yutakahirano.
-
Terminate WebTransport sessions when unloading page w3c/webtransport#309, by @yutakahirano.
-
Make "WebTransport session" scoped w3c/webtransport#308, by @yutakahirano.
-
Remove "SendStream" Web IDL interface w3c/webtransport#307, by @yutakahirano.
-
Incoming streams' pull algorithms should work even when unready w3c/webtransport#304, by @yutakahirano.
-
Remove SendStreamParameters w3c/webtransport#303, by @yutakahirano.
-
Remove .state and .onstatechange attributes w3c/webtransport#300, by @yutakahirano.
-
-
10 pull requests merged.
-
Set up ReceiveStream with proper algorithms w3c/webtransport#297.
-
Remove "SendStream" Web IDL interface w3c/webtransport#307.
-
Remove StreamAbortInfo and a step for remoteCancelled w3c/webtransport#310.
-
Terminate WebTransport sessions when unloading page w3c/webtransport#309.
-
Incoming streams' pull algorithms should work even when unready w3c/webtransport#304.
-
Make "WebTransport session" scoped w3c/webtransport#308.
-
Remove SendStreamParameters w3c/webtransport#303.
-
Allow storing/discarding datagrams while connecting w3c/webtransport#299.
-
Remove .state and .onstatechange attributes w3c/webtransport#300.
-
Refine session establishment error logic w3c/webtransport#296.
-
-
1 pull request closed.
-
Make WebTransport an EventTarget. w3c/webtransport#287.
-
-
13 pull requests received 77 new comments.
-
Set up ReceiveStream with proper algorithms w3c/webtransport#297 (33 comments by @domenic, @ricea, @yutakahirano)
-
Must not provide any credentials via HTTP headers w3c/webtransport#312 (4 comments by @martinthomson, @ricea, @vasilvv, @yutakahirano)
-
Remove StreamAbortInfo and a step for remoteCancelled w3c/webtransport#310 (2 comments by @yutakahirano)
-
Terminate WebTransport sessions when unloading page w3c/webtransport#309 (1 comment by @yutakahirano)
-
Incoming streams' pull algorithms should work even when unready w3c/webtransport#304 (1 comment by @yutakahirano)
-
Participants
-
1 participant joined.
-
Ming Yu (ByteDance) joined.
-
-
1 participant left.
-
Michael Paddon (Google LLC) left.
-
-
1 organization joined.
-
ByteDance joined.
-
GitHub
w3c/webtransport
-
7 issues opened.
-
SendStream abort reason w3c/webtransport#294, by @yutakahirano.
-
Sort out error handling w3c/webtransport#293, by @yutakahirano.
-
Deprecate state and onstatechange on WebTransport w3c/webtransport#292, by @yutakahirano.
-
Reference server implementation w3c/webtransport#291, by @FZambia.
-
Should WebTransport streams handle Uint8Array or BufferSource? w3c/webtransport#284, by @yutakahirano.
-
What to do with SendStreamParameters? w3c/webtransport#277, by @ricea.
-
Does CONNECT request mean WebTransport should use fetch? w3c/webtransport#272, by @annevk.
-
-
19 issues closed.
-
Use Application Error Code in a CONNECTION_CLOSE w3c/webtransport#80.
-
Do we need writable.reset() for "unreliable streams"? w3c/webtransport#260.
-
Two ways to abort read side of the stream w3c/webtransport#94.
-
Remove remaining "For QUIC" and quic-transport references w3c/webtransport#204.
-
Specify session termination w3c/webtransport#268.
-
Sort out error handling w3c/webtransport#293.
-
Datagram backpressure w3c/webtransport#105.
-
Reference server implementation w3c/webtransport#291.
-
QuicTransport consider exposing stream ids w3c/webtransport#124.
-
Should writable.close wait for all the data to be sent to the peer? w3c/webtransport#259.
-
Remove sender.remoteCanceled and receiver.remoteReset? w3c/webtransport#271.
-
SecureContext whole API? or Disable serverCertificateFingerprints for insecure contexts? w3c/webtransport#256.
-
Promise resolving/rejection unless done "synchronously" needs to happen from a task w3c/webtransport#112.
-
Add datagrams.setSendQueueExpiration(long duration)? w3c/webtransport#251.
-
In browser support, tunneling TURN traffic over webtransport w3c/webtransport#270.
-
problem in testing maximum datagram sending speed w3c/webtransport#152.
-
Abort after close w3c/webtransport#165.
-
Let's not make the 'central, single entry-point' mistake again w3c/webtransport#180.
-
Specify how the underlying datagram queue should work w3c/webtransport#187.
-
-
1 issue reopened.
-
Call the streams algorithms w3c/webtransport#185, by @yutakahirano.
-
-
37 issues received 66 new comments.
-
Does CONNECT request mean WebTransport should use fetch? w3c/webtransport#272 (7 comments by @annevk, @letitz, @ricea, @yutakahirano)
-
Should writable.close wait for all the data to be sent to the peer? w3c/webtransport#259 (3 comments by @vasilvv, @yutakahirano)
-
Add custom error property for Application Protocol Error Codes? w3c/webtransport#252 (2 comments by @jan-ivar, @yutakahirano)
-
w3c/webtransport#97 (2 comments by @jan-ivar)
-
Do we want to allow web developers to add headers of the CONNECT request? w3c/webtransport#263 (2 comments by @jan-ivar, @martinthomson)
-
w3c/webtransport#107 (1 comment by @yutakahirano)
-
w3c/webtransport#40 (1 comment by @yutakahirano)
-
w3c/webtransport#95 (1 comment by @yutakahirano)
-
w3c/webtransport#80 (1 comment by @yutakahirano)
-
w3c/webtransport#94 (1 comment by @yutakahirano)
-
Remove remaining "For QUIC" and quic-transport references w3c/webtransport#204 (1 comment by @yutakahirano)
-
w3c/webtransport#105 (1 comment by @wilaw)
-
w3c/webtransport#124 (1 comment by @yutakahirano)
-
w3c/webtransport#115 (1 comment by @martinthomson)
-
w3c/webtransport#125 (1 comment by @yutakahirano)
-
Should WebTransport streams handle Uint8Array or BufferSource? w3c/webtransport#284 (1 comment by @ricea)
-
w3c/webtransport#123 (1 comment by @wilaw)
-
In browser support, tunneling TURN traffic over webtransport w3c/webtransport#270 (1 comment by @jan-ivar)
-
SecureContext whole API? or Disable serverCertificateFingerprints for insecure contexts? w3c/webtransport#256 (1 comment by @jan-ivar)
-
Let's not make the 'central, single entry-point' mistake again w3c/webtransport#180 (1 comment by @jan-ivar)
-
21 pull requests opened.
-
Allow storing/discarding datagrams while connecting w3c/webtransport#299, by @yutakahirano.
-
[Editorial] Remove WebTransport.[[OutgoingStreams]] w3c/webtransport#298, by @yutakahirano.
-
Set up ReceiveStream with proper algorithms w3c/webtransport#297, by @yutakahirano.
-
Refine session establishment error logic w3c/webtransport#296, by @yutakahirano.
-
Have SendStream's write/close abortable w3c/webtransport#295, by @yutakahirano.
-
Merge consecutive "Procedures" sections in ReceiveStream w3c/webtransport#290, by @yutakahirano.
-
"incoming unidirectional" and "outgoing unidirectional" streams w3c/webtransport#289, by @yutakahirano.
-
Add WebTransportError interface. w3c/webtransport#288, by @jan-ivar.
-
Make WebTransport an EventTarget. w3c/webtransport#287, by @jan-ivar.
-
Remove stream.remoteCanceled and stream.remoteReset promises w3c/webtransport#286, by @jan-ivar.
-
Make API [SecureContext] w3c/webtransport#285, by @jan-ivar.
-
Specify SendStream algorithms w3c/webtransport#283, by @yutakahirano.
-
Define [[IncomingUnidirectionalStreams]] w3c/webtransport#282, by @yutakahirano.
-
Describe session termination not initiated by the client w3c/webtransport#281, by @yutakahirano.
-
Modernize createBidirectionalStream() w3c/webtransport#280, by @yutakahirano.
-
Run steps in correct sequences/tasks w3c/webtransport#279, by @yutakahirano.
-
[Editorial] Replace "remote host" with "server" w3c/webtransport#278, by @yutakahirano.
-
Fix the protocol link of "receiving a bidirectional stream" w3c/webtransport#276, by @yutakahirano.
-
[Editorial] Merge UnidirectionalStreamsTransport into WebTransport w3c/webtransport#275, by @yutakahirano.
-
Define "queue a network task" w3c/webtransport#274, by @yutakahirano.
-
chore: use v2 of spec-prod w3c/webtransport#273, by @marcoscaceres.
-
-
19 pull requests merged.
-
[Editorial] Remove WebTransport.[[OutgoingStreams]] w3c/webtransport#298.
-
Have SendStream's write/close abortable w3c/webtransport#295.
-
Describe session termination not initiated by the client w3c/webtransport#281.
-
"incoming unidirectional" and "outgoing unidirectional" streams w3c/webtransport#289.
-
Merge consecutive "Procedures" sections in ReceiveStream w3c/webtransport#290.
-
Modernize createBidirectionalStream() w3c/webtransport#280.
-
Define [[IncomingUnidirectionalStreams]] w3c/webtransport#282.
-
Specify SendStream algorithms w3c/webtransport#283.
-
Remove stream.remoteCanceled and stream.remoteReset promises w3c/webtransport#286.
-
Make API [SecureContext] w3c/webtransport#285.
-
Run steps in correct sequences/tasks w3c/webtransport#279.
-
[Editorial] Replace "remote host" with "server" w3c/webtransport#278.
-
Fix the protocol link of "receiving a bidirectional stream" w3c/webtransport#276.
-
Define datagram backpressure control attributes w3c/webtransport#267.
-
[Editorial] Merge UnidirectionalStreamsTransport into WebTransport w3c/webtransport#275.
-
Define "queue a network task" w3c/webtransport#274.
-
Define WebTransport.incomingBidirectionalStreams in more detail w3c/webtransport#266.
-
Define "cleanup" procedure for WebTransport w3c/webtransport#269.
-
chore: use v2 of spec-prod w3c/webtransport#273.
-
-
14 pull requests received 135 new comments.
-
Define WebTransport.incomingBidirectionalStreams in more detail w3c/webtransport#266 (41 comments by @jan-ivar, @ricea, @yutakahirano)
-
Specify SendStream algorithms w3c/webtransport#283 (21 comments by @jan-ivar, @ricea, @vasilvv, @yutakahirano)
-
Set up ReceiveStream with proper algorithms w3c/webtransport#297 (15 comments by @domenic, @ricea, @yutakahirano)
-
Define datagram backpressure control attributes w3c/webtransport#267 (15 comments by @jan-ivar, @ricea, @yutakahirano)
-
Add WebTransportError interface. w3c/webtransport#288 (12 comments by @jan-ivar, @martinthomson, @ricea, @yutakahirano)
-
Describe session termination not initiated by the client w3c/webtransport#281 (9 comments by @aboba, @jan-ivar, @ricea, @vasilvv, @yutakahirano)
-
Define [[IncomingUnidirectionalStreams]] w3c/webtransport#282 (7 comments by @jan-ivar, @yutakahirano)
-
Define "cleanup" procedure for WebTransport w3c/webtransport#269 (3 comments by @ricea, @yutakahirano)
-
Allow storing/discarding datagrams while connecting w3c/webtransport#299 (1 comment by @yutakahirano)
-
TR publications
-
1 document published.
-
WebTransport published as a First Public Working Draft. History of WebTransport
-
GitHub
w3c/webtransport
-
10 issues opened.
-
Remove sender.remoteCanceled and receiver.remoteReset? w3c/webtransport#271, by @jan-ivar.
-
In browser support, tunneling TURN traffic over webtransport w3c/webtransport#270, by @unicomp21.
-
Specify session termination w3c/webtransport#268, by @yutakahirano.
-
Define Send|Receive|Bidirectional Streams in more detail w3c/webtransport#265, by @yutakahirano.
-
Exposing headers of the CONNECT response w3c/webtransport#264, by @yutakahirano.
-
Do we want to allow web developers to add headers of the CONNECT request? w3c/webtransport#263, by @yutakahirano.
-
Do we need writable.reset() for "unreliable streams"? w3c/webtransport#260, by @yutakahirano.
-
Should writable.close wait for all the data to be sent to the peer? w3c/webtransport#259, by @yutakahirano.
-
Need protocol mappings table for QUIC→streams w3c/webtransport#257, by @jan-ivar.
-
SecureContext whole API? or Disable serverCertificateFingerprints for insecure contexts? w3c/webtransport#256, by @ricea.
-
-
8 issues closed.
-
New connection throttling w3c/webtransport#230.
-
Rename abortWriting() and remove abortReading()? w3c/webtransport#242.
-
Define Send|Receive|Bidirectional Streams in more detail w3c/webtransport#265.
-
Anti-affinity for unreliable datagrams w3c/webtransport#109.
-
HTTP/3 Transport and Alt-Svc w3c/webtransport#78.
-
Is it a good idea to define WebTransport "session"? w3c/webtransport#250.
-
How do we identify these things? w3c/webtransport#77.
-
Coalesce small writes w3c/webtransport#79.
-
-
19 issues received 71 new comments.
-
Do we want to allow web developers to add headers of the CONNECT request? w3c/webtransport#263 (21 comments by @annevk, @jan-ivar, @kixelated, @mnot, @ricea, @vasilvv, @yutakahirano)
-
In browser support, tunneling TURN traffic over webtransport w3c/webtransport#270 (8 comments by @aboba, @murillo128, @unicomp21)
-
Add custom error property for Application Protocol Error Codes? w3c/webtransport#252 (8 comments by @domenic, @jan-ivar, @ricea)
-
Do we need writable.reset() for "unreliable streams"? w3c/webtransport#260 (5 comments by @aboba, @jan-ivar, @ricea, @yutakahirano)
-
Add datagrams.setSendQueueExpiration(long duration)? w3c/webtransport#251 (4 comments by @ricea, @yutakahirano)
-
Need protocol mappings table for QUIC→streams w3c/webtransport#257 (3 comments by @jan-ivar, @ricea)
-
Define Send|Receive|Bidirectional Streams in more detail w3c/webtransport#265 (2 comments by @jan-ivar, @yutakahirano)
-
SecureContext whole API? or Disable serverCertificateFingerprints for insecure contexts? w3c/webtransport#256 (2 comments by @jan-ivar, @vasilvv)
-
Should writable.close wait for all the data to be sent to the peer? w3c/webtransport#259 (2 comments by @jan-ivar, @yutakahirano)
-
w3c/webtransport#107 (1 comment by @aboba)
-
w3c/webtransport#109 (1 comment by @jan-ivar)
-
w3c/webtransport#79 (1 comment by @wilaw)
-
-
7 pull requests opened.
-
Define "cleanup" procedure for WebTransport w3c/webtransport#269, by @yutakahirano.
-
Define datagram backpressure control attributes w3c/webtransport#267, by @yutakahirano.
-
Define WebTransport.incomingBidirectionalStreams in more detail w3c/webtransport#266, by @yutakahirano.
-
Fix Example w3c/webtransport#262, by @hst-m.
-
[Mostly editorial] Merge BidirectionalStreamsTransport into WebTransport w3c/webtransport#261, by @yutakahirano.
-
Merge DatagramTransport mixin into WebTransport w3c/webtransport#258, by @yutakahirano.
-
Create SECURITY.md w3c/webtransport#255, by @Sfaraahfarah.
-
-
6 pull requests merged.
-
Fix Example w3c/webtransport#262.
-
[Mostly editorial] Merge BidirectionalStreamsTransport into WebTransport w3c/webtransport#261.
-
Merge DatagramTransport mixin into WebTransport w3c/webtransport#258.
-
Move datagram related internal slots w3c/webtransport#254.
-
Define WebTransport session and stream w3c/webtransport#253.
-
4 pull requests closed.
-
Some algorithm cleanup split out from #211. w3c/webtransport#234.
-
Add WebTransport* prefix to SendStream, ReceiveStream & BidirectionalStream w3c/webtransport#232.
-
Add transport.bi/unidirectionalStreams duplex streams. w3c/webtransport#211.
-
Create SECURITY.md w3c/webtransport#255.
-
-
13 pull requests received 78 new comments.
-
Rename abortWriting()/writingAborted → reset()/remoteCanceled & abortReading()/readingAborted → cancel()/remoteReset w3c/webtransport#248 (24 comments by @domenic, @jan-ivar, @ricea, @yutakahirano)
-
Define WebTransport.incomingBidirectionalStreams in more detail w3c/webtransport#266 (14 comments by @jan-ivar, @ricea, @yutakahirano)
-
Define "cleanup" procedure for WebTransport w3c/webtransport#269 (11 comments by @jan-ivar, @yutakahirano)
-
Define datagram backpressure control attributes w3c/webtransport#267 (6 comments by @jan-ivar, @yutakahirano)
-
[Mostly editorial] Merge BidirectionalStreamsTransport into WebTransport w3c/webtransport#261 (4 comments by @ricea, @yutakahirano)
-
Add WebTransport* prefix to SendStream, ReceiveStream & BidirectionalStream w3c/webtransport#232 (1 comment by @jan-ivar)
-
Add transport.bi/unidirectionalStreams duplex streams. w3c/webtransport#211 (1 comment by @jan-ivar)
-
GitHub
w3c/webtransport
-
7 issues opened.
-
Add custom error property for Application Protocol Error Codes? w3c/webtransport#252, by @jan-ivar.
-
Add datagrams.setSendQueueExpiration(long duration)? w3c/webtransport#251, by @jan-ivar.
-
Is it a good idea to define WebTransport "session"? w3c/webtransport#250, by @yutakahirano.
-
Rewrite "create" streams algorithms w3c/webtransport#247, by @jan-ivar.
-
Web IDL syntax error w3c/webtransport#246, by @autokagami.
-
Web IDL syntax error w3c/webtransport#245, by @autokagami.
-
Invalid IDL for OutgoingStream and IncomingStream w3c/webtransport#243, by @foolip.
-
-
8 issues closed.
-
Rewrite "create" streams algorithms w3c/webtransport#247.
-
Editorial: Define internal slots outside of algorithms w3c/webtransport#222.
-
Editorial: "internal slot" w3c/webtransport#223.
-
mixin interfaces can't inherit w3c/webtransport#239.
-
Call For Consensus: advance current draft to First Public Working Draft status w3c/webtransport#240.
-
Web IDL syntax error w3c/webtransport#246.
-
Web IDL syntax error w3c/webtransport#245.
-
Invalid IDL for OutgoingStream and IncomingStream w3c/webtransport#243.
-
-
1 issue reopened.
-
WebTransport/WebCodecs interaction (copies) w3c/webtransport#231, by @aboba.
-
-
11 issues received 29 new comments.
-
WebTransport/WebCodecs interaction (copies) w3c/webtransport#231 (6 comments by @aboba, @wilaw, @yutakahirano)
-
Rename abortWriting() and remove abortReading()? w3c/webtransport#242 (5 comments by @aboba, @jan-ivar, @martinthomson, @ricea)
-
Is it a good idea to define WebTransport "session"? w3c/webtransport#250 (4 comments by @jan-ivar, @yutakahirano)
-
Add custom error property for Application Protocol Error Codes? w3c/webtransport#252 (3 comments by @jan-ivar, @ricea, @yutakahirano)
-
Stats: Which ones are appropriate for Http3Transport? w3c/webtransport#206 (3 comments by @jan-ivar)
-
Invalid IDL for OutgoingStream and IncomingStream w3c/webtransport#243 (2 comments by @foolip, @yutakahirano)
-
w3c/webtransport#45 (1 comment by @wilaw)
-
Call For Consensus: advance current draft to First Public Working Draft status w3c/webtransport#240 (1 comment by @wilaw)
-
Editorial: Define internal slots outside of algorithms w3c/webtransport#222 (1 comment by @yutakahirano)
-
-
5 pull requests opened.
-
Move datagram related internal slots w3c/webtransport#254, by @yutakahirano.
-
Define WebTransport session and stream w3c/webtransport#253, by @yutakahirano.
-
Specify incoming datagrams in more detail w3c/webtransport#249, by @yutakahirano.
-
[Editorial] Tidy up "internal slots" w3c/webtransport#244, by @yutakahirano.
-
-
3 pull requests merged.
-
Specify incoming datagrams in more detail w3c/webtransport#249.
-
[Editorial] Tidy up "internal slots" w3c/webtransport#244.
-
Inline mixins IncomingStream and OutgoingStream. w3c/webtransport#241.
-
-
1 pull request closed.
-
Control of datagramWritable Queue w3c/webtransport#179.
-
-
5 pull requests received 61 new comments.
-
Specify incoming datagrams in more detail w3c/webtransport#249 (35 comments by @ddragana, @martinthomson, @ricea, @yutakahirano)
-
Rename abortWriting()/writingAborted → reset()/remoteCanceled & abortReading()/readingAborted → cancel()/remoteReset w3c/webtransport#248 (18 comments by @domenic, @jan-ivar, @martinthomson, @ricea, @yutakahirano)
-
GitHub
w3c/webtransport
-
17 issues opened.
-
Rename abortWriting() and remove abortReading()? w3c/webtransport#242, by @jan-ivar.
-
Call For Consensus: advance current draft to First Public Working Draft status w3c/webtransport#240, by @wilaw.
-
mixin interfaces can't inherit w3c/webtransport#239, by @dontcallmedom.
-
Write up a list of usability pitfalls (streams arriving out of order etc) w3c/webtransport#237, by @jan-ivar.
-
Audit threading model of send datagrams algorithm. w3c/webtransport#236, by @jan-ivar.
-
Error codes for stream reset and connection close w3c/webtransport#235, by @vasilvv.
-
WebTransport/WebCodecs interaction (copies) w3c/webtransport#231, by @aboba.
-
New connection throttling w3c/webtransport#230, by @ricea.
-
Port blocking w3c/webtransport#229, by @ricea.
-
Decide on allowPooling default value w3c/webtransport#228, by @jan-ivar.
-
Garbage collection w3c/webtransport#225, by @yutakahirano.
-
Editorial: "internal slot" w3c/webtransport#223, by @yutakahirano.
-
Editorial: Define internal slots outside of algorithms w3c/webtransport#222, by @yutakahirano.
-
Discarding stale incoming datagrams w3c/webtransport#221, by @yutakahirano.
-
Error codes that don't fit w3c/webtransport#214, by @martinthomson.
-
Defining error codes w3c/webtransport#213, by @martinthomson.
-
Need the test server to mirror data. w3c/webtransport#212, by @jan-ivar.
-
-
9 issues closed.
-
Which scheme to use? w3c/webtransport#198.
-
Half-closed state w3c/webtransport#163.
-
Do we need QuicTransport when we have Http3Transport? w3c/webtransport#148.
-
Multi-source downloads? w3c/webtransport#184.
-
UnidirectionalStream could be simpler w3c/webtransport#210.
-
Interaction with tooling w3c/webtransport#22.
-
Acknowledgements section is wrong w3c/webtransport#200.
-
Add SendStream to UnidirectionalStreamsTransport can be racy w3c/webtransport#70.
-
Better error for when we can't send a datagram? w3c/webtransport#36.
-
-
28 issues received 58 new comments.
-
Editorial: Define internal slots outside of algorithms w3c/webtransport#222 (8 comments by @annevk, @ricea, @yutakahirano)
-
Defining error codes w3c/webtransport#213 (7 comments by @jan-ivar, @LPardue, @martinthomson, @ricea)
-
WebTransport/WebCodecs interaction (copies) w3c/webtransport#231 (2 comments by @aboba, @chcunningham)
-
Write up a list of usability pitfalls (streams arriving out of order etc) w3c/webtransport#237 (2 comments by @martinthomson)
-
Error codes for stream reset and connection close w3c/webtransport#235 (1 comment by @martinthomson)
-
w3c/webtransport#45 (1 comment by @vr000m)
-
w3c/webtransport#59 (1 comment by @jan-ivar)
-
Remove remaining "For QUIC" and quic-transport references w3c/webtransport#204 (1 comment by @aboba)
-
w3c/webtransport#36 (1 comment by @jan-ivar)
-
-
14 pull requests opened.
-
Inline mixins IncomingStream and OutgoingStream. w3c/webtransport#241, by @jan-ivar.
-
Change stream reset code to 8 bits. w3c/webtransport#238, by @vasilvv.
-
Some algorithm cleanup split out from #211. w3c/webtransport#234, by @jan-ivar.
-
Make ReceiveStream readable, and SendStream writable. w3c/webtransport#233, by @jan-ivar.
-
Add WebTransport* prefix to SendStream, ReceiveStream & BidirectionalStream w3c/webtransport#232, by @jan-ivar.
-
Fix Web IDL: "bool" -> "boolean" w3c/webtransport#227, by @tidoust.
-
Editorial: Align with Web IDL specification (and fix references) w3c/webtransport#226, by @autokagami.
-
Replace IETF spec links w3c/webtransport#224, by @yutakahirano.
-
Specify "writeDatagrams" in more detail w3c/webtransport#220, by @yutakahirano.
-
Editorial: Align with Web IDL specification w3c/webtransport#219, by @autokagami.
-
Editorial: Align with Web IDL specification w3c/webtransport#218, by @autokagami.
-
Specify WebTransport initialization in more detail w3c/webtransport#217, by @yutakahirano.
-
Editorial: Align with Web IDL specification w3c/webtransport#216, by @autokagami.
-
Reference QUIC as legend for the terms in the Protocol Mappings table. w3c/webtransport#215, by @jan-ivar.
-
-
11 pull requests merged.
-
Change stream reset code to 8 bits. w3c/webtransport#238.
-
Make ReceiveStream readable, and SendStream writable. w3c/webtransport#233.
-
Specify "writeDatagrams" in more detail w3c/webtransport#220.
-
Reference QUIC as legend for the terms in the Protocol Mappings table. w3c/webtransport#215.
-
Editorial: Align with Web IDL specification (and fix references) w3c/webtransport#226.
-
Fix Web IDL: "bool" -> "boolean" w3c/webtransport#227.
-
Specify WebTransport initialization in more detail w3c/webtransport#217.
-
Replace IETF spec links w3c/webtransport#224.
-
Fix races and respect max stream limit when creating streams. w3c/webtransport#202.
-
Acknowledgements section is wrong w3c/webtransport#207.
-
Remove remaining "For QUIC" and quic-transport references w3c/webtransport#205.
-
-
3 pull requests closed.
-
Editorial: Align with Web IDL specification w3c/webtransport#219.
-
Editorial: Align with Web IDL specification w3c/webtransport#218.
-
Editorial: Align with Web IDL specification w3c/webtransport#216.
-
-
12 pull requests received 46 new comments.
-
Specify "writeDatagrams" in more detail w3c/webtransport#220 (16 comments by @jan-ivar, @ricea, @yutakahirano)
-
Specify WebTransport initialization in more detail w3c/webtransport#217 (14 comments by @aboba, @annevk, @vasilvv, @yutakahirano)
-
Editorial: Align with Web IDL specification (and fix references) w3c/webtransport#226 (3 comments by @aboba, @yutakahirano)
-
Add transport.bi/unidirectionalStreams duplex streams. w3c/webtransport#211 (2 comments by @aboba, @yutakahirano)
-
Fix races and respect max stream limit when creating streams. w3c/webtransport#202 (2 comments by @jan-ivar, @ricea)
-
Add WebTransport* prefix to SendStream, ReceiveStream & BidirectionalStream w3c/webtransport#232 (1 comment by @aboba)
-
Reference QUIC as legend for the terms in the Protocol Mappings table. w3c/webtransport#215 (1 comment by @jan-ivar)
-
GitHub
w3c/webtransport
-
15 issues opened.
-
UnidirectionalStream could be simpler w3c/webtransport#210, by @jan-ivar.
-
Stats: Which ones are appropriate for Http3Transport? w3c/webtransport#206, by @aboba.
-
Remove remaining "For QUIC" and quic-transport references w3c/webtransport#204, by @jan-ivar.
-
Acknowledgements section is wrong w3c/webtransport#200, by @jan-ivar.
-
Maybe we shouldn't hog overly generic interface names? w3c/webtransport#199, by @jan-ivar.
-
Which scheme to use? w3c/webtransport#198, by @jan-ivar.
-
Effect of cancel() or abort() for datagrams w3c/webtransport#197, by @aboba.
-
Problems with Example 14.6 w3c/webtransport#193, by @aboba.
-
Shall we define transport concept? w3c/webtransport#191, by @yutakahirano.
-
Add example showing streaming of large data over datagrams performantly w3c/webtransport#190, by @jan-ivar.
-
Document that chunking boundaries aren't preserved in streams w3c/webtransport#189, by @martinthomson.
-
Clarify that we don't support cookies w3c/webtransport#188, by @jan-ivar.
-
Specify how the underlying datagram queue should work w3c/webtransport#187, by @jan-ivar.
-
Rename 'master' branch to 'main' at W3C request w3c/webtransport#186, by @wilaw.
-
Call the streams algorithms w3c/webtransport#185, by @jan-ivar.
-
-
11 issues closed.
-
Use "in parallel" concept defined in the HTML Standard w3c/webtransport#111.
-
Relation to HTTP3, "upgrades"? w3c/webtransport#118.
-
API design w3c/webtransport#126.
-
Make transport.datagram a duplex stream? w3c/webtransport#181.
-
Shall we define transport concept? w3c/webtransport#191.
-
(new WebTransport(protocol)).pipe w3c/webtransport#178.
-
Consequences of the IETF single protocol decision for connection construction w3c/webtransport#183.
-
Mapping to QUIC w3c/webtransport#137.
-
Datagrams always supported? w3c/webtransport#164.
-
Rename 'master' branch to 'main' at W3C request w3c/webtransport#186.
-
Is consent freshness really necessary? w3c/webtransport#174.
-
-
1 issue reopened.
-
Stats API Requirements w3c/webtransport#45, by @jan-ivar.
-
-
29 issues received 74 new comments.
-
Consequences of the IETF single protocol decision for connection construction w3c/webtransport#183 (11 comments by @jan-ivar, @lgrahl, @ricea, @yutakahirano)
-
Add example showing streaming of large data over datagrams performantly w3c/webtransport#190 (4 comments by @aboba, @jan-ivar)
-
w3c/webtransport#45 (3 comments by @jan-ivar)
-
w3c/webtransport#40 (3 comments by @jan-ivar)
-
Specify how the underlying datagram queue should work w3c/webtransport#187 (3 comments by @aboba, @jan-ivar)
-
Document that chunking boundaries aren't preserved in streams w3c/webtransport#189 (3 comments by @aboba, @jan-ivar, @martinthomson)
-
Rename 'master' branch to 'main' at W3C request w3c/webtransport#186 (3 comments by @martinthomson, @wilaw)
-
w3c/webtransport#70 (2 comments by @jan-ivar)
-
Effect of cancel() or abort() for datagrams w3c/webtransport#197 (2 comments by @jan-ivar, @yutakahirano)
-
Do we need QuicTransport when we have Http3Transport? w3c/webtransport#148 (2 comments by @aboba, @jan-ivar)
-
Remove remaining "For QUIC" and quic-transport references w3c/webtransport#204 (1 comment by @aboba)
-
w3c/webtransport#118 (1 comment by @jan-ivar)
-
w3c/webtransport#67 (1 comment by @jan-ivar)
-
w3c/webtransport#126 (1 comment by @jan-ivar)
-
w3c/webtransport#79 (1 comment by @jan-ivar)
-
w3c/webtransport#22 (1 comment by @jan-ivar)
-
w3c/webtransport#36 (1 comment by @jan-ivar)
-
w3c/webtransport#93 (1 comment by @jan-ivar)
-
w3c/webtransport#105 (1 comment by @jan-ivar)
-
-
12 pull requests opened.
-
Add transport.bi/unidirectionalStreams duplex streams. w3c/webtransport#211, by @jan-ivar.
-
Use wt in examples in place of transport. w3c/webtransport#209, by @jan-ivar.
-
Update draft-vvv-webtransport-http3 reference w3c/webtransport#208, by @aboba.
-
Acknowledgements section is wrong w3c/webtransport#207, by @aboba.
-
Remove remaining "For QUIC" and quic-transport references w3c/webtransport#205, by @aboba.
-
Fix remaining case of s/in background/in parallel/ w3c/webtransport#203, by @jan-ivar.
-
Fix races and respect max stream limit when creating streams. w3c/webtransport#202, by @jan-ivar.
-
Fix races and respect max stream limit when creating streams. w3c/webtransport#201, by @jan-ivar.
-
Single protocol decision/Removal of Quic-Transport w3c/webtransport#196, by @aboba.
-
Mapping to QUIC w3c/webtransport#195, by @aboba.
-
Fixes for Example 14.6 w3c/webtransport#194, by @aboba.
-
Add transport.datagrams duplex stream + algorithm outline. w3c/webtransport#192, by @jan-ivar.
-
-
9 pull requests merged.
-
Fix remaining case of s/in background/in parallel/ w3c/webtransport#203.
-
Use wt in examples in place of transport. w3c/webtransport#209.
-
Update draft-vvv-webtransport-http3 reference w3c/webtransport#208.
-
Add transport.datagrams duplex stream + algorithm outline. w3c/webtransport#192.
-
Single protocol decision/Removal of Quic-Transport w3c/webtransport#196.
-
Mapping to QUIC w3c/webtransport#195.
-
Fixes for Example 14.6 w3c/webtransport#194.
-
Improve examples. w3c/webtransport#182.
-
Remove "consent freshness" requirement w3c/webtransport#177.
-
-
2 pull requests closed.
-
Fix races and respect max stream limit when creating streams. w3c/webtransport#201.
-
Mapping to QUIC w3c/webtransport#176.
-
-
11 pull requests received 39 new comments.
-
Control of datagramWritable Queue w3c/webtransport#179 (10 comments by @aboba, @jan-ivar, @yutakahirano)
-
Add transport.datagrams duplex stream + algorithm outline. w3c/webtransport#192 (8 comments by @domenic, @jan-ivar, @vasilvv, @yutakahirano)
-
Fix races and respect max stream limit when creating streams. w3c/webtransport#202 (4 comments by @ricea)
-
Update draft-vvv-webtransport-http3 reference w3c/webtransport#208 (2 comments by @aboba, @yutakahirano)
-
Single protocol decision/Removal of Quic-Transport w3c/webtransport#196 (2 comments by @aboba, @jan-ivar)
-
Remove remaining "For QUIC" and quic-transport references w3c/webtransport#205 (1 comment by @aboba)
-
Fix races and respect max stream limit when creating streams. w3c/webtransport#201 (1 comment by @jan-ivar)
-
Participants
-
3 participants left.
-
Jaco Myburg (Entersekt) left.
-
Gerhard Oosthuizen (Entersekt) left.
-
Andreas Tai (IRT Institut fuer Rundfunktechnik) left.
-
-
3 organizations joined.
-
Gooroomee Inc. joined.
-
CoSMo Software Consulting Pte Ltd joined.
-
Intel Corporation joined.
-
GitHub
w3c/webtransport
-
5 issues opened.
-
Multi-source downloads? w3c/webtransport#184, by @balupton.
-
Consequences of the IETF single protocol decision for connection construction w3c/webtransport#183, by @wilaw.
-
Make transport.datagram a duplex stream? w3c/webtransport#181, by @jan-ivar.
-
Let's not make the 'central, single entry-point' mistake again w3c/webtransport#180, by @lgrahl.
-
(new WebTransport(protocol)).pipe w3c/webtransport#178, by @Ayms.
-
-
8 issues received 26 new comments.
-
Let's not make the 'central, single entry-point' mistake again w3c/webtransport#180 (5 comments by @jan-ivar, @lgrahl, @yutakahirano)
-
w3c/webtransport#40 (4 comments by @jan-ivar)
-
Make transport.datagram a duplex stream? w3c/webtransport#181 (2 comments by @jan-ivar, @yutakahirano)
-
Request forgery/cross-protocol attacks w3c/webtransport#175 (2 comments by @jan-ivar, @martinthomson)
-
Consequences of the IETF single protocol decision for connection construction w3c/webtransport#183 (1 comment by @jan-ivar)
-
w3c/webtransport#128 (1 comment by @aboba)
-
2 pull requests opened.
-
Improve examples. w3c/webtransport#182, by @jan-ivar.
-
Control of datagramWritable Queue w3c/webtransport#179, by @aboba.
-
-
4 pull requests received 15 new comments.