IETF Last Call Review of draft-ietf-keytrans-architecture-10
review-ietf-keytrans-architecture-10-artart-lc-yao-2026-10-12-00

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

Document: draft-ietf-keytrans-architecture-10
Reviewer: Jiankang Yao
Review Date: 2026-10-12

Summary: Almost Ready.

This document defines the terminology and interaction patterns
involved in the deployment of Key Transparency in a general secure
group messaging infrastructure, and specifies the security properties
that the protocol provides. It aims for informational document.

Some issues below:

1) Section 3.3  said that “This provides ample opportunity for users to detect when a fork has
   been presented but isn't in itself sufficient for detection.  To
   detect forks, users require either a *trusted third party*,
   *anonymous communication* with the transparency log, or *peer-to-peer 
   communication*.”

It defines three fork detection mechanisms. However, it does not specify 
implementation behavior when none of these three methods can be used. 

When fork detection capability is unavailable, how does the implementation deal with this condition?


2) This document is explicitly marked as Informational,
 which is intended to provide architectural guidance rather than normative, 
interoperable protocol rules. However, the draft extensively uses 
uppercase RFC2119 "MUST" requirements throughout the text.


3)Title of the figure is too long.
for example,

"Figure 1: Example request and response flow.  Valid requests
        receive a response while invalid requests are blocked by the
                              transport layer.
"

"
 Figure 2: Example message flow in an anonymous deployment.  Users
     request their own label from the transparency log and provide the
       serialized response, functioning as a credential, in encrypted
         messages to other users.  Required monitoring is provided
                                proactively.
"