[MLS] Call for adoption: draft-mahy-mls-ratchet-tree-options-03 (Ends 2025-11-25)

Sean Turner via Datatracker <noreply@ietf.org> Tue, 04 November 2025 21:04 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: mls@ietf.org
Delivered-To: mls@mail2.ietf.org
Received: from [10.244.8.124] (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 780AF82EBF66; Tue, 4 Nov 2025 13:04:10 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Sean Turner via Datatracker <noreply@ietf.org>
To: draft-mahy-mls-ratchet-tree-options@ietf.org, mls-chairs@ietf.org, mls@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.53.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <176229025043.631120.16501239595776842986@dt-datatracker-5df8666cb-7l4w5>
Date: Tue, 04 Nov 2025 13:04:10 -0800
Message-ID-Hash: 33QZ3UY5UJSSF7A5J4CXXFSVVN6T4SMS
X-Message-ID-Hash: 33QZ3UY5UJSSF7A5J4CXXFSVVN6T4SMS
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-mls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Reply-To: Sean Turner <sean@sn3rd.com>
Subject: [MLS] Call for adoption: draft-mahy-mls-ratchet-tree-options-03 (Ends 2025-11-25)
List-Id: Messaging Layer Security <mls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mls/MT26sp6jxXFvKoecKatFkuVG2xA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mls>
List-Help: <mailto:mls-request@ietf.org?subject=help>
List-Owner: <mailto:mls-owner@ietf.org>
List-Post: <mailto:mls@ietf.org>
List-Subscribe: <mailto:mls-join@ietf.org>
List-Unsubscribe: <mailto:mls-leave@ietf.org>

Subject: Call for adoption: draft-mahy-mls-ratchet-tree-options-03  (Ends
2025-11-25)

This message starts a 3-week Call for Adoption for this document.

Abstract:
   The Messaging Layer Security (MLS) protocol needs to share its
   ratchet_tree object to welcome new clients into a group and in
   external joins.  While the protocol only defines a mechanism for
   sharing the entire tree, most implementations use various
   optimizations to avoid sending this structure repeatedly in large
   groups.  This document describes a way to convey these improvements
   in a standardized way and to convey the parts of a GroupInfo object
   that are not visible to an intermediary server.

File can be retrieved from:
https://datatracker.ietf.org/doc/draft-mahy-mls-ratchet-tree-options/

Please reply to this message keeping mls@ietf.org in copy by indicating
whether you support or not the adoption of this draft as a WG document.
Comments to motivate your preference are highly appreciated.

Authors, and WG participants in general, are reminded of the Intellectual
Property Rights (IPR) disclosure obligations described in BCP 79 [2].
Appropriate IPR disclosures required for full conformance with the provisions
of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
Sanctions available for application to violators of IETF IPR Policy can be
found at [3].

Thank you.
[1] https://datatracker.ietf.org/doc/bcp78/
[2] https://datatracker.ietf.org/doc/bcp79/
[3] https://datatracker.ietf.org/doc/rfc6701/