IETF Logo Mail Archive

RE: The Evils of Informational RFC's

Ronald Bonica <rbonica@juniper.net> Wed, 08 September 2010 20:32 UTC

Return-Path: <rbonica@juniper.net>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2D3F43A6834 for <ietf@core3.amsl.com>; Wed, 8 Sep 2010 13:32:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.481
X-Spam-Level:
X-Spam-Status: No, score=-106.481 tagged_above=-999 required=5 tests=[AWL=0.118, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nIyoLXl8Qf6i for <ietf@core3.amsl.com>; Wed, 8 Sep 2010 13:32:15 -0700 (PDT)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by core3.amsl.com (Postfix) with ESMTP id B93123A67B3 for <ietf@ietf.org>; Wed, 8 Sep 2010 13:32:12 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob120.postini.com ([64.18.6.12]) with SMTP ID DSNKTIfy55CUPgx87VdQfx+eEqoaOB7DpbdL@postini.com; Wed, 08 Sep 2010 13:32:42 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 8 Sep 2010 13:30:14 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Wed, 8 Sep 2010 16:30:14 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: Eric Burger <eburger@standardstrack.com>, Bob Hinden <bob.hinden@gmail.com>
Date: Wed, 08 Sep 2010 16:30:12 -0400
Subject: RE: The Evils of Informational RFC's
Thread-Topic: The Evils of Informational RFC's
Thread-Index: ActPkSrDmEuXsgQSRsqTgGwgTssQqQAAnTOw
Message-ID: <13205C286662DE4387D9AF3AC30EF456B016BDDD5B@EMBX01-WF.jnpr.net>
References: <4C815335.4050209@bennett.com> <4C81554D.5060000@gmail.com> <4C8169DF.7010202@bennett.com> <4C8172AC.9060202@gmail.com> <4C817866.7040400@bennett.com> <4C817C6F.8070303@gmail.com> <4C818963.4090106@bennett.com> <21B56D7B-F058-47C8-8CBB-B35F82E1A0D2@standardstrack.com> <0ECC03C0-63B9-401F-B395-ACFBDF427296@gmail.com> <7F4C5F55-E722-4DF4-8E84-8D25628C55A3@standardstrack.com>
In-Reply-To: <7F4C5F55-E722-4DF4-8E84-8D25628C55A3@standardstrack.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 08 Sep 2010 20:32:17 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Eric Burger
> Sent: Wednesday, September 08, 2010 4:05 PM
> To: Bob Hinden
> Cc: IETF Discussion
> Subject: Re: The Evils of Informational RFC's
> 
> I would offer RFC 5211 is PRECISELY the kind of RFC the IETF should NOT
> be publishing!  I can see the press release now: "IETF publishes IPv6
> transition plan."   NO ONE OUTSIDE THE IETF has a clue the RFC Editor
> is NOT the IETF.  "RFC = IETF" is the *reality*, no matter how much we
> say it is not.
> 


Eric,

The following text appears on page 1 of RFC 5211:

IESG Note

   This RFC is not a candidate for any level of Internet Standard.  The
   IETF disclaims any knowledge of the fitness of this RFC for any
   purpose and notes that the decision to publish is not based on IETF
   review apart from IESG review for conflict with IETF work.  RFC
   Editor has chosen to publish this document at its discretion.  See
   RFC 3932 for more information.

The IESG note should be clear to anyone who actually reads the RFC. 

                                                     Ron

v2.23.0 | Report a Bug | By Email