The IETF environment (was: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists)

ned+ietf@mauve.mrochek.com Fri, 25 April 2014 15:14 UTC

Return-Path: <ned+ietf@mauve.mrochek.com>
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 8CEAB1A02A6 for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 08:14:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.174
X-Spam-Level:
X-Spam-Status: No, score=-2.174 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 lKVQAHM3NtJi for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 08:14:19 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id AF3671A0300 for <ietf@ietf.org>; Fri, 25 Apr 2014 08:14:19 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P721I1GFRK00091L@mauve.mrochek.com> for ietf@ietf.org; Fri, 25 Apr 2014 08:09:09 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1; format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P714CWLY4W000052@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Fri, 25 Apr 2014 08:09:00 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P721HY5XZO000052@mauve.mrochek.com>
Date: Fri, 25 Apr 2014 07:56:54 -0700 (PDT)
Subject: The IETF environment (was: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists)
In-reply-to: "Your message dated Thu, 24 Apr 2014 20:23:47 -0700" <5359D543.5070900@dcrocker.net>
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>
To: Dave Crocker <dhc@dcrocker.net>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/5YgEOLzL1lTBf02zJO3pUO5lkO8
Cc: ned+ietf@mauve.mrochek.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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:14:21 -0000

I'm done with the original thread on this topic, but there's a bit here that
warrants a separate response.

> On 4/24/2014 7:45 PM, ned+ietf@mauve.mrochek.com wrote:
> >> It's incredibly obvious that the IETF either didn't listen to, or
> >> didn't act on clear messages from the operator community on this
> >> topic.
> >
> > Well, here I sort of agree. What the IETF didn't do is react to the
> > danger this posed in a timely way. Either on a technical or political
> > level.

> The fundamental flaw in this sort of view is that the IETF initiates
> organization efforts. Or that it acts on "messages".  It doesn't.  It
> provides an environment for workers from the community to organize open
> standards efforts.

You may want to argue that's how the IETF should work, but I'm afraid I don't
see it matching up with how it actually works.

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.

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.

Now, I suppose you could characterize both of these as "people  coming together
to work on stuff", with the IETF just providing the environment. But it seems
pretty clear that people regard the IETF as a bit more than that. Maybe they
shouldn't, but they do.

				Ned