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

Cullen Jennings <fluffy@cisco.com> Wed, 28 November 2007 22:14 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 1IxVB8-0005JW-JT; Wed, 28 Nov 2007 17:14:46 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IxVB6-0005Hm-59; Wed, 28 Nov 2007 17:14:44 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IxVB5-0006Z8-Pc; Wed, 28 Nov 2007 17:14:44 -0500
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-3.cisco.com with ESMTP; 28 Nov 2007 14:14:43 -0800
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id lASMEhw6014683; Wed, 28 Nov 2007 14:14:43 -0800
Received: from [128.107.139.94] (dhcp-128-107-139-94.cisco.com [128.107.139.94]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id lASMEh1f009673; Wed, 28 Nov 2007 22:14:43 GMT
In-Reply-To: <E1IxV26-0006Ne-TG@megatron.ietf.org>
References: <E1IxTPt-0006r4-ST@ietf.org> <474DD597.9040208@gmail.com><CC3C6CC7EE08DA90C239082B@p3.JCK.COM> <E1IxV26-0006Ne-TG@megatron.ietf.org>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <40F79287-713F-4167-8DC3-0DA35D565D54@cisco.com>
Content-Transfer-Encoding: 7bit
From: Cullen Jennings <fluffy@cisco.com>
Date: Wed, 28 Nov 2007 14:14:37 -0800
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.752.3)
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1099; t=1196288083; x=1197152083; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fluffy@cisco.com; z=From:=20Cullen=20Jennings=20<fluffy@cisco.com> |Subject:=20Re=3A=20Should=20the=20RFC=20Editor=20publish=20an=20RFC=20in =20less=20than=202=20months? |Sender:=20; bh=Ziba0VEk2TINOhGJZxVmQw1saz09PPzmvoZv4HDbAME=; b=Jn9TijNYDO8D6NncPddDYeU0DN6f1F/lKzD+6nqgca+0EtIPYibTweLyXaDC1LNmmf3/Dwf/ Mfy3j/Fzei6ePVRyDLt44NaWlaKZnQq/PBpMYzvkK0JlI1F9CiT/ypjZ;
Authentication-Results: sj-dkim-3; header.From=fluffy@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
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

What happens if the appeal is claiming that changes made in Auth 48  
should have been reviewed by the working group and go against WG  
consensus? Given some of the changes I have seen between IESG  
approval and published RFC, this seems like a reasonable plausible  
scenario.


On Nov 28, 2007, at 2:05 PM, Russ Housley wrote:

> John:
>
> RFC 2026 gives two months to appeal any decision.  IESG approval of a
> document publication is one such decision.  RFC 2026, section 6.5.4  
> says:
>
>     All appeals must be initiated within two months of the public
>     knowledge of the action or decision to be challenged.
>
> So, the two month timer begins when the approval announcement is sent.
>
> Russ
>
> At 04:02 PM 11/28/2007, John C Klensin wrote:
> >I don't see any possible reason why we need to give
> >people two months to get an appeal filed: a month or, at most,
> >six weeks ought to be more than sufficient.
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>

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