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

Benjamin Beurdouche <> Mon, 08 March 2021 13:26 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 923B43A29F3 for <>; Mon, 8 Mar 2021 05:26:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id fDnFlfJKsWOi for <>; Mon, 8 Mar 2021 05:26:45 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0BFE33A29F4 for <>; Mon, 8 Mar 2021 05:26:44 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.81,232,1610406000"; d="scan'208";a="496730075"
Received: from (HELO []) ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Mar 2021 14:26:42 +0100
From: Benjamin Beurdouche <>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.\))
Date: Mon, 8 Mar 2021 14:26:42 +0100
References: <>
To: ML Messaging Layer Security <>
In-Reply-To: <>
Message-Id: <>
X-Mailer: Apple Mail (2.3654.
Archived-At: <>
Subject: Re: [MLS] I-D Action: draft-ietf-mls-architecture-06.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Messaging Layer Security <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 08 Mar 2021 13:26:49 -0000

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.


> On 8 Mar 2021, at 14:12, 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:
> There is also an HTML version available at:
> A diff from the previous version is available at:
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at
> Internet-Drafts are also available by anonymous FTP at:
> _______________________________________________
> MLS mailing list