Re: Last call IETF experiments

Frank Ellermann <nobody@xyzzy.claranet.de> Tue, 13 December 2005 05:42 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Em2vJ-0005H5-Tv; Tue, 13 Dec 2005 00:42:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Em2vG-0005H0-Tv for ietf@megatron.ietf.org; Tue, 13 Dec 2005 00:41:59 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA01665 for <ietf@ietf.org>; Tue, 13 Dec 2005 00:40:58 -0500 (EST)
Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Em2w6-00014G-KF for ietf@ietf.org; Tue, 13 Dec 2005 00:42:55 -0500
Received: from root by ciao.gmane.org with local (Exim 4.43) id 1Em2uP-0004NH-IU for ietf@ietf.org; Tue, 13 Dec 2005 06:41:05 +0100
Received: from 1cust12.tnt8.hbg2.deu.da.uu.net ([149.225.138.12]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Tue, 13 Dec 2005 06:41:05 +0100
Received: from nobody by 1cust12.tnt8.hbg2.deu.da.uu.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Tue, 13 Dec 2005 06:41:05 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: ietf@ietf.org
From: Frank Ellermann <nobody@xyzzy.claranet.de>
Date: Tue, 13 Dec 2005 06:32:30 +0100
Organization: <URL:http://purl.net/xyzzy>
Lines: 31
Message-ID: <439E5CEE.5BAC@xyzzy.claranet.de>
References: <200512092141.NAA00720@gra.isi.edu> <439A0C1F.2FEC@xyzzy.claranet.de> <tsl4q5ghlsj.fsf@cz.mit.edu> <439CAF6D.1ECE@xyzzy.claranet.de> <B7AF3AAE9035805E5B963411@scan.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: 1cust12.tnt8.hbg2.deu.da.uu.net
X-Mailer: Mozilla 3.0 (OS/2; U)
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit
Cc: spf-discuss@v2.listbox.com
Subject: Re: Last call IETF experiments
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>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

John C Klensin wrote:

> 2026 basically discusses the cases where Last Calls are
> required, as one would expect.   But, by long-standing
> precedent and good sense, the IESG is permitted to Last
> Call anything they like on which they might need to make
> a decision in order to get a better sense of the consensus
> or preferences of the community.

Makes sense...

> Certainly one would not want to argue against that.

...based on the "old" informational RFC 3710 rules I could:

In chapter 5.2.2 it says "processed in the same fashion as
an Informational or Experimental document from a working
group", in other words an IETF Last Call (RFC 2026 4.2.3).

But as it happens I've already dismissed RFC 3710 as broken
beyond repair after an overdose of its chapter 4.3 in MARID.

> one would have a lot of trouble appealing a decision on the
> grounds that the relevant AD didn't ask for a Last Call
> first.  But that doesn't seem to be at issue here.

Yes, RFC 3710 is only informational, they are not forced to
follow their own published internal rules.

                           Bye, Frank



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