IETF Logo Mail Archive

Re: draft-bradner-rfc-extracts-00 and the risk of "false RFCs"

"'Stephane Bortzmeyer'" <bortzmeyer@nic.fr> Mon, 21 February 2005 13:07 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 IAA22546 for <ipr-wg-web-archive@ietf.org>; Mon, 21 Feb 2005 08:07:31 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3Ddw-0000N3-QO for ipr-wg-web-archive@ietf.org; Mon, 21 Feb 2005 08:30:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3CXW-0006Zg-Ou; Mon, 21 Feb 2005 07:19:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3Bml-0007DG-R4 for ipr-wg@megatron.ietf.org; Mon, 21 Feb 2005 06:31:32 -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 GAA13669 for <ipr-wg@ietf.org>; Mon, 21 Feb 2005 06:31:24 -0500 (EST)
Received: from mx2.nic.fr ([192.134.4.11]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3C8w-000654-Ll for ipr-wg@ietf.org; Mon, 21 Feb 2005 06:54:28 -0500
Received: from localhost (localhost.localdomain [127.0.0.1]) by mx2.nic.fr (Postfix) with ESMTP id 7EA0326C091; Mon, 21 Feb 2005 12:31:21 +0100 (CET)
Received: from maya20.nic.fr (maya20.nic.fr [192.134.4.152]) by mx2.nic.fr (Postfix) with ESMTP id 7644126C071; Mon, 21 Feb 2005 12:31:20 +0100 (CET)
Received: from batilda.nic.fr (postfix@batilda.nic.fr [192.134.4.69]) by maya20.nic.fr (8.12.4/8.12.4) with ESMTP id j1LBVK4u1484699; Mon, 21 Feb 2005 12:31:20 +0100 (CET)
Received: by batilda.nic.fr (Postfix, from userid 1000) id 19D8C16A9E3; Mon, 21 Feb 2005 12:31:20 +0100 (CET)
Date: Mon, 21 Feb 2005 12:31:20 +0100
From: 'Stephane Bortzmeyer' <bortzmeyer@nic.fr>
To: "Steven M. Bellovin" <smb@cs.columbia.edu>
Message-ID: <20050221113120.GA31071@nic.fr>
References: <20050218134018.GA47441@mail26b.sbc-webhosting.com> <20050218202702.E856E3C03BD@berkshire.machshav.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20050218202702.E856E3C03BD@berkshire.machshav.com>
X-Operating-System: Debian GNU/Linux 3.1
X-Kernel: Linux 2.6.8-1-686 i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.6+20040907i
X-Virus-Scanned: by amavisd-new at mx2.nic.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: lrosen@rosenlaw.com, ipr-wg@ietf.org
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
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: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3

On Fri, Feb 18, 2005 at 03:27:02PM -0500,
 Steven M. Bellovin <smb@cs.columbia.edu> wrote 
 a message of 15 lines which said:

> Several of us have already wondered if we should explore trademarks.

Trademarks is only one of the ways we could fight "rogue" RFCs. Other
ways (non-exclusive, BTW) have been mentioned in that thread:

- "You have to rename" licence (widely used: Mozilla, LaTeX, NetBSD)

- Certification ("ISOC-approved")

- Cryptographic signatures 

None is perfect (nothing is ever perfect in law) but they are lighter
than the trademark process (specially since "RFC" may be
non-trademarkable). 

What is clear is that preventing the modification of RFCs has
*nothing* to do with the fight against rogue RFCs.

_______________________________________________
Ipr-wg mailing list
Ipr-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/ipr-wg

v2.23.0 | Report a Bug | By Email