From d7983300fab06948417961af4c49bcc431ab24ab Mon Sep 17 00:00:00 2001 From: Bas Westerbaan Date: Fri, 22 Aug 2025 12:49:44 +0200 Subject: [PATCH] charter: require two implementations before publication of specs Suggested by Job. https://mailarchive.ietf.org/arch/msg/plants/J6kZUd38_OE9zO2exMnhqjgL_b0/ And, surprisingly, BCP 9 doesn't imply this: https://mailarchive.ietf.org/arch/msg/plants/n3bFDuR1OD6PhQEBcU3E3run7hs/ --- charter-ietf-plants.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/charter-ietf-plants.md b/charter-ietf-plants.md index fcf5718..0e8d113 100644 --- a/charter-ietf-plants.md +++ b/charter-ietf-plants.md @@ -31,3 +31,5 @@ Though not the initial focus, the PLANTS Working Group may consider other proper In evaluating decisions and design tradeoffs, the Working Group will consider security, privacy, transparency, performance, and deployment properties, aiming to comparably meet the needs of today's applications that use CT-based PKIs with TLS. The Working Group may consider how these mechanisms may apply to other PKIs or non-interactive protocols, but these will not be the primary use case and may ultimately have different requirements or limitations. The PLANTS Working Group's scope is to explore mechanisms for CAs and transparency ecosystems to certify key/identifier bindings in a publicly monitorable way. Alternate trust models and changes to how TLS uses the end-entity key are not in scope for the Working Group. + +The Working Group will not submit specifications for publication to the IESG before demonstrating two interoperable implementations.