Re: [ietf-outcomes] [OPS-AREA] IETF Outcomes wiki

Dave CROCKER <dhc@dcrocker.net> Wed, 10 February 2010 20:01 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf-outcomes@core3.amsl.com
Delivered-To: ietf-outcomes@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A15DF28C224 for <ietf-outcomes@core3.amsl.com>; Wed, 10 Feb 2010 12:01:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.556
X-Spam-Level:
X-Spam-Status: No, score=-6.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nJi8xfVw7M6L for <ietf-outcomes@core3.amsl.com>; Wed, 10 Feb 2010 12:01:05 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 26DF828C26A for <ietf-outcomes@ietf.org>; Wed, 10 Feb 2010 12:00:50 -0800 (PST)
Received: from [192.168.1.43] (adsl-68-122-70-87.dsl.pltn13.pacbell.net [68.122.70.87]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id o1AK1urr030658 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-outcomes@ietf.org>; Wed, 10 Feb 2010 12:02:01 -0800
Message-ID: <4B7310B0.7000807@dcrocker.net>
Date: Wed, 10 Feb 2010 12:01:52 -0800
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: ietf-outcomes@ietf.org
References: <EDC652A26FB23C4EB6384A4584434A0401F0D8DA@307622ANEX5.global.avaya.com> <048101caa80f$db2ee5a0$0600a8c0@china.huawei.com> <E25EFA3754F74B2AB6D11BBA3685FD70@BertLaptop> <4B70F71B.7080804@bogus.com> <BLU137-DS5E874A567D6039C93F14793500@phx.gbl><064301caa99f$fb5f6e30$0600a8c0@china.huawei.com><4B718B7B.6000401@dcrocker.net> <067401caa9b6$813ab210$0600a8c0@china.huawei.com> <EDC652A26FB23C4EB6384A4584434A0401F0E0A1@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0401F0E0A1@307622ANEX5.global.avaya.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV 0.92/10375/Wed Feb 10 09:24:44 2010 on sbh17.songbird.com
X-Virus-Status: Clean
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 10 Feb 2010 12:02:01 -0800 (PST)
Subject: Re: [ietf-outcomes] [OPS-AREA] IETF Outcomes wiki
X-BeenThere: ietf-outcomes@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF Outcomes Wiki discussion list <ietf-outcomes.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-outcomes>, <mailto:ietf-outcomes-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-outcomes>
List-Post: <mailto:ietf-outcomes@ietf.org>
List-Help: <mailto:ietf-outcomes-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-outcomes>, <mailto:ietf-outcomes-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2010 20:01:06 -0000

On 2/10/2010 2:45 AM, Romascanu, Dan (Dan) wrote:
> 'The wiki is only as complete and accurate as community effort makes it.'
>
> It would probably be good to add a phrase that makes clear that the
> information contained here does not represent the consensus of the IETF.


I'll offer a friendly amendment, in the hopes of achieving some... ummm... 
consensus...


Outcomes home page
------------------

Currently:
> The IETF has operated in its current form since 1989. Some of its standards
> have succeeded on a very large and visible scale. Others are successful, but
> visible only to a more limited community. Others have fared poorly. This
> wiki lists technologies and services that were developed in the IETF and
> represent notable successes or failures. It is a collaborative effort of
> IETF participants, to provide feedback to the community about the utility of
> IETF efforts, as well as to facilitate public understanding of IETF work and
> impact.


Proposed revision:

The IETF has operated in its current form since 1989. Some of its standards have
succeeded on a very large and visible scale. Others are successful, but visible
only to a more limited community. Others have fared poorly. This wiki lists
technologies and services that were developed in the IETF and represent notable
successes or failures. It is an informal, collaborative effort of IETF
participants, to provide feedback to the community about the utility of IETF
efforts, as well as to facilitate public understanding of IETF work and impact.
The contents of the are revised according to the views of individual
contributors and have not been subject to IETF Rough Consensus assessment.



Charter page
------------

Currently:

> The IETF produces technical specifications, with the goal of their being used
> on the Internet. Once a specification is published, there is no formal
> mechanism for assessing the eventual utility of the work. However feedback
> about successes or problems can be useful in developing a shared community
> sense of the way work is -- or should be -- done. The IETF Outcomes Wiki is a
> collaborative effort to produce subjective assessments about successes and
> failures of notable efforts, based on rough consensus.


Proposed revision:

The IETF produces technical specifications, with the goal of their being used on 
the Internet. Once a specification is published, there is no formal mechanism 
for assessing the eventual utility of the work. However feedback about successes 
or problems can be useful in developing a shared community sense of the way work 
is -- or should be -- done. The IETF Outcomes Wiki is
an informal, collaborative, incremental effort among individual IETF 
participants, to produce subjective assessments about successes and failures of 
notable efforts.  Although tending to reflect a degree of community agreement, 
the contents of the wiki are not subject to formal IETF Rough Consensus assessment.

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net