Re: Appointment of a Transport Area Director

Dave Crocker <dhc@dcrocker.net> Mon, 04 March 2013 16:40 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12ECD21F8CD7 for <ietf@ietfa.amsl.com>; Mon, 4 Mar 2013 08:40:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JmFb+3HR7vYO for <ietf@ietfa.amsl.com>; Mon, 4 Mar 2013 08:40:23 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id F358B21F8CD4 for <ietf@ietf.org>; Mon, 4 Mar 2013 08:40:22 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r24GeL0Q017773 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 4 Mar 2013 08:40:22 -0800
Message-ID: <5134CE73.7060801@dcrocker.net>
Date: Mon, 04 Mar 2013 08:40:19 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Appointment of a Transport Area Director
References: <21B86E13-B8DA-4119-BBB1-B5EE6D2B5C1D@ietf.org> <51330179.3040500@gmail.com> <919840EE-BEC8-4F82-8D3C-B116698A4262@gmx.net> <1D88E6E9-33DE-4C4D-89F4-B0B762155D6F@standardstrack.com> <D4D47BCFFE5A004F95D707546AC0D7E91F77BA46@SACEXCMBX01-PRD.hq.netapp.com> <3CB8992B-212A-4776-95FE-71CA1E382FFF@standardstrack.com> <513376DB.7000200@dcrocker.net> <E22ACC99-B465-4769-8B59-BB98A7BA93DF@gmx.net> <79E77523-3D92-4CE9-8689-483D416794EF@standardstrack.com> <D4D47BCFFE5A004F95D707546AC0D7E91F780D2F@SACEXCMBX01-PRD.hq.netapp.com> <071C6ED7-352C-4E74-A483-F5E7A3270FA5@gmail.com> <C726E531-57DC-4C42-9053-1394983126D6@vigilsec.com>
In-Reply-To: <C726E531-57DC-4C42-9053-1394983126D6@vigilsec.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 04 Mar 2013 08:40:22 -0800 (PST)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Mar 2013 16:40:27 -0000

On 3/4/2013 7:26 AM, Russ Housley wrote:
> The leadership in the ITU does not read the documents.  Why?  Their job is to make sure that the process was followed.
>
> The IESG needs to make sure the process was followed too.  But, the IESG also has a quality check job.  I would hate for this debate to lead to a step toward the ITU model.


As specious lines of logic go, your note was pretty efficient.  It 
ignored the specifics of the concerns being raised in this thread, their 
merits, and the suggestions being made, and it invokes a cliche'd 
bogeyman.

For example, the suggestions being made do not intent or imply that 
there would be no technical content to the work of an AD. Also note that 
there are many things that the ITU does; are we supposed to make a point 
of not doing any of them, simply because the ITU does them?

The IETF culture, structure and process are massively different from the 
ITU's.  None of the changes being proposed would turn the IETF into the 
ITU or even move us towards them.

If the merit of a suggestion is good or bad, let's focus on that, rather 
than on who else is or is not doing it.

But if you really want to focus on ITU fear, take a look at the time it 
now takes to produce IETF specs, their increased complexity and the 
degree of their eventual industry deployment.  A comparison on the style 
and substance of IETF vs. ITU technical work might prove enlightening...

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net