RE: Running code, take 2
"Adrian Farrel" <adrian@olddog.co.uk> Thu, 13 December 2012 14:16 UTC
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FF5721F8B0C for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 06:16:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level:
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t2UAUmQ+KSyc for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 06:16:30 -0800 (PST)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 8586F21F8B0B for <ietf@ietf.org>; Thu, 13 Dec 2012 06:16:29 -0800 (PST)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id qBDEGR51015993; Thu, 13 Dec 2012 14:16:27 GMT
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id qBDEGQjq015973 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 13 Dec 2012 14:16:27 GMT
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Alessandro Vesely' <vesely@tana.it>, ietf@ietf.org
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it>
In-Reply-To: <50C9DED7.8060604@tana.it>
Subject: RE: Running code, take 2
Date: Thu, 13 Dec 2012 14:16:24 -0000
Message-ID: <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGe4+QL1KmOUmkeH6pPkukeTFqmiwITGFE+mGQXbyA=
Content-Language: en-gb
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
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: Thu, 13 Dec 2012 14:16:30 -0000
I'm interested in this idea. However, I note that an "implementation status" section of a document is frozen in time when a document goes to RFC. I wonder whether we could leverage our tools and do something similar to IPR disclosures. That is, provide a semi-formal web page where implementation details could be recorded and updated. These would then be searchable and linked to from the tools page for the I-D / RFC. They could record the document version that has been implemented, and also allow space for other notes. Adrian (Just thinking aloud) > -----Original Message----- > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of > Alessandro Vesely > Sent: 13 December 2012 13:58 > To: ietf@ietf.org > Subject: Re: Running code, take 2 > > On Wed 12/Dec/2012 20:31:04 +0100 Yaron Sheffer wrote: > > > > I have just published a draft that proposes an alternative to > > Stephen's "fast track". My proposal simply allows authors to document, > > in a semi-standard way, whatever implementations exist for their > > protocol, as well as their interoperability. > > > > http://www.ietf.org/id/draft-sheffer-running-code-00.txt > > > > [...] > > > > I am looking forward to comments and discussion on this list. > > As an occasional I-D reader, I'd appreciate "Implementation Status" > sections, including IPR info. I don't think anything forbids to add > such sections, if the authors wish. I'd add a count of the number of > I-Ds that actually have it among the experiment's success criteria.
- Running code, take 2 Yaron Sheffer
- Re: Running code, take 2 Alessandro Vesely
- RE: Running code, take 2 Adrian Farrel
- Re: Running code, take 2 Marc Blanchet
- Re: Running code, take 2 Yaron Sheffer
- Re: Running code, take 2 Yaron Sheffer
- Re: Running code, take 2 Marc Blanchet
- Re: Running code, take 2 Yaron Sheffer
- Re: Running code, take 2 Marc Blanchet
- RE: Running code, take 2 Adrian Farrel
- Re: Running code, take 2 Yaron Sheffer
- RE: Running code, take 2 Adrian Farrel
- Re: Running code, take 2 Marc Blanchet
- Re: Running code, take 2 Loa Andersson
- Re: Running code, take 2 Marc Blanchet
- RE: Running code, take 2 Yaron Sheffer
- Re: Running code, take 2 Ted Hardie
- Re: Running code, take 2 Loa Andersson
- Re: Running code, take 2 Melinda Shore
- Re: Running code, take 2 Randy Bush
- Re: Running code, take 2 Melinda Shore
- Re: Running code, take 2 Randy Bush
- Re: Running code, take 2 Yaron Sheffer
- Re: Running code, take 2 John C Klensin
- Re: Running code, take 2 Randy Bush
- Re: Running code, take 2 Melinda Shore
- Re: Running code, take 2 John C Klensin
- Re: Running code, take 2 Yaron Sheffer
- Re: Running code, take 2 t.p.
- Re: Running code, take 2 t.p.
- Re: Running code, take 2 Randy Bush
- Re: Running code, take 2 Randy Bush
- Re: Running code, take 2 Alessandro Vesely
- Re: Running code, take 2 Yaron Sheffer
- Re: Running code, take 2 Riccardo Bernardini
- Re: Running code, take 2 Stephen Farrell
- Re: Running code, take 2 Yaron Sheffer
- The notion of "fast tracking" drafts (was: Re: Ru… John C Klensin
- Re: Running code, take 2 John C Klensin
- Re: The notion of "fast tracking" drafts Stephen Farrell
- Re: Running code, take 2 Yaron Sheffer
- Re: Running code, take 2 John C Klensin
- Re: The notion of "fast tracking" drafts Keith Moore
- Re: The notion of "fast tracking" drafts John C Klensin
- Re: The notion of "fast tracking" drafts Stephen Farrell
- Re: The notion of "fast tracking" drafts Keith Moore
- Re: The notion of "fast tracking" drafts Stephen Farrell