IETF Logo Mail Archive

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

Paul Hoffman <paul.hoffman@vpnc.org> Thu, 29 November 2007 15: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 1Ixllh-0004xL-Ll; Thu, 29 Nov 2007 10:57:37 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ixlle-0004no-RB; Thu, 29 Nov 2007 10:57:34 -0500
Received: from balder-227.proper.com ([192.245.12.227]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Ixlle-0004Pl-GT; Thu, 29 Nov 2007 10:57:34 -0500
Received: from [10.20.30.108] (dsl-63-249-108-169.cruzio.com [63.249.108.169]) (authenticated bits=0) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id lATFvVev049120 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 29 Nov 2007 08:57:32 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240838c37490dfe8b5@[10.20.30.108]>
In-Reply-To: <474EBF98.4000509@piuha.net>
References: <E1IxTPt-0006r4-ST@ietf.org> <474DD597.9040208@gmail.com><CC3C6CC7EE08DA90C239082B@p3.JCK.COM> <E1IxV26-0006Ne-TG@megatron.ietf.org> <40F79287-713F-4167-8DC3-0DA35D565D54@cisco.com> <23E55AFB-7AE6-4142-9ACC-0C2969B5D1DF@nist.gov> <474EAEAB.9070702@dcrocker.net> <474EBF98.4000509@piuha.net>
Date: Thu, 29 Nov 2007 07:57:11 -0800
To: Jari Arkko <jari.arkko@piuha.net>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Cc: IAB <iab@ietf.org>, ietf@ietf.org, IESG 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

At 3:33 PM +0200 11/29/07, Jari Arkko wrote:
>And we
>can move a document to historic,

Note that there are two different "no process change needed" 
proposals on the table: obsoleting with NULL (or a bit of 
explanation) and moving to Historic. Obsoleting a document is much 
easier for the outside world to understand than changing its status 
to Historic, given that we have many different reasons for Historic.

--Paul Hoffman, Director
--VPN Consortium

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

v2.23.0 | Report a Bug | By Email