Re: [Ianaplan] Process concern regarding the IETF proposal development process

Andrew Sullivan <ajs@anvilwalrusden.com> Mon, 19 January 2015 16:02 UTC

Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ianaplan@ietfa.amsl.com
Delivered-To: ianaplan@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FF411B2ACA for <ianaplan@ietfa.amsl.com>; Mon, 19 Jan 2015 08:02:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.559
X-Spam-Level: **
X-Spam-Status: No, score=2.559 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BbPPwfBh17CO for <ianaplan@ietfa.amsl.com>; Mon, 19 Jan 2015 08:02:00 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9104E1B2ACD for <ianaplan@ietf.org>; Mon, 19 Jan 2015 08:02:00 -0800 (PST)
Received: from mx1.yitter.info (nat-08-mht.dyndns.com [216.146.45.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 647A48A031 for <ianaplan@ietf.org>; Mon, 19 Jan 2015 16:01:59 +0000 (UTC)
Date: Mon, 19 Jan 2015 11:01:55 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ianaplan@ietf.org
Message-ID: <20150119160154.GA73402@mx1.yitter.info>
References: <C172BBB7-9BA4-4BA7-848C-C7FE5B66CBF7@cooperw.in>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <C172BBB7-9BA4-4BA7-848C-C7FE5B66CBF7@cooperw.in>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/Mt1bfDyhuFxZ6U29xSNbn8eB0BE>
Subject: Re: [Ianaplan] Process concern regarding the IETF proposal development process
X-BeenThere: ianaplan@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IANA Plan <ianaplan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ianaplan/>
List-Post: <mailto:ianaplan@ietf.org>
List-Help: <mailto:ianaplan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Jan 2015 16:02:06 -0000

I am speaking only for myself in this message (as usual).

On Mon, Jan 19, 2015 at 06:33:23AM -0800, Alissa Cooper wrote:
> After draft-ietf-ianaplan-icg-response was submitted to the ICG, the ICG received the following comment: http://forum.icann.org/lists/icg-forum/msg00017.html

I think Richard Hill's argument in that message contains a number of
faulty premises.  I disagree with most of the message.

To begin with, he supposes that there is a hard line between "bottom
up" and "the leadership".  This represents a misunderstanding of how
the IETF works.  We expect the so-called leadership to participate.
(I say "so called", because anyone who has worked in the IETF for any
length of time knows that the IETF leadership relies on the respect of
its IETF peers: an IESG member who does not command professional
respect will quickly find him or herself isolated and unable to
function.)  In the case of the IESG members (all the examples are of
one particular IESG member), we expect them not to abuse their
position of control, or even threaten to do that.  I see no hint of
any such threat in any of the example posts.  It's true that the
example messages are a little sharp.  That is a style of debate we
sometimes see in the IETF.

I disagree that with Richard's claim that the chairs did not justify
their view.  I think they did, at least in the ways that I would
expect in the IETF.  It could be that this is a cultural understanding
of people who have participated in the IETF for some time and that is
not widely shared among the rest of the human population.  But it
appears to me that the chairs referred to both the outcome of the
meeting in Honolulu and the messages to the list to justify their
conclusions of rough consensus.  I had to pay attention to their
decision as part of my duties as the WG document shepherd, and
certainly I was not confused about what they were saying or why they
said it.

I believe that I understand what Richard is saying in his paragraph
beginning, "In my view, as I tried…," and as nearly as I can tell the
WG simply disagreed with him.  That is sometimes what happens with
rough consensus.  I think Richard is "in the rough."  I am not a person
who makes that determination for the WG or the IETF, but I agree with
that determination on the part of the chairs and the responsible AD.

Finally, if Richard believes that there was a process irregularity
(and he seems to be arguing that), then he is quite mistaken that he
cannot appeal the decision.  That would indeed be grounds for appeal.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com