Re: The IETF environment

S Moonesamy <sm+ietf@elandsys.com> Mon, 28 April 2014 18:53 UTC

Return-Path: <sm@elandsys.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 A46151A701D for <ietf@ietfa.amsl.com>; Mon, 28 Apr 2014 11:53:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.651
X-Spam-Level:
X-Spam-Status: No, score=-2.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.651] 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 91DPKG95NH7d for <ietf@ietfa.amsl.com>; Mon, 28 Apr 2014 11:52:58 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 983561A6FE8 for <ietf@ietf.org>; Mon, 28 Apr 2014 11:52:58 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.135.94]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s3SIqjRY006918 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Apr 2014 11:52:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1398711177; bh=aaOvkPa5T7RRNF80qLm5lhI0z+NSbQzCe0NLHSkq5Zg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=RnFpHcAvJG6I9ICgdWLfvPvqMJIvbzrJpBcFdvqIbV/CH3mJIjz/hDmWREMrxyvFr 92vVFqr+9NMtUhjx3T6YJC+HN5NzR8eq5byr+oSg5mYP0iBg4390crcJw+zqkjwIY5 3hdFtOGJisM/JJHMOsxRP/VHTcWPFHGfCKW/V2Mo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1398711177; i=@elandsys.com; bh=aaOvkPa5T7RRNF80qLm5lhI0z+NSbQzCe0NLHSkq5Zg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=P90jMEd0MM/lXQTSFuG7WKnEaScIjq3uKCpr9O/PZ4DG1dlOeheFKiyyUotbLcPm4 +qMrtkhqWrYSQbttDEnG0Ksa6a7wFltlEaJaYEB7qxJFngwpua4D3ucT89Qkmz+Ycw ou2J6qerNtnpDAtdA/Fk0hka6vREG9Q/D+yldKXo=
Message-Id: <6.2.5.6.2.20140428101558.0d859f50@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 28 Apr 2014 11:28:15 -0700
To: Miles Fidelman <mfidelman@meetinghouse.net>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: The IETF environment
In-Reply-To: <535E7378.7040401@meetinghouse.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> <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>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/JVNtlRuIjMVe4p6aXpvMRwVv7kk
Cc: 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: Mon, 28 Apr 2014 18:53:00 -0000

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".

Regards,
S. Moonesamy