From: Sean Turner <sean@sn3rd.com>
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Fri, 16 Feb 2018 12:21:34 -0500
References: <151880080195.1349.14035524657942875385.idtracker@ietfa.amsl.com>
To: "<tls@ietf.org>" <tls@ietf.org>
In-Reply-To: <151880080195.1349.14035524657942875385.idtracker@ietfa.amsl.com>
Message-Id: <8A8213B0-F2C4-4C46-B858-09FB4EF608E3@sn3rd.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/6KNDFgDqziZBKymCTpvizMVNuZo>
Subject: Re: [TLS] UPDATED Last Call: <draft-ietf-tls-tls13-24.txt> (The
 Transport Layer Security (TLS) Protocol Version 1.3) to Proposed Standard
Precedence: list

The difference here is that this LC includes all of the downrefs =
according to the process described in [0].  Including the downward =
references to non-stardards track RFCs will ensure we=E2=80=99re not =
delayed due to process issues.  Most of these are as a result of how we =
publish algorithm drafts, i.e., from the CFRG through through the IRTF =
stream, and none are a surprise.

spt

[0] https://tools.ietf.org/html/bcp97

> On Feb 16, 2018, at 12:06, The IESG <iesg-secretary@ietf.org> wrote:
>=20
>=20
> The IESG has received a request from the Transport Layer Security WG =
(tls) to
> consider the following document: - 'The Transport Layer Security (TLS)
> Protocol Version 1.3'
>  <draft-ietf-tls-tls13-24.txt> as Proposed Standard
>=20
> 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
> ietf@ietf.org mailing lists by 2018-03-02. 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.
>=20
> Abstract
>=20
>=20
>   This document specifies version 1.3 of the Transport Layer Security
>   (TLS) protocol.  TLS allows client/server applications to =
communicate
>   over the Internet in a way that is designed to prevent =
eavesdropping,
>   tampering, and message forgery.
>=20
>=20
>=20
>=20
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-tls-tls13/
>=20
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-tls-tls13/ballot/
>=20
> The following IPR Declarations may be related to this I-D:
>=20
>   https://datatracker.ietf.org/ipr/2900/
>=20
>=20
>=20
> The document contains these normative downward references.
> See RFC 3967 for additional information:=20
>    rfc8017: PKCS #1: RSA Cryptography Specifications Version 2.2 =
(Informational - IETF stream)
> rfc6962: Certificate Transparency (Experimental - IETF stream)
> rfc6979: Deterministic Usage of the Digital Signature Algorithm (DSA)
> and Elliptic Curve Digital Signature Algorithm (ECDSA) (informational
> - Independent Stream)
> rfc7539: ChaCha20 and Poly1305 for IETF Protocols (Informational - =
IRTF stream)
> rfc7748: Elliptic Curves for Security (Informational - IRTF stream)
> rfc8017: PKCS #1: RSA Cryptography Specifications Version 2.2 =
(Informational - IETF stream)
> rfc8032: Edwards-Curve Digital Signature Algorithm (EdDSA) =
(Informational - IRTF stream)
>=20
>=20