Re: Rights in early RFCs

John C Klensin <john-ietf@jck.com> Fri, 14 June 2019 23:06 UTC

Return-Path: <john-ietf@jck.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 B40481200E5 for <ietf@ietfa.amsl.com>; Fri, 14 Jun 2019 16:06:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 GY-wkyZpDAkO for <ietf@ietfa.amsl.com>; Fri, 14 Jun 2019 16:06:26 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C77A1200C4 for <ietf@ietf.org>; Fri, 14 Jun 2019 16:06:25 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1hbvH5-000552-To; Fri, 14 Jun 2019 19:06:23 -0400
Date: Fri, 14 Jun 2019 19:06:17 -0400
From: John C Klensin <john-ietf@jck.com>
To: John R Levine <johnl@taugh.com>
cc: IETF general list <ietf@ietf.org>
Subject: Re: Rights in early RFCs
Message-ID: <A89856255D980EBDE462508F@PSB>
In-Reply-To: <alpine.OSX.2.21.9999.1906141728410.11884@ary.qy>
References: <alpine.OSX.2.21.9999.1906141728410.11884@ary.qy>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GkUfW7pYCsIwJyzvdwT1lfZRW_Q>
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: Fri, 14 Jun 2019 23:06:28 -0000


--On Friday, June 14, 2019 17:45 -0400 John R Levine
<johnl@taugh.com> 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.

Yes.  Jon did.  More than once and under pressure from people
with whom he was usually fairly impatient.  I think it is a fair
summary of his personal preference -- about the series, not
[jist] things of which he was the author would be pretty close
to "just use it, ideally with credit as appropriate".  The bad
news was (and is) that things get complicated as soon as either
IPR lawyers or other people interested in talking about
"ownership" or either text or ideas -or- people who are inclined
to take the idea of others and try to pass them off as their own
get involved.   

Your notion of "US government works" didn't help either because
very few of the early authors were actually government employees
but, instead, were employees of various universities or [other[
government contractors.  A number of those organizations
successfully argued that they could, and would, do a better job
of technology transfer if they had ownership rights in whatever
they were producing than if the technology (and documents) were
free for anyone to pick up and use because the latter
organizations would have little incentive to commercial
technology for which they had no special rights.   (The
contemporary argument by various pharma companies that they
should be able to take federal funds to develop drugs that they
then patent is not much different from that old technology
transfer one.)  In addition, [D]ARPA, at least at that time, did
not do its own contracting and I have some reason to believe
(and think we discovered during those discussions) that the
details of the arrangements different contractor organizations
had with different contract management organizations differed,
and may have differed quite a bit.

One of the outcomes of the above was the general rule that
persisted into IETF Trust policy, i.e., that anyone can
reproduce RFC text as long as it remains intact and unchanged --
issues arise only if someone wants to make excerpts or derived
works.

There were several later rounds of conversations about the
general topic on which Scott Bradber would be m8ch more expert
than I am, but I'd be surprised if the answer from him would be
significantly different from the above.

You didn't identify you "we" was in your question but, if the
answer is, e.g., the IETF Trust, good luck and this is why we
pay you folks the big bucks.

   best,
     john