Re: RFC Editor doc approvals (RE: [mpowr] Mailing List Management)
Dave Crocker <dhc@dcrocker.net> Thu, 25 December 2003 06:53 UTC
Received: from optimus.ietf.org ([132.151.1.19])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06295
for <mpowr-archive@odin.ietf.org>; Thu, 25 Dec 2003 01:53:14 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20) id 1AZPMU-00042r-MD
for mpowr-archive@odin.ietf.org; Thu, 25 Dec 2003 01:52:46 -0500
Received: (from exim@localhost)
by www1.ietf.org (8.12.8/8.12.8/Submit) id hBP6qkPM015546
for mpowr-archive@odin.ietf.org; Thu, 25 Dec 2003 01:52:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20) id 1AZPMU-00042f-Fm
for mpowr-web-archive@optimus.ietf.org; Thu, 25 Dec 2003 01:52:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06275
for <mpowr-web-archive@ietf.org>; Thu, 25 Dec 2003 01:52:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12)
id 1AZPMR-0006NG-00
for mpowr-web-archive@ietf.org; Thu, 25 Dec 2003 01:52:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
id 1AZPKG-0006Kj-00
for mpowr-web-archive@ietf.org; Thu, 25 Dec 2003 01:50:29 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
by ietf-mx with esmtp (Exim 4.12) id 1AZPI9-0006Hh-00
for mpowr-web-archive@ietf.org; Thu, 25 Dec 2003 01:48:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20)
id 1AZPHt-0003uk-1x; Thu, 25 Dec 2003 01:48:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20) id 1AZPHW-0003uH-GX
for mpowr@optimus.ietf.org; Thu, 25 Dec 2003 01:47:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06202
for <mpowr@ietf.org>; Thu, 25 Dec 2003 01:47:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12)
id 1AZPHM-0006HS-00
for mpowr@ietf.org; Thu, 25 Dec 2003 01:47:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
id 1AZPEC-0006Fv-00
for mpowr@ietf.org; Thu, 25 Dec 2003 01:44:13 -0500
Received: from joy.songbird.com ([208.184.79.7])
by ietf-mx with esmtp (Exim 4.12) id 1AZPD2-0006EU-00
for mpowr@ietf.org; Thu, 25 Dec 2003 01:43:00 -0500
Received: from bbprime (jay.songbird.com [208.184.79.253])
by joy.songbird.com (8.11.6/8.11.6) with SMTP id hBP6nlc07534
for <mpowr@ietf.org>; Wed, 24 Dec 2003 22:49:47 -0800
From: Dave Crocker <dhc@dcrocker.net>
To: <mpowr@ietf.org>
X-Mailer: PocoMail 3.03 (1740) - EVALUATION VERSION
X-URL: http://www.pocomail.com/
Reply-To: dcrocker@brandenburg.com
Date: Wed, 24 Dec 2003 22:42:22 -0800
Message-ID: <20031224224222.696311@bbprime>
In-Reply-To: <35351182.1072254430@scan.jck.com>
Subject: Re: RFC Editor doc approvals (RE: [mpowr] Mailing List Management)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: mpowr-admin@ietf.org
Errors-To: mpowr-admin@ietf.org
X-BeenThere: mpowr@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpowr>,
<mailto:mpowr-request@ietf.org?subject=unsubscribe>
List-Id: Management Positions -- Oversight, Work and Results <mpowr.ietf.org>
List-Post: <mailto:mpowr@ietf.org>
List-Help: <mailto:mpowr-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpowr>,
<mailto:mpowr-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on
ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
On Wed, 24 Dec 2003 08:27:10 -0500, John C Klensin wrote: > > > =09* At the time 2026 was written, the RFC Editor timeout > > > =09for IESG review of an independent submission document > > > =09was two weeks. > > > > 1) as far as I remember, the rfc editor never did anything when > > the timeout expired. not even when it was 2 weeks. > > If the RFC Editor is following this list, I'll let them respond. But > my recollection is that "never did anything" was the result of a > clear understanding that the IESG would be very irritated if they > did so and, perhaps, would even attempt to retaliate. This thread is missing some fairly basic underpinnings that were true during the 1989-1993 period that I was an AD, which I generally call the start of the "modern" IETF: 1. The RFC Editor operation was independent of the IETF, although it of course had a number of substantial points of coordination. 2. The IESG did not get to do a pocket veto on any documentfor which there was no serious claim it impacted existing IETF work or would likely have significant, negative impact on Internet operation. In other words, folks, the RFC Editor engaged in a number of courtesies with the IETF, via the IESG, but was entirely free to exercise its own judgments about documents that did not originate in the IETF and did not seek standards status. This has changed in recent years, much to the detriment of the open publication policy that used to hold true for the RFC series. Now, it appears that the IESG gets a complete veto over any RFC, no matter its source or desired status. d/ _______________________________________________ mpowr mailing list mpowr@ietf.org https://www1.ietf.org/mailman/listinfo/mpowr
- [mpowr] Mailing List Management James Kempf
- RE: [mpowr] Mailing List Management Margaret.Wasserman
- Re: [mpowr] Mailing List Management Alex Rousskov
- Re: [mpowr] Mailing List Management Alex Conta
- Re: [mpowr] Mailing List Management James Kempf
- Re: [mpowr] Mailing List Management Alex Conta
- RE: [mpowr] Mailing List Management Alex Rousskov
- Re: [mpowr] Mailing List Management Spencer Dawkins
- Re: [mpowr] Mailing List Management Harald Tveit Alvestrand
- Re: [mpowr] Mailing List Management John C Klensin
- Re: [mpowr] Mailing List Management Alex Conta
- Re: [mpowr] Mailing List Management Alex Rousskov
- Re: [mpowr] Mailing List Management Alex Conta
- Re: [mpowr] Mailing List Management James Kempf
- Re: [mpowr] Mailing List Management Alex Rousskov
- Re: [mpowr] Mailing List Management James Kempf
- Re: [mpowr] Mailing List Management Melinda Shore
- Re: [mpowr] Mailing List Management Alex Rousskov
- Re: [mpowr] Mailing List Management James Kempf
- RE: [mpowr] Mailing List Management Margaret.Wasserman
- RE: [mpowr] Mailing List Management Margaret.Wasserman
- RE: [mpowr] Mailing List Management Alex Rousskov
- Re: [mpowr] Mailing List Management Alex Rousskov
- Re: [mpowr] Mailing List Management James Kempf
- RE: [mpowr] Mailing List Management John C Klensin
- Re: [mpowr] Mailing List Management Spencer Dawkins
- RE: [mpowr] Mailing List Management Margaret.Wasserman
- Re: [mpowr] Mailing List Management Alex Conta
- Re: [mpowr] Mailing List Management Alex Conta
- Re: [mpowr] Mailing List Management Spencer Dawkins
- RE: [mpowr] Mailing List Management John C Klensin
- RFC Editor doc approvals (RE: [mpowr] Mailing Lis… Harald Tveit Alvestrand
- Re: RFC Editor doc approvals (RE: [mpowr] Mailing… John C Klensin
- Re: RFC Editor doc approvals (RE: [mpowr] Mailing… Harald Tveit Alvestrand
- Re: RFC Editor doc approvals (RE: [mpowr] Mailing… Dave Crocker
- Re: [mpowr] Mailing List Management Harald Tveit Alvestrand
- Re: [mpowr] Mailing List Management Alex Rousskov
- Re: [mpowr] Mailing List Management Harald Tveit Alvestrand
- Re: [mpowr] Mailing List Management Alex Rousskov
- Re: [mpowr] Mailing List Management John C Klensin
- Re: Re: [mpowr] Mailing List Management Dave Crocker
- Re: [mpowr] Mailing List Management Alex Rousskov