Re: The IETF environment

Miles Fidelman <mfidelman@meetinghouse.net> Mon, 28 April 2014 19:16 UTC

Return-Path: <mfidelman@meetinghouse.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 2AF761A067C for <ietf@ietfa.amsl.com>; Mon, 28 Apr 2014 12:16:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.881
X-Spam-Level:
X-Spam-Status: No, score=-0.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 vnzIY7w8tH4Y for <ietf@ietfa.amsl.com>; Mon, 28 Apr 2014 12:16:33 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 3BA831A064C for <ietf@ietf.org>; Mon, 28 Apr 2014 12:16:33 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id E6AA7CC0AB for <ietf@ietf.org>; Mon, 28 Apr 2014 15:16:31 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id v7cHfGfof2A7 for <ietf@ietf.org>; Mon, 28 Apr 2014 15:16:23 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 01B56CC0AC for <ietf@ietf.org>; Mon, 28 Apr 2014 15:16:22 -0400 (EDT)
Message-ID: <535EA906.7000900@meetinghouse.net>
Date: Mon, 28 Apr 2014 15:16:22 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: ietf@ietf.org
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> <535A7D87.6080200@dcrocker.net> <CAMm+LwgVjd7V08OHkV90QeJDwkEdA7S+yvwenO4K2hrDxV-icg@mail.gmail.com> <6.2.5.6.2.20140428055512.0d3d6088@resistor.net> <535E7378.7040401@meetinghouse.net> <6.2.5.6.2.20140428101558.0d859f50@resistor.net>
In-Reply-To: <6.2.5.6.2.20140428101558.0d859f50@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/lgcc5DTameiRUoCJO6DMMXztbZk
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: Mon, 28 Apr 2014 19:16:34 -0000

S Moonesamy wrote:
> Hi Miles,
> At 08:27 28-04-2014, Miles Fidelman wrote:
>> I think it's more accurate to say that the IETF has an "official 
>> role" as the standards body for Internet protocols - and there may be 
>> a mismatch between:
>
> I was looking at the matter from an appeals perspective.  I think that 
> it might be more effective than discussing about "official role".
>
>> - how that role is "officially defined" (such that it is)
>>
>> - what responsibilities go with such a role (based on expectations 
>> and experience with analogous environments and standards bodies that 
>> have a longer history - such as IEEE, ANSI, ISO, ITU, ...)
>
> I'll leave the above questions to people with expertise about these 
> topics.
>
>> - how IETF understands and executes its role (and given the somewhat 
>> bottom-up, ad hoc nature of IETF - how it's organization, policies, 
>> and operating procedures map onto exercising "official" roles and 
>> responsibilities"
>
> That's an IETF governance question. :-)
>
>> - what holes there are that might need to be plugged, and how they 
>> might be plugged
>
> The missing question in the above is "who is going to do the work".

Well, that's kind of implied :-)

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra