[ietf-outcomes] "+>" ?

Dave CROCKER <dhc@dcrocker.net> Thu, 11 February 2010 21:00 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 []) by core3.amsl.com (Postfix) with ESMTP id 869863A75CD for <ietf-outcomes@core3.amsl.com>; Thu, 11 Feb 2010 13:00:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.562
X-Spam-Status: No, score=-6.562 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id wCVQXgsNLciP for <ietf-outcomes@core3.amsl.com>; Thu, 11 Feb 2010 13:00:26 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com []) by core3.amsl.com (Postfix) with ESMTP id 7E8373A75B3 for <ietf-outcomes@ietf.org>; Thu, 11 Feb 2010 13:00:26 -0800 (PST)
Received: from [] (adsl-68-122-70-87.dsl.pltn13.pacbell.net []) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id o1BL1adB026875 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 11 Feb 2010 13:01:41 -0800
Message-ID: <4B74702B.90501@dcrocker.net>
Date: Thu, 11 Feb 2010 13:01:31 -0800
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv: 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/10382/Thu Feb 11 10:54:02 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 []); Thu, 11 Feb 2010 13:01:41 -0800 (PST)
Subject: [ietf-outcomes] "+>" ?
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: Thu, 11 Feb 2010 21:00:27 -0000


Dave Harrington just made an interesting change to the SNMPv3 entry(*) that I'd 
like to get some comments on:


The change specifies an Adoption value of "+>".  That's one + and not two, so 
it's not in the current Legend.

In formulating the original list of Adoption values, I had assumed that 
prompting "extensive derivative work" was an additional /degree/ of success, not 
a different /kind/.  So it did not occur to me that something could have "some 
adoption" and also prompt derivative work.

It well may be that David has correctly implied that derivative work is really a 
measure that is independent of "success".  (And this might satisfy an opinion 
Jon Callas expressed to me that a 'failed' effort can nonetheless be extremely 
valuable for learning how to do later work better.  So I suppose that "-->" 
would be a reasonable value for PEM...?)

It might also be that the definition of + vs. ++ need changing.  The more I'm 
thinking about David's change, the more I think this is the case.

The problem is my original choice of wording in the Legend.  "massive adoption" 
seems to imply getting a large percentage of a large market, and that's not 
really what I had meant for that value.  Since the Target Adoption column, and 
some accompanying text, cite the potential for becoming a critical resource, but 
within a smaller market -- and that that would be a major success -- the current 
Adoption definition for ++ might be off the mark.

This suggests that the definitions in the Legend should be changed to be 
something like:

    +:  gained some usefulness

    +:  became an essential capability

(The use of past tense is to avoid any implication about current utility, since 
the wiki is not trying to track the later reduction in usefulness over time, but 
rather whether a capability has /ever/ become useful.)

And my meanderings that cite PEM, above, are causing me to think that ">" should 
be defined as separately applicable, to any level of utility assessment, 
including --.



(*)  David has been a busy guy this week, tweaking entries in the wiki.  Thanks, 


   Dave Crocker
   Brandenburg InternetWorking