WebTransport Working Group - Activity in 2022
No matches.
Participants
-
2 participants joined.
-
Aleix Conchillo Flaqué (Daily, Co) joined.
-
Varun Singh (Daily, Co) joined.
-
-
1 participant left.
-
Yutaka Hirano (Google LLC) left.
-
-
1 organization joined.
-
Daily, Co joined.
-
-
1 organization left.
-
CoSMo Software Consulting Pte Ltd left.
-
GitHub
w3c/webtransport
-
9 issues opened.
-
Relative send priority between datagrams and streams w3c/webtransport#451, by @wilaw.
-
Handling of negative values and 0 for incomingMaxAge w3c/webtransport#450, by @zcorpan.
-
Can we multiplex more than one session per connection in the same browser tab? w3c/webtransport#449, by @pthatcher.
-
Explainer and use-case documents include out-of-scope p2p references w3c/webtransport#447, by @wilaw.
-
MAX_STREAM limit (Client→Server) (still need an event when stream ids become available again) w3c/webtransport#446, by @aboba.
-
implementation wording in the Charter w3c/webtransport#445, by @ylafon.
-
Possible new wording for the implementation / testing criteria w3c/webtransport#444, by @ylafon.
-
Incorrect handling of unpaired surrogates in wt.close({reason}) w3c/webtransport#442, by @jan-ivar.
-
Is WebTransport compatible with Node.js QUIC? w3c/webtransport#439, by @PNys.
-
-
8 issues closed.
-
Do we need to specify default send behavior for web compat? w3c/webtransport#428.
-
Explainer and use-case documents include out-of-scope p2p references w3c/webtransport#447.
-
Incorrect handling of unpaired surrogates in wt.close({reason}) w3c/webtransport#442.
-
allow opening streams and sending datagrams in parallel to the CONNECT request w3c/webtransport#435.
-
Support minimal prioritization necessary to enable IETF MoQ base streaming protocol w3c/webtransport#431.
-
implementation wording in the Charter w3c/webtransport#445.
-
Is WebTransport compatible with Node.js QUIC? w3c/webtransport#439.
-
Should WebTransportSendStream and WebTransportReceiveStream be transferable? w3c/webtransport#424.
-
-
9 issues received 12 new comments.
-
Can we multiplex more than one session per connection in the same browser tab? w3c/webtransport#449 (3 comments by @aboba, @ekinnear, @jan-ivar)
-
Possible new wording for the implementation / testing criteria w3c/webtransport#444 (2 comments by @jan-ivar, @wilaw)
-
MAX_STREAM limit (Client→Server) (still need an event when stream ids become available again) w3c/webtransport#446 (1 comment by @martinthomson)
-
allow opening streams and sending datagrams in parallel to the CONNECT request w3c/webtransport#435 (1 comment by @aboba)
-
-
4 pull requests opened.
-
Update explainer.md and use-cases.md w3c/webtransport#448, by @wilaw.
-
Use USVString for closeInfo.reason w3c/webtransport#443, by @jan-ivar.
-
Define default send order. w3c/webtransport#441, by @jan-ivar.
-
Allow opening streams in parallel to the CONNECT request w3c/webtransport#440, by @aboba.
-
-
6 pull requests merged.
-
Define default send order. w3c/webtransport#441.
-
Update explainer.md and use-cases.md w3c/webtransport#448.
-
Use USVString for closeInfo.reason w3c/webtransport#443.
-
Allow opening streams in parallel to the CONNECT request w3c/webtransport#440.
-
Add sendOrder option to createUnidirectionalStream(). w3c/webtransport#438.
-
Make WebTransportSendStream & WebTransportReceiveStream transferable. w3c/webtransport#433.
-
-
6 pull requests received 44 new comments.
-
Receiving a DRAIN_WEBTRANSPORT_SESSION capsule w3c/webtransport#437 (14 comments by @aboba, @jan-ivar)
-
Add sendOrder option to createUnidirectionalStream(). w3c/webtransport#438 (6 comments by @jan-ivar, @martinthomson)
-
Allow opening streams in parallel to the CONNECT request w3c/webtransport#440 (2 comments by @jan-ivar)
Participants
-
2 participants joined.
-
Harald Alvestrand (Google LLC) joined.
-
Eric Kinnear (Apple Inc.) joined.
-
GitHub
w3c/webtransport
-
4 issues opened.
-
Client initiated drain w3c/webtransport#436, by @wilaw.
-
allow opening streams and sending datagrams in parallel to the CONNECT request w3c/webtransport#435, by @marten-seemann.
-
Draining WebTransport connections w3c/webtransport#432, by @aboba.
-
Support minimal prioritization necessary to enable IETF MoQ base streaming protocol w3c/webtransport#431, by @wilaw.
-
-
1 issue closed.
-
Q: When does writer.write() resolve? w3c/webtransport#402.
-
-
9 issues received 36 new comments.
-
Support minimal prioritization necessary to enable IETF MoQ base streaming protocol w3c/webtransport#431 (10 comments by @aboba, @jan-ivar, @LPardue, @pthatcher, @wilaw)
-
Draining WebTransport connections w3c/webtransport#432 (6 comments by @afrind, @jan-ivar, @pthatcher, @wilaw)
-
Do we need to specify default send behavior for web compat? w3c/webtransport#428 (4 comments by @aboba, @jan-ivar, @pthatcher)
-
allow opening streams and sending datagrams in parallel to the CONNECT request w3c/webtransport#435 (2 comments by @jan-ivar, @martinthomson)
-
expose a TLS Keying Material Exporter / unique value for the TLS session w3c/webtransport#411 (2 comments by @martinthomson, @pthatcher)
-
Consider aligning WebTransportError with upcoming guidance w3c/webtransport#425 (1 comment by @jan-ivar)
-
-
4 pull requests opened.
-
Add sendOrder option to createUnidirectionalStream(). w3c/webtransport#438, by @jan-ivar.
-
Receiving a DRAIN_WEBTRANSPORT_SESSION capsule w3c/webtransport#437, by @aboba.
-
Update examples to not await write(bytes) w3c/webtransport#434, by @jan-ivar.
-
Make WebTransportSendStream & WebTransportReceiveStream transferable. w3c/webtransport#433, by @jan-ivar.
-
-
1 pull request merged.
-
Update examples to not await write(bytes) w3c/webtransport#434.
-
-
5 pull requests received 17 new comments.
-
Receiving a DRAIN_WEBTRANSPORT_SESSION capsule w3c/webtransport#437 (2 comments by @aboba, @vasilvv)
-
Make WebTransportSendStream & WebTransportReceiveStream transferable. w3c/webtransport#433 (1 comment by @ricea)
Participants
-
2 participants joined.
-
Valentin Gosu (Mozilla Foundation) joined.
-
Randell Jesup (Mozilla Foundation) joined.
-
GitHub
w3c/webtransport
-
5 issues opened.
-
hole punching support w3c/webtransport#429, by @marten-seemann.
-
Do we need to specify default send behavior for web compat? w3c/webtransport#428, by @jan-ivar.
-
When flow control is blocked w3c/webtransport#426, by @martinthomson.
-
Consider aligning WebTransportError with upcoming guidance w3c/webtransport#425, by @domenic.
-
Should WebTransportSendStream and WebTransportReceiveStream be transferable? w3c/webtransport#424, by @jan-ivar.
-
-
2 issues closed.
-
Question: Sharing a WebTransport connection in multiple workers? w3c/webtransport#420.
-
WPT's echo server not available for webplatform tests run by wpt.live w3c/webtransport#381.
-
-
1 issue reopened.
-
Q: When does writer.write() resolve? w3c/webtransport#402, by @aboba.
-
-
13 issues received 62 new comments.
-
When flow control is blocked w3c/webtransport#426 (23 comments by @aboba, @afrind, @jan-ivar, @martinthomson, @vasilvv)
-
Weighted flows of datagrams and short-lived streams w3c/webtransport#419 (10 comments by @jan-ivar, @kixelated, @LPardue)
-
Question: Sharing a WebTransport connection in multiple workers? w3c/webtransport#420 (7 comments by @aboba, @jan-ivar)
-
Consider aligning WebTransportError with upcoming guidance w3c/webtransport#425 (5 comments by @jan-ivar, @ricea)
-
Should WebTransportSendStream and WebTransportReceiveStream be transferable? w3c/webtransport#424 (4 comments by @aboba, @jan-ivar, @ricea)
-
expose a TLS Keying Material Exporter / unique value for the TLS session w3c/webtransport#411 (2 comments by @jan-ivar, @martinthomson)
-
w3c/webtransport#125 (1 comment by @dontcallmedom)
-
WPT's echo server not available for webplatform tests run by wpt.live w3c/webtransport#381 (1 comment by @jan-ivar)
-
-
3 pull requests opened.
-
Add WebCodecs-Echo to the samples directory w3c/webtransport#430, by @aboba.
-
Add simple echo sample w3c/webtransport#427, by @aboba.
-
BidirectionalStream's readable and writable lost their types. w3c/webtransport#423, by @jan-ivar.
-
-
2 pull requests merged.
-
Add simple echo sample w3c/webtransport#427.
-
BidirectionalStream's readable and writable lost their types. w3c/webtransport#423.
-
-
1 pull request closed.
-
Add Samples Directory (and WebCodecs Echo Sample) w3c/webtransport#415.
-
-
3 pull requests received 4 new comments.
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
SEUKYOON KANG (Gooroomee Inc.) joined.
-
GitHub
w3c/webtransport
-
3 issues opened.
-
Question: Partial Reliability w3c/webtransport#422, by @aboba.
-
Question: Sharing a WebTransport connection in multiple workers? w3c/webtransport#420, by @aboba.
-
Weighted flows of datagrams and short-lived streams w3c/webtransport#419, by @jan-ivar.
-
-
6 issues received 17 new comments.
-
Weighted flows of datagrams and short-lived streams w3c/webtransport#419 (8 comments by @jan-ivar, @kixelated, @LPardue, @vasilvv)
-
Question: Sharing a WebTransport connection in multiple workers? w3c/webtransport#420 (1 comment by @aboba)
-
w3c/webtransport#21 (1 comment by @aboba)
-
WPT's echo server not available for webplatform tests run by wpt.live w3c/webtransport#381 (1 comment by @aboba)
-
-
2 pull requests opened.
-
Add rate control event w3c/webtransport#421, by @pthatcher.
-
Update link to websockets spec w3c/webtransport#418, by @dontcallmedom.
-
-
1 pull request merged.
-
Update link to websockets spec w3c/webtransport#418.
-
-
1 pull request received 2 new comments.
Participants
-
3 participants joined.
-
Nidhi Jaju (Google LLC) joined.
-
Peter Thatcher (Microsoft Corporation) joined.
-
Lucas Pardue (Cloudflare) joined.
-
-
1 organization joined.
-
Cloudflare joined.
-
GitHub
w3c/webtransport
-
7 issues opened.
-
Add WPT to determine whether reception is interleaved w3c/webtransport#417, by @jan-ivar.
-
Human readable error message without language info w3c/webtransport#414, by @himorin.
-
Clarify DOMString comparison method in dictionaly WebTransportHash w3c/webtransport#413, by @himorin.
-
Abort reason should be serialized w3c/webtransport#412, by @noamr.
-
expose a TLS Keying Material Exporter / unique value for the TLS session w3c/webtransport#411, by @marten-seemann.
-
"QUIC Protocol Action" in #protocol-mapping is misleading w3c/webtransport#410, by @yutakahirano.
-
-
3 issues closed.
-
Pluggable Congestion Control w3c/webtransport#365.
-
Abort reason should be serialized w3c/webtransport#412.
-
Need protocol mappings table for QUIC→streams w3c/webtransport#257.
-
-
11 issues received 16 new comments.
-
w3c/webtransport#62 (2 comments by @jan-ivar)
-
expose a TLS Keying Material Exporter / unique value for the TLS session w3c/webtransport#411 (2 comments by @jan-ivar, @marten-seemann)
-
"QUIC Protocol Action" in #protocol-mapping is misleading w3c/webtransport#410 (1 comment by @jan-ivar)
-
Can we feed the [[OutgoingDatagramsQueue]] without prematurely resolving write promises? w3c/webtransport#400 (1 comment by @jan-ivar)
-
Opening WebTransport streams before the WebTransport session is established w3c/webtransport#409 (1 comment by @jan-ivar)
-
w3c/webtransport#128 (1 comment by @jan-ivar)
-
1 pull request opened.
-
Add Samples Directory (and WebCodecs Echo Sample) w3c/webtransport#415, by @aboba.
-
-
2 pull requests merged.
-
Add congestionControl contructor arg and readonly attribute w3c/webtransport#406.
-
Add protocol mappings table for QUIC→streams and clean close w3c/webtransport#407.
-
-
3 pull requests received 34 new comments.
-
Add Samples Directory (and WebCodecs Echo Sample) w3c/webtransport#415 (23 comments by @aboba, @jan-ivar)
-
Add protocol mappings table for QUIC→streams and clean close w3c/webtransport#407 (7 comments by @jan-ivar, @yutakahirano)
-
Add congestionControl contructor arg and readonly attribute w3c/webtransport#406 (4 comments by @jan-ivar)
-
GitHub
w3c/webtransport
-
2 issues opened.
-
Opening WebTransport streams before the WebTransport session is established w3c/webtransport#409, by @aboba.
-
Rewrite the text of the specification to be independent of the underlying transport w3c/webtransport#408, by @vasilvv.
-
-
5 issues received 5 new comments.
-
w3c/webtransport#62 (1 comment by @kixelated)
-
w3c/webtransport#128 (1 comment by @yutakahirano)
-
w3c/webtransport#59 (1 comment by @jan-ivar)
-
w3c/webtransport#21 (1 comment by @jan-ivar)
-
2 pull requests opened.
-
Add protocol mappings table for QUIC→streams and clean close w3c/webtransport#407, by @jan-ivar.
-
Add congestionControl contructor arg and readonly attribute w3c/webtransport#406, by @jan-ivar.
-
-
2 pull requests received 13 new comments.
-
Add congestionControl contructor arg and readonly attribute w3c/webtransport#406 (8 comments by @jan-ivar, @LPardue, @martinthomson)
-
Add protocol mappings table for QUIC→streams and clean close w3c/webtransport#407 (5 comments by @jan-ivar, @martinthomson, @yutakahirano)
-
TR publications
-
1 document published.
-
WebTransport published as a Working Draft. History of WebTransport
-
GitHub
w3c/webtransport
-
3 issues opened.
-
Review Framework for Accessibility in the Specification of Technologies (FAST) checklist w3c/webtransport#405, by @wilaw.
-
Complete W3C Internationalization (i18n) review checklist w3c/webtransport#404, by @wilaw.
-
Q: When does writer.write() resolve? w3c/webtransport#402, by @jan-ivar.
-
-
5 issues received 24 new comments.
-
Pluggable Congestion Control w3c/webtransport#365 (6 comments by @aboba, @bschlinker, @jan-ivar, @martinthomson)
-
Can we feed the [[OutgoingDatagramsQueue]] without prematurely resolving write promises? w3c/webtransport#400 (2 comments by @jan-ivar)
-
1 pull request opened.
-
html validity w3c/webtransport#403, by @ylafon.
-
-
1 pull request merged.
-
html validity w3c/webtransport#403.
-
Participants
-
1 participant left.
-
Sergio Garcia Murillo (CoSMo Software Consulting Pte Ltd) left.
-
GitHub
w3c/webtransport
-
2 issues opened.
-
Can we feed the [[OutgoingDatagramsQueue]] without prematurely resolving write promises? w3c/webtransport#400, by @jan-ivar.
-
How to correctly set the serverCertificateHashes parameter w3c/webtransport#398, by @wanwusangzhi.
-
-
2 issues closed.
-
How to correctly set the serverCertificateHashes parameter w3c/webtransport#398.
-
Update explainer.md w3c/webtransport#319.
-
-
5 issues received 25 new comments.
-
Can we feed the [[OutgoingDatagramsQueue]] without prematurely resolving write promises? w3c/webtransport#400 (4 comments by @jan-ivar, @MattiasBuelens, @ricea, @yutakahirano)
-
WPT's echo server not available for webplatform tests run by wpt.live w3c/webtransport#381 (2 comments by @jan-ivar, @yutakahirano)
-
2 pull requests opened.
-
Reword HTTP/2 and HTTP/3 pieces of explainer w3c/webtransport#401, by @martinthomson.
-
-
2 pull requests merged.
-
Reword HTTP/2 and HTTP/3 pieces of explainer w3c/webtransport#401.
-
fix typo w3c/webtransport#399.
-
GitHub
w3c/webtransport
-
4 issues closed.
-
Do we need to specify or let apps control receiver-side chunking? w3c/webtransport#396.
-
Per-stream stats w3c/webtransport#372.
-
Cap on 1024 bytes in closeInfo.reason risks clipping multi-byte UTF8 sequence w3c/webtransport#382.
-
Stats: Which ones are appropriate for Http3Transport? w3c/webtransport#206.
-
-
6 issues received 39 new comments.
-
w3c/webtransport#62 (18 comments by @alvestrand, @jan-ivar, @kixelated, @LPardue, @martinthomson, @wilaw)
-
Do we need to specify or let apps control receiver-side chunking? w3c/webtransport#396 (5 comments by @jan-ivar, @yutakahirano)
-
Cap on 1024 bytes in closeInfo.reason risks clipping multi-byte UTF8 sequence w3c/webtransport#382 (2 comments by @wilaw, @yutakahirano)
-
-
1 pull request opened.
-
Ensure the reason string is valid even when clipped w3c/webtransport#397, by @yutakahirano.
-
-
2 pull requests merged.
-
Add per-stream getStats(). w3c/webtransport#395.
-
Ensure the reason string is valid even when clipped w3c/webtransport#397.
-
-
2 pull requests received 4 new comments.
TR publications
-
1 document published.
-
WebTransport published as a Working Draft. History of WebTransport
-
Participants
-
1 participant joined.
-
Brian Baldino (Cisco) joined.
-
-
1 participant left.
-
Tao Mu (Loongson Technology Corporation Limited) left.
-
-
1 organization joined.
-
Cisco joined.
-
GitHub
w3c/webtransport
-
2 issues opened.
-
Do we need to specify or let apps control receiver-side chunking? w3c/webtransport#396, by @jan-ivar.
-
Is connection pooling off the right default? w3c/webtransport#393, by @martinthomson.
-
-
4 issues closed.
-
Datagram priority algorithm fails to account for chunk size of reliable streams w3c/webtransport#388.
-
Alternatively using stats for dropped datagrams w3c/webtransport#97.
-
Fallback support w3c/webtransport#107.
-
Is connection pooling off the right default? w3c/webtransport#393.
-
-
9 issues received 12 new comments.
-
w3c/webtransport#59 (2 comments by @jan-ivar)
-
Do we need to specify or let apps control receiver-side chunking? w3c/webtransport#396 (1 comment by @ricea)
-
Document that chunking boundaries aren't preserved in streams w3c/webtransport#189 (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)
-
Datagram priority algorithm fails to account for chunk size of reliable streams w3c/webtransport#388 (1 comment by @jan-ivar)
-
w3c/webtransport#97 (1 comment by @jan-ivar)
-
3 pull requests opened.
-
Add per-stream getStats(). w3c/webtransport#395, by @jan-ivar.
-
Reduce priority algorithm to normative guidance. w3c/webtransport#394, by @jan-ivar.
-
Add datagrams stats to wt.getStats() w3c/webtransport#392, by @jan-ivar.
-
-
5 pull requests merged.
-
Reduce priority algorithm to normative guidance. w3c/webtransport#394.
-
Add datagrams stats to wt.getStats() w3c/webtransport#392.
-
Add wt.reliability attr and {requireUnreliable} constructor option. w3c/webtransport#385.
-
Improve markup for definitions and automatic links w3c/webtransport#391.
-
Simplify cleanup steps by avoiding type variance. w3c/webtransport#380.
-
-
6 pull requests received 50 new comments.
-
Add per-stream getStats(). w3c/webtransport#395 (17 comments by @dontcallmedom, @jan-ivar, @martinthomson, @ricea)
-
Add wt.reliability attr and {requireUnreliable} constructor option. w3c/webtransport#385 (9 comments by @jan-ivar, @vasilvv)
-
Improve markup for definitions and automatic links w3c/webtransport#391 (9 comments by @dontcallmedom, @jan-ivar, @yutakahirano)
-
Reduce priority algorithm to normative guidance. w3c/webtransport#394 (4 comments by @jan-ivar, @LPardue)
-
Participants
-
2 participants joined.
-
Tao Mu (Loongson Technology Corporation Limited) joined.
-
quanqing li (ByteDance) joined.
-
-
1 organization joined.
-
Loongson Technology Corporation Limited joined.
-
GitHub
w3c/webtransport
-
2 issues opened.
-
Add an example showing receive side throttling w3c/webtransport#389, by @jan-ivar.
-
Datagram priority algorithm fails to account for chunk size of reliable streams w3c/webtransport#388, by @jan-ivar.
-
-
3 issues closed.
-
serverCertificateFingerprints security properties w3c/webtransport#349.
-
Break out stats on retransmits w3c/webtransport#373.
-
Figure out how to expose rolling average stats like RTT w3c/webtransport#374.
-
-
10 issues received 39 new comments.
-
Datagram priority algorithm fails to account for chunk size of reliable streams w3c/webtransport#388 (10 comments by @aboba, @jan-ivar, @LPardue, @martinthomson)
-
Do we want to allow web developers to add headers of the CONNECT request? w3c/webtransport#263 (5 comments by @annevk, @jan-ivar, @jlpettersson)
-
WPT's echo server not available for webplatform tests run by wpt.live w3c/webtransport#381 (2 comments by @aboba, @yutakahirano)
-
w3c/webtransport#107 (2 comments by @jan-ivar)
-
w3c/webtransport#96 (1 comment by @jan-ivar)
-
-
5 pull requests opened.
-
Improve markup for definitions and automatic links w3c/webtransport#391, by @dontcallmedom.
-
Improve markup for definitions and automatic links w3c/webtransport#390, by @dontcallmedom.
-
Add packetsLost to WebTransportStats. w3c/webtransport#387, by @jan-ivar.
-
Add smoothedRtt & rttVariation to WebTransportStats w3c/webtransport#386, by @jan-ivar.
-
Add wt.reliability attr and {requireUnreliable} constructor option. w3c/webtransport#385, by @jan-ivar.
-
-
3 pull requests merged.
-
Elaborate requirements on custom certificate hashes w3c/webtransport#375.
-
Add packetsLost to WebTransportStats. w3c/webtransport#387.
-
Add smoothedRtt & rttVariation to WebTransportStats w3c/webtransport#386.
-
-
1 pull request closed.
-
Improve markup for definitions and automatic links w3c/webtransport#390.
-
-
4 pull requests received 14 new comments.
-
Add packetsLost to WebTransportStats. w3c/webtransport#387 (5 comments by @jan-ivar, @martinthomson)
-
Add smoothedRtt & rttVariation to WebTransportStats w3c/webtransport#386 (4 comments by @jan-ivar, @martinthomson)
-
Elaborate requirements on custom certificate hashes w3c/webtransport#375 (3 comments by @jan-ivar, @vasilvv)
-
Add wt.reliability attr and {requireUnreliable} constructor option. w3c/webtransport#385 (2 comments by @jan-ivar, @martinthomson)
-
Participants
-
4 participants joined.
-
Stefan Holmer (Google LLC) joined.
-
youenn fablet (Apple Inc.) joined.
-
bdrtc bdrtc (ByteDance) joined.
-
Cheng Chen (ByteDance) joined.
-
-
1 organization joined.
-
Apple Inc. joined.
-
GitHub
w3c/webtransport
-
5 issues closed.
-
Stream prioritization w3c/webtransport#33.
-
Stats API Requirements w3c/webtransport#45.
-
Problems with Example 14.6 w3c/webtransport#193.
-
Add server-to-client multicast datagrams as a use case w3c/webtransport#371.
-
-
13 issues received 40 new comments.
-
Block source (incoming) ports w3c/webtransport#376 (11 comments by @DavidSchinazi, @jan-ivar, @LPardue, @ricea)
-
serverCertificateFingerprints security properties w3c/webtransport#349 (6 comments by @davidben, @letitz, @martinthomson, @vasilvv)
-
Figure out how to expose rolling average stats like RTT w3c/webtransport#374 (4 comments by @jan-ivar, @martinthomson, @wilaw)
-
w3c/webtransport#33 (1 comment by @jan-ivar)
-
w3c/webtransport#45 (1 comment by @jan-ivar)
-
w3c/webtransport#67 (1 comment by @jan-ivar)
-
w3c/webtransport#97 (1 comment by @jan-ivar)
-
-
1 pull request opened.
-
Fix stray character in sample source code w3c/webtransport#383, by @slobo.
-
-
1 pull request merged.
-
Fix stray character in sample source code w3c/webtransport#383.
-
-
2 pull requests received 9 new comments.
-
Elaborate requirements on custom certificate hashes w3c/webtransport#375 (7 comments by @jan-ivar, @martinthomson, @vasilvv)
-
Fix stray character in sample source code w3c/webtransport#383 (2 comments by @w3cbot, @yutakahirano)
-