Re: Should the RFC Editor publish an RFC in less than 2 months?
Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 28 November 2007 20:55 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 1IxTvy-0000Hi-Ju; Wed, 28 Nov 2007 15:55:02 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IxTvw-0000Gx-E9 for ietf@ietf.org; Wed, 28 Nov 2007 15:55:00 -0500
Received: from rv-out-0910.google.com ([209.85.198.188]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IxTvw-0001af-0p for ietf@ietf.org; Wed, 28 Nov 2007 15:55:00 -0500
Received: by rv-out-0910.google.com with SMTP id l15so1271465rvb for <ietf@ietf.org>; Wed, 28 Nov 2007 12:54:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:organization:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=iiJfOWJZ6G8WPqLZudHp5uOz5bCjHkay37me8LJKJCg=; b=nggw/a+zKJHLmGActlzqSNzvgOl6/a9V0d6ZKcEB4RIyS1ARmczeAFmxPenOlEjErofC/BFJksNYIArGBw+l8QFQtMbbkSaha56//V0Yj8E6JwLNcLMFPw7uZ1zpyDk+VFSz2aiIpC8a6ZhfQ242oSwPP4HqShYumx7hGzkDzGY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=received:message-id:date:from:organization:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=V7DOg2axQROMNVsKVzBU7YDhls2e1qfj3VgDr8+0H/lixl57R5d5K+bkMwoY/dsK3JwMomxez2qsP2PX8hOypNmz7E9H3P6/h7605Gx5F1pmz36wH3xHMmPV2hMpgwreshPoQYlXv3Y0w3QaCBuLCD7F3d8RMuhDsov//Sz2vEg=
Received: by 10.141.151.20 with SMTP id d20mr2867996rvo.1196283299383; Wed, 28 Nov 2007 12:54:59 -0800 (PST)
Received: from ?130.216.38.124? ( [130.216.38.124]) by mx.google.com with ESMTPS id f42sm2104784rvb.2007.11.28.12.54.53 (version=SSLv3 cipher=RC4-MD5); Wed, 28 Nov 2007 12:54:58 -0800 (PST)
Message-ID: <474DD597.9040208@gmail.com>
Date: Thu, 29 Nov 2007 09:54:47 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: ietf@ietf.org
References: <E1IxTPt-0006r4-ST@ietf.org>
In-Reply-To: <E1IxTPt-0006r4-ST@ietf.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
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 2007-11-29 09:21, IETF Chair wrote: ... > If we receive an appeal before the RFC is published, we can put a hold on > the document, preventing pblication until the appeal has been studied. > However, we have no way to pull an RFC back if it is published before the > appeal arrives. As we all know, once an RFC is published, it cannot be > changed. Thus, the RFCs form an archival series. If we find a bug in an > RFC, we write a revised RFC that obsoletes the one that contains the > error. So, what should we do if there is a successful appeal after the > RFC is published? 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. Brian _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- Re: Should the RFC Editor publish an RFC in less … Eric Rescorla
- Should the RFC Editor publish an RFC in less than… IETF Chair
- Re: Should the RFC Editor publish an RFC in less … Brian E Carpenter
- Re: Should the RFC Editor publish an RFC in less … John C Klensin
- RE: Should the RFC Editor publish an RFC in less … Wassim Haddad
- Re: Should the RFC Editor publish an RFC in less … Ted Hardie
- Re: Should the RFC Editor publish an RFC in less … Brian E Carpenter
- Re: Should the RFC Editor publish an RFC in less … Leslie Daigle
- Re: Should the RFC Editor publish an RFC in less … Russ Housley
- Re: Should the RFC Editor publish an RFC in less … Cullen Jennings
- Re: Should the RFC Editor publish an RFC in less … Sam Hartman
- Re: Should the RFC Editor publish an RFC in less … Eric Rescorla
- Re: Should the RFC Editor publish an RFC in less … Tim Polk
- Re: Should the RFC Editor publish an RFC in less … Paul Hoffman
- Re: Should the RFC Editor publish an RFC in less … Sam Hartman
- Re: Should the RFC Editor publish an RFC in less … Sam Hartman
- Re: Should the RFC Editor publish an RFC in less … Frank Ellermann
- Re: Should the RFC Editor publish an RFC in less … Eric Rescorla
- Re: Should the RFC Editor publish an RFC in less … Tom.Petch
- Re: Should the RFC Editor publish an RFC in less … Harald Alvestrand
- Re: Should the RFC Editor publish an RFC in less … John C Klensin
- Re: Should the RFC Editor publish an RFC in less … Norbert Bollow
- Re: Should the RFC Editor publish an RFC in less … Iljitsch van Beijnum
- Re: Should the RFC Editor publish an RFC in less … Eric Rescorla
- Re: Should the RFC Editor publish an RFC in less … Dave Crocker
- Re: Should the RFC Editor publish an RFC in less … Alexey Melnikov
- Re: Should the RFC Editor publish an RFC in less … Jari Arkko
- Re: Should the RFC Editor publish an RFC in less … Sam Hartman
- Re: Should the RFC Editor publish an RFC in less … John C Klensin
- Re: Should the RFC Editor publish an RFC in less … Paul Hoffman
- Re: Should the RFC Editor publish an RFC in less … Sam Hartman
- Re: Should the RFC Editor publish an RFC in less … Harald Alvestrand
- Re: Should the RFC Editor publish an RFC in less … Brian E Carpenter
- Re: Should the RFC Editor publish an RFC in less … Bob Hinden
- Re: Should the RFC Editor publish an RFC in less … Frank Ellermann
- Re: Should the RFC Editor publish an RFC in less … John C Klensin
- Re: Should the RFC Editor publish an RFC in less … Spencer Dawkins
- Re: Should the RFC Editor publish an RFC in less … Magnus Westerlund
- Re: Should the RFC Editor publish an RFC in less … Frank Ellermann
- Re: Should the RFC Editor publish an RFC in less … John C Klensin
- Re: Should the RFC Editor publish an RFC in less … Alexey Melnikov
- Re: Should the RFC Editor publish an RFC in less … Jari Arkko
- Re: Should the RFC Editor publish an RFC in less … Russ Housley
- Re: Should the RFC Editor publish an RFC in less … Bob Hinden
- Re: Should the RFC Editor publish an RFC in less … Harald Tveit Alvestrand
- Re: Should the RFC Editor publish an RFC in less … John C Klensin
- Re: Should the RFC Editor publish an RFC in less … Frank Ellermann
- Re: Should the RFC Editor publish an RFC in less … Bob Hinden
- Re: Should the RFC Editor publish an RFC in less … Lixia Zhang
- Re: Should the RFC Editor publish an RFC in less … Frank Ellermann
- Re: Should the RFC Editor publish an RFC in less … Iljitsch van Beijnum
- Re: Should the RFC Editor publish an RFC in less … Frank Ellermann
- Re: Should the RFC Editor publish an RFC in less … Hallam-Baker, Phillip
- Re: Should the RFC Editor publish an RFC in less … Robert Elz
- OOXML (was Re: Should the RFC Editor...) Norbert Bollow
- Re: Should the RFC Editor publish an RFC in less … Norbert Bollow
- Re: Should the RFC Editor publish an RFC in less … Tom.Petch
- Re: Should the RFC Editor publish an RFC in less … Daniel Brown
- Re: Should the RFC Editor publish an RFC in less … Brian E Carpenter
- Re: Should the RFC Editor publish an RFC in less … Harald Tveit Alvestrand
- Re: Should the RFC Editor publish an RFC in less … Scott O. Bradner
- Re: Should the RFC Editor publish an RFC in less … Robert Elz
- RE: Should the RFC Editor publish an RFC in less … Tobias Gondrom
- Re: Should the RFC Editor publish an RFC in less … Frank Ellermann
- Re: Should the RFC Editor publish an RFC in less … Henrik Levkowetz
- Re: Should the RFC Editor publish an RFC in less … Loa Andersson
- Re: Should the RFC Editor publish an RFC in less … JP Vasseur
- Re: Should the RFC Editor publish an RFC in less … Russ Housley