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

Bill Sommerfeld <sommerfeld@sun.com> Fri, 18 February 2005 22:30 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 RAA12228 for <ipr-wg-web-archive@ietf.org>; Fri, 18 Feb 2005 17:30:56 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2H01-0003d1-R4 for ipr-wg-web-archive@ietf.org; Fri, 18 Feb 2005 17:53:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D2FDw-0007cL-Ai; Fri, 18 Feb 2005 15:59:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D2Es4-0007MX-QE for ipr-wg@megatron.ietf.org; Fri, 18 Feb 2005 15:37:04 -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 PAA10282 for <ipr-wg@ietf.org>; Fri, 18 Feb 2005 15:37:03 -0500 (EST)
Received: from nwkea-mail-2.sun.com ([192.18.42.14]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2FDm-0001Q4-Sk for ipr-wg@ietf.org; Fri, 18 Feb 2005 15:59:32 -0500
Received: from eastmail2bur.East.Sun.COM ([129.148.13.40]) by nwkea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id j1IKb1NV025539; Fri, 18 Feb 2005 12:37:01 -0800 (PST)
Received: from thunk (thunk.East.Sun.COM [129.148.174.66]) by eastmail2bur.East.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL,v2.2) with ESMTP id j1IKb0Op000444; Fri, 18 Feb 2005 15:37:01 -0500 (EST)
Received: from thunk.east.sun.com (localhost [127.0.0.1]) by thunk (8.13.3+Sun/8.13.3) with ESMTP id j1IKb0wm002646; Fri, 18 Feb 2005 15:37:00 -0500 (EST)
Received: (from sommerfeld@localhost) by thunk.east.sun.com (8.13.3+Sun/8.13.3/Submit) id j1IKb0pF002645; Fri, 18 Feb 2005 15:37:00 -0500 (EST)
X-Authentication-Warning: thunk.east.sun.com: sommerfeld set sender to sommerfeld@sun.com using -f
From: Bill Sommerfeld <sommerfeld@sun.com>
To: todd glassey <todd.glassey@worldnet.att.net>
In-Reply-To: <01a601c515f4$6aef5340$010aff0a@gw>
References: <20050218134018.GA47441@mail26b.sbc-webhosting.com> <01a601c515f4$6aef5340$010aff0a@gw>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1108759019.28925.221.camel@thunk>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6.325
Date: Fri, 18 Feb 2005 15:37:00 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit
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: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit

On Fri, 2005-02-18 at 14:54, todd glassey wrote:
> 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??? 

Nothing, and nothing should.

That's known as "participating in the IETF standards process".

							- Bill










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