[ippm] draft-ietf-ippm-qoo-06 ietf last call Secdir review

Mališa Vučinić via Datatracker <noreply@ietf.org> Tue, 17 February 2026 13:51 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Mališa Vučinić via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <177133626824.1045386.6498907563879240749@dt-datatracker-6ff7c68975-7k42g>
Date: Tue, 17 Feb 2026 05:51:08 -0800
Message-ID-Hash: ZVNWGPKQIW3LAEFCWRAPS4VJUJBSKB7Y
CC: draft-ietf-ippm-qoo.all@ietf.org, ippm@ietf.org, last-call@ietf.org
Reply-To: Mališa Vučinić <malisa.vucinic@inria.fr>
Subject: [ippm] draft-ietf-ippm-qoo-06 ietf last call Secdir review
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/WZbUOnllv1USRCKWkkBDtWOBj8Q>

Document: draft-ietf-ippm-qoo
Title: Quality of Outcome (QoO)
Reviewer: Mališa Vučinić
Review result: Ready

I 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
authors, document editors, and WG chairs should treat these comments just like
any other IETF Last Call comments.

The document is clear and well-written. It does not define a new protocol, yet
it discusses the security considerations arising from the operational
perspective. I agree with the considerations outlined and I find the proposed
mitigations effective. I have no additional considerations pertaining to the
proposed framework.

[ippm] draft-ietf-ippm-qoo-06 ietf last call Secd… Mališa Vučinić via Datatracker
[ippm] Re: draft-ietf-ippm-qoo-06 ietf last call … Ike Kunze