[TLS] Opsdir telechat review of draft-ietf-tls-record-limit-02

Éric Vyncke <evyncke@cisco.com> Wed, 21 February 2018 13:46 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Éric Vyncke <evyncke@cisco.com>
To: ops-dir@ietf.org
Cc: tls@ietf.org, ietf@ietf.org, draft-ietf-tls-record-limit.all@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151922077388.9603.11906306194638042902@ietfa.amsl.com>
Date: Wed, 21 Feb 2018 05:46:13 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/RPJOlYzZ0gH5niFmoH-OMKCCr7U>
Subject: [TLS] Opsdir telechat review of draft-ietf-tls-record-limit-02

Reviewer: Éric Vyncke
Review result: Has Nits

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

[TLS] Opsdir telechat review of draft-ietf-tls-re… Éric Vyncke
Re: [TLS] Opsdir telechat review of draft-ietf-tl… Martin Thomson