[Keytrans] Re: WG Last Call: draft-ietf-keytrans-architecture-06 (Ends 2026-02-10)

[Thibault Meunier <[e-mail]>]

Hi keytrans,

I agree with Felix, the document is a good overview of KT.

Some small nits for the third party auditing section:
* in section 4.2, it is mentioned that the auditor is expected to run asynchronously. Maybe phrase it as "When running synchronously, the auditor may become a bottleneck for the Log service. It is expected that it would run asynchronously". Essentially changing the order of the sentences.
* the auditor role is to "attest to the fact the tree has been constructed correctly". This is the minimal requirement. An auditor may also serve copies of the updates, or even provide healthcheck services. It could be relevant to use the following "from a third-party auditor that is at minimum attesting to the fact that ..."

Thibault



On Tuesday, February 10th, 2026 at 16:10, Prachi Jain <[e-mail]> wrote:

> Thanks for sharing your inputs, Felix.
> 
> KEYTRANS Enthusiasts, We are seeing limited to no discussion so far on this document. To assist chairs in making a decision, please provide your feedback on the proposal - support, technical concerns, suggestions, or any other thoughts. Brief comments are very welcome. IETF advances on rough consensus and we need to see it (in either direction) to move forward.
> 
> Thanks, Chairs.
> 
> 
> On Tue, Feb 10, 2026 at 7:50 AM Felix Linker <[e-mail]> wrote:
> 
> > Hi everyone,
> > 
> > I've read and like the document! I think it gives a good overview of KT deployments and what the protocol can offer.
> > 
> > A small note: I don't think it's ideal that contact monitoring is initially explained by reference to the protocol document (see https://www.ietf.org/archive/id/draft-ietf-keytrans-architecture-06.html#section-4-5) The explanation that follows in Section 4.1 is much better and independent of the protocol. But this is certainly not a deal breaker.
> > 
> > Best,
> > Felix
> > 
> > Am So., 8. Feb. 2026 um 12:22 Uhr schrieb Deb Cooley <[e-mail]>:
> > 
> > > Hi,
> > > 
> > > I'd like to hear positive (as well as negative) comments, as well as who has reviewed the draft.
> > > 
> > > Thank you,
> > > 
> > > Deb Cooley
> > > Sec AD
> > > 
> > > On Sat, Feb 7, 2026 at 10:16 PM Prachi Jain <[e-mail]> wrote:
> > > 
> > > > Dear Working Group,
> > > > 
> > > > 
> > > > 
> > > > This is another gentle reminder to please submit your feedback, concerns, suggestions, or any other input on the architecture document currently under last call to the mailing list.
> > > > 
> > > > 
> > > > 
> > > > As we approach the end of the review period, it will become increasingly difficult for the chairs and document authors to make progress without feedback from the Working Group.
> > > > 
> > > > 
> > > > 
> > > > Your participation is greatly appreciated.
> > > > 
> > > > 
> > > > 
> > > > Thanks,
> > > > Prachi
> > > > 
> > > > 
> > > > On Mon, Feb 2, 2026 at 9:52 AM Prachi Jain <[e-mail]> wrote:
> > > > 
> > > > > Hello Keytrans enthusiasts,
> > > > > 
> > > > > We have a week left in WGLC for the architecture document and we have not received any responses yet. Please raise your support or concerns on the list or reach out to the chairs directly, so that we can make progress with this document.
> > > > > 
> > > > > Thanks,
> > > > > Prachi
> > > > > 
> > > > > On Tue, Jan 27, 2026 at 8:38 AM Prachi Jain <[e-mail]> wrote:
> > > > > 
> > > > > > Hello All,
> > > > > > 
> > > > > > As decided during the KEYTRANS session at IETF 124, the authors have published a revision of the architecture document. The document draft-ietf-keytrans-architecture is now ready for the Working Group Last Call.
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > If anyone on the list has concerns or believes there is a reason not to advance this document at this time, please raise them on the mailing list as soon as possible.
> > > > > > 
> > > > > > Thanks,
> > > > > > Chairs
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > On Tue, Jan 27, 2026 at 8:23 AM Prachi Jain via Datatracker <[e-mail]> wrote:
> > > > > > 
> > > > > > > This message starts a WG Last Call for:
> > > > > > > draft-ietf-keytrans-architecture-06
> > > > > > > 
> > > > > > > This Working Group Last Call ends on 2026-02-10
> > > > > > > 
> > > > > > > Abstract:
> > > > > > > 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 also gives more general, non-
> > > > > > > prescriptive guidance on how to securely apply Key Transparency to a
> > > > > > > number of common applications.
> > > > > > > 
> > > > > > > File can be retrieved from:
> > > > > > > 
> > > > > > > Please review and indicate your support or objection to proceed with the
> > > > > > > publication of this document by replying to this email keeping
> > > > > > > [e-mail] in copy. Objections should be explained and suggestions to
> > > > > > > resolve them are highly appreciated.
> > > > > > > 
> > > > > > > Authors, and WG participants in general, are reminded of the Intellectual
> > > > > > > Property Rights (IPR) disclosure obligations described in BCP 79 [1].
> > > > > > > Appropriate IPR disclosures required for full conformance with the provisions
> > > > > > > of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
> > > > > > > Sanctions available for application to violators of IETF IPR Policy can be
> > > > > > > found at [3].
> > > > > > > 
> > > > > > > Thank you.
> > > > > > > 
> > > > > > > [1] https://datatracker.ietf.org/doc/bcp78/
> > > > > > > [2] https://datatracker.ietf.org/doc/bcp79/
> > > > > > > [3] https://datatracker.ietf.org/doc/rfc6701/
> > > > > > > 
> > > > > > > The IETF datatracker status page for this Internet-Draft is:
> > > > > > > https://datatracker.ietf.org/doc/draft-ietf-keytrans-architecture/
> > > > > > > 
> > > > > > > There is also an HTML version available at:
> > > > > > > https://www.ietf.org/archive/id/draft-ietf-keytrans-architecture-06.html
> > > > > > > 
> > > > > > > A diff from the previous version is available at:
> > > > > > > https://author-tools.ietf.org/iddiff?url2=draft-ietf-keytrans-architecture-06
> > > > 
> > > > --
> > > > Keytrans mailing list -- [e-mail]
> > > > To unsubscribe send an email to [e-mail]
> > > 
> > > --
> > > Keytrans mailing list -- [e-mail]
> > > To unsubscribe send an email to [e-mail]