RFC 9001 on Using TLS to Secure QUIC
rfc-editor@rfc-editor.org Thu, 27 May 2021 21:37 UTC
Return-Path: <wwwrun@rfc-editor.org>
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 2B6693A1406; Thu, 27 May 2021 14:37:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id frJBa2sIg2HE; Thu, 27 May 2021 14:37:43 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B58123A1408; Thu, 27 May 2021 14:37:43 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id DBD8CF40743; Thu, 27 May 2021 14:37:29 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9001 on Using TLS to Secure QUIC
X-PHP-Originating-Script: 1005:ams_util_lib.php
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: <20210527213729.DBD8CF40743@rfc-editor.org>
Date: Thu, 27 May 2021 14:37:29 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/mu9dlAt0NJHHQfe3bgZulTZD6BQ>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 27 May 2021 21:37:55 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9001
Title: Using TLS to Secure QUIC
Author: M. Thomson, Ed.,
S. Turner, Ed.
Status: Standards Track
Stream: IETF
Date: May 2021
Mailbox: mt@lowentropy.net,
sean@sn3rd.com
Pages: 52
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-quic-tls-34.txt
URL: https://www.rfc-editor.org/info/rfc9001
DOI: 10.17487/RFC9001
This document describes how Transport Layer Security (TLS) is used to
secure QUIC.
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 9001 on Using TLS to Secure QUIC rfc-editor