Re: The IETF environment

Dave Crocker <dhc@dcrocker.net> Fri, 25 April 2014 15:24 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C2681A050E for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 08:24:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 Qiw38h6n6qRT for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 08:24:08 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 598FD1A0345 for <ietf@ietf.org>; Fri, 25 Apr 2014 08:24:08 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3PFNvWp004240 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 25 Apr 2014 08:24:01 -0700
Message-ID: <535A7D87.6080200@dcrocker.net>
Date: Fri, 25 Apr 2014 08:21:43 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Ned Freed <ned.freed@mrochek.com>
Subject: Re: The IETF environment
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5356F23F.40909@dougbarton.us> <01P71CGX4VD8000052@mauve.mrochek.com> <5359D543.5070900@dcrocker.net> <01P721HY5XZO000052@mauve.mrochek.com>
In-Reply-To: <01P721HY5XZO000052@mauve.mrochek.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.66]); Fri, 25 Apr 2014 08:24:01 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/xk72xDH3_TVxRAlV8UAozSiVkyM
Cc: ned+ietf@mauve.mrochek.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 25 Apr 2014 15:24:12 -0000

On 4/25/2014 7:56 AM, Ned Freed wrote:
> An obvious counterexample is what recently happened in perpass and
> the various works it has started. Regardless of what anyone thinks of
> perpass or its outcome, a fair characterization is that it was an
> IETF repsonse to the message delivered by Snoden et al.

Yup.  It's a singular example, but that's the point.  It's not what the 
IETF (usually) does.

It's fine that it's being attempted and it might (or might not) prove 
useful.  But there is no pattern of the IETF doing such a thing.

My point was not meant as a statement of philosophy or criticism of the 
IETF, but a description of the long-term operational model that covers 
its actual history.

That model is for initiatives to come from the grass roots of the 
community, seeking facilitation within the IETF.  These do not depend 
upon strategic management directions being set.


> And maybe something has changed since the four years I spent going to
> IESG retreats, but I recall lots of discussion of how the IETF as an
>  organization should respond to various industry trends.

Yes, we often have such discussions.  My observation is that it has 
typically had little or no effect on what work is actually done, absent 
initiative from the community.

With respect to getting work done, this is a bottom-up organization, not 
a top-down one.  (That's why I think Area "Director" is a serious 
misnomer and Area "Facilitator" would be far more accurate.)


>  But it seems pretty clear that people regard the IETF as
> a bit more than that. Maybe they shouldn't, but they do.

Yes, there is quite a bit of mythology about the IETF.  Sometimes it 
borders on mysticism...

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net