Re: Rights in early RFCs

Joe Touch <touch@strayalpha.com> Sun, 16 June 2019 15:19 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 963D21201CA for <ietf@ietfa.amsl.com>; Sun, 16 Jun 2019 08:19:45 -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 suQ6hJ4SjMGZ for <ietf@ietfa.amsl.com>; Sun, 16 Jun 2019 08:19:44 -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 671A812003E for <ietf@ietf.org>; Sun, 16 Jun 2019 08:19:44 -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=9VncnYfDBzHghEmDJN/9urz+S6z+SD/dP07TYeKSdoY=; b=RIYVJeldptDiQTAbvHB/DiCVi gBA59uWYN6dSeXLGN8G3pJRaFGO89FnNuzztLxI0iJMz7RO4FWqCNT2exwi0yNxinfr3XCAvfAjxX 3lKvkjNe25E2XNbZjQ0cxJN3sJswvqDibLozWDCCbZfEGeDkTNhdUWjwnwXiNHHidpOAR20YNJQDD Npwvo2dmDh6Ue2sALufRfUelJCOpCoEqP68worr51KwGRJ8iINHTeiGknTllIV/rnb7k1R6tbxmih Hm0vtIfNJWJIiUjRtpeI6byGXRsW7GnmPVQZNPubDBaDbApQHISqMTccQP8DNoit/5YjgLsFQi7Yz J45utvfcg==;
Received: from cpe-172-250-240-132.socal.res.rr.com ([172.250.240.132]:50371 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 1hcWwU-002aUD-W1; Sun, 16 Jun 2019 11:19:43 -0400
Content-Type: text/plain; charset="utf-8"
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: <22dd0f4e-60a3-f81d-b8ea-58b10e8d4bc9@comcast.net>
Date: Sun, 16 Jun 2019 08:19:40 -0700
Cc: ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <DBBD6A8A-A1CB-4672-BE09-20BADBFB41CC@strayalpha.com>
References: <alpine.OSX.2.21.9999.1906141728410.11884@ary.qy> <674dde53-a9d1-13b6-b665-cf62d41366f8@gmail.com> <B3180AF8-AD1E-4997-B566-B912B9B77B9D@strayalpha.com> <d2d3523f-6fe6-749a-a74e-567c967ea5f6@gmail.com> <22dd0f4e-60a3-f81d-b8ea-58b10e8d4bc9@comcast.net>
To: Michael StJohns <mstjohns@comcast.net>
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/jDpf8gE9BVB7JA0psoA7vvzOnpQ>
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: Sun, 16 Jun 2019 15:19:45 -0000


> On Jun 15, 2019, at 10:53 PM, Michael StJohns <mstjohns@comcast.net> wrote:
> 
> 
> On 6/14/2019 10:22 PM, Brian E Carpenter wrote:
>> On 15-Jun-19 12:38, Joe Touch wrote:
>>> 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.
>> No, pre-October 1998 is specifically included in the first one. The two are slightly different for reasons that various lawyers no doubt explained at the time.
>>  
>>> 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).
>> It applies to all rights that ISI *might have had*, which is all they could offer. It doesn't apply to any rights that third parties might have had, obviously. So it is the maximum that ISI could offer, which is all we could ask for. (IANAL, but I was in the discussion loop with the Trust's lawyer.)
> FWIW, RFC768 would have been considered a work-for-hire by Jon on behalf of ISI, and ISI could then grant the rights wherever they wanted that wasn't inconsistent with the contract between ISI and the US Government that covered Jon's work.

That may - or may not - be true for Jon, but he was staff at the time.

It’s useful to note that this would not affect *faculty* at USC (other faculty elsewhere might have the same privileges); at USC, they have always been given rights to their research, except only when it is specifically identified as a product of a contract, in specific exception to “work for hire” copyright. There are also other workarounds - e.g., hiring someone to write a book is work for hire; hiring them to investigate a topic and submit periodic progress reports - and having them write the book based on that research but on their own time - is not. And those two cases aren’t hypothetical; IANAL but they are based on direct experience at USC with the appropriate experts, FWIW.

Joe