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

Richard Barnes <rlb@ipv.sx> Mon, 26 March 2018 21:46 UTC

Return-Path: <rlb@ipv.sx>
X-Original-To: mls@ietfa.amsl.com
Delivered-To: mls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1818E126CF6 for <mls@ietfa.amsl.com>; Mon, 26 Mar 2018 14:46:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ipv-sx.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1tz5KQXEMszN for <mls@ietfa.amsl.com>; Mon, 26 Mar 2018 14:46:17 -0700 (PDT)
Received: from mail-wr0-x229.google.com (mail-wr0-x229.google.com [IPv6:2a00:1450:400c:c0c::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03096126CB6 for <mls@ietf.org>; Mon, 26 Mar 2018 14:46:16 -0700 (PDT)
Received: by mail-wr0-x229.google.com with SMTP id z8so20360955wrh.7 for <mls@ietf.org>; Mon, 26 Mar 2018 14:46:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=/7PX27/A5ult43GOUbAmn1QFSBXTD0fTyBuZo7go9BU=; b=UI96EetzChCY6rKZStzZUNu4KstphvseJoZa9jt7FnnLSaYHuCg/MzeyuGzTJMnojE JJel/xBXGF0pMpRACkdfNNaemNnBXXBh0vGfsz8GfpTG3q9rCcSovBNH8tbZBMI4C3p5 OgvgnoaBgdOllHW32HeCbbsPttBZEj7HDbA5d5A3F8duZuSIRFKSZyYyY1z/H/P3NmZM e8Po9+RWd8bKpkcHXh5M8BiivnsDQQ8MUQmcotW0hzfL20o2EBEbto7UBoQCCxCRuvQT v1JfSTBaBiPdWe0Vhjcv718WbZURxvLsBAp1XB2l6BvVFg6YpdQxq4aXh+2wGOdSubgF u1jQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=/7PX27/A5ult43GOUbAmn1QFSBXTD0fTyBuZo7go9BU=; b=RxhyPAzGJUV5kxXNvu3iY5Sm4hENiGEllJ2oVEN7UACtKUnM87ANbGy2rFYip9nhWD j5pZwF6zQYBGvNHD9sjDXMHzA/yJLmXjwP8uPuof+PZ0f1qPt9OUCFyT3livAGYZl3vr Mja13kciKNbt6MgklxP7rvEMrIaYaTY6DURHmraZnV4QQMcwbB4fh1IbplATRG5jm8ri 9F/VSzYxEm51xGWG2soR4OpBfxPW6TRqYyTDzg5MnI2H7IG3ONmSSJWMLWuKYnttTqzP Cnua8HIxv8WPHSNE0xDwrLwMufjD+d1SpX/QCVvg5CD442+Dxr84ew9ghBgYnMxiYHej MuCQ==
X-Gm-Message-State: AElRT7HmKCgmAS8//3JKK/a/7/azbY/QRVdY0LRdcYBiBRocSftciKiQ w7Il5WFjHs2jciGEdXhShUqWsLIo9s8FFlJ1qiQ1oQ==
X-Google-Smtp-Source: AG47ELvLoXNh+iGrsT5IPfYLG63FSplICsX494Vf705HZpmxyvvq4tRcdjAsiMTaCWM7QuTGNTEAt5jTHNYFPwLxcuk=
X-Received: by 10.223.135.83 with SMTP id 19mr17485956wrz.150.1522100775454; Mon, 26 Mar 2018 14:46:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.12.140 with HTTP; Mon, 26 Mar 2018 14:46:14 -0700 (PDT)
In-Reply-To: <29A3652D-76EB-4830-8337-819EE19D597C@gmail.com>
References: <87r2o9n277.fsf@fifthhorseman.net> <CAG3f7MiJ5Jtxtk9OLMx10HApx7gV6xn103qaPBrGpH7kKgnQOA@mail.gmail.com> <FD644F8C-38BA-4573-B7F6-EF6AC4FEB57C@fb.com> <1521900339.2114148.1314586920.36507FA3@webmail.messagingengine.com> <E0F60678-8BAD-42C3-893F-A71685C60B23@wire.com> <29A3652D-76EB-4830-8337-819EE19D597C@gmail.com>
From: Richard Barnes <rlb@ipv.sx>
Date: Mon, 26 Mar 2018 22:46:14 +0100
Message-ID: <CAL02cgTap4TD0UiyqsQ0Ltdhv=iaXTBoaZrVi3HRmR3q84VboA@mail.gmail.com>
To: Rich Persaud <persaur@gmail.com>
Cc: Raphael Robert <raphael@wire.com>, mls@ietf.org
Content-Type: multipart/alternative; boundary="001a1146c2f8089df4056857b4ba"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mls/LK3zaEsNOUVU2BVHGXyrq62hWtw>
Subject: Re: [MLS] MLS: the WG name should include "group"
X-BeenThere: mls@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Messaging Layer Security <mls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mls>, <mailto:mls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mls/>
List-Post: <mailto:mls@ietf.org>
List-Help: <mailto:mls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mls>, <mailto:mls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2018 21:46:19 -0000

While I have some sympathy for DKG's point, I agree with Raphel and Katriel
that things are clear enough as-is.  In addition, if there's any ambiguity,
it should be cleared up by the charter.

If we're going to change, I admit that I find MSG pretty appealing.
Topical and tasty!

On Mon, Mar 26, 2018 at 10:23 AM, Rich Persaud <persaur@gmail.com> wrote:

> On Mar 24, 2018, at 11:25, Raphael Robert <raphael@wire.com> wrote:
>
> We looked at a number of alternatives to MLS and in the end none of them
> seemed to be substantially better than “Messaging Layer Security”, but that
> doesn’t mean the name cannot be changed.
>
>
> There is potential for collision with the MLS acronym that has been used
> for years (decades?), especially when combined with search terms like
> "security" or "cryptography":  https://en.wikipedia.org/
> wiki/Multilevel_security
> <https://en.m.wikipedia.org/wiki/Multilevel_security>
>
> Rich
>
> _______________________________________________
> MLS mailing list
> MLS@ietf.org
> https://www.ietf.org/mailman/listinfo/mls
>
>