Re: Appeals, post-appeal discussions, DoS attacks on the IETF, and the depth of turtles

Frank Ellermann <nobody@xyzzy.claranet.de> Mon, 24 July 2006 08:28 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G4vnF-0000si-FH; Mon, 24 Jul 2006 04:28:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G4vnD-0000j5-B9 for ietf@ietf.org; Mon, 24 Jul 2006 04:27:59 -0400
Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G4vnC-0002C6-0Z for ietf@ietf.org; Mon, 24 Jul 2006 04:27:59 -0400
Received: from list by ciao.gmane.org with local (Exim 4.43) id 1G4vn3-0001at-RU for ietf@ietf.org; Mon, 24 Jul 2006 10:27:49 +0200
Received: from pd9fba92d.dip0.t-ipconnect.de ([217.251.169.45]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Mon, 24 Jul 2006 10:27:49 +0200
Received: from nobody by pd9fba92d.dip0.t-ipconnect.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Mon, 24 Jul 2006 10:27:49 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: ietf@ietf.org
From: Frank Ellermann <nobody@xyzzy.claranet.de>
Date: Mon, 24 Jul 2006 10:26:24 +0200
Organization: <URL:http://purl.net/xyzzy>
Lines: 39
Message-ID: <44C48430.5485@xyzzy.claranet.de>
References: <CB6B4943D1AFDB6F2BF7D4C2@p3.JCK.COM> <44C4557C.372@xyzzy.claranet.de> <93C005091860A559C9DF2DC3@p3.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: pd9fba92d.dip0.t-ipconnect.de
X-Mailer: Mozilla 3.0 (OS/2; U)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Subject: Re: Appeals, post-appeal discussions, DoS attacks on the IETF, and the depth of turtles
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

John C Klensin wrote:

 [DRP excl. last calls]
> in general, if an AD, or the IESG, as a whole, is asked to
> issue a Last Call and declines to do so, that decision
> should be subject to appeal.   And, if the IESG wants to see
> that "in general" narrowed --as I think it should be-- then
> they should be generating, or convincing someone else to
> generate-- a clear statement about the conditions under which
> Last Calls will and will not be issued and get community
> consensus behind that statement.

Yes, they need something against bogus (or malicious) last call
requests.  That something would have the same DoS protection as
the proposed 'dispute resolution process'.

 [active participants for the recall procedure]
> it is hard to identify them in a clear way
 [...]
> IAB and IESG members were excluded as an unintended side-
> effect.

Maybe - if you intend to revive that draft -  you could add all
(co-) authors of "n" or more standards track documents, for an
"n" covering all past and present IAB and IESG members.

 [duel draft]
> the Nomcom Chair could wait a week before doing anything,
> then ask the Chair if he or she was still serious and notify
> the relevant IESG member to see if any other action was
> likely to be forthcoming before presenting the question to
> the Nomcom.  Is that what you had in mind?

Yes, maybe as explicit right.  If the IETF or IESG Chair added
Cc: ietf@ietf.org or similar it's hopeless, no further delay,
they have to shoot it out.

Frank



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