Re: no no derivatives, was legal consultation (was List moderator action)

John Levine <johnl@ietf.email> Thu, 07 May 2026 18:38 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: ietf@mail2.ietf.org
Delivered-To: ietf@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 0B1FCEAC0BF1 for <ietf@mail2.ietf.org>; Thu, 7 May 2026 11:38:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1778179092; bh=LpHFjn1zcUZGOqip0MQ5Ial3mjHM8/uILFsdhdk6cok=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=vdT8tYvSJtRKTHcZNq6aFidUQig+CK4z4mE5E4q6zfysajtU0rmpozmSywoN4uAhi QXviPXD3r6EBD1PsOw73+wWeIXZDwNTx+S9WOEZ3WExCuafdnrwLesW6AqtzlD7Z9h HEPimk0e2ETVYApbhFVKoRKOeTwWz1/VSu7nIXyY=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.4
X-Spam-Level:
X-Spam-Status: No, score=-4.4 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, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b="egOMmnnz"; dkim=pass (2048-bit key) header.d=ietf.email header.b="HeOY5DJ3"
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 bT9y6WiNotox for <ietf@mail2.ietf.org>; Thu, 7 May 2026 11:38:07 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 6586BEAC0AF3 for <ietf@ietf.org>; Thu, 7 May 2026 11:38:07 -0700 (PDT)
Received: (qmail 74414 invoked from network); 7 May 2026 18:38:06 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-transfer-encoding:cleverness; s=122aa69fcdc0e.k2605; t=1778179076; x=1778524676; bh=LpHFjn1zcUZGOqip0MQ5Ial3mjHM8/uILFsdhdk6cok=; b=egOMmnnzPfRtf2LOOd1cGlQmcr4/RetshWQkBzYLBGRqzIFeLMeXp05OFFinCc0mOjIouK9lpmbjPXflxK6+ziwfGJ16t+uU2PxA8BZEkcqfe8N1slxBfI4yQQCmeBNWwJbuQ2T1qONedAvtXYHQCDrJS6TiiSxI3/QT2sbGglMfcm8kGIAzP0mXai3qy8F7Qt0IJo1X1VGAm6F+jp5/9LTOMdfG5KAI2Qz4ZPM2rZ0HOJfYJGnc0r+shmzeNHi2GPVKI5gZJxyxOQa0ti/MHzirZ/QZ9LsIjvLJdzaPA2CsW98dcuAKJh8+aWTSlYmgGIcmpbcIH7L6WoCzoLnc7A==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=ietf.email; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-transfer-encoding:cleverness; s=122aa69fcdc0e.k2605; bh=LpHFjn1zcUZGOqip0MQ5Ial3mjHM8/uILFsdhdk6cok=; b=HeOY5DJ3WR/knn+vjDAgWQwB3rRrJqUYhgBMuZi8ogTmctd9QcHEVNh/dyMdy8gV9Nnq+3k6LyUI/53MBBn6ni54Mu1//13xUZ15NFd/S8nO5KqS8sHo0G5LxoVYXcXddXxIWaSAqyXGBuC2N9W6TeukbDKp3IJS3s5OkMIrfdq3y3y29IPdtyh0TLR68Cf+1HrfsLD1ZEZst/Ylci9PevCin7OP3jGPgyObzh2bqlGAs+2j8RW+LzwFXxGGcGuFvcpHvqTtIqLAKRTAa0RmXxShAn4BRFOjIyKPXbV2g9sCaWGwSeQHUAwzARSFUqbFZEEzdf4In5NpD2YYMuP6uw==
Received: from ary.qy ([IPv6:2001:470:1f07:1126:0:78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126:0:78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA CHACHA20-POLY1305 AEAD) via TCP6; 07 May 2026 18:38:06 -0000
Received: by ary.qy (Postfix, from userid 501) id 039971088CBBE; Thu, 7 May 2026 14:38:05 -0400 (EDT)
Date: Thu, 07 May 2026 14:38:05 -0400
Message-Id: <20260507183806.039971088CBBE@ary.qy>
From: John Levine <johnl@ietf.email>
To: ietf@ietf.org
Subject: Re: no no derivatives, was legal consultation (was List moderator action)
In-Reply-To: <MN2PR17MB4031C41F79382775E779E441CD3C2@MN2PR17MB4031.namprd17.prod.outlook.com>
Organization: Taughannock Networks
References: <CAChr6Sy1jsjNzh1qMEDVx7ABp_1_uPkfx_tY-T7zPpXTdZiXtQ@mail.gmail.com> <877bpgb7bq.fsf@josefsson.org> <c7aae006-be27-4beb-9553-0b8efb4bd600@gmail.com> <MN2PR17MB4031C41F79382775E779E441CD3C2@MN2PR17MB4031.namprd17.prod.outlook.com>
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Message-ID-Hash: QHMLQ7YIFLW2YD44TJOSHAIARP5CKVQ2
X-Message-ID-Hash: QHMLQ7YIFLW2YD44TJOSHAIARP5CKVQ2
X-MailFrom: johnl@iecc.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf.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
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/myn93NQpqRq-Yfz8G_IBLN4tJ4E>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-owner@ietf.org>
List-Post: <mailto:ietf@ietf.org>
List-Subscribe: <mailto:ietf-join@ietf.org>
List-Unsubscribe: <mailto:ietf-leave@ietf.org>

It appears that Salz, Rich <rsalz@akamai.com> said:
>-=-=-=-=-=-
>
>  *
>Therefore, IMHO it would be perfectly reasonable to disallow "no
>  *
>derivative rights" for all IETF stream contributions.
>
>That’s a really bad idea.  For example, I could post a draft with no-derivative as a trial balloon to see if the IETF is interested, say as a DISPATCH presentation. If not,
>then I am free to take it to other places or to seek a patent.

Twenty years ago I would have agreed with you. These days, it would take about
10 seconds to stick a draft or draft-like thing on a server somewhere else and
send a note to an IETF list saying take a look at my document at https://blah
and tell us if you're interested.

Considering the length of this thread, I think the simplification would be worth it.
I realize there is a process nit about how you might ask to DISPATCH somehthing if
there isn't an I-D but I think we can deal with it.

By my count there have been 21 RFCs published with "no derivatives" lanaguage,
the most recent RFC8216 in 2017. The last in the IETF stream was RFC7016 in
2013, over a decade ago.

R's,
John