Re: Running Code
ned+ietf@mauve.mrochek.com Wed, 04 March 2009 19:52 UTC
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 47FAC3A6BA4 for <ietf@core3.amsl.com>; Wed, 4 Mar 2009 11:52:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.556
X-Spam-Level:
X-Spam-Status: No, score=-2.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599]
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 khiMWw91FWG1 for <ietf@core3.amsl.com>; Wed, 4 Mar 2009 11:52:45 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by core3.amsl.com (Postfix) with ESMTP id 84D993A6A3F for <ietf@ietf.org>; Wed, 4 Mar 2009 11:52:45 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01N66Q28N2WW00N8DZ@mauve.mrochek.com> for ietf@ietf.org; Wed, 4 Mar 2009 11:53:12 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01N66OXPKHSW00007A@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Wed, 04 Mar 2009 11:53:07 -0800 (PST)
Date: Wed, 04 Mar 2009 11:45:46 -0800
From: ned+ietf@mauve.mrochek.com
Subject: Re: Running Code
In-reply-to: "Your message dated Wed, 04 Mar 2009 10:42:32 -0800" <49AECB98.9050307@acm.org>
To: Marc Petit-Huguenin <petithug@acm.org>
Message-id: <01N66Q26XB8000007A@mauve.mrochek.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
Content-transfer-encoding: 7bit
References: <C5D430A5.4140%mshore@cisco.com> <49AECB98.9050307@acm.org>
Cc: Melinda Shore <mshore@cisco.com>, Harald Alvestrand <harald@alvestrand.no>, Ned Freed <ned.freed@mrochek.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 04 Mar 2009 19:52:46 -0000
> I assumed that acknowledgement would be a good enough incentive for > developers to contribute early implementations, but you seem to > think that there would be other reasons. The fact is that feedback > from early implementations is rare, THat may be true in your neck of the woods, but not in mine. I try and do at least a preliminary implementation for every specification I write (the notable exception for me on this was RFC 2231, and boy do I wish I had done one in that case), and I routinely receive notes from other implementors saying they've iimplemented some draft of mine long before publication or even WG last call. > so what other reasons do you > think early implementers would have? Cannot be money - early > implementations are very likely to become obsolete at the next > version of the I-D, and so have to be rewritten. Again, if there's a problem with people not getting proper recognition for having contributed to a specification, irrespective of whether that contribution is based on implementation work or just reading the specification, that needs to be addressed independently of this proposal. It is wrong to take credit for someone else's work. Ned
- Re: Running Code Scott Lawrence
- RE: Running Code Hallam-Baker, Phillip
- Running Code Marc Petit-Huguenin
- Re: Running Code Brian E Carpenter
- Re: Running Code Peter Saint-Andre
- Re: Running Code Marc Petit-Huguenin
- Re: Running Code Harald Alvestrand
- Re: Running Code Marc Petit-Huguenin
- Re: Running Code Henning Schulzrinne
- Re: Running Code Masataka Ohta
- Re: Running Code Gary E. Miller
- Re: Running Code Andy Bierman
- Re: Running Code ned+ietf
- Re: Running Code Masataka Ohta
- Re: Running Code Marc Petit-Huguenin
- Re: Running Code Marc Petit-Huguenin
- RE: Running Code Hannes Tschofenig
- Re: Running Code Alessandro Vesely
- Re: Running Code Lars Eggert
- Re: Running Code Jari Arkko
- Re: Running Code Andrew Sullivan
- Re: Running Code ned+ietf
- Re: Running Code Peter Saint-Andre
- RE: Running Code Hannes Tschofenig
- Re: Running Code Andy Bierman
- Re: Running Code Marc Petit-Huguenin
- Re: Running Code Marc Petit-Huguenin
- Re: Running Code Marc Petit-Huguenin
- Re: Running Code Henry Sinnreich
- Re: Running Code Henning Schulzrinne
- Re: Running Code Melinda Shore
- Re: Running Code Marc Petit-Huguenin
- Re: Running Code Melinda Shore
- RE: Running Code Hannes Tschofenig
- Re: Running Code ned+ietf
- Re: Running Code ned+ietf
- Early implementers motivations [was Re: Running C… Marc Petit-Huguenin
- Re: Running Code Pete Resnick
- Re: Running Code Henning Schulzrinne
- Re: Early implementers motivations [was Re: Runni… Doug Ewell
- Re: Early implementers motivations [was Re: Runni… ned+ietf
- Re: Running Code Marc Petit-Huguenin
- Re: Running Code Marc Petit-Huguenin
- Re: Running Code Doug Ewell
- Re: Running Code Cullen Jennings
- Re: Running Code ned+ietf
- Re: Running Code Marc Petit-Huguenin
- Re: Running Code Marc Petit-Huguenin
- Re: Running Code ned+ietf
- Re: Running Code Marc Petit-Huguenin
- Re: Early implementers motivations [was Re: Runni… Alexandru Petrescu
- Re: Running Code Philip Matthews