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

Dave Cridland <> Mon, 26 March 2018 08:24 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 07E581205F0 for <>; Mon, 26 Mar 2018 01:24:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 304RgAFYPIwT for <>; Mon, 26 Mar 2018 01:24:13 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4010:c07::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 27DF51204DA for <>; Mon, 26 Mar 2018 01:24:13 -0700 (PDT)
Received: by with SMTP id t132-v6so26837038lfe.2 for <>; Mon, 26 Mar 2018 01:24:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=hejmSc4pQ/kjDXiIwc/9HmP+OfWCR7bEwVeGeurXfH4=; b=iKcCItlbTqw47FQzDtZPr1c3eXaE/7ZPVSYbcb/v2qsDtft2bPM3SEUXHbRt0J3ToD iZS/uUqG5FRzOqcp2ynTGeeX9CdVNUcynmA5uroPsHCJ5gEQLJnnMA1ygI0GZFyyCNXP 6j7TCD5b/iMcRoHyzBEAOVng0WK3m/mrHtBas=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=hejmSc4pQ/kjDXiIwc/9HmP+OfWCR7bEwVeGeurXfH4=; b=ZvI6MaMlHXwu20/jySyfX1Pjq1VyGcl6LYMpOTf/JaLbjJGN1x4GHKJOVdGfEm4lzC mqtHUc0NWp2dZzA8iJjEwkv24aU1/nw3GX1O6nIcWeAozRNQhaedza+hp9cL4GPTrHuR pRVrPxK5SyHvZZ/GzRg5QDyH9LuPfDGWxodIqe4GvVKmaecB7ksfbLAFv2AkdxXi4BLl FYl9MRs7kQChUIqLOqWQEJ56RtThGtboUh9WsLLtt29HWArevJCS2vywxDgMBksHsa3q ngWZvc3UXNnVnSrYYEurjVTKYEvYcO57jn9Uva79x2zfx7hf83MRUfMRuN9PokKBJrXA 9yQg==
X-Gm-Message-State: AElRT7HHjXjHioDamDdcvceqgGXEQdwdrkWImV7RBO7PmgNWxxR3f2sV wRsxeLEw+Q0iQoyvWKevGIKwHalrmee47H+MWXIdpD63
X-Google-Smtp-Source: AG47ELtcyGK5UtfnTmwKWU9Uv5tgiECMVfXpWQVAu0ul3AGnXvuCkOA3tUYVuOsM+6YGmms4dijqTwVBjB21Cch/XQo=
X-Received: by 2002:a19:9904:: with SMTP id b4-v6mr25142150lfe.51.1522052651317; Mon, 26 Mar 2018 01:24:11 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Mon, 26 Mar 2018 01:24:10 -0700 (PDT)
In-Reply-To: <>
References: <>
From: Dave Cridland <>
Date: Mon, 26 Mar 2018 09:24:10 +0100
Message-ID: <>
To: Daniel Kahn Gillmor <>
Content-Type: multipart/alternative; boundary="0000000000009c964705684c7ff8"
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: Mon, 26 Mar 2018 08:24:15 -0000

I believe we should make it out of wood. It's a renewable resource and, if
well-treated, will be more than adequate for keeping the effects of weather
off the cycles stored inside.

On 24 March 2018 at 11:27, 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