Skip to main content

IETF Last Call Review of draft-ietf-ippm-qoo-06
review-ietf-ippm-qoo-06-genart-lc-kyzivat-2026-02-09-00

Request Review of draft-ietf-ippm-qoo
Requested revision No specific revision (document currently at 07)
Type IETF Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2026-02-13
Requested 2026-01-30
Authors Bjørn Ivar Teigen , Magnus Olden , Ike Kunze
I-D last updated 2026-03-08 (Latest revision 2026-02-19)
Completed reviews Perfmetrdir Early review of -04 by Paul Aitken (diff)
Tsvart IETF Last Call review of -07 by Joerg Ott
Genart IETF Last Call review of -06 by Paul Kyzivat (diff)
Secdir IETF Last Call review of -06 by Mališa Vučinić (diff)
Artart IETF Last Call review of -06 by Martin Thomson (diff)
Opsdir Telechat review of -07 by Will (Shucheng) LIU
Assignment Reviewer Paul Kyzivat
State Completed
Request IETF Last Call review on draft-ietf-ippm-qoo by General Area Review Team (Gen-ART) Assigned
Posted at https://mailarchive.ietf.org/arch/msg/gen-art/QNG7a4Z_6mWmlFXC1FVfpfBBQRc/
Reviewed revision 06 (document currently at 07)
Result Ready w/issues
Completed 2026-02-09
review-ietf-ippm-qoo-06-genart-lc-kyzivat-2026-02-09-00
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://wiki.ietf.org/en/group/gen/GenArtFAQ>.

Document: draft-ietf-ippm-qoo
Title: Quality of Outcome (QoO)
Reviewer: Paul Kyzivat
Review Date: 2026-02-09
IETF LC End Date: 2026-02-13
IESG Telechat date: ?

Summary: This draft is on the right track but has open issues, described 
in the review.

Note: This reviewer has no experience in, or knowledge of, network 
performance measurement. Hence I'm unqualified to comment on the 
semantics of this draft. In such cases I usually fall back to reviewing 
the form and syntax. Even that is hard here, since there is little in 
the way of formal specification.

Issue:

My impression is that for QoO values to be composable, they must be 
based on the same measurement percentiles. Achieving that across the 
managers of connected networks seems difficult. Is it realistic?

Issue:

I had difficulty understanding the notation used in the formula in 
section 7:

   QoO_latency = min_{i}(min(
      max((1 - ((ML_i - ROP_i) / (CPUP_i - ROP_i))) * 100, 0), 100))

Fortunately, Martin Thompson has posted an alternative rendition for 
this formula, that I find much more understandable:

    for i in ROP:
      m = (ML[i] - ROP[i]) / (CPUP[i] - ROP[i])
      metrics[i] = clamp(0, m, 1)
    QoO_latency = find_min(metrics) * 100

(It is in his followup message to his ArtArt review of this document. 
<https://mailarchive.ietf.org/arch/msg/art/BC-qxC6pD_63lfHfLd1R4n_KA8c/>)

Martin considers this a nit, but I consider it to be a significant 
issue. It is the closest thing this document has to a normative 
requirement, so it is essential that all readers understand it 
consistently. I recommend reworking the rendition of this formula into a 
form that will be clear to all who need to understand it.

I found Martin's full ArtArt review insightful. While it goes beyond my 
understanding of the subject material, I agree with it to the extent of 
my understanding.