Last Call Review of draft-ietf-tls-grease-03
review-ietf-tls-grease-03-secdir-lc-wallace-2019-08-15-00

Request Review of draft-ietf-tls-grease
Requested rev. no specific revision (document currently at 04)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2019-08-12
Requested 2019-07-29
Draft last updated 2019-08-15
Completed reviews Secdir Last Call review of -03 by Carl Wallace (diff)
Genart Last Call review of -03 by Francis Dupont (diff)
Assignment Reviewer Carl Wallace
State Completed
Review review-ietf-tls-grease-03-secdir-lc-wallace-2019-08-15
Posted at https://mailarchive.ietf.org/arch/msg/secdir/oHShmWZ43cGRIGnmbrnz1BoDlxI
Reviewed rev. 03 (document currently at 04)
Review result Ready
Review completed: 2019-08-15

Review
review-ietf-tls-grease-03-secdir-lc-wallace-2019-08-15

I have reviewed this document as part of the security directorate's
ongoing effort to review all IETF documents being processed by the IESG.
These comments were written primarily for the benefit of the security area
directors.  Document editors and WG chairs should treat these comments
just like any other last call comments.

This document describes a mechanism to prevent extensibility failures in
the TLS ecosystem.  It reserves a set of TLS protocol values that may be
advertised to ensure peers correctly handle unknown values. Aside from a
nit/question, the document is ready.

The question relates to language in section 2. which states: "The values
allocated above are thus no longer available for use as TLS or DTLS
[RFC6347] version numbers." Should this draft be marked as updating 6347
and 8446 as a result? At present it is Informational and does not update
any other specifications.