Yeah!!!! Great work everybody! And a huge thanks to the editors (of all RFCs)!
On 27.05.21, 23:40, "QUIC on behalf of [email protected]" <[email protected] on behalf of [email protected]> wrote: A new Request for Comments is now available in online RFC libraries. RFC 9000 Title: QUIC: A UDP-Based Multiplexed and Secure Transport Author: J. Iyengar, Ed., M. Thomson, Ed. Status: Standards Track Stream: IETF Date: May 2021 Mailbox: [email protected], [email protected] Pages: 151 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-quic-transport-34.txt URL: https://protect2.fireeye.com/v1/url?k=4c0971e3-13924931-4c093178-866132fe445e-64ad4b752e91f559&q=1&e=e195985b-1bc7-46ba-924b-ec887dde4103&u=https%3A%2F%2Fwww.rfc-editor.org%2Finfo%2Frfc9000 DOI: 10.17487/RFC9000 This document defines the core of the QUIC transport protocol. QUIC provides applications with flow-controlled streams for structured communication, low-latency connection establishment, and network path migration. QUIC includes security measures that ensure confidentiality, integrity, and availability in a range of deployment circumstances. Accompanying documents describe the integration of TLS for key negotiation, loss detection, and an exemplary congestion control algorithm. This document is a product of the QUIC Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://protect2.fireeye.com/v1/url?k=5c4fe193-03d4d941-5c4fa108-866132fe445e-b39c82f53e2846e7&q=1&e=e195985b-1bc7-46ba-924b-ec887dde4103&u=https%3A%2F%2Fwww.rfc-editor.org%2Fstandards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://protect2.fireeye.com/v1/url?k=395fb930-66c481e2-395ff9ab-866132fe445e-30c0a739d8510073&q=1&e=e195985b-1bc7-46ba-924b-ec887dde4103&u=https%3A%2F%2Fmailman.rfc-editor.org%2Fmailman%2Flistinfo%2Frfc-dist For searching the RFC series, see https://protect2.fireeye.com/v1/url?k=f14f1c76-aed424a4-f14f5ced-866132fe445e-b8d7bba3e57c13ec&q=1&e=e195985b-1bc7-46ba-924b-ec887dde4103&u=https%3A%2F%2Fwww.rfc-editor.org%2Fsearch For downloading RFCs, see https://protect2.fireeye.com/v1/url?k=d150b7d0-8ecb8f02-d150f74b-866132fe445e-b1b5007dd32a3d05&q=1&e=e195985b-1bc7-46ba-924b-ec887dde4103&u=https%3A%2F%2Fwww.rfc-editor.org%2Fretrieve%2Fbulk Requests for special distribution should be addressed to either the author of the RFC in question, or to [email protected]. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC
