Re: [e2md] Dean's Proxy-Shill Version of the Problem statement

Dean Willis <dean.willis@softarmor.com> Fri, 14 May 2010 16:09 UTC

Return-Path: <dean.willis@softarmor.com>
X-Original-To: e2md@core3.amsl.com
Delivered-To: e2md@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6FFCF3A6B4E for <e2md@core3.amsl.com>; Fri, 14 May 2010 09:09:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.678
X-Spam-Level:
X-Spam-Status: No, score=-0.678 tagged_above=-999 required=5 tests=[AWL=-0.679, BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UntQAcqR7oXd for <e2md@core3.amsl.com>; Fri, 14 May 2010 09:09:49 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164]) by core3.amsl.com (Postfix) with ESMTP id 73CBC3A6B5D for <e2md@ietf.org>; Fri, 14 May 2010 09:09:49 -0700 (PDT)
Received: from [192.168.2.109] (cpe-66-25-30-183.tx.res.rr.com [66.25.30.183]) (authenticated bits=0) by nylon.softarmor.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id o4EG9ckB028765 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 14 May 2010 11:09:40 -0500
Message-ID: <4BED75BA.1010508@softarmor.com>
Date: Fri, 14 May 2010 11:09:30 -0500
From: Dean Willis <dean.willis@softarmor.com>
User-Agent: Mozilla Thunderbird 1.0.5 (Windows/20050711)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jim Reid <jim@rfc1035.com>
References: <C8121E93.5688%ray.bellis@nominet.org.uk> <4BEC7C1A.7050306@softarmor.com> <280CDB63-BC7F-413D-BD38-440CA42E134E@rfc1035.com>
In-Reply-To: <280CDB63-BC7F-413D-BD38-440CA42E134E@rfc1035.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "E.164 To MetaData BOF discussion list" <e2md@ietf.org>
Subject: Re: [e2md] Dean's Proxy-Shill Version of the Problem statement
X-BeenThere: e2md@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "E.164 To MetaData \(E2MD\) BOF discussion list" <e2md.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/e2md>, <mailto:e2md-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/e2md>
List-Post: <mailto:e2md@ietf.org>
List-Help: <mailto:e2md-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/e2md>, <mailto:e2md-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 May 2010 16:09:50 -0000

Jim Reid wrote:
> On 13 May 2010, at 23:24, Dean Willis wrote:
> 
>> Practically speaking, they don't need to come here and we can't expect
>> them to.
> 
> 
> EH? Let me see if I've got this right. Some anonymous greybeards (who  
> may or may not exist) don't/won't participate in the discussion or  
> provide a clear indication of their concerns and requirements. But  they 
> get an absolute veto whatever bottom-up consensus the rest of us  agree. 
> Is this how the IETF works these days?
> 

Yep. That's pretty much the BOF process in a nutshell.

The BOF makes areguments "for". The opposition makes arguments -- 
usually "against", but there can be more than one faction. The I* weighs 
the arguments. The decision is "rough consensus".

Note that resources meeting rooms, meeting slots, IESG attention, RFC 
editor, etc. are all scarce. This biases the process towards rejecting 
new work, especially if that work is controversial.

They have no responsibility to let us form a working group just because 
we want to. We have to be able to form a consensus in the greater 
community that the work is doable, benefits the Internet, has a 
community of interest that will deploy IN THE INTERNET, and that we have 
the right people committed to doing the work in the IETF. Lacking such 
consensus, the default answer is "No."

--
Dean