Last Call: <draft-ietf-quic-tls-32.txt> (Using TLS to Secure QUIC) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Wed, 21 October 2020 13:27 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-quic-tls-32.txt> (Using TLS to Secure QUIC) to Proposed Standard
Auto-Submitted: auto-generated
Precedence: bulk
CC: draft-ietf-quic-tls@ietf.org, magnus.westerlund@ericsson.com, quic@ietf.org, mnot@mnot.net, quic-chairs@ietf.org
Reply-To: last-call@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <160328687373.25781.15246016624289104534@ietfa.amsl.com>
Date: Wed, 21 Oct 2020 06:27:54 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/soLv8NRqxKuG2ob4k-hlSc6iSSM>

The IESG has received a request from the QUIC WG (quic) to consider the
following document: - 'Using TLS to Secure QUIC'
  <draft-ietf-quic-tls-32.txt> as Proposed Standard

This document is part of a combined 26-day last call for multiple 
related documents that defines the QUIC protocol and the HTTP mapping
onto QUIC. The documents are:
	
   - draft-ietf-quic-transport
   - draft-ietf-quic-recovery
   - draft-ietf-quic-tls
   - draft-ietf-quic-invariants
   - draft-ietf-quic-http
   - draft-ietf-quic-qpack

Due to its GitHub-centric work style, the QUIC WG requests that LC review 
comments are individually filed as issues in the WG repository at 
https://github.com/quicwg/base-drafts if at all possible. A summary email with 
URLs to the individual issue should then also be sent to the relevant mailing list 
(primarily last-call@ietf.org and quic@ietf.org).	

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2020-11-16. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.


Abstract


   This document describes how Transport Layer Security (TLS) is used to
   secure QUIC.

Note to Readers

   Discussion of this draft takes place on the QUIC working group
   mailing list (quic@ietf.org), which is archived at
   https://mailarchive.ietf.org/arch/search/?email_list=quic.

   Working Group information can be found at https://github.com/quicwg;
   source code and issues list for this draft can be found at
   https://github.com/quicwg/base-drafts/labels/-tls.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-quic-tls/



No IPR declarations have been submitted directly on this I-D.


The document contains these normative downward references.
See RFC 3967 for additional information: 
    rfc8439: ChaCha20 and Poly1305 for IETF Protocols (Informational - IRTF Stream)

The intention is to add this RFC to the downref registry 
(https://datatracker.ietf.org/doc/downref/) after this last call.

Last Call: <draft-ietf-quic-tls-32.txt> (Using TL… The IESG
Fwd: [IANA #1180852] Last Call: <draft-ietf-quic-… Lars Eggert