[ietf-outcomes] "Instances" column

Dave CROCKER <dhc@dcrocker.net> Sat, 13 February 2010 22:02 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 8C2F13A720D for <ietf-outcomes@core3.amsl.com>; Sat, 13 Feb 2010 14:02:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.565
X-Spam-Level:
X-Spam-Status: No, score=-6.565 tagged_above=-999 required=5 tests=[AWL=0.034, 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 3RMSNZCKqmd6 for <ietf-outcomes@core3.amsl.com>; Sat, 13 Feb 2010 14:02:52 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 79FE93A6A80 for <ietf-outcomes@ietf.org>; Sat, 13 Feb 2010 14:02:52 -0800 (PST)
Received: from [192.168.1.43] (adsl-68-122-34-69.dsl.pltn13.pacbell.net [68.122.34.69]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id o1DM4ASj011546 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-outcomes@ietf.org>; Sat, 13 Feb 2010 14:04:16 -0800
Message-ID: <4B7721D4.7070402@dcrocker.net>
Date: Sat, 13 Feb 2010 14:04:04 -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
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV 0.92/10389/Fri Feb 12 17:11:17 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]); Sat, 13 Feb 2010 14:04:16 -0800 (PST)
Subject: [ietf-outcomes] "Instances" column
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: Sat, 13 Feb 2010 22:02:53 -0000

Folks,

Ray is a busy guy today.  He looked at the Outcomes pages some more and went the 
next step in thinking of a way to make it easier for average, non-geek/non-IETF 
folk to relate to particular pieces of work, by asking whether it would be 
possible to indicate products implement the work.

I did a version of this for DKIM

    <http://dkim.org/deploy/index.html>

but it is manually maintained and was for the purpose of /promoting/ DKIM 
adoption, rather than /demonstrating/ it.  At the least, it has more detail than 
I would suggest for the Outcomes page.

I do think that some amount of pointing to implementations could be helpful, 
since it provide concrete demonstration of availability (if not actual use.) 
However, it needs to be self-administered, carry no implications of quality or 
conformance, and no marketing.

I've created an example of this on the Security page

    <http://trac.tools.ietf.org/misc/outcomes/wiki/IetfSecurity>

and would appreciate comments.

It has an example of pointing to a list that is maintained outside (the DKIM 
page) and one that is part of the wiki (DNSSec).  Since I don't know anything 
about DNSSec, I've only created the skeleton for the sub-page; but I am guessing 
that there are folk who are highly motivated to tout DNSSec support...)

OK.  Start shooting...

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net