[Din] Re: an AT protocol BOF at IETF 124

[Lixia Zhang <[e-mail]>]

> On Oct 24, 2025, at 2:29 AM, Jon Crowcroft <jon.crowcroft=[e-mail]> wrote:
> 
> I guess the work in MIMI is also kind of related...

Hi Jon, I agree that MIMI is kind of related. 
Maybe we could discuss ATP as a specific design first, then apply what we learn from this first study to other related protocols?

Lixia

> On Fri, Oct 24, 2025, at 7:22 AM, Lixia Zhang wrote:
>> DINRG folks,
>> 
>> In case you have not noticed, an AT protocol BOF has been scheduled at IETF 124; I attached the BOF description below. Since Bluesky as a decentralized social app is built on the AT Protocol, this BOF should be highly relevant to DIN's interest.
>> 
>> A mailing list has also been set up for this BOF, people may be interested in joining the conversation: https://mailarchive.ietf.org/arch/browse/atp/ 
>> 
>> FYI, Lixia
>> ====================
>> Name: Authenticated Transfer BOF
>> Description: Self-Certifying data structures make it possible to efficiently synchronize public content across organizational boundaries, while preserving authenticity. These techniques have found broad adoption in some areas (such as software code versioning with git), but for the most part not in traditional web publishing or social web applications. On the social web today, authority and authenticity remain rooted in specific network locations and service providers, not network identities controlled by individuals or organizations.
>> 
>> Authenticated Transfer (AT) is a collection of protocol components which together provide a generic framework for interoperable social web applications, using self-certifying network data. The framework includes several components which could be in-scope for the IETF, as well as other components which are likely not. It builds on existing IETF technologies including CBOR, OAuth, HTTP, WebSockets, and DNS. The overall framework includes a schema system, but does not specify application-specific document formats.
>> 
>> This BoF is to discuss developing a narrowly-defined subset of protocol components within the IETF: the public repository data structure, wire serialization format, and public synchronization mechanism.
>> 
>> This follows a successful side-meeting at IETF 123 in Madrid, and many conversations with individuals over the years. The goal of this non-working-group-forming BoF is to open the topic to the entire IETF community for feedback, share experiences from early experimentation and implementation, and address as many chartering and scope questions as possible. This BoF would be followed on by a formal WG-forming BoF, possibly in an interim meeting.
>> 
>> _______________________________________________
>> Din mailing list -- [e-mail] <mailto:[e-mail]>
>> To unsubscribe send an email to [e-mail] <mailto:[e-mail]>
>> 
> 
> _______________________________________________
> Din mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]