Re: Should the RFC Editor publish an RFC in less than 2 months?
Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 30 November 2007 19:26 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 1IyBVM-0000S8-DI; Fri, 30 Nov 2007 14:26:28 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IyBVK-0000Rf-PV for ietf@ietf.org; Fri, 30 Nov 2007 14:26:26 -0500
Received: from rv-out-0910.google.com ([209.85.198.187]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IyBVK-0004sY-2W for ietf@ietf.org; Fri, 30 Nov 2007 14:26:26 -0500
Received: by rv-out-0910.google.com with SMTP id l15so1891351rvb for <ietf@ietf.org>; Fri, 30 Nov 2007 11:26:25 -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=s1PRaiEirMYmh8OnvBSEgopSDfaF1qzDH1j2t9bmI9c=; b=dRmCWuOcMYR/3knIaoyXILWFPxdPG8QJvtdwAm4DseJf/eW2pphxb9h9T4epnqyR32ATsPJzEe12sTLfkBLr4lOCbW2g9UCHJAZK8gCTg7sODdW4wudJSVpA5yyUsklN0N3robuk0sdV2NqFNLx7LhwgmucwMPI2E50b9FdcPzI=
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=qYizWwOleDTijPiW54ZoM6hYM8lf5dkLCXszoMqyqhptwPrD50wmIC2bTxm0bvBjlbZGOtBaUybGuN677tNeQbmg/DZaniWt14dQdNSeFQNdkmgpSgX9qfQc5DbqtbRsuahLELVvyJvT4nqKhtgsPDTiEM7U4sVbWcHLvD7Akg8=
Received: by 10.140.207.2 with SMTP id e2mr4229507rvg.1196450785375; Fri, 30 Nov 2007 11:26:25 -0800 (PST)
Received: from ?10.1.1.5? ( [203.173.152.165]) by mx.google.com with ESMTPS id g22sm12212478rvb.2007.11.30.11.26.22 (version=SSLv3 cipher=RC4-MD5); Fri, 30 Nov 2007 11:26:25 -0800 (PST)
Message-ID: <475063D9.9040806@gmail.com>
Date: Sat, 01 Dec 2007 08:26:17 +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: Harald Alvestrand <harald@alvestrand.no>
References: <E1IxTPt-0006r4-ST@ietf.org> <474E61A4.2000201@alvestrand.no> <010901c83339$b56e0d20$0601a8c0@pc6> <474FF7E2.7060107@alvestrand.no>
In-Reply-To: <474FF7E2.7060107@alvestrand.no>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: iab@ietf.org, ietf <ietf@ietf.org>, iesg <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-01 00:45, Harald Alvestrand wrote: > Tom.Petch wrote: >> I recall a recent occasion when the IESG withdrew its approval, for >> draft-housley-tls-authz-extns >> a document that both before and after its approval generated a lot of >> heat, >> within and without a WG. >> >> Presumably the expedited process would, or at least could, have seen that >> published as an RFC. >> >> With that example in mind, a 60 day hold seems rather a good idea. >> > In that case, it went into the RFC Editor queue on June 30,, 2006, and > was yanked from the queue on February 26, 2007 - 8 months later. > > According to the "third last call" announcement: > > On June 27, 2006, the IESG approved "Transport Layer Security (TLS) > Authorization Extensions," (draft-housley-tls-authz-extns) as a > proposed standard. On November 29, 2006, Redphone Security (with whom > Mark Brown, a co-author of the draft is affiliated) filed IETF IPR > disclosure 767. > > it was five months between approval and the IPR disclosure. > > A two-month hold wouldn't have caught it. > (No idea why it was still hanging there long enough for the IPR > disclosure to catch up with it...) In any case, I would much rather have seen that published and later declared Historic than hold up all other RFCs. It isn't as if the IETF can control what actually gets implemented and deployed in any case - so why on earth does it *matter*? Whereas getting the vast majority of RFCs published promptly *does* matter. 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