[TLS] Opsdir telechat review of draft-ietf-tls-tls12-frozen-06

Jen Linkova via Datatracker <noreply@ietf.org> Sun, 16 March 2025 06:37 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: tls@ietf.org
Delivered-To: tls@mail2.ietf.org
Received: from [10.244.8.216] (unknown [104.131.183.230]) by mail2.ietf.org (Postfix) with ESMTP id E3382BF81C2; Sat, 15 Mar 2025 23:37:11 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jen Linkova via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.37.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <174210703164.124993.17661986887788893733@dt-datatracker-5b9b68c5b6-zxk6z>
Date: Sat, 15 Mar 2025 23:37:11 -0700
Message-ID-Hash: MZWOQTT734W6F3DLVEVJLXWAUP2L3J6F
X-Message-ID-Hash: MZWOQTT734W6F3DLVEVJLXWAUP2L3J6F
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-tls-tls12-frozen.all@ietf.org, last-call@ietf.org, tls@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: Jen Linkova <furry13@gmail.com>
Subject: [TLS] Opsdir telechat review of draft-ietf-tls-tls12-frozen-06
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/1I_Y9Fmmi-PCeyz1hyIA3cgVMlY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Owner: <mailto:tls-owner@ietf.org>
List-Post: <mailto:tls@ietf.org>
List-Subscribe: <mailto:tls-join@ietf.org>
List-Unsubscribe: <mailto:tls-leave@ietf.org>

Reviewer: Jen Linkova
Review result: Ready

The document is clearly written and easy to understand even by people who knows
very little about TLS (like this reviewer ;) I think the document has no
negative impact on deployments: quite the opposite, it might motivate people to
move to TLS1.3.

I think the document is ready. I do have a minor editorial comment, feel free
to address or ignore:

"Use of TLS 1.3 [TLS13] is growing, and it fixes most known deficiencies with
TLS 1.2 [TLS12], such as encrypting more of the traffic so that it is not
readable by outsiders and removing most cryptographic primitives now considered
weak"

I'm not a native speaker but I'm afraid this sentence may be read as
'encrypting more of the traffic' and 'removing primitives" are examples of
known deficiencies, not fixes. Maybe rephrase as '...it fixes most known
deficiencies with TLS 1.2 [TLS12]. In particular, TLS 1.3 encrypting more..."?