[MLS] mls wg milestones

Sean Turner <sean@sn3rd.com> Wed, 13 February 2019 02:49 UTC

Return-Path: <sean@sn3rd.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 052421277D2 for <mls@ietfa.amsl.com>; Tue, 12 Feb 2019 18:49:01 -0800 (PST)
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=sn3rd.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 st6keik0d0Hb for <mls@ietfa.amsl.com>; Tue, 12 Feb 2019 18:48:59 -0800 (PST)
Received: from mail-qt1-x832.google.com (mail-qt1-x832.google.com [IPv6:2607:f8b0:4864:20::832]) (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 AF31F130F2B for <mls@ietf.org>; Tue, 12 Feb 2019 18:48:59 -0800 (PST)
Received: by mail-qt1-x832.google.com with SMTP id p25so705765qtb.3 for <mls@ietf.org>; Tue, 12 Feb 2019 18:48:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=oEFGVmXGz5z30PzZzgdJav6n+Re4ZdLHZxjfsmfDx9g=; b=SgYBgE6Z1du2HPC7nMV/KSue2f8aZvCWGjb1ZFy/sUK7kqGWgwVSqxs1ono0xfFWtf thzuiQTnkpX/Ghwalq6+L8QCjn+3EG5rEOwE8xof5IUR2HUXB0DkvjVHuevg9F+MpIMS VVX9D4O3onJUxrjVI76gbTydqpy12VFu8TYnU=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=oEFGVmXGz5z30PzZzgdJav6n+Re4ZdLHZxjfsmfDx9g=; b=e/KwPbSIHxPUa6eGq1X9d1dadkmPnhVZznamNjVIY4VQPRN7lTwNCZAMvXodX8k0bt NmrACWynR59SrY6Y0jf9xQZe4xyXE+o/bkIdvtj4iUricER5lf2CVYPc8hLQI+HXFE3H OqbK5JVrAGIz5QUKXo9NW2EDLC3sMXe5GbwJk5JdZCFRwld19wfXbnwAuT/TIqQyZA44 8hTm4f73orIRBMLJdo6DPX6sbPlFPyZdw7nQFWpJurRCz30KwM5vbXzMG/Ye3nrmQ4fJ iC7m4Lq5PncMItKQX8JoIDP4JgLZB+FqfV2sPZ03Sd/NQGl9v967F5LuSp9r5yEKGtRM Mxrg==
X-Gm-Message-State: AHQUAuajJaBcYL8ypk/WY1sxSfMCcZJfYqQKJ3Jpw4hH60Q3qiiQKA1s DVkw9jxmH61qcalMpvry8IqTi8kKRSc=
X-Google-Smtp-Source: AHgI3IbOq3x2KGH5benM6iEHvP3GkSRqWdbr4oGToR1RRnPBLiBW3UlAy2Ch8e2ShoZEaJqZlTgzHA==
X-Received: by 2002:a0c:d968:: with SMTP id t37mr5078724qvj.195.1550026138244; Tue, 12 Feb 2019 18:48:58 -0800 (PST)
Received: from [172.16.0.18] ([96.231.217.246]) by smtp.gmail.com with ESMTPSA id m65sm14797024qkf.48.2019.02.12.18.48.57 for <mls@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Feb 2019 18:48:57 -0800 (PST)
From: Sean Turner <sean@sn3rd.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Message-Id: <2F1087EE-17F6-41E5-8BE5-FF782E136042@sn3rd.com>
Date: Tue, 12 Feb 2019 21:48:56 -0500
To: mls@ietf.org
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mls/sGn5Fp6Y6T2OJ7eKdEUwhab1cDA>
Subject: [MLS] mls wg milestones
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: Wed, 13 Feb 2019 02:49:01 -0000

All,

Ben has reminded us that our current milestones need to be updated.  Instead of the chairs randomly picking some dates we’d like to hear from you what you think about the following changes:

1. Merge the following because message protection ended up in the key management draft:

Initial working group document adopted for message protection
Initial working group documents for architecture and key management

to become

Initial working group documents for architecture and key management (includes message protection)

and mark them as done.

2) Add the following because we’re planning to adopt a federation draft and Emad said he can get an initial draft done before Prague:

Date: May 2019
Milestone: Initial working group document adopted for federation (key establishment, authentication, and confidentiality services)

3) Push the following dates out:

Add 9 month because because we’re planning on a pause:

Sep 2019  Submit message protection protocol to IESG as Proposed Standard
Jun 2019  Submit key management protocol to IESG as Proposed Standard

Add 6 months:

Jan 2019 Submit architecture document to IESG as Informational

spt