Rights in early RFCs
"John R Levine" <johnl@taugh.com> Fri, 14 June 2019 21:45 UTC
Return-Path: <johnl@taugh.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 287F612016E for <ietf@ietfa.amsl.com>; Fri, 14 Jun 2019 14:45:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=EdYrTL2e; dkim=pass (1536-bit key) header.d=taugh.com header.b=FpBB42eV
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 pMQdo77g7ete for <ietf@ietfa.amsl.com>; Fri, 14 Jun 2019 14:45:21 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 EE7DB120047 for <ietf@ietf.org>; Fri, 14 Jun 2019 14:45:20 -0700 (PDT)
Received: (qmail 27157 invoked from network); 14 Jun 2019 21:45:18 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type:user-agent; s=6a10.5d04156e.k1906; i=johnl-iecc.com@submit.iecc.com; bh=ZqGnWFrILGMzrftF582tjg2qXKkEopaVixOXD7sjKmQ=; b=EdYrTL2ez1I8cERn+Thh/Y/gJHFoDwhKpKuM/qZ0AgEo6l6wP0OkRRolojGJxN6GlOpP4hTQK3xGrMHQ/H5iLs4R+z5k90LgyiB1HvrsVuNQh8uEW+zZ44P6GT/QGmbtxtv3Y8X4QXBc/2t+XpI9179MWGz5y5yxCy4tasObjcghcO009/wrCHsr3TNPJl56q/U8/G8meYgHoSUxWhja8zksPsCfDzsy68zotXCpmM0lISek6gDaOKwCRC3XvtJW
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:mime-version:content-type:user-agent; s=6a10.5d04156e.k1906; olt=johnl-iecc.com@submit.iecc.com; bh=ZqGnWFrILGMzrftF582tjg2qXKkEopaVixOXD7sjKmQ=; b=FpBB42eV2FxB/nn0cy3D00fu8I5kj2Sh5zF93Q/SL6IgHYND9wGu4O8WIqGHduG6VBPaSq6hbOr1c8cK8sAlDqRkdjwyEPCbMyxewQS3RFXoMKtJbvfyzNu5wecUZOiQkR9hvAFXJzKihmiXCgclT9zglSKrJLquZXHFNEtEbUHCmjejiYoRiPsazung9BoAeucgoGnabRVVSAvPtyNR5C7UlyhJjYofGI2eiGZotJPlgQb+zx4zBim/Ih1SEb/m
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.2 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP6; 14 Jun 2019 21:45:18 -0000
Date: Fri, 14 Jun 2019 17:45:17 -0400
Message-ID: <alpine.OSX.2.21.9999.1906141728410.11884@ary.qy>
From: John R Levine <johnl@taugh.com>
To: IETF general list <ietf@ietf.org>
Subject: Rights in early RFCs
User-Agent: Alpine 2.21.9999 (OSX 337 2019-05-05)
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JhLrCPAt1RqHn-DHMKxVKMYfpBA>
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 21:45:23 -0000
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.
- Rights in early RFCs John R Levine
- Re: Rights in early RFCs John C Klensin
- Re: Rights in early RFCs Scott Bradner
- Re: Rights in early RFCs Paul Hoffman
- Re: Rights in early RFCs Brian E Carpenter
- Re: Rights in early RFCs John R Levine
- Re: Rights in early RFCs Joe Touch
- Re: Rights in early RFCs Brian E Carpenter
- Re: Rights in early RFCs Joe Touch
- Re: Rights in early RFCs Kathleen Moriarty
- Re: Rights in early RFCs Miles Fidelman
- Re: Rights in early RFCs John C Klensin
- Re: Rights in early RFCs Keith Moore
- Re: Rights in early RFCs John Levine
- Re: Rights in early RFCs Keith Moore
- Re: Rights in early RFCs Salz, Rich
- Re: Rights in early RFCs Joel M. Halpern
- Re: Rights in early RFCs Masataka Ohta
- Re: Rights in early RFCs Masataka Ohta
- Re: Rights in early RFCs Michael StJohns
- Re: Rights in early RFCs Keith Moore
- Re: Rights in early RFCs Joel M. Halpern
- Re: Rights in early RFCs Keith Moore
- Re: Rights in early RFCs John C Klensin
- Re: Rights in early RFCs Joe Touch
- Re: Rights in early RFCs Masataka Ohta
- Re: Rights in early RFCs John Levine
- Re: Rights in early RFCs Michael StJohns
- Re: Rights in early RFCs Masataka Ohta