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

[Prachi Jain <[e-mail]>]

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
>> <https://datatracker.ietf.org/doc/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
>>>
>>