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

jeff.hodges@kingsmountain.com Tue, 27 March 2018 23:02 UTC

Return-Path: <jeff.hodges@kingsmountain.com>
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 EEFA1126CB6 for <mls@ietfa.amsl.com>; Tue, 27 Mar 2018 16:02:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.737
X-Spam-Level:
X-Spam-Status: No, score=-0.737 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_NUMERIC_HELO=1.164, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=kingsmountain.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 GlE7qvi2HrQ2 for <mls@ietfa.amsl.com>; Tue, 27 Mar 2018 16:02:46 -0700 (PDT)
Received: from gproxy2-pub.mail.unifiedlayer.com (gproxy2-pub.mail.unifiedlayer.com [69.89.18.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12D9B124B18 for <mls@ietf.org>; Tue, 27 Mar 2018 16:02:46 -0700 (PDT)
Received: from cmgw2 (unknown [10.0.90.83]) by gproxy2.mail.unifiedlayer.com (Postfix) with ESMTP id 161C91E0A0D for <mls@ietf.org>; Tue, 27 Mar 2018 17:02:39 -0600 (MDT)
Received: from box514.bluehost.com ([74.220.219.114]) by cmgw2 with id TB2b1x00J2UhLwi01B2eqL; Tue, 27 Mar 2018 17:02:39 -0600
X-Authority-Analysis: v=2.2 cv=M5g9E24s c=1 sm=1 tr=0 a=9W6Fsu4pMcyimqnCr1W0/w==:117 a=9W6Fsu4pMcyimqnCr1W0/w==:17 a=IkcTkHD0fZMA:10 a=v2DPQv5-lfwA:10 a=skbIlk6SAAAA:8 a=zfccQYhVbGtIfRN0bH8A:9 a=QEXdDO2ut3YA:10 a=P5SZwATmzn4K3VfFWgKo:22
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kingsmountain.com; s=default; h=MIME-Version:Content-Type:In-Reply-To: References:Subject:Cc:To:From:Message-ID:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=lzoOLEYHzIaosns+z1jGLd1uX3mCo6kxAw4RDdhVOoQ=; b=CRk6QBeidTJDH8Gm3mDz+xOR+ r2IUmG3tKz/qjdLV+2qKmnIm7+PgvdxgpyCBgS+lyNIV7AtX1PiWQ5sjgjhKg5szFHDVzFsVyRCth WCIjKX2PebWl2n+qwwdiM6jyxX;
Received: from [127.0.0.1] (port=39109 helo=box514.bluehost.com) by box514.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89_1) (envelope-from <jeff.hodges@kingsmountain.com>) id 1f0xbv-0019Y2-0I; Tue, 27 Mar 2018 17:02:35 -0600
Received: from 67.188.157.169 ([67.188.157.169]) by box514.bluehost.com (Horde Framework) with HTTPS; Tue, 27 Mar 2018 17:02:34 -0600
Date: Tue, 27 Mar 2018 17:02:34 -0600
Message-ID: <20180327170234.Horde.43MSPLLX_Qj2qLxxX-UUuL3@box514.bluehost.com>
From: jeff.hodges@kingsmountain.com
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Cc: Nadim Kobeissi <nadim@symbolic.software>, Suhas Nandakumar <suhasietf@gmail.com>, mls@ietf.org, Raphael Robert <raphael@wire.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> <CAMRcRGSz031jYrvOHi1aMVEofxnYHjBODvaR7PJg5bF-Lw_59w@mail.gmail.com> <6A75C740-6759-448D-9BC8-17A459D5F36E@symbolic.software> <87370lkzmn.fsf@fifthhorseman.net>
In-Reply-To: <87370lkzmn.fsf@fifthhorseman.net>
User-Agent: Horde Application Framework 5
Content-Type: text/plain; charset="utf-8"; format="flowed"; DelSp="Yes"
MIME-Version: 1.0
Content-Disposition: inline
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box514.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - kingsmountain.com
X-BWhitelist: no
X-Source-IP: 127.0.0.1
X-Exim-ID: 1f0xbv-0019Y2-0I
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: (box514.bluehost.com) [127.0.0.1]:39109
X-Source-Auth: jeff.hodges@kingsmountain.com
X-Email-Count: 2
X-Source-Cap: a2luZ3Ntb3U7a2luZ3Ntb3U7Ym94NTE0LmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/mls/H9MAHOHBzSTLPLOgyWy0YJv2LAI>
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: Tue, 27 Mar 2018 23:02:47 -0000

+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