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

Russ Housley <housley@vigilsec.com> Sun, 02 December 2007 01: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 1Iye59-0002sv-Q4; Sat, 01 Dec 2007 20:57:19 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iye59-0002so-0L for ietf@ietf.org; Sat, 01 Dec 2007 20:57:19 -0500
Received: from woodstock.binhost.com ([8.8.40.152]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Iye58-0000BT-Mr for ietf@ietf.org; Sat, 01 Dec 2007 20:57:18 -0500
Received: (qmail 29500 invoked by uid 0); 2 Dec 2007 01:50:29 -0000
Received: from unknown (HELO THINKPADR52.vigilsec.com) (130.129.17.218) by woodstock.binhost.com with SMTP; 2 Dec 2007 01:50:29 -0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Sat, 01 Dec 2007 20:48:55 -0500
To: Alexey Melnikov <alexey.melnikov@isode.com>, ietf@ietf.org
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4751F44D.3050207@isode.com>
References: <E1IxTPt-0006r4-ST@ietf.org> <4751F44D.3050207@isode.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: iab@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
Message-Id: <E1Iye59-0002sv-Q4@megatron.ietf.org>

Alexey:

The latter.  If the Auth48 completes before the 60 day appeal timer 
has expired, then the RFC Editor will hold off on publication until 
the 60 days have gone by.

Russ

P.S. A document that I wrote was the first document to get snagged in 
this situation.  I guess it is only fair....  It got published yesterday.


At 06:54 PM 12/1/2007, Alexey Melnikov wrote:
>Russ,
>
>IETF Chair wrote:
>
>>While we figure out what policy we want, I have asked the RFC Editor to
>>not publish any IESG approved documents until their appeal timer has
>>expired.  I also challenged the RFC Editor to move things along so fast
>>that this matters.  I suspect they can.  Which means that the whole IETF
>>community needs to help the leadership figure out the appropriate policy
>>before the rapid processing of Internet-Draft documents into RFCs becomes
>>the norm.
>>
>I would like to ask a clarifying question: does this mean that RFC 
>editors are not going to start editing the document until after 2 
>months since approval of a document, or does it mean that RFC 
>editors start editing right away, can issue AUTH48 request, but will 
>delay publication until after 2 months?
>
>I think the latter is better, because (a) appeals are not that 
>frequent and (b) AUTH48 usually takes way longer than 2 days ;-).
>
>Regards,
>Alexey
>
>P.S. I apologize in advance for asking the question before reading 
>the whole thread. Maybe it was already asked.
>
>
>


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