Telechat Review of draft-ietf-tls-record-limit-02
review-ietf-tls-record-limit-02-opsdir-telechat-vyncke-2018-02-21-00

Request Review of draft-ietf-tls-record-limit
Requested rev. no specific revision (document currently at 03)
Type Telechat Review
Team Ops Directorate (opsdir)
Deadline 2018-03-06
Requested 2018-02-16
Other Reviews Secdir Telechat review of -02 by Alan DeKok (diff)
Genart Telechat review of -02 by Francis Dupont (diff)
Review State Completed
Reviewer Éric Vyncke
Review review-ietf-tls-record-limit-02-opsdir-telechat-vyncke-2018-02-21
Posted at https://mailarchive.ietf.org/arch/msg/ops-dir/8FmdInfdqjlbxdxlWPrf1lSB1QQ
Reviewed rev. 02 (document currently at 03)
Review result Has Nits
Draft last updated 2018-02-21
Review completed: 2018-02-21

Review
review-ietf-tls-record-limit-02-opsdir-telechat-vyncke-2018-02-21

Reviewer: Eric Vyncke
Review results: has nits

Hello Martin,

I have reviewed this document as part of the Operational directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written with the intent of improving the operational aspects of the IETF drafts.

The document is about an extension to TLS (record_size_limit) allowing endpoints to negotiate the maximum size of protected records. The document also deprecates a previous extension max_fragment_length.

The different scenarios (whether endpoints support this option or not) as well as behavior of future versions of TLS are specified. Section 5 also describes the behavior when endpoints use the proposed and the deprecated TLS options.

Nits in section 5: "MUST ignore *and* "max_fragment_length""

This is a short document and IMHO all operational issues are well documented and correct.

-éric