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

Joseph Lorenzo Hall <joe@cdt.org> Thu, 19 July 2018 22:51 UTC

Return-Path: <jhall@cdt.org>
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 6BACC130F16 for <mls@ietfa.amsl.com>; Thu, 19 Jul 2018 15:51:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cdt.org
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 5t_GIWrQ0lmW for <mls@ietfa.amsl.com>; Thu, 19 Jul 2018 15:50:52 -0700 (PDT)
Received: from mail-vk0-x234.google.com (mail-vk0-x234.google.com [IPv6:2607:f8b0:400c:c05::234]) (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 8E857130E5B for <mls@ietf.org>; Thu, 19 Jul 2018 15:50:52 -0700 (PDT)
Received: by mail-vk0-x234.google.com with SMTP id o82-v6so3369343vko.8 for <mls@ietf.org>; Thu, 19 Jul 2018 15:50:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cdt.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=treqjlSAzCT8IGVI1CPWTsoqRIDG6eXU3oM5Umecf6g=; b=TBevkspFGLvvGKfJqG1Y2bftVAKdhiNXNhp1HGsmQy/+ddOZ6hpl7UdmnZS6qDzeww K1o71bzy8+OEq1wWFPsWvuKgWjyQxILensuks8nKkM3x9rp2S4aM/CeLkoC2YAMQMVEI /z7MVtHpjYQCEddSMrn8OI0MERxGTiow67v7Q=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=treqjlSAzCT8IGVI1CPWTsoqRIDG6eXU3oM5Umecf6g=; b=F9aHtXc45GsdsGBotRFgL64wCcVBKJd9OZ3iOJ9l/DYQl6jDTavx6jgzbbMg0+oVrD virPHjMVKwsPho5e1OeEupFRVHk6it+FVIdmZ/Z5uCIYXwzasrgBzgwakhayH0TSEjPS XRUFImKRenhFT0gFCpmhEW+PladWC4Fjd10ensNPOuLI77ALZM4RnREBRCYrRtr3u3yk M62u3i8ilWVrHE0v/+nuBByAE2JeatpJZl4JPia9veYOOx7U3ob8lD50+kK5xNUWxh9g ODwnXp9kTExKbmmOcAIlSyNUuO7MNHzQ3TKgjqjUl/Q5gjIzWnkmtDRDcz46Ehk5J6gC 9+SQ==
X-Gm-Message-State: AOUpUlFy/uNu1KbUVQYupioA7xtc4p0pxQR9yh+G7UoxCB/5WDK+449u mOCwZcSkEIqa2WumKmyLY9FiFUuAeJEgapTQskH++sm5RWU=
X-Google-Smtp-Source: AAOMgped8P+0orLWIQkrN3PEtG0WAS134cViKTvytT7++nZGAkocyTqaY35HBF2PIiQDERj3fF6b5Kl7C3IjbT6zInw=
X-Received: by 2002:a1f:88ce:: with SMTP id k197-v6mr7093610vkd.85.1532040651201; Thu, 19 Jul 2018 15:50:51 -0700 (PDT)
MIME-Version: 1.0
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> <CAMRcRGSz031jYrvOHi1aMVEofxnYHjBODvaR7PJg5bF-Lw_59w@mail.gmail.com> <6A75C740-6759-448D-9BC8-17A459D5F36E@symbolic.software> <87370lkzmn.fsf@fifthhorseman.net> <20180327170234.Horde.43MSPLLX_Qj2qLxxX-UUuL3@box514.bluehost.com> <396D9379-92F6-47F1-97D0-B50400E92816@fb.com>
In-Reply-To: <396D9379-92F6-47F1-97D0-B50400E92816@fb.com>
From: Joseph Lorenzo Hall <joe@cdt.org>
Date: Thu, 19 Jul 2018 18:50:39 -0400
Message-ID: <CABtrr-V5ur3=mvS1sq1ZmMg4bKoUwZBeYGE5xfYr0TScs9CGDQ@mail.gmail.com>
To: jmillican@fb.com
Cc: =JeffH <jeff.hodges@kingsmountain.com>, Daniel Kahn Gillmor <dkg@fifthhorseman.net>, mls@ietf.org, raphael@wire.com, suhasietf@gmail.com, nadim@symbolic.software
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/mls/J41Usit-o5Ohd3Gc4MHeFlekl_4>
Subject: Re: [MLS] MLS: the WG name should include "group"
X-BeenThere: mls@ietf.org
X-Mailman-Version: 2.1.27
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: Thu, 19 Jul 2018 22:51:04 -0000

+1
On Thu, Jul 19, 2018 at 6:43 PM Jon Millican <jmillican@fb.com> wrote:
>
> This discussion came up again at the hackathon, and I think there was a fair bit of sympathy for the idea of at least changing the protocol name to MSG; for the reasons described in this thread.
>
> Personally I'd be keen to have something slightly more uniquely Googleable than MSG, but I don't think that MLS is any better in this regard.
>
> On 27/03/2018, 19:03, "MLS on behalf of jeff.hodges@kingsmountain.com" <mls-bounces@ietf.org on behalf of jeff.hodges@kingsmountain.com> wrote:
>
>     +1
>
>     Quoting Daniel Kahn Gillmor <dkg@fifthhorseman.net>:
>     > On Sun 2018-03-25 21:33:42 +0200, Nadim Kobeissi wrote:
>     >> I do not believe the name should be changed:
>     >>
>     >> 1. MLS is a protocol that is equally suited for pairwise messaging
>     >> as it is for group messaging
>     >> 2. The MLS name is elegant and mirrors TLS.
>     >
>     > "Mirroring TLS" is exactly what i'm afraid of.  This is a radically
>     > different protocol, performing demonstrably different work at a
>     > different position within the stack, with a different view on what
>     > interoperability even means.
>     >
>     > Let's make it very clear that this *is not* TLS, and that it is not a
>     > substitute for TLS.
>     >
>     > The protocol described in the documents is *not* equally-suited for
>     > pairwise messaging -- it has a number of subtle features that are
>     > included solely because it is intended to handle group messaging.  As
>     > other people have written upthread, the protocol this nascent WG aims to
>     > describe will handle pairwise messaging as a special case of group
>     > messaging.  It is not designed intentionally for pairwise messaging and
>     > if it were, it would have a different design.
>     >
>     >           --dkg
>
>
>
>     _______________________________________________
>     MLS mailing list
>     MLS@ietf.org
>     https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_mls&d=DwICAg&c=5VD0RTtNlTh3ycd41b3MUw&r=M0CVEJydBVUX_bvEqMa84Q&m=rfhSuK8vpcpFLcVQ8OMeZLwppm8O9uVb1XZ27wXlf60&s=BQG3-r7qCBQlhrrPGVNVJj6heSZcsNivR8jfE1ZmqzY&e=
>
>
> _______________________________________________
> MLS mailing list
> MLS@ietf.org
> https://www.ietf.org/mailman/listinfo/mls



-- 
Joseph Lorenzo Hall
Chief Technologist, Center for Democracy & Technology [https://www.cdt.org]
1401 K ST NW STE 200, Washington DC 20005-3497
e: joe@cdt.org, p: 202.407.8825, pgp: https://josephhall.org/gpg-key
Fingerprint: 3CA2 8D7B 9F6D DBD3 4B10  1607 5F86 6987 40A9 A871