[tlp-interest] Seeking feedback on Code License in TLP 6 draft

Wendy Seltzer <wendy@seltzer.org> Thu, 13 August 2026 19:13 UTC

Return-Path: <wendy@seltzer.org>
X-Original-To: tlp-interest@mail2.ietf.org
Delivered-To: tlp-interest@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 54D861295AEEC for <tlp-interest@mail2.ietf.org>; Thu, 13 Aug 2026 12:13:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1786648397; bh=PZg9Vf0Yg3beSwiGR/buzyQONL7//8VgSF1/VCrm14Y=; h=From:Date:Subject:To; b=QkYSqLBLUQ2qNEmGwasJXaQH9/Px6cYGTggIfU6yAu9SEi+vm4qWlXxvNV1C9RRZN ch6yMxaLyaYHz6vylsyI8nCqtpAyc7343OjyAjvoXbgGlX5rXgrdamJz5gv/QNG/EI r9UiMBL4OfWPfrAK9bysAocZiIAMHMvVl0t6rfDk=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TOwN4NbTJjph for <tlp-interest@mail2.ietf.org>; Thu, 13 Aug 2026 12:13:16 -0700 (PDT)
Received: from mail.seltzer.org (peppercorn.seltzer.org [166.84.7.31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 78F771295AEE6 for <tlp-interest@ietf.org>; Thu, 13 Aug 2026 12:13:16 -0700 (PDT)
From: Wendy Seltzer <wendy@seltzer.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.600.51.1.1\))
Date: Thu, 13 Aug 2026 12:12:58 -0700
Message-Id: <81E8519F-E5FE-4300-A774-4DBD9F934B38@seltzer.org>
To: tlp-interest@ietf.org
X-Mailer: Apple Mail (2.3864.600.51.1.1)
X-MailFrom: wendy@seltzer.org
X-Mailman-Rule-Hits: header-match-tlp-interest.ietf.org-0
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation
Message-ID-Hash: EWHHUULR2SYSBPGQDMNU3GCMTN5DFVTF
X-Message-ID-Hash: EWHHUULR2SYSBPGQDMNU3GCMTN5DFVTF
X-Mailman-Approved-At: Thu, 13 Aug 2026 12:14:08 -0700
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [tlp-interest] Seeking feedback on Code License in TLP 6 draft
List-Id: Discussion of proposed revisions to the Trust Legal Provisions <tlp-interest.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tlp-interest/X0cwDnMpf_9QZU4J98LTQW7QguU>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tlp-interest>
List-Help: <mailto:tlp-interest-request@ietf.org?subject=help>
List-Owner: <mailto:tlp-interest-owner@ietf.org>
List-Post: <mailto:tlp-interest@ietf.org>
List-Subscribe: <mailto:tlp-interest-join@ietf.org>
List-Unsubscribe: <mailto:tlp-interest-leave@ietf.org>

Hi TLP-interest,

Off-list, we have heard comments about the way the proposed TLP 6 refers to its code license.[1] 

While the code license is substantively unchanged, we now name it by reference, as the “Code License” instead of referring everywhere to the “Revised" or "3-Clause BSD License.” At least one reviewer worries that legal teams would have to investigate the change and so might make it more difficult for people to contribute.  

Our intent is to simplify the references, not add complexity. We’d like to hear from others whether the changes to Section 4, "License to Code Components," raise concern.

Thanks!
—Wendy

[1] https://www.ietf-ipm.org/tlp/ , see Section 4 of the July TLP 6 draft, redline at https://www.ietf-ipm.org/uploads/IETF-IPMC-IETF-Technical-License-Provisions-6.0-DRAFT-JULY-19-2026-redlines.pdf

— 
Wendy Seltzer, IETF IPMC Director