IETF Logo Mail Archive

Re: Running code, take 2

Randy Bush <randy@psg.com> Fri, 14 December 2012 12:10 UTC

Return-Path: <randy@psg.com>
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 4570221F85FE for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 04:10:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 MxflqKvWS62y for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 04:09:59 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id DDFDF21F85EE for <ietf@ietf.org>; Fri, 14 Dec 2012 04:09:59 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1TjU5O-000OrI-3F; Fri, 14 Dec 2012 12:09:50 +0000
Date: Fri, 14 Dec 2012 04:09:49 -0800
Message-ID: <m28v90zvg2.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Subject: Re: Running code, take 2
In-Reply-To: <50CAE81A.4040807@gmail.com>
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <9F862855-15A5-4109-88AE-32AAD7D1C21C@viagenie.ca> <50CA189E.1090002@gmail.com> <m2sj79zuot.wl%randy@psg.com> <50CA4DFA.9050500@gmail.com> <CD38357DE61404E1B49E9B93@JcK-HP8200.jck.com> <50CAE81A.4040807@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Cc: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
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: Fri, 14 Dec 2012 12:10:00 -0000

> to clarify, my proposal only applies to Internet Drafts, and clearly 
> states that the implementation section should be removed from the 
> document before it is published as RFC.
> 
> Formally, we don't want non-permanent stuff in RFCs. And realistically, 
> even if we had an implementation wiki, it is unlikely to be kept up to 
> date once the RFC is published.

so, we act on implementation and interoperability data which are not
kept?

randy

v2.23.0 | Report a Bug | By Email