[Last-Call] draft-ietf-opsawg-rfc5706bis-09 ietf last call Secdir review

Jacqueline McCall via Datatracker <noreply@ietf.org> Thu, 22 October 2026 22:01 UTC

Received: by mx.ietf.org (Postfix) id 7112F46; Thu, 22 Oct 2026 22:01:31 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ietf.org; s=mail; t=1792706491; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=krBhIgeWsU9TbLk8eHZxaIQGSYp3zIYsRPQ91QT4ZTk=; b=QBm5tg4IVU7ONfqUnTk0ypOapUG0VBU2XMKik+xTWXyRDLG39dTQd0/dErcpxPWXRKgj6C Ym8n/90DgE3vaHYs3sLW8c8mDph4MZyoFuhTqBTAoJ5j4aEgnHT0EXsr/7BUutB7hduFog x7r9fqd1RSkMn7TXmwqk5+8tVIU4qhc=
Authentication-Results: ORIGINATING; auth=pass smtp.auth=mail2@ietf.org smtp.mailfrom=noreply@ietf.org
Received: from [10.244.9.159] (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 3476213AF2A81; Thu, 22 Oct 2026 15:01:31 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Jacqueline McCall via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.81.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <179270649097.764072.14471326143233228702@dt-datatracker-7457c9c988-pqlqx>
Date: Thu, 22 Oct 2026 15:01:31 -0700
Message-ID-Hash: VSPRH25DCYJBVWCCTDUNQOLQG4MPD43P
X-Message-ID-Hash: VSPRH25DCYJBVWCCTDUNQOLQG4MPD43P
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-opsawg-rfc5706bis.all@ietf.org, last-call@ietf.org, opsawg@ietf.org
X-Mailman-Version: 3.3.10
Reply-To: Jacqueline McCall <jacqui.ietf@gmail.com>
Subject: [Last-Call] draft-ietf-opsawg-rfc5706bis-09 ietf last call Secdir review
List-Id: IETF Last Calls <last-call.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/LB8Mu8cstl8toJORx3StmSI3Jjw>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Owner: <mailto:last-call-owner@ietf.org>
List-Post: <mailto:last-call@ietf.org>
List-Subscribe: <mailto:last-call-join@ietf.org>
List-Unsubscribe: <mailto:last-call-leave@ietf.org>

Document: draft-ietf-opsawg-rfc5706bis
Title: Guidelines for Considering Operations and Management in IETF
Specifications Reviewer: Jacqueline McCall Review result: Ready

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.

The summary of the review is Ready

Purely through a security lens, the document provides solid guidance for
protocol designers to consider which will be useful from both an operational
and security point of view. Since the initial early review, I appreciate the
updates that have been made to the security sections. By removing the bulk of
content from the Security Considerations (9) to Security Management (5.8) has
helped focus the aim of the security discussions to the relevant operational
objectives. The Impact on Security Operations (4.5) section has also been built
out and is quite comprehensive, serving as a useful resource. Highlighting the
tension between privacy and visibility is a welcome addition and very relevant
to modern times. From a Security perspective, the document content combined
with the “Operational Considerations Checklist” is relevant and refined to
provide genuine guidance to protocol designers.

From a non-security perspective, I do want to acknowledge the discussion’s
happening around the requirement for "Operational Considerations" inclusion in
future documents and interested to see how these concerns will be addressed.