RFC 9369 on QUIC Version 2
rfc-editor@rfc-editor.org Wed, 31 May 2023 17:34 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D42FC15171B; Wed, 31 May 2023 10:34:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.947
X-Spam-Level:
X-Spam-Status: No, score=-3.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u4D8k19z4C8A; Wed, 31 May 2023 10:34:10 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37FD9C1519A8; Wed, 31 May 2023 10:33:29 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 302747FDE0; Wed, 31 May 2023 10:33:29 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9369 on QUIC Version 2
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, quic@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20230531173329.302747FDE0@rfcpa.amsl.com>
Date: Wed, 31 May 2023 10:33:29 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/8IzmtrzD615qsOYbymNiHvgfh50>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 May 2023 17:34:11 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9369
Title: QUIC Version 2
Author: M. Duke
Status: Standards Track
Stream: IETF
Date: May 2023
Mailbox: martin.h.duke@gmail.com
Pages: 14
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-quic-v2-10.txt
URL: https://www.rfc-editor.org/info/rfc9369
DOI: 10.17487/RFC9369
This document specifies QUIC version 2, which is identical to QUIC
version 1 except for some trivial details. Its purpose is to combat
various ossification vectors and exercise the version negotiation
framework. It also serves as a template for the minimum changes in
any future version of QUIC.
Note that "version 2" is an informal name for this proposal that
indicates it is the second version of QUIC to be published as a
Standards Track document. The protocol specified here uses a version
number other than 2 in the wire image, in order to minimize
ossification risks.
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://www.rfc-editor.org/standards) 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://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
- RFC 9369 on QUIC Version 2 rfc-editor