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

"todd glassey" <todd.glassey@worldnet.att.net> Fri, 18 February 2005 23:44 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 SAA23336 for <ipr-wg-web-archive@ietf.org>; Fri, 18 Feb 2005 18:44:08 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2I8t-0006ul-PC for ipr-wg-web-archive@ietf.org; Fri, 18 Feb 2005 19:06:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D2HH5-0005t0-IA; Fri, 18 Feb 2005 18:11:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D2Fw4-0004jJ-8Z for ipr-wg@megatron.ietf.org; Fri, 18 Feb 2005 16:45:16 -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 QAA27328 for <ipr-wg@ietf.org>; Fri, 18 Feb 2005 16:45:14 -0500 (EST)
Received: from mtiwmhc13.worldnet.att.net ([204.127.131.117]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2GHl-00074D-9M for ipr-wg@ietf.org; Fri, 18 Feb 2005 17:07:44 -0500
Received: from gw (104.san-jose-04-05rs.ca.dial-access.att.net[12.72.193.104]) by worldnet.att.net (mtiwmhc13) with SMTP id <20050218214440113002p341e>; Fri, 18 Feb 2005 21:44:41 +0000
Message-ID: <020a01c51603$0db18d60$010aff0a@gw>
From: todd glassey <todd.glassey@worldnet.att.net>
To: bortzmeyer@nic.fr, ipr-wg@ietf.org, lrosen@rosenlaw.com, Scott Bradner <sob@harvard.edu>
References: <20050218204703.CBFFB226B56@newdev.harvard.edu>
Date: Fri, 18 Feb 2005 13:44:34 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit
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.1 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit

So then what happens when the original authors try and rework their
document? now there are two separate documents with the same identity
progressing... Really smart eh? - So then no one ever really needs to draft
a I-D - just pick some RFC and strip ALL of the content out of it and
install new content.

Just as Scott says, there is nothing in the IETF process to prevent this
type of Hijack.

Todd

----- Original Message ----- 
From: "Scott Bradner" <sob@harvard.edu>
To: <bortzmeyer@nic.fr>; <ipr-wg@ietf.org>; <lrosen@rosenlaw.com>;
<todd.glassey@worldnet.att.net>
Sent: Friday, February 18, 2005 12:47 PM
Subject: Re: draft-bradner-rfc-extracts-00 and the risk of "false RFCs"


> > I have a dumb question - what's to stop anyone from taking an RFC and
> > rewriting part of it and re-filing it with the IETF as the next instance
in
> > that RFC's evolution??? I have seen absolutely nothing in any of the
IETF
> > process documents that would prohibit this.
>
> maybe because that is specifically permitted
>
> Scott


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