IETF Logo Mail Archive

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

Bob Hinden <bob.hinden@nokia.com> Fri, 30 November 2007 19:57 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 1IyBzP-0004oL-0z; Fri, 30 Nov 2007 14:57:31 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IyBzM-0004mr-D3; Fri, 30 Nov 2007 14:57:28 -0500
Received: from smtp.nokia.com ([192.100.105.134] helo=mgw-mx09.nokia.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IyBzM-0002Wp-3U; Fri, 30 Nov 2007 14:57:28 -0500
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id lAUJuqer004648; Fri, 30 Nov 2007 13:57:28 -0600
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 30 Nov 2007 21:57:11 +0200
Received: from mgw-int02.ntc.nokia.com ([172.21.143.97]) by esebh103.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Fri, 30 Nov 2007 21:57:11 +0200
Received: from [172.19.74.206] (dadhcp-172019074206.americas.nokia.com [172.19.74.206]) by mgw-int02.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id lAUJv8QK012121; Fri, 30 Nov 2007 21:57:08 +0200
In-Reply-To: <475063D9.9040806@gmail.com>
References: <E1IxTPt-0006r4-ST@ietf.org> <474E61A4.2000201@alvestrand.no> <010901c83339$b56e0d20$0601a8c0@pc6> <474FF7E2.7060107@alvestrand.no> <475063D9.9040806@gmail.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <A1AE0FF2-B0F7-4D50-862B-23DE5819F788@nokia.com>
Content-Transfer-Encoding: 7bit
From: Bob Hinden <bob.hinden@nokia.com>
Date: Fri, 30 Nov 2007 11:57:19 -0800
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 30 Nov 2007 19:57:11.0596 (UTC) FILETIME=[323676C0:01C8338B]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: Harald Alvestrand <harald@alvestrand.no>, 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
Reply-To: bob.hinden@nokia.com
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

> 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.

I agree.  I don't think there should be any additional delay in RFC  
publication.  It takes long enough as is.

Unless we hold them up till any possible patent expires (e.g., 17+  
years).....

Bob


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

v2.23.0 | Report a Bug | By Email