Re: draft-bradner-rfc-extracts-00 and the risk of "false RFCs"
Don Armstrong <don@debian.org> Sat, 19 February 2005 03:58 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20117 for <ipr-wg-web-archive@ietf.org>; Fri, 18 Feb 2005 22:58:31 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2M75-0007UW-N1 for ipr-wg-web-archive@ietf.org; Fri, 18 Feb 2005 23:21:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D2Ld2-0000KM-RD; Fri, 18 Feb 2005 22:50:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D2LVs-0005fA-Fr for ipr-wg@megatron.ietf.org; Fri, 18 Feb 2005 22:42:36 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19048 for <ipr-wg@ietf.org>; Fri, 18 Feb 2005 22:42:34 -0500 (EST)
Received: from rzlab.ucr.edu ([138.23.92.77] helo=epsilon.donarmstrong.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2Lrf-00076s-V2 for ipr-wg@ietf.org; Fri, 18 Feb 2005 23:05:08 -0500
Received: from archimedes.ucr.edu (archimedes.ucr.edu [138.23.92.79]) by epsilon.donarmstrong.com (8.13.2/8.13.2/Debian-1) with SMTP id j1J3gTPi028208 for <ipr-wg@ietf.org>; Fri, 18 Feb 2005 19:42:30 -0800
Received: (nullmailer pid 16262 invoked by uid 1000); Sat, 19 Feb 2005 03:42:28 -0000
Date: Fri, 18 Feb 2005 19:42:28 -0800
From: Don Armstrong <don@debian.org>
To: ipr-wg@ietf.org
Message-ID: <20050219034228.GM25430@archimedes.ucr.edu>
Mail-Followup-To: ipr-wg@ietf.org
References: <20050218171352.GA18414@nic.fr> <20050218134018.GA47441@mail26b.sbc-webhosting.com> <20050219010211.GJ25430@archimedes.ucr.edu> <1108777462.28925.266.camel@thunk> <20050219021108.GL25430@archimedes.ucr.edu> <1108783431.51832.2037.camel@unknown.hamachi.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <1108783431.51832.2037.camel@unknown.hamachi.org>
User-Agent: Mutt/1.5.6+20040907i
X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.0.0-pre4
X-Spam-Checker-Version: SpamAssassin 3.0.0-pre4 (2004-08-05) on epsilon.donarmstrong.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Subject: Re: draft-bradner-rfc-extracts-00 and the risk of "false RFCs"
X-BeenThere: ipr-wg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ipr-wg@ietf.org
List-Id: IPR-WG <ipr-wg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipr-wg>, <mailto:ipr-wg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipr-wg@ietf.org>
List-Help: <mailto:ipr-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipr-wg>, <mailto:ipr-wg-request@ietf.org?subject=subscribe>
Sender: ipr-wg-bounces@ietf.org
Errors-To: ipr-wg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
[Please refrain from Cc:'ing me. I'm subscribed.] On Fri, 18 Feb 2005, Bill Sommerfeld wrote: > On Fri, 2005-02-18 at 21:11, Don Armstrong wrote: > > > the people most likely to be harmed by an unofficial RFC would > > > be the ones who would not know how to check the signature. > > > > Are such people even capable of writing software that actually > > conforms to an RFC? > > you have an unrealistically narrow view of the target audience of > IETF documents. Perhaps I do have unrealistic assumptions about the average intelligence of the target audience of IETF documents,[1] but assuming the target audience of IETF documents is capable of the following: 1) reading and understanding them 2) following simple directions to verify the authenticity of the document then I really don't see the difficulty. It really is quite trivial to verify a PGP signature, as I demonstrated previously. Surely anyone for whom the accuracy of an RFC was important would be capable of undertaking such a simple task. This also has the added advantage of taking care of malicious RFC-look alikes that aren't derivative works of an actual RFC and thus aren't covered by the license at all. Don Armstrong 1: It wouldn't be the first time that I've been surprised by assuming an audience was capable of rather rudementary tasks... -- DIE! -- Maritza Campos http://www.crfh.net/d/20020601.html http://www.donarmstrong.com http://rzlab.ucr.edu _______________________________________________ Ipr-wg mailing list Ipr-wg@ietf.org https://www1.ietf.org/mailman/listinfo/ipr-wg
- draft-bradner-rfc-extracts-00 and the risk of "fa… Stephane Bortzmeyer
- RE: draft-bradner-rfc-extracts-00 and the risk of… Lawrence Rosen
- RE: draft-bradner-rfc-extracts-00 and the risk of… Bill Sommerfeld
- RE: draft-bradner-rfc-extracts-00 and the risk of… Lawrence Rosen
- Re: draft-bradner-rfc-extracts-00 and the risk of… todd glassey
- RE: draft-bradner-rfc-extracts-00 and the risk of… Joel M. Halpern
- Re: draft-bradner-rfc-extracts-00 and the risk of… Steven M. Bellovin
- Re: draft-bradner-rfc-extracts-00 and the risk of… Bill Sommerfeld
- Re: draft-bradner-rfc-extracts-00 and the risk of… Scott Bradner
- Re: draft-bradner-rfc-extracts-00 and the risk of… todd glassey
- Re: draft-bradner-rfc-extracts-00 and the risk of… John C Klensin
- Re: draft-bradner-rfc-extracts-00 and the risk of… Don Armstrong
- Re: draft-bradner-rfc-extracts-00 and the risk of… Bill Sommerfeld
- RE: draft-bradner-rfc-extracts-00 and the risk of… Matthew Garrett
- Re: draft-bradner-rfc-extracts-00 and the risk of… Don Armstrong
- Re: draft-bradner-rfc-extracts-00 and the risk of… Bill Sommerfeld
- Re: draft-bradner-rfc-extracts-00 and the risk of… Don Armstrong
- Re: draft-bradner-rfc-extracts-00 and the risk of… 'Stephane Bortzmeyer'