Re: Should the RFC Editor publish an RFC in less than 2 months?

John C Klensin <john-ietf@jck.com> Wed, 28 November 2007 21:02 UTC

Return-path: <ietf-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IxU3Z-0005UB-5G; Wed, 28 Nov 2007 16:02:53 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IxU3W-0005Ns-Ox; Wed, 28 Nov 2007 16:02:50 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IxU3W-0003yZ-A8; Wed, 28 Nov 2007 16:02:50 -0500
Received: from [127.0.0.1] (helo=p3.JCK.COM) by bs.jck.com with esmtp (Exim 4.34) id 1IxU3V-000CYp-8S; Wed, 28 Nov 2007 16:02:49 -0500
Date: Wed, 28 Nov 2007 16:02:48 -0500
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, ietf@ietf.org
Message-ID: <CC3C6CC7EE08DA90C239082B@p3.JCK.COM>
In-Reply-To: <474DD597.9040208@gmail.com>
References: <E1IxTPt-0006r4-ST@ietf.org> <474DD597.9040208@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: iab@ietf.org, iesg@ietf.org
Subject: Re: Should the RFC Editor publish an RFC in less than 2 months?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org


--On Thursday, 29 November, 2007 09:54 +1300 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> I thought about this a bit when the RFC Editor started to
> catch up and
> accelerate; it's excellent news that it's no longer a
> theoretical
> question, so kudos to the Editor team (and IANA, who also have
> a role
> to play in getting many RFCs out).
> 
> My conclusion is that the number of appeals is relatively low.
> I'd hate
> for the low risk of having to roll back an approval to slow
> down all
> publications. So my personal preference is to not hold up
> publication
> (unless there is good reason to expect an appeal), but to add
> a new
> RFC status, let's call it PROVISIONAL for the sake of
> argument, that
> would be applied if an appeal is received within the 2 month
> window
> but after publication. If the appeal succeeds, the status can
> be
> changed as appropriate (likely to HISTORIC), and if the appeal
> fails
> it can revert to its original value.

I'd like to see something like the above combined with a shorter
window, maybe at two levels ("hold publication until..." and
"provisional until...").  Of course, if an appeal is actually
filed, it would be sensible to hold publication until it is
resolved.  I don't see any possible reason why we need to give
people two months to get an appeal filed: a month or, at most,
six weeks ought to be more than sufficient.

     john


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf