IETF Logo Mail Archive

Re: Rights in early RFCs

"John Levine" <johnl@taugh.com> Sun, 16 June 2019 16:45 UTC

Return-Path: <johnl@iecc.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 5DDE4120077 for <ietf@ietfa.amsl.com>; Sun, 16 Jun 2019 09:45:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, 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=vUYyx/pL; dkim=pass (1536-bit key) header.d=taugh.com header.b=QRvnjFBk
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 nWSchH7D1qpa for <ietf@ietfa.amsl.com>; Sun, 16 Jun 2019 09:45:02 -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 D0BFC12003E for <ietf@ietf.org>; Sun, 16 Jun 2019 09:45:01 -0700 (PDT)
Received: (qmail 42956 invoked from network); 16 Jun 2019 16:44:58 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=a7ca.5d06720a.k1906; i=johnl-iecc.com@submit.iecc.com; bh=QQUTzsHviVQQN9ciUkU7WFwOGyuolXSbVSeLRLYj1EU=; b=vUYyx/pL1azuHAqldGPBgg0S+yxGId5bqpnJMHe5UxeDp2ma9rlRsO/j0sQaoHXZv78qhYyR8pnEihqOTnI6a5sJvQJkGP6WxNuHeHFvrIZd326ERQV6Dper0C6yhNe1z6p/O1jTIVwD+CtOQ76l9ATEpdzy5VGBNHAh8sqiGIcUzjAQAkW4KdUYoqYOtEQv0HuKE/bZLZ78zR5gk+Dv1pknsod/I1HOwQdrUlUm/7iXQ6cwoJfCq2QUsF2ob6/K
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=a7ca.5d06720a.k1906; olt=johnl-iecc.com@submit.iecc.com; bh=QQUTzsHviVQQN9ciUkU7WFwOGyuolXSbVSeLRLYj1EU=; b=QRvnjFBkPyBy4a8FIQkaS+K0VoR7jn4hkLWa9OJg23gfdNHJecSp+SMCHbpxN6BeOrnzJ91H2ZZsv0TTH9HilCv+OtKAb0iErjgcgixaEg03N9ukbMCY4lZyLTnLfCGBDWZRzYJKLpASaVqgOFdtgKNea4+1fcosV1vYHuGuS4nUwisruMyZKpXwlGB0U4S3BJGslOj+omNiRzB6iy8Cs9LtxNp4wjOU8aFd/u4GxLD5ixGE7YRQdpKrAsrufgaO
Received: from ary.qy ([64.246.232.221]) by imap.iecc.com ([64.57.183.75]) with ESMTPSA (TLS1.2 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP; 16 Jun 2019 16:44:58 -0000
Received: by ary.qy (Postfix, from userid 501) id 3E52F201598237; Sun, 16 Jun 2019 12:44:57 -0400 (EDT)
Date: Sun, 16 Jun 2019 12:44:57 -0400
Message-Id: <20190616164458.3E52F201598237@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Cc: john-ietf@jck.com
Subject: Re: Rights in early RFCs
In-Reply-To: <8E62BC2B27B814095E7E051A@JcK-HP5.jck.com>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vTaAv3VulV0rCf2JBBxDMTboM6U>
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 16:45:04 -0000

In article <8E62BC2B27B814095E7E051A@JcK-HP5.jck.com> you write:
>Colleagues, can an we please stop the amateur lawyering?  It is
>not, at least IMO, helpful, nor does it address the question
>that, AFAICT, John Levine was asking when the thread started.

Yes, please.  I'm trying to figure out what rights we have to what
documents and what rights we might be able to license if we believe it
is in the IETF's interests to do so.

For the document in question, RFC 768, it appears that the Trust has
and can have no rights at all, because it is in the public domain
according to the copyright law in effect in the US when it was
published in 1980.

R's,
John

v2.23.0 | Report a Bug | By Email