-
Notifications
You must be signed in to change notification settings - Fork 51
Issues: w3c/webtransport
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
When should a client initiated unidirectional stream be available on the server side?
Discuss at next meeting
Flags an issue to be discussed at the next WG working
Ready for PR
Reference overview doc instead of HTTP3 doc in two places
IETF dependency
#616
opened Sep 10, 2024 by
jan-ivar
Specify keep-alive and idle timeouts
Discuss at next meeting
Flags an issue to be discussed at the next WG working
Relative prioritization of streams and datagrams
Discuss at next meeting
Flags an issue to be discussed at the next WG working
Ready for PR
Should incomingUni/BidirectionalStreams be "owning"?
Waiting-for-feedback
Waiting on requested input or feedback
expose a TLS Keying Material Exporter / unique value for the TLS session
Discuss at next meeting
Flags an issue to be discussed at the next WG working
Ready for PR
Can we feed the [[OutgoingDatagramsQueue]] without prematurely resolving write promises?
hard
Things to discuss and think about
Write up a list of usability pitfalls (streams arriving out of order etc)
Editorial
This is an editorial PR that can be merged by editors without discussion
Ready for PR
Document that chunking boundaries aren't preserved in streams
Editorial
This is an editorial PR that can be merged by editors without discussion
CSP policies for WebTransport?
Discuss at next meeting
Flags an issue to be discussed at the next WG working
Ready for PR
ProTip!
Updated in the last three days: updated:>2024-10-05.