Re: Running code, take 2
Marc Blanchet <marc.blanchet@viagenie.ca> Thu, 13 December 2012 14:55 UTC
Return-Path: <marc.blanchet@viagenie.ca>
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 1D4C721F8AD0 for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 06:55:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.511
X-Spam-Level:
X-Spam-Status: No, score=-102.511 tagged_above=-999 required=5 tests=[AWL=0.088, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 BARufobNEj-2 for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 06:55:32 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 59C2521F880D for <ietf@ietf.org>; Thu, 13 Dec 2012 06:55:32 -0800 (PST)
Received: from mb.lan (modemcable180.211-203-24.mc.videotron.ca [24.203.211.180]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 0021B41474; Thu, 13 Dec 2012 09:55:22 -0500 (EST)
Subject: Re: Running code, take 2
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset="windows-1252"
From: Marc Blanchet <marc.blanchet@viagenie.ca>
In-Reply-To: <50C9EBB3.5040901@gmail.com>
Date: Thu, 13 Dec 2012 09:55:22 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <B73F381B-93E7-4158-B5C5-D1F88994E7DF@viagenie.ca>
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <50C9EBB3.5040901@gmail.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
X-Mailer: Apple Mail (2.1283)
Cc: adrian@olddog.co.uk, ietf@ietf.org, 'Alessandro Vesely' <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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:55:33 -0000
Le 2012-12-13 à 09:52, Yaron Sheffer a écrit : > Hi Adrian, > > I would suggest to start with my proposal, because it requires zero implementation effort. disagree. phase 1: use IETF wiki. phase 2: develop an widget within data tracker. Marc. > If this catches on, I see a lot of value in your proposal. > > Please also note that the "implementation status" section (according to my proposal) is not "frozen" when published as an RFC, rather it is deleted. RFCs are forever, and I think a point-in-time implementation status is not appropriate in an RFC. > > Thanks, > Yaron > > On 12/13/2012 04:16 PM, Adrian Farrel wrote: >> 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