We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Now that HTTP/3 is being updated per ietf-wg-webtrans/draft-ietf-webtrans-http3#143, ietf-wg-webtrans/draft-ietf-webtrans-http3#141, ietf-wg-webtrans/draft-ietf-webtrans-http3#140, and ietf-wg-webtrans/draft-ietf-webtrans-http3#135, we should update HTTP/2 to match.
See ietf-wg-webtrans/draft-ietf-webtrans-http3#135 (comment)
The text was updated successfully, but these errors were encountered:
Chair: discussed at IETF 120. Eric presented some slides. We got a few thumbs up from the room and no concerns, so this is ready for a PR.
Sorry, something went wrong.
ekinnear
No branches or pull requests
Now that HTTP/3 is being updated per ietf-wg-webtrans/draft-ietf-webtrans-http3#143, ietf-wg-webtrans/draft-ietf-webtrans-http3#141, ietf-wg-webtrans/draft-ietf-webtrans-http3#140, and ietf-wg-webtrans/draft-ietf-webtrans-http3#135, we should update HTTP/2 to match.
See ietf-wg-webtrans/draft-ietf-webtrans-http3#135 (comment)
The text was updated successfully, but these errors were encountered: