Re: [MLS] RFC 9420 on The Messaging Layer Security (MLS) Protocol

[Benjamin Beurdouche <[e-mail]>]

Congrats everyone ! Hope that we can build our next project using the same collaborative approach ! ; )

Best,
Benjamin

> On 18 Jul 2023, at 15:36, Raphael Robert <ietf=[e-mail]> wrote:
> 
> I can only second this. It was great to see the industry and academia come together to work on this. Thanks and congratulations!
> 
> Raphael
> 
>> On 18. Jul 2023, at 15:33, Richard Barnes <[e-mail]> wrote:
>> 
>> And many thanks to the many people who helped make this happen.  MLS was truly a group effort; we would have been worse off if we didn't have folks contributing a bunch of different perspectives.  Great job, everyone!
>> 
>> On Tue, Jul 18, 2023 at 9:30 AM Sean Turner <[e-mail] <mailto:[e-mail]>> wrote:
>>> Congrats to all those who contributed!
>>> 
>>> spt
>>> 
>>> > On Jul 18, 2023, at 09:12, [e-mail] <mailto:[e-mail]> wrote:
>>> > 
>>> > A new Request for Comments is now available in online RFC libraries.
>>> > 
>>> > 
>>> >        RFC 9420
>>> > 
>>> >        Title:      The Messaging Layer Security (MLS) Protocol 
>>> >        Author:     R. Barnes,
>>> >                    B. Beurdouche,
>>> >                    R. Robert,
>>> >                    J. Millican,
>>> >                    E. Omara,
>>> >                    K. Cohn-Gordon
>>> >        Status:     Standards Track
>>> >        Stream:     IETF
>>> >        Date:       July 2023
>>> >        Mailbox:    [e-mail] <mailto:[e-mail]>,
>>> >                    [e-mail] <mailto:[e-mail]>,
>>> >                    [e-mail] <mailto:[e-mail]>,
>>> >                    [e-mail] <mailto:[e-mail]>,
>>> >                    [e-mail] <mailto:[e-mail]>,
>>> >                    [e-mail] <mailto:[e-mail]>
>>> >        Pages:      132
>>> >        Updates/Obsoletes/SeeAlso:   None
>>> > 
>>> >        I-D Tag:    draft-ietf-mls-protocol-20.txt
>>> > 
>>> >        URL:        https://www.rfc-editor.org/info/rfc9420
>>> > 
>>> >        DOI:        10.17487/RFC9420
>>> > 
>>> > Messaging applications are increasingly making use of end-to-end
>>> > security mechanisms to ensure that messages are only accessible to
>>> > the communicating endpoints, and not to any servers involved in
>>> > delivering messages.  Establishing keys to provide such protections
>>> > is challenging for group chat settings, in which more than two
>>> > clients need to agree on a key but may not be online at the same
>>> > time.  In this document, we specify a key establishment protocol that
>>> > provides efficient asynchronous group key establishment with forward
>>> > secrecy (FS) and post-compromise security (PCS) for groups in size
>>> > ranging from two to thousands.
>>> > 
>>> > This document is a product of the Messaging Layer Security Working Group of the IETF.
>>> > 
>>> > This is now a Proposed Standard.
>>> > 
>>> > STANDARDS TRACK: This document specifies an Internet Standards Track
>>> > protocol for the Internet community, and requests discussion and suggestions
>>> > for improvements.  Please refer to the current edition of the Official
>>> > Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
>>> > standardization state and status of this protocol.  Distribution of this 
>>> > memo is unlimited.
>>> > 
>>> > This announcement is sent to the IETF-Announce and rfc-dist lists.
>>> > To subscribe or unsubscribe, see
>>> >  https://www.ietf.org/mailman/listinfo/ietf-announce
>>> >  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>>> > 
>>> > For searching the RFC series, see https://www.rfc-editor.org/search
>>> > For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
>>> > 
>>> > Requests for special distribution should be addressed to either the
>>> > author of the RFC in question, or to [e-mail] <mailto:[e-mail]>.  Unless
>>> > specifically noted otherwise on the RFC itself, all RFCs are for
>>> > unlimited distribution.
>>> > 
>>> > 
>>> > The RFC Editor Team
>>> > Association Management Solutions, LLC
>>> > 
>>> > 
>>> > _______________________________________________
>>> > IETF-Announce mailing list
>>> > [e-mail] <mailto:[e-mail]>
>>> > https://www.ietf.org/mailman/listinfo/ietf-announce
>>> 
>>> _______________________________________________
>>> MLS mailing list
>>> [e-mail] <mailto:[e-mail]>
>>> https://www.ietf.org/mailman/listinfo/mls
>> _______________________________________________
>> MLS mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/mls
> 
> _______________________________________________
> MLS mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/mls