Re: Status of this memo
"Joel M. Halpern" <jmh@joelhalpern.com> Tue, 27 April 2021 23:27 UTC
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C60473A251A for <ietf@ietfa.amsl.com>; Tue, 27 Apr 2021 16:27:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.801
X-Spam-Level:
X-Spam-Status: No, score=-2.801 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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TlS3r5rL6DpE for <ietf@ietfa.amsl.com>; Tue, 27 Apr 2021 16:27:12 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC5DD3A2514 for <ietf@ietf.org>; Tue, 27 Apr 2021 16:26:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4FVHwB2jprz6G9wt; Tue, 27 Apr 2021 16:26:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1619566010; bh=iX86gciSzxru3br41Zs7DlQ71rQhgcEe1KAWYzpepBU=; h=Subject:To:References:From:Date:In-Reply-To:From; b=Q16/vLuyGmPP0BxrBFKKOLJ+D6ssgp3Xp2WDsUIaHZb4pPBobVuEHRMoPVuaxGWDW E0Qu+GO6tgApLPgk8BOWPOZpsLzgzQPZE4RC5qh9rHhWepqIk2pvM0GCvk3bdyeSO8 bwN5Y1eZfZdFo5tPMCD1rJKwXNaiVSlHkBadsrBM=
X-Quarantine-ID: <6ERFnO7fNKta>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.128.43] (unknown [50.225.209.66]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4FVHw94rbmz6G9wh; Tue, 27 Apr 2021 16:26:49 -0700 (PDT)
Subject: Re: Status of this memo
To: Keith Moore <moore@network-heretics.com>, ietf@ietf.org
References: <9ACE59FA-30B6-475A-AF6B-4B874E4A2788@eggert.org> <1804294246.5904.1619512137931@appsuite-gw2.open-xchange.com> <D653D3B2-7666-409A-B856-2A4B1BA958CA@eggert.org> <3DBB64B1-40B8-4BC3-B66C-7F9B7F395874@akamai.com> <b5210c71-9500-3dba-05d2-4ae1c6ad16e9@network-heretics.com> <CAA=duU1VJs2vCE=uCF=fXO7FNedn9yPAaZWTgcaAiHTexA8uWA@mail.gmail.com> <CAF4+nEEz4x3HtUhWQ0ONYCpyHy27E4u7_chVEuHi3rDr+sc39A@mail.gmail.com> <b3762d56-bff2-6f71-caa2-69d34e81b9dc@network-heretics.com> <20210427215415.GK79563@kduck.mit.edu> <aafedd93-0f90-aaa4-966e-8fef9573149e@network-heretics.com> <20210427222219.GN79563@kduck.mit.edu> <b5741e60-fd4c-ca3d-3973-ae1652bb42e9@network-heretics.com> <a6b57eef-1a1e-2416-a98d-dfeda824dcf0@joelhalpern.com> <02555a2f-dbbc-18a1-0cbb-aab73f62b8f5@network-heretics.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <81b940cf-c0e1-7a68-cafb-87b6e6e653b7@joelhalpern.com>
Date: Tue, 27 Apr 2021 19:26:48 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <02555a2f-dbbc-18a1-0cbb-aab73f62b8f5@network-heretics.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yoYMGXShsiR66_Uwbg1KufcCMW8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Apr 2021 23:27:17 -0000
If the pen holder wants to take their original text, and apply any changes they personally have made to the document, I think they can do that. If the original authors want to write another I-D that uses the words from the WG, they probably can, as the note well from everyone else grants the rights to use the words in IETF work. But if the original author wants to take his work somewhere else, and make derivative works, he better get rid of all the words from IETF contributors. Heck, any author can create an I-D using any words from any I-Ds or RFCs, as long as what they are doing is contributing it to the IETF. But they can't just use those words elsewhere. And the original author does not have any special authority to tell the WG what words it will work with. I do not know of any reason for the WG to change the name of a WG adopted draft just because they make some content changes (with or without the original author's agreement. If someone does not like what the WG does with their document, they can ask to have their name removed (and people have done so). The WG can change the name (and does if the content changes far enough that they want to talk about it as a different thing.) But that is up to the WG, not copyright law or moral right. And in terms of IETF rights, this goes back quite a number of years. Yours, Joel On 4/27/2021 7:14 PM, Keith Moore wrote: > On 4/27/21 7:12 PM, Joel M. Halpern wrote: > >> Keith, I have to fundamentally disagree with you. >> Once the WG adopts the document, the WG owns it, and the document pen >> holder (original author or otherwise) is expected to work according to >> the direciton of the WG. > > That's not how I read BCP78, and I'm not aware of any other instrument > by which the document's original authors give up their right to create > derivative works. > >> The pen holder retains their rights in their original contribution. >> But in fact, once it is incorporating text from the WG, it belongs to >> the WG. > > Emphatically disagree. I believe this to be an entirely false statement. > > Keith >
- Status of this memo Brian E Carpenter
- Re: Status of this memo Phillip Hallam-Baker
- Re: Status of this memo Lars Eggert
- Re: Status of this memo Vittorio Bertola
- Re: Status of this memo Lars Eggert
- Re: Status of this memo Donald Eastlake
- Re: Status of this memo Carsten Bormann
- Re: Status of this memo Andrew G. Malis
- Re: Status of this memo Keith Moore
- Re: Status of this memo Carsten Bormann
- Re: Status of this memo Keith Moore
- Re: Status of this memo Lars Eggert
- Re: Status of this memo Lloyd W
- Re: Status of this memo Keith Moore
- Re: Status of this memo Lars Eggert
- Re: Status of this memo Scott Brim
- Re: Status of this memo Vittorio Bertola
- Re: Status of this memo Keith Moore
- Re: Status of this memo Scott Bradner
- Re: Status of this memo Phillip Hallam-Baker
- Re: Status of this memo Keith Moore
- Re: Status of this memo Keith Moore
- Re: Status of this memo Charles Eckel (eckelcu)
- Re: Status of this memo Salz, Rich
- Re: Status of this memo Keith Moore
- Re: Status of this memo Andrew G. Malis
- Re: Status of this memo Phillip Hallam-Baker
- Re: Status of this memo Keith Moore
- Re: Status of this memo Joel M. Halpern
- Re: Status of this memo Keith Moore
- Re: Status of this memo Martin Vigoureux
- Re: Status of this memo Carsten Bormann
- Re: Status of this memo Phillip Hallam-Baker
- Re: Status of this memo Keith Moore
- Re: Status of this memo Bob Hinden
- Re: Status of this memo Phillip Hallam-Baker
- Re: Status of this memo Andrew G. Malis
- Re: Status of this memo Donald Eastlake
- Re: Status of this memo Keith Moore
- Re: Status of this memo Donald Eastlake
- Re: Status of this memo Keith Moore
- Re: Status of this memo Donald Eastlake
- Re: Status of this memo Donald Eastlake
- Re: Status of this memo Keith Moore
- RE: Status of this memo Michael McBride
- Re: Status of this memo Keith Moore
- Re: Status of this memo Carsten Bormann
- Re: Status of this memo Keith Moore
- Re: Status of this memo Donald Eastlake
- Re: Status of this memo Donald Eastlake
- Re: Status of this memo Donald Eastlake
- Re: Status of this memo John C Klensin
- Re: Status of this memo Martin Vigoureux
- Re: Status of this memo Phillip Hallam-Baker
- Re: Status of this memo John C Klensin
- Re: Status of this memo Michael StJohns
- Re: Status of this memo Martin Vigoureux
- Re: Status of this memo Benjamin Kaduk
- Re: Status of this memo Randy Presuhn
- Re: Status of this memo Keith Moore
- Re: Status of this memo Phillip Hallam-Baker
- Re: Status of this memo Benjamin Kaduk
- Re: Status of this memo Joel M. Halpern
- Re: Status of this memo John C Klensin
- Re: Status of this memo ned+ietf
- Re: Status of this memo Keith Moore
- Re: Status of this memo Keith Moore
- Re: Status of this memo Joel M. Halpern
- Re: Status of this memo [NOTE WELL] Brian E Carpenter
- Re: Status of this memo Keith Moore
- Re: Status of this memo [WG consensus] Brian E Carpenter
- Re: Status of this memo [name remixing] Brian E Carpenter
- Re: Status of this memo Scott Bradner
- Re: Status of this memo Joel M. Halpern
- Re: Status of this memo [name remixing] Christian Huitema
- Re: Status of this memo Michael StJohns
- Re: Status of this memo Keith Moore
- Re: Status of this memo ned+ietf
- Re: Status of this memo Joel M. Halpern
- Re: Status of this memo [NOTE WELL] Phillip Hallam-Baker
- Re: Status of this memo [WG consensus] Theodore Ts'o
- Re: Status of this memo Benjamin Kaduk
- Re: Status of this memo John C Klensin
- Re: Status of this memo Lloyd W
- Re: Status of this memo John C Klensin
- Re: Status of this memo Murray S. Kucherawy
- Re: Status of this memo Simon Josefsson
- Re: Status of this memo Lloyd W
- Re: Status of this memo Keith Moore
- Re: Status of this memo Keith Moore
- Re: Status of this memo Keith Moore
- Re: Status of this memo Salz, Rich
- RE: Status of this memo Gorman, Pierce
- Re: Status of this memo Nick Hilliard
- Re: Status of this memo tom petch
- Re: Status of this memo Warren Kumari
- Re: Status of this memo Brian E Carpenter
- Re: Status of this memo S Moonesamy