Re: Rights in early RFCs

"Paul Hoffman" <paul.hoffman@vpnc.org> Fri, 14 June 2019 23:43 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 857E91200C4 for <ietf@ietfa.amsl.com>; Fri, 14 Jun 2019 16:43:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 TKbVjnjr36lm for <ietf@ietfa.amsl.com>; Fri, 14 Jun 2019 16:43:46 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (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 1536112009E for <ietf@ietf.org>; Fri, 14 Jun 2019 16:43:46 -0700 (PDT)
Received: from [10.32.60.57] (50-1-99-176.dsl.dynamic.fusionbroadband.com [50.1.99.176]) (authenticated bits=0) by mail.proper.com (8.15.2/8.15.2) with ESMTPSA id x5ENfbaT019924 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 14 Jun 2019 16:41:38 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 50-1-99-176.dsl.dynamic.fusionbroadband.com [50.1.99.176] claimed to be [10.32.60.57]
From: Paul Hoffman <paul.hoffman@vpnc.org>
To: Scott Bradner <sob@sobco.com>
Cc: IETF general list <ietf@ietf.org>
Subject: Re: Rights in early RFCs
Date: Fri, 14 Jun 2019 16:43:42 -0700
X-Mailer: MailMate (1.12.5r5635)
Message-ID: <A3DE5329-2B88-4FB4-A1D5-E85EEC409A08@vpnc.org>
In-Reply-To: <F1C084A6-BB9E-4AFB-AB31-C547FD0FEEE4@sobco.com>
References: <alpine.OSX.2.21.9999.1906141728410.11884@ary.qy> <A89856255D980EBDE462508F@PSB> <F1C084A6-BB9E-4AFB-AB31-C547FD0FEEE4@sobco.com>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5e0vy6ezLY5TBUpwZe9qA9EXAeY>
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 23:43:48 -0000

On 14 Jun 2019, at 16:14, Scott Bradner wrote:

>> On Jun 14, 2019, at 7:06 PM, John C Klensin <john-ietf@jck.com> 
>> wrote:
>>
>> There were several later rounds of conversations about the
>> general topic on which Scott Bradber would be m8ch more expert
>> than I am, but I'd be surprised if the answer from him would be
>> significantly different from the above.
>
> It is not
>
> but I do have a question for John Levine - what is the context of your 
> question?
>
> republish? produce a revision? ???

Oddly, I can answer that one. Some people quite outside the IETF want to 
publish a spec for how to do $foo over the Internet. Their spec quotes 
small parts of various RFCs to make the requirements clear for the 
vendors who will implement $foo because those vendors do not normally 
use IETF standards. They were unsuccessful in finding how to get 
permission to quote from RFCs, and by circuitous route got to me. I 
passed them along to the IETF Trust, and that's where John's message 
originates. (Side-note: they didn't know who Jon Postel was or how to 
reach him to ask about getting the right to quote RFC 768. I had to 
break that news to them...)

--Paul Hoffman