Re: Should the RFC Editor publish an RFC in less than 2 months?
Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 04 December 2007 02:03 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 1IzN8h-0006zu-J3; Mon, 03 Dec 2007 21:03:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IzN8g-0006ql-6Q for ietf@ietf.org; Mon, 03 Dec 2007 21:03:58 -0500
Received: from ro-out-1112.google.com ([72.14.202.177]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IzN8f-00060y-NZ for ietf@ietf.org; Mon, 03 Dec 2007 21:03:58 -0500
Received: by ro-out-1112.google.com with SMTP id k4so5330247rog for <ietf@ietf.org>; Mon, 03 Dec 2007 18:03:57 -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=5DlojlYC7KfEguWfAp12X516p/HdzHa1joagmTWkzPo=; b=CaFasL4a0vi10POsXFFikQd+rUBHnRgA4IG+BgCoqeIiUvQ597LWHn1QbqAYxyGq2aozg/GqIwBFmk/9CnXyCfZJRNHjIe5QLtRbp87AJnZcvVB3OMlcXPTJVQeY5qYjxH1n6WdU98Lsha8UT2NuJ77VKFOUCrJUruLIU+MIZlM=
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=j5FXh296GFWR8GZSC3CwywdO4Mlla/3SY+UTc+HD4XOHj2v/xQd8YyjxQUR5E4qhVjDAR7bSlU6UpCjCff61CcLKXe053XiFTOCOXbV+g/S0ACUjo99l2W0PKeviFH3WBWJiihr7rlf1WWFh2UwjI7yUTiujwyMoUJ3IgMoqQtk=
Received: by 10.114.195.19 with SMTP id s19mr97898waf.1196733836412; Mon, 03 Dec 2007 18:03:56 -0800 (PST)
Received: from ?10.1.130.54? ( [203.98.10.198]) by mx.google.com with ESMTPS id j28sm1862214waf.2007.12.03.18.03.53 (version=SSLv3 cipher=RC4-MD5); Mon, 03 Dec 2007 18:03:55 -0800 (PST)
Message-ID: <47546156.3070304@gmail.com>
Date: Tue, 04 Dec 2007 09:04:38 +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: Robert Elz <kre@munnari.OZ.AU>
References: <2788466ED3E31C418E9ACC5C316615570462D9@mou1wnexmb09.vcorp.ad.vrsn.com> <24721.1196675381@munnari.OZ.AU>
In-Reply-To: <24721.1196675381@munnari.OZ.AU>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 1.4 (+)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: iab@ietf.org, ietf@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-12-03 22:49, Robert Elz wrote: ... > Everyone (almost everyone) seems to be assuming that getting the RFC > published as quickly as possible is the aim. Why? What does actual > appearance of the file in the directories really change? It's the instant of formal publication, and that changes at least two things: 1. It allows other SDOs that require a normative citation to proceed with *their* publication process, in order to meet their own deadlines. This has been a much more frequent situation than appeals in recent years (with ITU-T and 3GPP being the SDOs mainly concerned, iirc). 2. It triggers action by product developers and writers of RFPs, especially those not actively involved in the IETF. The RFC name is powerful enough that there really is an impact - people *do* wait until the RFC comes out, or hear about things for the first time then. > Sure, it makes > access a little easier, but that's it (and I guess that now, we could have > a temporary placeholder installed, a file called rfcNNNN.2b or something, > containing the URL of the I-D that will become the RFC when the editing > process is finished - I personally doubt it is necessary, but it could be > done). The RFC Editor hates to reveal RFC numbers until publication is a certainty. There is an unofficial list of approved but not published drafts, however, at http://rtg.ietf.org:8080/Test/parking (assuming it still works - I'm off line and can't check). 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