IETF Logo Mail Archive

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

Jon Millican <jmillican@fb.com> Thu, 19 July 2018 22:43 UTC

Return-Path: <prvs=0738e67540=jmillican@fb.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 4F34F131069 for <mls@ietfa.amsl.com>; Thu, 19 Jul 2018 15:43:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.741
X-Spam-Level:
X-Spam-Status: No, score=-2.741 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_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fb.com header.b=M8pJ7EPN; dkim=pass (1024-bit key) header.d=fb.onmicrosoft.com header.b=ONod7Sk2
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 J-IoVyubhQ4W for <mls@ietfa.amsl.com>; Thu, 19 Jul 2018 15:43:18 -0700 (PDT)
Received: from mx0a-00082601.pphosted.com (mx0a-00082601.pphosted.com [67.231.145.42]) (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 B1BF413103C for <mls@ietf.org>; Thu, 19 Jul 2018 15:43:18 -0700 (PDT)
Received: from pps.filterd (m0044012.ppops.net [127.0.0.1]) by mx0a-00082601.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w6JMeUmk013796; Thu, 19 Jul 2018 15:43:16 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=facebook; bh=utLs40cYQdkRgEaAV0xve++l/qo+zcRU30+gu3a9W38=; b=M8pJ7EPN83VHDekSLcyzsGfPQhoB/KbwnqEKFZde2mT9Xb/S9T7SGsOVS2xiTKmiF/pg EZRAW++06PU2rTEJ7NX4+Q4Ogl9aHzSzdwzNGzLXECUL88NGojwJOLolZoJZfyoVd4W7 o1m5faHflTZ+IqU1XUdvBUQjUvOeic0hTEc=
Received: from mail.thefacebook.com ([199.201.64.23]) by mx0a-00082601.pphosted.com with ESMTP id 2kb1wsr9j2-1 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 19 Jul 2018 15:43:16 -0700
Received: from NAM04-SN1-obe.outbound.protection.outlook.com (192.168.54.28) by o365-in.thefacebook.com (192.168.16.19) with Microsoft SMTP Server (TLS) id 14.3.361.1; Thu, 19 Jul 2018 15:43:14 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.onmicrosoft.com; s=selector1-fb-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=utLs40cYQdkRgEaAV0xve++l/qo+zcRU30+gu3a9W38=; b=ONod7Sk2u4UuuH0KLm28WOUzEjkLuH0mkBgef13A8B3QnLOcUbYtpRket4hhHNczI9T+UXXnLh260ZWhSHDookK2ENLNXTBSHdBoAszOyGrj3OfRO3xX7CQwT0FRdJ7tV5jym3So4CNzu4cojxLO2HYcTDlLoDmSQTeDo8H1l4k=
Received: from SN6PR15MB2205.namprd15.prod.outlook.com (52.135.64.145) by SN6PR15MB2383.namprd15.prod.outlook.com (52.135.65.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.952.18; Thu, 19 Jul 2018 22:43:12 +0000
Received: from SN6PR15MB2205.namprd15.prod.outlook.com ([fe80::543d:ab65:689f:8f6b]) by SN6PR15MB2205.namprd15.prod.outlook.com ([fe80::543d:ab65:689f:8f6b%3]) with mapi id 15.20.0973.016; Thu, 19 Jul 2018 22:43:12 +0000
From: Jon Millican <jmillican@fb.com>
To: "jeff.hodges@kingsmountain.com" <jeff.hodges@kingsmountain.com>, Daniel Kahn Gillmor <dkg@fifthhorseman.net>
CC: "mls@ietf.org" <mls@ietf.org>, Raphael Robert <raphael@wire.com>, Suhas Nandakumar <suhasietf@gmail.com>, Nadim Kobeissi <nadim@symbolic.software>
Thread-Topic: [MLS] MLS: the WG name should include "group"
Thread-Index: AQHTw2NOh1i9TiA6Lk6ldNKeXbExraPfXXAAgAAIAt2AAAYngIAAFj8AgAABzgCAAdXwAIADO1wAgAAjqQCAsuFLgA==
Date: Thu, 19 Jul 2018 22:43:12 +0000
Message-ID: <396D9379-92F6-47F1-97D0-B50400E92816@fb.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> <20180327170234.Horde.43MSPLLX_Qj2qLxxX-UUuL3@box514.bluehost.com>
In-Reply-To: <20180327170234.Horde.43MSPLLX_Qj2qLxxX-UUuL3@box514.bluehost.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.252.136.137]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SN6PR15MB2383; 7:nLYWZTHvGJkH1DpmuekpI9g0rDs12yPlXhWRvWG+IqxkNknsJRjV+ijfoP44Iag2ugzVQsHB8+fybGx9ut8ORrqPdcVv1uJh271bvbAYrur2JHvhXvUArbztoqfucz63V6auEtCW1HBJH45TbUQcRcCtC1xIMDFDBvym9Wksw2XiU10XWQdeQps3EB0QVieF2ljPgAr2+jei8SMP44byIr212lkqnz7GUOVFBWOczydRut96rbOK4Q1vpAOIRwp+; 20:JMZ6nt0mYnSaxQ2nl7aCZyAitQUzPwC0huUpxoC7O2ZRPFvy8+YNPO+Jmx1eaq7oJmWOa8gSe2XxRKKOJT0/77Ln9cX5TDozE/fWXu6cTw5GOeypqqrGzmZkNBrt4MMRu7XVPhZgBwaXxI8veWoKXtc2QMaRC5SnEEWpfnTAM8Y=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 4109e348-784d-4893-8ba4-08d5edc90285
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989117)(5600067)(711020)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(2017052603328)(7153060)(7193020); SRVR:SN6PR15MB2383;
x-ms-traffictypediagnostic: SN6PR15MB2383:
x-microsoft-antispam-prvs: <SN6PR15MB23837AAFBA67B32812668E37DA520@SN6PR15MB2383.namprd15.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(10436049006162);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3231311)(11241501184)(944501410)(52105095)(10201501046)(3002001)(93006095)(93001095)(149027)(150027)(6041310)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123558120)(20161123562045)(6072148)(201708071742011)(7699016); SRVR:SN6PR15MB2383; BCL:0; PCL:0; RULEID:; SRVR:SN6PR15MB2383;
x-forefront-prvs: 0738AF4208
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(136003)(366004)(39860400002)(376002)(346002)(199004)(189003)(7736002)(66066001)(486006)(575784001)(6116002)(6486002)(82746002)(305945005)(2900100001)(4326008)(5250100002)(39060400002)(316002)(2906002)(83716003)(6306002)(2501003)(86362001)(33656002)(68736007)(14454004)(36756003)(478600001)(966005)(25786009)(476003)(6436002)(8676002)(186003)(53936002)(93886005)(26005)(8936002)(81166006)(97736004)(105586002)(81156014)(102836004)(110136005)(6246003)(229853002)(5660300001)(2616005)(11346002)(446003)(3846002)(76176011)(54906003)(256004)(6512007)(99286004)(6506007)(106356001); DIR:OUT; SFP:1102; SCL:1; SRVR:SN6PR15MB2383; H:SN6PR15MB2205.namprd15.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: fb.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: 5QiQ4DNjRHJXOaCauOK5IghtsYah3l+dgfhWB8oig5NofvZLxShlVnoINdEXY4mHtl1rRMx7is+rzOtPhKQShPtA8AHd4+I7ax2f0b8sD3HhnDrfczpSognttsTixHCw+hxomWK++Ejrv3lP7uikS5ymYky1UNZeESc6HFc0H8P0FuNftLEMLcntq9EcomMXTNe8impPJ/ezrlajtQ8Xtf7sbT1Z6rJrk/P04tpm6kt8ev3LP4AwvYj7untJHnxoSmLW1K9JEkoVET2hZai3VTUtQcJIOabJkfd7Wm+Cbel+R/zxrODINj0dX2I14vYaq8nu9xW+1dFYOMVrdhWSAbE5VYPByGtxKNh6jUXNQUg=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <BF65A162429C544DABEE96FB0E0946B5@namprd15.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 4109e348-784d-4893-8ba4-08d5edc90285
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Jul 2018 22:43:12.8059 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8ae927fe-1255-47a7-a2af-5f3a069daaa2
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR15MB2383
X-OriginatorOrg: fb.com
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-07-19_08:, , signatures=0
X-Proofpoint-Spam-Reason: safe
X-FB-Internal: Safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/mls/XyTgW8vZwnL-FmpOOfhOoy8PEjQ>
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:43:22 -0000

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=

v2.23.0 | Report a Bug | By Email