Meta tags:

Headings (most frequently used words):

quic, and, published, rfcs, in, progress, documents, implementing, upcoming, meetings, reporting, vulnerabilities, see, also, core, specifications, extensions, applicability, manageability, operations, http, qpack,

Text of the page (most frequently used words):
quic (31), the (30), and (19), github (13), rfc (13), for (11), repo (11), datatracker (11), ietf (8), http (8), working (7), group (7), you (7), protocol (7), are (7), implementations (6), these (5), rfcs (5), see (4), vulnerability (4), documents (4), qpack (4), transport (4), specifications (4), version (4), source (3), this (3), believe (3), using (3), implementers (3), please (3), related (3), note (3), core (3), extensions (3), extended (3), progress (3), now (3), published (3), code (2), webpages (2), site (2), located (2), welcome (2), issues (2), prs (2), agendas (2), minutes (2), etc (2), materials (2), discovered (2), then (2), should (2), report (2), responsible (2), have (2), reach (2), operators (2), provide (2), their (2), available (2), disclosure (2), that (2), contact (2), guidelines (2), may (2), under (2), reporting (2), further (2), chairs (2), tools (2), join (2), compatible (2), testing (2), slack (2), there (2), range (2), with (2), stream (2), event (2), definitions (2), maintenance (2), evolution (2), our (2), originated (2), drafts (2), manageability (2), applicability (2), secure (2), udp (2), based (2), 9000 (2), work (2), also, implementation, product, open, project, service, directly, party, does, not, formal, means, parties, cannot, your, behalf, often, own, publicly, details, reporters, page, include, link, such, field, same, affects, multiple, different, deployments, coordinated, best, path, forward, out, information, protocols, guidance, how, vulnerabilities, 125, shenzen, thursday, 2026, local, upcoming, meetings, performed, participating, encouraged, effort, making, docker, images, automated, continuous, interop, coordinate, invitation, discussions, considered, contributions, well, quicdev, support, features, implementing, load, balancers, ack, timestamps, key, update, qmux, address, discovery, resets, partial, delivery, qlog, main, logging, schema, acknowledgement, frequency, multipath, continued, described, charter, 9204, 9114, ownership, has, transferred, back, 9312, 9308, providing, considerations, application, developers, deployment, network, managing, carrying, operations, 9369, negotiation, 9368, greasing, bit, 9287, unreliable, datagram, extension, 9221, can, several, ways, following, been, formally, standardized, loss, detection, congestion, control, 9002, tls, 9001, multiplexed, independent, properties, 8999, comprising, like, participate, activities, contribution, mapping, header, compression, scheme, maintained, focal, point, any, covers, deployability, new, chartered, produced, multiplexing, encrypted, itself, other, below, survey, packet, sizes, pmtud, codepoint, selector, external, more, resources, home, current,

Text of the page (random words):
quic working group home current rfcs in progress drafts implementations more resources working group materials minutes agendas etc codepoint selector external survey of packet sizes and pmtud the ietf quic working group produced quic version 1 a udp based stream multiplexing encrypted transport protocol the protocol itself is published as rfc 9000 and there are other related rfcs of note see below we are now chartered to be the focal point for any quic related work in the ietf our work covers maintenance and evolution of published specifications the deployability of quic and new extensions to quic the quic working group originated http 3 the mapping of http to quic and the qpack header compression scheme these are now maintained by the http working group if you d like to participate in ietf working group activities please see the contribution guidelines source code for the webpages on this site is located on github we welcome issues and prs published rfcs core specifications the core specifications comprising quic are rfc 8999 version independent properties of quic rfc 9000 quic a udp based multiplexed and secure transport rfc 9001 using tls to secure quic rfc 9002 quic loss detection and congestion control quic extensions quic can be extended in several ways the following have been formally standardized as rfcs rfc 9221 an unreliable datagram extension to quic rfc 9287 greasing the quic bit rfc 9368 compatible version negotiation for quic rfc 9369 quic version 2 applicability manageability and operations specifications providing considerations for application protocol developers using quic and deployment network operators managing carrying quic rfc 9308 applicability of the quic transport protocol rfc 9312 manageability of the quic transport protocol http 3 and qpack we originated the http 3 and qpack rfcs ownership of these drafts has now transferred back to the http wg rfc 9114 http 3 rfc 9204 qpack in progress documents in progress documents for continued maintenance and evolution of quic as described further in our charter multipath datatracker github repo acknowledgement frequency datatracker github repo qlog main logging schema datatracker github repo quic event definitions datatracker github repo http 3 event definitions datatracker github repo 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 with a range of support for features of the core protocol and extensions implementers should join the quicdev slack to coordinate testing contact the wg chairs for an invitation note that discussions on slack are considered ietf contributions under note well automated continuous interop testing is performed for participating quic implementations implementers are encouraged to join this effort by making compatible docker images 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 related ietf protocols please see the ietf s guidance on how to report these if you believe you ve discovered an implementation vulnerability in a product open source project or service using quic then you should report these directly to the responsible party the ietf does not have a formal means to reach these parties and cannot do so on your behalf implementers or operators often provide their own publicly available disclosure documents that provide contact details and guidelines for reporters the implementations and tools page may include a link to such documents under the vulnerability reporting field if you believe the same vulnerability affects multiple different implementations or deployments then a coordinated responsible disclosure may be the best path forward please reach out to wg chairs for further information see also working group materials agendas minutes etc source code for the webpages on this site is located on github we welcome issues and prs