Re: [MLS] MLS: the WG name should include "group"

Shivan <> Sat, 24 March 2018 13:15 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1BCD7128D2E for <>; Sat, 24 Mar 2018 06:15:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id kaFm-zyxP_Tk for <>; Sat, 24 Mar 2018 06:15:12 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4010:c07::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B1E341201F2 for <>; Sat, 24 Mar 2018 06:15:11 -0700 (PDT)
Received: by with SMTP id a22-v6so22050623lfg.9 for <>; Sat, 24 Mar 2018 06:15:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=dFHgFTfvJlSjXDaf+DbKQzTeO5MLjBPuD3Z+t8TKNw8=; b=J5N0ToZJswxsr8FAjAccjHQCG7TK6jY/szWNXO5yvRUndldrKl4DJ5MYRAiQot0pUe T/UY0+hOj545CNCA2eKsoFcvT3sRxB0NGL7Ka1skqxeVrRreUXffsxBOJytuZLwopksB J8BhEyE49axfvhYlkclf4De5Ak7ndPg52hGcRN2dxXdNAAZCokXM/c/Gak1vEFneTivs Vcl4e3vNvpzH8vsTfMzIBYB44/f6F1NkgYwBXRKmPW6lRtbLxlWZpID1t7wkNi30vmqz DCN0i4SbuA5E8Ou+yifzgKWnlhEPbj7a4jZTyi8A31kgFh7fiWhNyuxg0LYM5vFEiINn WfKw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=dFHgFTfvJlSjXDaf+DbKQzTeO5MLjBPuD3Z+t8TKNw8=; b=lahxp8Le61F3FbSvePG8lldXlmOqRl06H6qyn19Ctiabet8ecrHpXH4RXhRmmSgMgx FyEIz5/H0sFf4224p4DNujzHDTby4zlCo0Mu8A7q0KS+LgsGCgmcNDrMt2JXN3Ln8sfi hHl+CXAd66ZSb5re4CShmsQHa2OEEKIjtx4Gp9ErsSPwiSLGncYrRU3/uh9vrd2+6U3I yL7AwqcGVQ2H5IZ4UdFwu3bKQd2wvLqmkhnzQ5RM6YYKXYhaE5FY1IPcnW85K/vvybdh VWjrIarnv1/fBuq5DmQIU/bUmossLzgk5IiXYREcahSqwF/wEQDfGVXzsGzIInP2Ix15 JEmw==
X-Gm-Message-State: AElRT7EiIpULEg4GIAHqdAV5uiJWun5l7TrGDKTcRS6PajZltIFpC6Yc uakyKkvApllAtYJljTSBWs3jnSyM5fq9R8UC82Y=
X-Google-Smtp-Source: AG47ELsPySNhCTPIc/4gWCnSo+5mASOKij68bv8yfigaVo4T9N5+udFOeANpa9GP22PLLjeZ73Wx+Q5pbpYhL7Cbeyg=
X-Received: by with SMTP id y6mr13483599lje.118.1521897309797; Sat, 24 Mar 2018 06:15:09 -0700 (PDT)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Shivan <>
Date: Sat, 24 Mar 2018 13:14:58 +0000
Message-ID: <>
To: Daniel Kahn Gillmor <>
Content-Type: multipart/alternative; boundary="94eb2c1909b889028b056828548c"
Archived-At: <>
Subject: Re: [MLS] MLS: the WG name should include "group"
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Messaging Layer Security <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 24 Mar 2018 13:15:14 -0000

+1 the name seems to be inspired by TLS but the drafts concern themselves
explicitly with group messaging, not messaging as a whole.

On Sat, Mar 24, 2018, 11:28 AM Daniel Kahn Gillmor <>

> Thanks for all the work that has gone into the proposed MLS architecture
> and protocol drafts already.
> As we move toward working group formation, i'm a little bit concerned
> that the ostensible name of the project ("message layer security")
> doesn't adequately describe the most salient features.
> We spent most of the time at the BoF in IETF 101 London talking about
> the design of the group key agreement scheme and the strong
> cryptographic properties we want it to provide -- and i suspect that
> most of the work in any formed WG will center around that problem.
> So it seems odd to me that the word "group" doesn't appear in the name
> "MLS".
> I'm no good at acronyms, but i'll just throw out two alternatives:
>   MSG: Messaging Security for Groups
>   MESSAGE: Message Encryption and Security Standard for Asynchronous Group
> Environments
> I hope since the WG isn't yet formed, it's not too late to consider a
> change to the name.  We ought to be up front about the group-specific
> context that we're talking about here, as we already have a security
> layer that works for messages passing between two endpoints
> synchronously (TLS) and it'd be nice to clearly carve up the territory.
>         --dkg
> _______________________________________________
> MLS mailing list