Re: [MLS] I-D Action: draft-ietf-mls-architecture-06.txt

[Benjamin Beurdouche <[e-mail]>]

Dear all,

I just submitted a new version of the architecture document, there is
still a lot of work to do but we are making good progress...

In particular, we still need to work on:
- security considerations need to be completed, discussed with academics and cite papers
- the functional requirements section needs to be rewritten
- Brendan suggested to list different use cases and I really like the idea

Still lot of work, but I think we are roughly to a point where we can have a look and make sure we
are not missing important things, so feel free to open issues to point things that are missing or incorrect on the Github.

Best,
Benjamin



> On 8 Mar 2021, at 14:12, [e-mail] wrote:
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Messaging Layer Security WG of the IETF.
> 
>        Title           : The Messaging Layer Security (MLS) Architecture
>        Authors         : Emad Omara
>                          Benjamin Beurdouche
>                          Eric Rescorla
>                          Srinivas Inguva
>                          Albert Kwon
>                          Alan Duric
> 	Filename        : draft-ietf-mls-architecture-06.txt
> 	Pages           : 33
> 	Date            : 2021-03-08
> 
> Abstract:
>   The Messaging Layer Security (MLS) protocol [MLSPROTO] document has
>   the role of defining a Group Key Agreement, all the necessary
>   cryptographic operations, and serialization/deserialization functions
>   necessary to create a scalable and secure group messaging protocol.
>   The MLS protocol is meant to protect against eavesdropping,
>   tampering, message forgery, and provide good properties such as
>   forward-secrecy (FS) and post-compromise security (PCS) in the case
>   of past or future device compromises.
> 
>   This document, on the other hand is intended to describe a general
>   secure group messaging infrastructure and its security goals.  It
>   provides guidance on building a group messaging system and discusses
>   security and privacy tradeoffs offered by multiple security mechanism
>   that are part of the MLS protocol (ie. frequency of public encryption
>   key rotation).
> 
>   The document also extends the guidance to parts of the infrastructure
>   that are not standardized by the MLS Protocol document and left to
>   the application or the infrastructure architects to design.
> 
>   While the recommendations of this document are not mandatory to
>   follow in order to interoperate at the protocol level, most will
>   vastly influence the overall security guarantees that are achieved by
>   the overall messaging system.  This is especially true in case of
>   active adversaries that are able to compromise clients, the delivery
>   service or the authentication service.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-mls-architecture/
> 
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-mls-architecture-06.html
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-mls-architecture-06
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> 
> _______________________________________________
> MLS mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/mls