Re: RFC 6982: Improving Awareness of Running Code: The Implementation Status Section
Benoit Claise <bclaise@cisco.com> Mon, 11 May 2015 06:58 UTC
Return-Path: <bclaise@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A93CF1A1B79; Sun, 10 May 2015 23:58:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id brnk-GH9GULB; Sun, 10 May 2015 23:58:25 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D33011A1B87; Sun, 10 May 2015 23:58:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=37544; q=dns/txt; s=iport; t=1431327504; x=1432537104; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=LA0yCXjOZuCI7XtLUmY50D57n1nup8AT+cfxHlhj2bI=; b=HWHX1LUYT7lktPsjm1WVd5UgS+QqLZPX8jFtGaokLXmohOJpxI6j+Afa AG3d2seW7G+NB+wry+gVlryWtM3XkccBcdg8GSr2SM145DXvcyYsbjthP 2eCyYHEcAxMGHPIADLVo7Je5g35q9B/D3xuuU887fSJuCmeh64w2XuYQB 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D+AwCZUlBV/xbLJq1cgkWBfIMeuG+DXYUGCYddAoFdFAEBAQEBAQGBCoQgAQEBAwEjCksBBQsJAhEBAwEBChYBAQYDAgIJAwIBAgEUIAMGCAYBDAEEAQIBAYggCJZ9nQeTHAEBAQEBAQEBAQEBAQEBAQEBAQEBAReLOYE9gmURAVEGAYJogUUBBIUFlhKCCYEkg1qCW4spg1UjYYEoDQ8VgT88MYEMgToBAQE
X-IronPort-AV: E=Sophos;i="5.13,405,1427760000"; d="scan'208,217";a="491034655"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP; 11 May 2015 06:58:20 +0000
Received: from [10.149.0.19] (dhcp-10-149-0-19.cisco.com [10.149.0.19]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t4B6wCTE003009; Mon, 11 May 2015 06:58:20 GMT
Message-ID: <55505304.6030304@cisco.com>
Date: Mon, 11 May 2015 08:58:12 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: adrian@olddog.co.uk, 'WG Chairs' <wgchairs@ietf.org>
Subject: Re: RFC 6982: Improving Awareness of Running Code: The Implementation Status Section
References: <554B86EA.2020306@cisco.com> <072501d088e0$46e578c0$d4b06a40$@olddog.co.uk>
In-Reply-To: <072501d088e0$46e578c0$d4b06a40$@olddog.co.uk>
Content-Type: multipart/alternative; boundary="------------000406090209050205080407"
Archived-At: <http://mailarchive.ietf.org/arch/msg/wgchairs/y6ajSnErXdPF94uZMMY2a9zgOhY>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 May 2015 06:58:27 -0000
Adrian, > > As one of the authors of 6982 I would like some feedback. > > Thoughts from authors would be interesting, especially about "why not > include this information?" > > Thoughts from WG chairs would be valuable, especially about "did this > information help you make any decisions?" > > Thoughts from the IESG would be useful, especially about "did this > information help you when advancing the document?" > From an IESG review point of view, yes this is useful information. I find this section also useful when reviewing WG documents: the specifications with implementation experience prove more mature. > I have my suspicions about answers to all three questions. > > The authors of 6982 had agreed that we would report back on the > experiment (possibly sooner than now). We talked briefly in Dallas > about when would be the right time to do that and concluded that there > is no pressing need - i.e., that we should let the experiment run on > to gather more data. Indeed, it is possible that the original > experiment time was not long enough to produce meaningful data. > > We also discussed how this might fold into CodeMatch, but looking at > the timeline for that project we thought that it was too early to know > whether that would be possible. > > Options for now appear to be: > > - refine the experiment and continue > > - let the experiment continue as is > > - replace the experiment with a permanent, but optional feature > > - replace the experiment with a permanent and mandatory feature > > - scrap the experiment and clean the floor > My preference would be for "let the experiment continues as is", and potentially, in the future, "replace the experiment with a permanent, but optional feature" assuming that we see more occurrences of it ... which was the point behind the initial email. Regards, Benoit > > Any continuation could be re-assessed in a year and/or when CodeMatch > has got momentum. > > Ciao, > > Adrian > > *From:*WGChairs [mailto:wgchairs-bounces@ietf.org] *On Behalf Of > *Benoit Claise > *Sent:* 07 May 2015 16:38 > *To:* WG Chairs > *Subject:* RFC 6982: Improving Awareness of Running Code: The > Implementation Status Section > > Dear WG chairs, > > During the IESG retreat this week, we discussed running code. We would > like to bring your attention to this RFC: 6982, "Improving Awareness > of Running Code: The Implementation Status Section" (experimental). > You can review section 4 for an explanation of the benefits. > Interestingly, out of the 1918 current drafts, _only _32 use that > "Implementation Status" section. > > Please advertise this capability within your WGs. > > If you want to see examples, the 32 drafts are: > > draft-barre-mptcp-tfo-01.txt: > draft-ietf-avtcore-rfc5764-mux-fixes-02.txt: > draft-ietf-ccamp-flexible-grid-ospf-ext-01.txt: > draft-ietf-ccamp-flexible-grid-rsvp-te-ext-02.txt: > draft-ietf-ccamp-flexigrid-lambda-label-03.txt: > draft-ietf-codec-oggopus-07.txt: > draft-ietf-dnsop-edns-chain-query-02.txt: > draft-ietf-dnsop-qname-minimisation-02.txt: > draft-ietf-dnssd-hybrid-00.txt: > draft-ietf-eppext-launchphase-05.txt: > draft-ietf-eppext-tmch-smd-01.txt: > draft-ietf-isis-mrt-00.txt: > draft-ietf-netmod-syslog-model-03.txt: > draft-ietf-ospf-mrt-00.txt: > draft-ietf-pce-hierarchy-extensions-02.txt: > draft-ietf-pce-pce-initiated-lsp-04.txt: > draft-ietf-rmcat-nada-00.txt: > draft-ietf-rtgwg-mrt-frr-algorithm-03.txt: > draft-ietf-rtgwg-mrt-frr-architecture-05.txt: > draft-ietf-tram-stun-origin-05.txt: > draft-kong-eppext-bundling-registration-01.txt: > draft-kouvelas-lisp-rloc-membership-01.txt: > draft-li-isis-mrt-02.txt: > draft-martinsen-tram-discuss-02.txt: > draft-mrw-homenet-rtg-comparison-02.txt: > draft-murchison-webdav-prefer-08.txt: > draft-nottingham-safe-hint-06.txt: > draft-pd-dispatch-msrp-websocket-08.txt: > draft-petithuguenin-tram-stun-pmtud-00.txt: > draft-templin-aerolink-52.txt: > draft-yi-manet-reactive-jitter-04.txt: > draft-zhu-rmcat-nada-06.txt: > > Regards, Benoit > >
- RFC 6982: Improving Awareness of Running Code: Th… Benoit Claise
- RE: RFC 6982: Improving Awareness of Running Code… Adrian Farrel
- Re: RFC 6982: Improving Awareness of Running Code… Adam W. Montville
- Re: RFC 6982: Improving Awareness of Running Code… Stephen Farrell
- Re: RFC 6982: Improving Awareness of Running Code… Benoit Claise