Re: [MLS] February MLS interop event

Richard Barnes <rlb@ipv.sx> Fri, 08 February 2019 17:15 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 8864112867A for <mls@ietfa.amsl.com>; Fri, 8 Feb 2019 09:15:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, 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 ewLwztEbcXDm for <mls@ietfa.amsl.com>; Fri, 8 Feb 2019 09:15:18 -0800 (PST)
Received: from mail-ot1-x334.google.com (mail-ot1-x334.google.com [IPv6:2607:f8b0:4864:20::334]) (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 8A6511200ED for <mls@ietf.org>; Fri, 8 Feb 2019 09:15:18 -0800 (PST)
Received: by mail-ot1-x334.google.com with SMTP id 32so6952601ota.12 for <mls@ietf.org>; Fri, 08 Feb 2019 09:15:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=CytonYcPVNVie2jz5MV7JrFNkZJ3tOzxxwkYEOAAT1c=; b=UpkTbQeokkb8ub8YhTWjv9Rvr8uv+ZkRmP7CKj165d00kY4KB9FKj7cInrHLec77XB kbzWRmrUbz4tXOm8JDWFxRDSQr8uDcdIXnDM3wDgQavs8O/E6JZoDjo9GHOoij0U2JUi EWkqm/jE1KDTrm7GNN8OrkcioyaxQi3mPI7TNuu3a1u/OPx0z28JbQV51FkX5sIplOfs mI+d7LYgBlUv6/fgf95a4lXOAUsaEUnxLA4pJRAMq7DMDPA9uWZ7qo304Vte+4pSpS/O f5UdNaF6LUGOz/gAhomWwfnS0htEBv4gH0F0sJ2ILmsvkV2+Koz5BOGdPVdRjEA4WdMz 3cbQ==
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; bh=CytonYcPVNVie2jz5MV7JrFNkZJ3tOzxxwkYEOAAT1c=; b=WaVg9PfQs8TyawP6ldw2WWTVyHUHo0yWJOs4wOS/g9QcLsH2//2q0oodZNVCEAy0cr YD741levN5ZyjXmyANC8Nz+lQMHZez41pqCohM6cd4umBjBEgFJrjut7EKop9Ph28LeH 9CLMclnOBC5j30AJCrBXnIFCQDLNug1zyvX65FZQR4dUDPdhsYLVRyxIbtb7PZt60KQm HWxHG+GVKdY15nfxP78Ldf2yh8x4Bu8un3SqP9S2SpSC7sML5ck51awfLPg03W97iV3/ WIe6ctd68FZgoR26sNBCn3lkCS6MLCadC3x+JL+MakiPqYWijX/L4fVSFvU6KbZ6TqKR Khdw==
X-Gm-Message-State: AHQUAuYVshizXmwTQ1rlrzVY9UH1NlEmFqu9hVmHQ/RwfJv9RrvE+xQa 1gHefbiskJnrqLMH6/o8jkqKugC0C8wk9Dspk8zKqZdCP2g=
X-Google-Smtp-Source: AHgI3IZSQgdR5Fk9tW4cJK/zF3vCyz2FfiQQMMB90AUcLMVd/JsaRReLNZMyEomYa8q7r1S1e0sEGROx0rupOTkwdr0=
X-Received: by 2002:a9d:6a92:: with SMTP id l18mr7306392otq.81.1549646117443; Fri, 08 Feb 2019 09:15:17 -0800 (PST)
MIME-Version: 1.0
References: <CAL02cgREZRVX3c_spWC+uR=Hx-4Q5-Oog0Sa71Gd77c72Wp8Zg@mail.gmail.com> <CAL02cgRoC7yQVys6fi44A8X1aU-yHX-sF2i1pG9XDBDOk9Zyrw@mail.gmail.com>
In-Reply-To: <CAL02cgRoC7yQVys6fi44A8X1aU-yHX-sF2i1pG9XDBDOk9Zyrw@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
Date: Fri, 08 Feb 2019 12:15:06 -0500
Message-ID: <CAL02cgTO3aiLGms_0-3V+AsigNTidDM0c6ePwaNC1pO75pN28w@mail.gmail.com>
To: Messaging Layer Security WG <mls@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005bafb80581651a57"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mls/HsIUd3w_X4lltpBqAqQ5DPTAWF8>
Subject: Re: [MLS] February MLS interop event
X-BeenThere: mls@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 08 Feb 2019 17:15:21 -0000

Summary of conclusions from this call:

- Folks weren't quite ready to do live interop
- In general, we should do interop async, via test vectors, and use calls
to debrief / discuss issues
- Next interop check-in targeted for Feb 18
  - Still targeting -03 test vectors in mls-implementations repo
  - ... with #115 to fix application key schedule
- A couple of actual test changes would be useful
  - Tests for the resolution algorithm
  - Tests for the key schedule (decoupled from a session)

Please indicate your availability for the next check-in in this Doodle:

https://doodle.com/poll/7b7hurwg268e86a9


On Sat, Jan 26, 2019 at 1:25 PM Richard Barnes <rlb@ipv.sx> wrote:

> OK, based on the Doodle results, let's shoot for 16:00-19:00 UTC
>
>
> https://www.timeanddate.com/worldclock/fixedtime.html?msg=MLS+Interop&iso=20190208T16&p1=1440&ah=3
>
> We can use the following Webex bridge:
>
> Join from a video conferencing system or application
> Meeting link: https://cisco.webex.com/meet/richbarn
> Dial: richbarn@cisco.webex.com
> Join using Microsoft Skype for Business: richbarn.cisco@lync.webex.com
> Toll Free: +1-866-432-9903
> Toll: +1-408-525-6800
> Access Code: 201006237
>
> If you're interested in joining, please make sure you're in the MLS
> Implementors Wire channel, which we'll use for text-based coordination.
>
>
> https://app.wire.com/join/?key=3tL-NJOoCKZlDXNU1H2c&code=kZOc0ujnDQ9Tq98tLfSt
>
>
> On Tue, Jan 15, 2019 at 8:01 PM Richard Barnes <rlb@ipv.sx> wrote:
>
>> Hey all,
>>
>> A few of us who are writing code for MLS are thinking of having an
>> informal interop event in early February.  If you'd like to participate,
>> please fill out this Doodle to help pick dates:
>>
>> https://doodle.com/poll/2yd3b2eydchis82b#table
>>
>> The interop target will be draft-ietf-mls-protocol-03.  We will try to
>> get everyone passing a common set of test vectors, covering, e.g.:
>>
>> - Tree math
>> - Derive-Key-Pair
>> - Message parsing and serialization
>> - Fully crypto calculations for a simple scenario
>>
>> This will be a remote meeting / teleconference.  I will send out Webex
>> details once we've picked a date/time.
>>
>> --Richard
>>
>>