IETF Logo Mail Archive

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

Sam Hartman <hartmans-ietf@mit.edu> Thu, 29 November 2007 16:09 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 1Ixlx1-0003E9-5i; Thu, 29 Nov 2007 11:09:19 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ixlwy-00037S-4u; Thu, 29 Nov 2007 11:09:16 -0500
Received: from carter-zimmerman.suchdamage.org ([69.25.196.178]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ixlwx-0007S1-SS; Thu, 29 Nov 2007 11:09:16 -0500
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 094754815; Thu, 29 Nov 2007 11:09:12 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Paul Hoffman <paul.hoffman@vpnc.org>
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> <p06240838c37490dfe8b5@[10.20.30.108]>
Date: Thu, 29 Nov 2007 11:09:12 -0500
In-Reply-To: <p06240838c37490dfe8b5@[10.20.30.108]> (Paul Hoffman's message of "Thu, 29 Nov 2007 07:57:11 -0800")
Message-ID: <tslwss15907.fsf@mit.edu>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: IAB <iab@ietf.org>, Jari Arkko <jari.arkko@piuha.net>, 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

>>>>> "Paul" == Paul Hoffman <paul.hoffman@vpnc.org> writes:

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

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

I'd assume that you want to do both.  Remember that obseleting a
document does not imply it goes to historic.  I've never fully agreed
with that bit of rfc-editor-process trivia.


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

v2.23.0 | Report a Bug | By Email