Re: [Cfrg] IETF Networking Working Group proposal: Messaging Layer Security Architecture

Richard Barnes <rlb@ipv.sx> Sat, 03 February 2018 16:54 UTC

Return-Path: <rlb@ipv.sx>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F74F12D946 for <cfrg@ietfa.amsl.com>; Sat, 3 Feb 2018 08:54:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 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, URIBL_BLOCKED=0.001] 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 RSp2kS0pmPyT for <cfrg@ietfa.amsl.com>; Sat, 3 Feb 2018 08:54:29 -0800 (PST)
Received: from mail-wr0-x236.google.com (mail-wr0-x236.google.com [IPv6:2a00:1450:400c:c0c::236]) (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 5F42C12D941 for <cfrg@ietf.org>; Sat, 3 Feb 2018 08:54:29 -0800 (PST)
Received: by mail-wr0-x236.google.com with SMTP id h9so12469478wre.12 for <cfrg@ietf.org>; Sat, 03 Feb 2018 08:54:29 -0800 (PST)
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=N7B4ACLwfzRI6873/c7T3wkDJD+Vx+CUR3GB08/mvhE=; b=f86XkrTrl7SHRCJa0ly0EoAMNANkxf5+CIMN57BC0xVIcBlEe1pdNusWaE618rc1XT yrOvXe2VQ9CuxqmA3YpTZNgg4QztKxiI90Gv3Zp3MtHNAch7VlMB7Uts9sdU9+jHhMUw 4QxviG464noJLvoBwF5y0LJDO7Uy+PQiJXbZpU0ZR2LfRS1ukuPlobwxb3IOEyV7TEgv vKF91XAcnSHg2KoPOk2kBhypZcK+wc0U/eyME99QUVc4NkuHp/t7wlVfsDdN4k7AG7u5 IK8hz2n9okUg2Nhp2VoJTjP//4zqE7guvLkKP221WsgRq8+GIg4FsZmVxA9dXmkBLRJW winA==
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=N7B4ACLwfzRI6873/c7T3wkDJD+Vx+CUR3GB08/mvhE=; b=m7mQGjEeEGRRvnFEs3VElSlbv8oOW5qECRBSoqk+d6ExJ+0r/bk+SNGYoP+/Nt5hlM maSqAnX9NMkfF+IxKBt25yCCF/GinAI7d71rcc53nzpd6AObkdhQbeAQ1uH73/2sPCS8 YfIHx2NgSnqp5j6yYaPIQFyRwh6lE740v+waHEqeKpuc5HhNEgbOGSSyRt2/vLggn67U 0KHiLLYa0KmZXLynH4KfX94Nq+XwucmEVG9pRSK9/hRZlKWexlJTaklOupsZHHQ9r1nH QuSkwS+onkXAmWPRRlZP55MEw8zswTWfKGt9MMEVtNnNotLGw0NOOu4mdP2WtMLVNVAc q0Sg==
X-Gm-Message-State: AKwxytceTeourhnlaL52uacGqgB4ZJM0wxNKvbFrmdGjAsLeHD6FiZiZ eAFe/Yw4FUCiQvZoxuqgom6+F0OYH3sn5pzXGY3b4Q==
X-Google-Smtp-Source: AH8x227Si90zavC1dHwiWHlECA4LMjg94rADCQqdg7YS+a5cUIrZoZnkWwrIrS+e217prL8bO5qFlxzCZzfAlqkANQ4=
X-Received: by 10.223.131.230 with SMTP id 93mr14660992wre.59.1517676867834; Sat, 03 Feb 2018 08:54:27 -0800 (PST)
MIME-Version: 1.0
Received: by 10.28.20.66 with HTTP; Sat, 3 Feb 2018 08:54:27 -0800 (PST)
In-Reply-To: <FC887F36-8025-47E2-88B7-411DE7C426CB@nadim.computer>
References: <d67bb7b0-7a2b-f21e-3209-cdf67d5bc72c@a-oben.org> <81B7992A-D88C-45AA-856B-7C0F834B43AF@inria.fr> <FC887F36-8025-47E2-88B7-411DE7C426CB@nadim.computer>
From: Richard Barnes <rlb@ipv.sx>
Date: Sat, 03 Feb 2018 08:54:27 -0800
Message-ID: <CAL02cgT52oTNZgi6RSM9-Skm6+Hmg6Df+roZvbc3XYhjx+7CEQ@mail.gmail.com>
To: Nadim Kobeissi <nadim@nadim.computer>
Cc: Benjamin Beurdouche <benjamin.beurdouche@inria.fr>, Simon Friedberger <simon.cfrg@a-oben.org>, draft-omara-mls-architecture@ietf.org, draft-barnes-mls-protocol@ietf.org, cfrg@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c0defd2976842056451aeab"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/1b2KJQO902I5WaZHG99dq3aoX4M>
Subject: Re: [Cfrg] IETF Networking Working Group proposal: Messaging Layer Security Architecture
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cfrg/>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Feb 2018 16:54:34 -0000

Hey Nadim,

Yeah, a few of us were discussing this privately to get it to escape
velocity, but it'll all be public from here on out.  We submitted a request
for an IETF mailing list yesterday, so it should be set up soon.  I think
an announcement will go out automatically on ietf-announce@ietf.org when
it's created, but I'll try to remember to copy it here.

--Richard


On Sat, Feb 3, 2018 at 6:48 AM, Nadim Kobeissi <nadim@nadim.computer> wrote:

> Hi there Benjamin & al.,
> A lot of us have been kept in the dark regard this. Is there a mailing
> list where future drafts can be discussed? How can one contribute
> improvements, suggestions etc. for review and future inclusion?
>
> Nadim
> Sent from my computer
>
> > On Feb 3, 2018, at 12:41 PM, Benjamin Beurdouche <
> benjamin.beurdouche@inria.fr> wrote:
> >
> > Hi Simon,
> >
> >> On Feb 3, 2018, at 12:30 PM, Simon Friedberger <simon.cfrg@a-oben.org>
> wrote:
> >>
> >> I haven't seen this being discussed here and some people might be
> >> interested:
> >>
> >> https://datatracker.ietf.org/doc/draft-omara-mls-architecture/
> >>
> >> Unfortunately the MLSPROTO reference doesn't have a link. Does anybody
> >> have more info on this? What is the intended use-case? What is the
> >> attacker model?
> >
> > Here is the reference for the MLS protocol spec draft -00
> > https://datatracker.ietf.org/doc/draft-barnes-mls-protocol/
> >
> > Keep in mind that as it is an initial document, many of these things
> > have yet to be discussed in depth and formalized… :)
> >
> > Best,
> > Benjamin & al.
> > _______________________________________________
> > Cfrg mailing list
> > Cfrg@irtf.org
> > https://www.irtf.org/mailman/listinfo/cfrg
>
>