[OPSAWG] Genart last call review of draft-ietf-opsawg-tlstm-update-11

Joel Halpern via Datatracker <noreply@ietf.org> Thu, 09 February 2023 23:56 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: opsawg@ietf.org
Delivered-To: opsawg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 95EC1C17D66B; Thu, 9 Feb 2023 15:56:43 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Halpern via Datatracker <noreply@ietf.org>
To: gen-art@ietf.org
Cc: draft-ietf-opsawg-tlstm-update.all@ietf.org, last-call@ietf.org, opsawg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 9.8.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <167598700360.63022.14982926534464297252@ietfa.amsl.com>
Reply-To: Joel Halpern <jmh@joelhalpern.com>
Date: Thu, 09 Feb 2023 15:56:43 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/CftveLTdL3NRbH0nB8zpc9c_7vY>
Subject: [OPSAWG] Genart last call review of draft-ietf-opsawg-tlstm-update-11
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.39
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2023 23:56:43 -0000

Reviewer: Joel Halpern
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-opsawg-tlstm-update-11
Reviewer: Joel Halpern
Review Date: 2023-02-09
IETF LC End Date: 2023-02-20
IESG Telechat date: Not scheduled for a telechat

Summary: This document is ready for publication as a Proposed Standard RFC

Major issues: N/A

Minor issues:
    In the fourth paragraph of section 1.1, the text refers to "a secure
    association between two TLS Transport Models (TLSTMs)".  As I understand
    the terminology, there is one TLSTM.  There are two instances of /
    realizations of the model.  Should the sentence refer to instances or
    realizations, rather than two models? (i-d nits gets confused by the
    references to rfc 5953 in the revision description.  After looking at it, I
    realized there was no problem here, rather it is accurate.  A comment on
    this in item 14 of the shepherd writeup would have been helpful.)

Nits/editorial comments: N/A