Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / w3c/webtransport issues and pull requests

#520 - Do we need to say something about default priority and fairness?

Issue - State: closed - Opened by jan-ivar over 1 year ago - 2 comments
Labels: Ready for PR

#519 - Add automated glass-glass latency calculation via RVFC

Pull Request - State: closed - Opened by aboba over 1 year ago
Labels: Editors can integrate

#518 - WebTransport http2 idea's suggestions

Issue - State: closed - Opened by martenrichter over 1 year ago - 15 comments
Labels: Discuss at next meeting

#517 - Sorry for the interruption

Issue - State: closed - Opened by lemanschik over 1 year ago - 2 comments

#516 - WPT tests are needed for sendOrder

Issue - State: open - Opened by jesup over 1 year ago - 2 comments

#515 - Priority groups

Issue - State: closed - Opened by vasilvv over 1 year ago - 15 comments
Labels: Ready for PR

#512 - Update normative key words

Pull Request - State: closed - Opened by wilaw over 1 year ago

#511 - Node.js support for WebTransport

Issue - State: open - Opened by wilaw over 1 year ago - 12 comments

#510 - Add sendStream.sendOrder = n attribute.

Pull Request - State: closed - Opened by jan-ivar over 1 year ago - 1 comment

#509 - Make streamErrorCode 32-bit long

Pull Request - State: closed - Opened by vasilvv over 1 year ago
Labels: Needs test

#508 - Confirm behaviour of server certificates.

Issue - State: closed - Opened by hamishwillee over 1 year ago - 7 comments
Labels: Editorial, PR exists

#507 - Should incomingUni/BidirectionalStreams be "owning"?

Issue - State: open - Opened by jan-ivar over 1 year ago - 2 comments
Labels: Waiting-for-feedback

#506 - WebTransport new features

Issue - State: closed - Opened by MuratovBektur over 1 year ago - 2 comments

#505 - Normative key words

Issue - State: closed - Opened by LPardue over 1 year ago
Labels: Ready for PR

#503 - Update BFCache interaction

Pull Request - State: closed - Opened by nidhijaju over 1 year ago - 3 comments

#502 - Add getAtomicWriter() API.

Pull Request - State: closed - Opened by jan-ivar over 1 year ago - 12 comments

#502 - Add getAtomicWriter() API.

Pull Request - State: closed - Opened by jan-ivar over 1 year ago - 12 comments

#499 - API handling of redirects

Issue - State: closed - Opened by vasilvv over 1 year ago - 8 comments
Labels: Ready for PR

#497 - Support sendRateEstimate for pooled connections

Issue - State: closed - Opened by jan-ivar over 1 year ago - 3 comments
Labels: Ready for PR

#492 - Allow updating send order for streams

Issue - State: closed - Opened by vasilvv over 1 year ago - 1 comment
Labels: Ready for PR

#489 - Throwing serverCertificateHashes related errors

Pull Request - State: closed - Opened by nidhijaju over 1 year ago - 2 comments

#476 - Does sendRate drop if I stop sending?

Issue - State: closed - Opened by jan-ivar almost 2 years ago - 7 comments
Labels: Discuss at next meeting

#463 - Accept ∞ for incoming/outgoingHighWaterMark and incoming/outgoingMaxAge for consistency

Issue - State: closed - Opened by jan-ivar almost 2 years ago - 2 comments
Labels: Ready for PR

#456 - serverCertificateHashes

Issue - State: closed - Opened by jesup almost 2 years ago - 1 comment
Labels: Editorial, PR exists

#452 - IncomingStreams pullUnidirectionStream algorithm

Issue - State: closed - Opened by jesup almost 2 years ago - 3 comments
Labels: Editorial

#451 - Relative send priority between datagrams and streams

Issue - State: closed - Opened by wilaw almost 2 years ago - 13 comments
Labels: Ready for PR

#449 - Can we multiplex more than one session per connection in the same browser tab?

Issue - State: closed - Opened by pthatcher almost 2 years ago - 4 comments
Labels: Discuss at next meeting

#446 - MAX_STREAM limit (Client→Server) (still need an event when stream ids become available again)

Issue - State: closed - Opened by aboba almost 2 years ago - 16 comments
Labels: Ready for PR

#444 - Possible new wording for the implementation / testing criteria

Issue - State: closed - Opened by ylafon almost 2 years ago - 3 comments
Labels: Ready for PR

#436 - Client initiated drain

Issue - State: closed - Opened by wilaw about 2 years ago - 20 comments
Labels: Ready for PR, IETF dependency

#436 - Client initiated drain

Issue - State: open - Opened by wilaw about 2 years ago - 12 comments
Labels: Ready for PR, Discuss at next meeting

#426 - When flow control is blocked

Issue - State: closed - Opened by martinthomson about 2 years ago - 27 comments
Labels: Ready for PR

#417 - Add WPT to determine whether reception is interleaved

Issue - State: open - Opened by jan-ivar about 2 years ago - 1 comment
Labels: Ready for PR

#414 - Human readable error message without language info

Issue - State: closed - Opened by himorin over 2 years ago - 4 comments
Labels: i18n-needs-resolution, Ready for PR

#414 - Human readable error message without language info

Issue - State: closed - Opened by himorin over 2 years ago - 4 comments
Labels: i18n-needs-resolution, Ready for PR

#411 - expose a TLS Keying Material Exporter / unique value for the TLS session

Issue - State: open - Opened by marten-seemann over 2 years ago - 24 comments
Labels: Discuss at next meeting

#408 - Rewrite the text of the specification to be independent of the underlying transport

Issue - State: closed - Opened by vasilvv over 2 years ago - 1 comment
Labels: Ready for PR

#389 - Add an example showing receive side throttling

Issue - State: open - Opened by jan-ivar almost 3 years ago - 3 comments
Labels: Ready for PR

#376 - Block source (incoming) ports

Issue - State: closed - Opened by jan-ivar about 3 years ago - 17 comments
Labels: Ready for PR

#365 - Pluggable Congestion Control

Issue - State: closed - Opened by aboba about 3 years ago - 41 comments
Labels: Discuss at next meeting

#359 - "compute a certificate hash" / "verify a certificate hash" should have explicit parameters

Issue - State: closed - Opened by yutakahirano about 3 years ago
Labels: Editorial, PR exists

#317 - WebTransportError.isInitiatedByClient

Issue - State: open - Opened by yutakahirano over 3 years ago - 3 comments
Labels: Ready for PR

#263 - Do we want to allow web developers to add headers of the CONNECT request?

Issue - State: open - Opened by yutakahirano over 3 years ago - 36 comments

#237 - Write up a list of usability pitfalls (streams arriving out of order etc)

Issue - State: open - Opened by jan-ivar over 3 years ago - 2 comments
Labels: Ready for PR, Editorial

#236 - Audit threading model of send datagrams algorithm.

Issue - State: open - Opened by jan-ivar over 3 years ago - 1 comment
Labels: Ready for PR

#190 - Add example showing streaming of large data over datagrams performantly

Issue - State: open - Opened by jan-ivar almost 4 years ago - 4 comments
Labels: Ready for PR

#131 - Zero copy support via BYOB (add an example)

Issue - State: closed - Opened by aboba over 4 years ago - 13 comments
Labels: Editorial, PR exists

#128 - Connection sharing/pooling

Issue - State: closed - Opened by aboba over 4 years ago - 14 comments
Labels: Discuss at next meeting

#127 - behavior for close connection when browser reload & close

Issue - State: open - Opened by Jxck over 4 years ago - 13 comments
Labels: Ready for PR

#115 - Section 8.1: Crypto-agility in certificate hash verification

Issue - State: open - Opened by aboba over 4 years ago - 1 comment
Labels: Ready for PR

#96 - Spec should define how the feature interacts with blocking tools (filterlists etc.)

Issue - State: closed - Opened by pes10k almost 5 years ago - 16 comments
Labels: privacy-needs-resolution

#59 - CSP policies for WebTransport?

Issue - State: open - Opened by markafoltz about 5 years ago - 30 comments
Labels: Discuss at next meeting