Re: [Gendispatch] why the trust is not your lawyer

Jay Daley <exec-director@ietf.org> Tue, 01 November 2022 09:10 UTC

Return-Path: <exec-director@ietf.org>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0955C14F73F for <gendispatch@ietfa.amsl.com>; Tue, 1 Nov 2022 02:10:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kSEeD9k4_FvL for <gendispatch@ietfa.amsl.com>; Tue, 1 Nov 2022 02:10:39 -0700 (PDT)
Received: from ietfx.amsl.com (ietfx.amsl.com [50.223.129.196]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50C29C14F734 for <gendispatch@ietf.org>; Tue, 1 Nov 2022 02:10:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by ietfx.amsl.com (Postfix) with ESMTP id 4527C4053E21; Tue, 1 Nov 2022 02:10:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from ietfx.amsl.com ([50.223.129.196]) by localhost (ietfx.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pbHjRwWzgBXy; Tue, 1 Nov 2022 02:10:39 -0700 (PDT)
Received: from smtpclient.apple (host-92-27-125-209.static.as13285.net [92.27.125.209]) by ietfx.amsl.com (Postfix) with ESMTPSA id 8B9FE4051053; Tue, 1 Nov 2022 02:10:38 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
From: Jay Daley <exec-director@ietf.org>
In-Reply-To: <20221031182416.7FEB34DAFDE1@ary.qy>
Date: Tue, 01 Nov 2022 09:10:36 +0000
Cc: gendispatch@ietf.org, lloyd.wood@yahoo.co.uk
Content-Transfer-Encoding: quoted-printable
Message-Id: <F4459402-0C55-4027-9FD8-5C5A2CBACCE7@ietf.org>
References: <20221031182416.7FEB34DAFDE1@ary.qy>
To: John Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/7jRm0YsIT4P50acWQZUtB6Xi6tE>
Subject: Re: [Gendispatch] why the trust is not your lawyer
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Nov 2022 09:10:43 -0000


> On 31 Oct 2022, at 18:24, John Levine <johnl@taugh.com> wrote:
> 
> It appears that Lloyd W  <lloyd.wood@yahoo.co.uk> said:
>> Did RFC9293 updating RFC793 for STD7 expose any copyright issues? I don't think RFC793 has a copyright statement, but wouldn't
>> presume 'govt contract, therefore no copyright'.
> 
> Keeping in mind that I am not your lawyer even more than the Trust is
> not your lawyer, and this is not legal advice:
> 
> RFC793 says it was written by ISI for DARPA. Without seeing the
> agreement between them there is no way to tell who owns the document.
> ISI has given a license to the Trust, and DARPA is the federal
> government which does not assert copyright so either way we seem to
> have the rights. It was written after 1976 so the lack of a copyright
> notice doesn't make any difference.
> 
> So for this particular document, I would say the copyright risk is
> very low. We have licenses for many early RFCs still in use, or
> believe they are out of copyright. RFCs 768 for UDP, 791 for IP, and
> 792 for ICMP, are all from ISI.
> 
> On the other hand, if we wanted to update RFC894, IP datagrams over
> Ethernet, that would be more of a problem. There's no trace of the
> author in our mail archive, his employer Symbolics went bankrupt, and
> it is unclear whether an apparent successor company owns the copyright
> on that document. But we can wait and burn that bridge if and when we
> get to it.

That’s excellent information, but it provides yet more evidence to me that information like this needs to recorded in a database so that we don’t have to rely on the memory of individuals and the ability of people to access that memory.

Jay

> 
> R's,
> John
> 
> -- 
> Gendispatch mailing list
> Gendispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/gendispatch

-- 
Jay Daley
IETF Executive Director
exec-director@ietf.org