[MLS] revising mls-architecture I-D

Sean Turner <sean@sn3rd.com> Thu, 12 November 2020 18:12 UTC

Return-Path: <sean@sn3rd.com>
X-Original-To: mls@ietfa.amsl.com
Delivered-To: mls@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id A51C53A146D for <mls@ietfa.amsl.com>; Thu, 12 Nov 2020 10:12:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 7qyDKKPFMPiY for <mls@ietfa.amsl.com>; Thu, 12 Nov 2020 10:12:23 -0800 (PST)
Received: from mail-qt1-x835.google.com (mail-qt1-x835.google.com [IPv6:2607:f8b0:4864:20::835]) (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 8CD003A146B for <mls@ietf.org>; Thu, 12 Nov 2020 10:12:23 -0800 (PST)
Received: by mail-qt1-x835.google.com with SMTP id n63so4651369qte.4 for <mls@ietf.org>; Thu, 12 Nov 2020 10:12:23 -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=Zoy2BHb8FAbLPKPJvA1Nz+Qc2DCliDagtPhHeQHEAoA=; b=XGQLcDjmtEJGpHujTS/i/l4RHls+csg30Kek62++saPxXIfdu2TF6CyKPb8hc+ys2g 3GqmhxhqwMW0sVxBgZsWdpL0hqHT3MNJFBlNClLCg+nUZgGtMOfTYcOWwxUnW3XuujrN HEg74UtBQthlrA2+F2JzBPBuSVkloDdlAIAsY=
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=Zoy2BHb8FAbLPKPJvA1Nz+Qc2DCliDagtPhHeQHEAoA=; b=SQLqaU34eTLGNyONHotC/lNZT9nsUG7qyVXvjssYYPEtYjDF7zqsSCRBv16gGSpKZW xk348Pv7zr8ld34a/uC16x18RMu9wK93IW3Ec5Uh/+GD5YlUhXn03mTchP+gnMuGhghL SxNuEF/hTQadk3XtC9PgKPffd1YOQ5jVUu054JN5KjPMT5uIVEpml9NrzqlOjDWafMCj mXZLGAySZm8+AXTOfEkyFCUe8kxSlvFxiNBBrpqBznwhsaNIHGUxEkaXMJVUL3yfyLgA /qvMqYICZ0E5graeVMD2IZPhanr0BsuMILp1VNgHjYlGzVUNz3R2vMn+MXhlYn7Fk1nt AZnw==
X-Gm-Message-State: AOAM533CY3VcEmWB8xbD82OZKd6vkESu/FGY89kPudkaGvuytpTdYUOB 9f04jlC9N4PBrNeIS8x1c0trORApp/cq7w==
X-Google-Smtp-Source: ABdhPJxzLL3OS+fmju1LK98tdHrRbzpfE6eYMGzGyrbW5ttqhkqlG3IU3TkDl6Ylff3sBGPaoHR2KQ==
X-Received: by 2002:ac8:4d5b:: with SMTP id x27mr379459qtv.135.1605204742139; Thu, 12 Nov 2020 10:12:22 -0800 (PST)
Received: from [] (pool-108-31-39-252.washdc.fios.verizon.net. []) by smtp.gmail.com with ESMTPSA id d188sm5566843qkb.10.2020. for <mls@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Nov 2020 10:12:19 -0800 (PST)
From: Sean Turner <sean@sn3rd.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.\))
Message-Id: <56DD9D08-FC27-48C0-819A-B8EF422CE088@sn3rd.com>
Date: Thu, 12 Nov 2020 13:12:18 -0500
To: MLS List <mls@ietf.org>
X-Mailer: Apple Mail (2.3608.
Archived-At: <https://mailarchive.ietf.org/arch/msg/mls/vLsJCLccE77cdsQvilMjDFcvvjM>
Subject: [MLS] revising mls-architecture I-D
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: Thu, 12 Nov 2020 18:12:25 -0000


Now that the WG is winding down on the mls-protocol I-D, the WG will shift its focus to the mls-architecture I-D. There is really no way the mls-protocol I-D could progress beyond the WG (i.e., to IETF LC and subsequent IESG review) without the mls-architecture I-D because the mls-architecture I-D provides detail the IESG would ask for. For the next version of the mls-architecture draft, the chairs are proposing that the authors submit a version that the authors believe brings the I-D up to date (i.e., fast-forward it). After that version is posted, the WG can then do its thing: provide comments on the new I-D, discuss the comments and how to resolve them, and reach consensus on the final text. We can use virtual interim meetings to work through thorny issues because sometimes voice is better than email; we need to be clear about the properties provided when combining the various options mls provides or we are going to have a tough time getting through the rest of the IETF standardization process.

Part of this effort is going to be a pretty aggressive stance on closing existing issues in both GitHub and the I-D. Many are just stale. Some will be addressed either in part or entirely by the next version. If we are too aggressive in closing issues in this phase, have no fear we can always reintroduce them and the WG will do its thing (see above).

Stay tuned for a new version of the mls-architecture I-D!


Nick and Sean