Re: Rights in early RFCs

Joe Touch <touch@strayalpha.com> Sat, 15 June 2019 00:38 UTC

Return-Path: <touch@strayalpha.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 8FC9D120099 for <ietf@ietfa.amsl.com>; Fri, 14 Jun 2019 17:38:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.22
X-Spam-Level:
X-Spam-Status: No, score=-1.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 pb1qE7vymbNe for <ietf@ietfa.amsl.com>; Fri, 14 Jun 2019 17:38:12 -0700 (PDT)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (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 55423120058 for <ietf@ietf.org>; Fri, 14 Jun 2019 17:38:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id: Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version: Content-Type:Sender:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=BBvxp9BtAmEvRERLJ57G6vZdAiA5GUjRdUJnhmveGc4=; b=IMEyMie/gLzXpnna0MiKy1sJj b+zPT/+VKa0RdfpUmCM39p82mqwfP0mHpKMqrnnZwG6S8wm3jD8myI3XOFIytcIlxcKiCxFAltyrf bZRmuCnrHGGNE7TYVVkoahRlQG5wot2yUETKwsd4bmakx0mDYvmEUHASI37R1Iai1AnfqQhhPFBtq 11r9Oc5X3rTlzr9P+vlus4zLXxI6NsGVOhlG06RoXkuPVO+8FV5jUMYOfhUCrL27OgPpKol7u4/RA 1YBWPvs6Wpb0Q965E+KzCr5iWk+Dq9BA1dgpue/T0U74IqI47ocrBHeWKRwn8EFYJC5V/LEfqRXJs 97Vj/n2Xg==;
Received: from cpe-172-250-240-132.socal.res.rr.com ([172.250.240.132]:54225 helo=[192.168.1.77]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <touch@strayalpha.com>) id 1hbwhq-002yMP-OI; Fri, 14 Jun 2019 20:38:11 -0400
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: Rights in early RFCs
From: Joe Touch <touch@strayalpha.com>
In-Reply-To: <674dde53-a9d1-13b6-b665-cf62d41366f8@gmail.com>
Date: Fri, 14 Jun 2019 17:38:07 -0700
Cc: John R Levine <johnl@taugh.com>, IETF general list <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B3180AF8-AD1E-4997-B566-B912B9B77B9D@strayalpha.com>
References: <alpine.OSX.2.21.9999.1906141728410.11884@ary.qy> <674dde53-a9d1-13b6-b665-cf62d41366f8@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BkBaXEy6p3hrvUfDl1ULjWhk8jo>
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: Sat, 15 Jun 2019 00:38:15 -0000

FWIW, IANAL but the agreements below affect only the editing and publication functions of ISI during the period indicated, which (AFAICT) was after Jon died.

I.e, this refers to the RFC Editor contributions. It does not appear (again, IANAL) to affect either previous works or even RFC work done by others during that period (granted that the ISOC started adding copyright statements to RFCs somewhere in that time too).

Joe

> On Jun 14, 2019, at 4:46 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> John,
> 
> When we set up the IETF Trust, we did what we could to get all the rights. We discussed this actively in late 2006, and I found a list of test cases that includes RFC 791-793, but not RFC 768 for some reason. 
> 
> With a little research:
> ISI assigned all its rights to ISOC on May 2, 2007:
> https://iaoc.ietf.org/documents/Confirmatory_License_Pre_1998_Executed.pdf
> https://iaoc.ietf.org/documents/Confirmatory_Addendum_Post_1998_Executed.pdf
> 
> ISOC assigned all its rights in RFCs to the Trust in 2006 (April or thereabouts). I hope this was updated to cover the rights obtained from ISI, but I don't know about that since I left the Trust in March 2007. If it was overlooked, the Trust will need to fix it.
> 
> However, this certainly leaves open the question of the rights of the *authors* (or their estates) since there were no formalities in place, apart from whatever was hidden in employment contracts and USG-funded contracts. A few RFC authors signed a "Contributor Non-Exclusive Document License" to cover the pre-RFC5378 problem; I believe Steve Crocker signed one for RFC1, for example. But the Trust never followed up on this for the important early RFCs.
> 
> Regards
>   Brian Carpenter
> 
> On 15-Jun-19 09:45, John R Levine wrote:
>> We recently got an inquiry about RFC 768.  Jon Postel published it in 1980 
>> without a copyright notice, it's never been updated, and since it defines 
>> UDP, it's implemented in billions of devices around the world.
>> 
>> If someone wanted to reuse it, I can only guess where to ask.  Since Jon 
>> wrote it, perhaps it'd be his heirs, or perhaps it'd be USC since that's 
>> who he worked for, or perhaps it'd be nobody since the government funded 
>> him and US government works are P.D.
>> 
>> Has anyone ever tried to work out who owns what for the early RFCs?  I 
>> think I understand what the rules are from RFC 1602 onward, but there's a 
>> bunch of important ones earlier than that.
>> 
>> Regards,
>> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
>> Please consider the environment before reading this e-mail. https://jl.ly
>> 
>> PS: In case it's not clear, I'm not asking what anyone thinks the rules 
>> should be or should have been, I'm asking to what extent we know what they 
>> actually are.
>> 
>> 
>