Re: Rights in early RFCs
"John R Levine" <johnl@taugh.com> Sat, 15 June 2019 00:36 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 A913B120099 for <ietf@ietfa.amsl.com>; Fri, 14 Jun 2019 17:36:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=KEVCU05V; dkim=pass (1536-bit key) header.d=taugh.com header.b=Yf8UWiho
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 wFM0_CsvojFq for <ietf@ietfa.amsl.com>; Fri, 14 Jun 2019 17:36:24 -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 98D61120058 for <ietf@ietf.org>; Fri, 14 Jun 2019 17:36:24 -0700 (PDT)
Received: (qmail 65136 invoked from network); 15 Jun 2019 00:36:23 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=fe6e.5d043d87.k1906; i=johnl-iecc.com@submit.iecc.com; bh=nczX8UBIM80vNaGDuqf6odE2CwXCs9gukUssGToNbrI=; b=KEVCU05VAGobkuCqLCgEGsE/2AocaAsy6VstXJH9kjErpR0gpLpVo5WCQlDBsUVxZ1CPRzd0es1rJr2Qz+XmLW9Cm9Bg9ePmikMjlae95MIoQ6eD3eFDp77l4xSs37W85zsbRO8K20uBbLG2IOUiAnAJLhyGSwBSw58XG+EgeAHVfSqjF8ikcb8jbIoc0rarOYvaqwFajvKYWzmtP3wVhH7U8ues6FWgtLRnD2+leFIV9VG7fQAmXQhtIsYvIDQB
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=fe6e.5d043d87.k1906; olt=johnl-iecc.com@submit.iecc.com; bh=nczX8UBIM80vNaGDuqf6odE2CwXCs9gukUssGToNbrI=; b=Yf8UWihoPP/t15cDq6GyO3cLevRX+f4GQQkO6bXlNdwLevejIY6N54R98XfQn7luO8LzmMGQHKj1zD/MjeoYat85vQN2bwv4aZyUFOPXUEjjZUfZvDnFwxKZuscqX/Y28/wuMnLZhPaETZBSDYWeqTATwJ6Z5OaVcp5XFCcyXVytRi5SwDxRVWaBvUsmDGjCJRNxVkw0q3F9OWxFPnFCn+PPkX1RKO1hUZ0B3yOWxKUQYEXJ5AMY1UT/J3sElRGa
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; 15 Jun 2019 00:36:22 -0000
Date: Fri, 14 Jun 2019 20:36:22 -0400
Message-ID: <alpine.OSX.2.21.9999.1906142032530.12251@ary.qy>
From: John R Levine <johnl@taugh.com>
To: John C Klensin <john-ietf@jck.com>
Cc: IETF general list <ietf@ietf.org>
Subject: Re: Rights in early RFCs
In-Reply-To: <A89856255D980EBDE462508F@PSB>
References: <alpine.OSX.2.21.9999.1906141728410.11884@ary.qy> <A89856255D980EBDE462508F@PSB>
User-Agent: Alpine 2.21.9999 (OSX 337 2019-05-05)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XZqkPyP56VonPWFdSYFtVjg5KoY>
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: Sat, 15 Jun 2019 00:36:27 -0000
> 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. Yeah, we're trying to see if we can come up with some guidance for other organizations that want to use RFCs, apropos of a request from a SDO in a completely different industry that uses IP protocols in some internal protocols. I'm sure you can see why "Jon told me 20 years ago that it was OK" is not going to impress their lawyers, but if that's all we've got, that's all we've got. Regards, John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY Please consider the environment before reading this e-mail. https://jl.ly
- 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