[MLS] Erik Kline's No Objection on draft-ietf-mls-protocol-17: (with COMMENT)
Erik Kline via Datatracker <noreply@ietf.org> Tue, 31 January 2023 07:25 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: mls@ietf.org
Delivered-To: mls@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A3481C14E514; Mon, 30 Jan 2023 23:25:13 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Erik Kline via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-mls-protocol@ietf.org, mls-chairs@ietf.org, mls@ietf.org, benjamin.beurdouche@ens.fr, karthikeyan.bhargavan@inria.fr, cas.cremers@cs.ox.ac.uk, alan@wire.com, singuva@twitter.com, kwonal@mit.edu, ekr@rtfm.com, thyla.van.der@merwe.tech, sean@sn3rd.com, sean@sn3rd.com
X-Test-IDTracker: no
X-IETF-IDTracker: 9.6.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Erik Kline <ek.ietf@gmail.com>
Message-ID: <167514991366.26632.7090779328804294577@ietfa.amsl.com>
Date: Mon, 30 Jan 2023 23:25:13 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mls/IMh2ZhW5DbK0Wb9InbaK7isxxEA>
X-Mailman-Approved-At: Tue, 31 Jan 2023 06:04:28 -0800
Subject: [MLS] Erik Kline's No Objection on draft-ietf-mls-protocol-17: (with COMMENT)
X-BeenThere: mls@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 31 Jan 2023 07:25:13 -0000
Erik Kline has entered the following ballot position for draft-ietf-mls-protocol-17: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-mls-protocol/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- # Internet AD comments for draft-ietf-mls-protocol-17 CC @ekline ## Comments * Thank you very much for all of the explicitly worked examples. ### S7.3 * What is the reason for MUST vs RECOMMENDED difference in the two different circumstances when validating the `lifetime` field? * Consider adding a platitude about communicating nodes SHOULD use some method of time synchronization... ## Nits ### S3.2 * "top of these basic mechanism" -> "top of these basic mechanisms" (or maybe "top of this basic mechanism") ### S6.3.1 * "in an PrivateContentTBE structure" -> "in a PrivateContentTBE structure"
- [MLS] Erik Kline's No Objection on draft-ietf-mls… Erik Kline via Datatracker
- Re: [MLS] Erik Kline's No Objection on draft-ietf… Richard Barnes
- Re: [MLS] Erik Kline's No Objection on draft-ietf… Erik Kline
- Re: [MLS] Erik Kline's No Objection on draft-ietf… Richard Barnes