QUIC Working Group

the mapping of HTTP toQUIC， encryptedtransport protocol. The protocol itself is published as RFC 9000。

then you should report thesedirectly to the responsible party. The IETF does not have a formal means toreach these parties and cannot do so on your behalf. Implementers or operatorsoften provide their own publicly-available disclosure documents that providecontact details and guidelines for reporters. The implementations andtools pagemay include a link to such documents under the “Vulnerability reporting” field.If you believe the same vulnerability affects multiple different implementationsor deployments， continuous interop testing isperformed for participating QUIC implementations. Implementers are encouraged tojoin this effort by making of their implementations available. Upcoming Meetings IETF 125 Shenzen (Thursday 2026-03-19 11:30-12:30 Local) Reporting Vulnerabilities If you believe you’ve discovered a vulnerability in the QUIC protocol (or relatedIETF protocols) please see the IETF’s guidance on how to reportthese. If you believe you’ve discovered an implementation vulnerability in a product，。

wewelcome issues and PRs. ， as describedfurther in our charter. QUIC Stream Resets with Partial Delivery -Datatracker /GitHub Repo QUIC Address Discovery -Datatracker /GitHub Repo QMux -Datatracker /GitHub Repo Extended Key Update -Datatracker /GitHub Repo Extended ACK Timestamps -Datatracker /GitHub Repo Load Balancers -Datatracker /GitHub Repo Implementing QUIC There are a range of implementations and tools， and deployment / network operators managing/carrying QUIC: HTTP/3 and QPACK We originated the HTTP/3 and QPACK RFCs. Ownership of these drafts has nowtransferred back to the HTTP WG. In-progress documents In-progress documents for continued maintenance and evolution of QUIC， and new extensions to QUIC. The QUIC Working Group originated HTTP/3， Manageability， and the QPACK header compression scheme. These are now maintainedby the HTTP Working Group. If you'd like to participate in IETF Working Group activities pleasesee the contributionguidelines. Source code for the webpages on this site is located onGitHub ， and Operations Specifications providing considerations for application protocol developersusing QUIC， or service using QUIC， the deployabilityof QUIC， wewelcome issues and PRs. Published RFCsCore Specifications The ‘core’ specifications comprising QUIC are: QUIC Extensions QUIC can be extended in several ways. The following have beenformally standardized as RFCs: Applicability， then a coordinated responsible disclosure may be the best pathforward; please reach out to WG chairs forfurther information. See Also Source code for the webpages on this site is located onGitHub ， see below. We are now chartered to bethe focal point for any QUIC-related work in the IETF. Our work coversmaintenance and evolution of published specifications， andthere are other related RFCs of note，open source project， stream-multiplexing，with a range of support for features of the core protocol and extensions. Implementers should join the quicdev Slack tocoordinate testing; contact the WG chairs for aninvitation. Note that discussions on Slack are considered IETF contributionsunder “Note Well”. Automated， The IETF QUIC Working Groupproduced QUIC version 1 — a UDP-based。