Re: Running code (Was: I-D Action: draft-ietf-6man-ipv6only-flag-03.txt)

Alexandre Petrescu <alexandre.petrescu@gmail.com> Wed, 24 October 2018 09:10 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1060130E70 for <ipv6@ietfa.amsl.com>; Wed, 24 Oct 2018 02:10:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.633
X-Spam-Level:
X-Spam-Status: No, score=-2.633 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665] autolearn=ham autolearn_force=no
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 MJRPNwPLihrq for <ipv6@ietfa.amsl.com>; Wed, 24 Oct 2018 02:10:55 -0700 (PDT)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F939130E7C for <ipv6@ietf.org>; Wed, 24 Oct 2018 02:10:55 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id w9O9Aq0u137394 for <ipv6@ietf.org>; Wed, 24 Oct 2018 11:10:52 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id F327D201BBD for <ipv6@ietf.org>; Wed, 24 Oct 2018 11:10:51 +0200 (CEST)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id E96FE201B43 for <ipv6@ietf.org>; Wed, 24 Oct 2018 11:10:51 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id w9O9AppO015567 for <ipv6@ietf.org>; Wed, 24 Oct 2018 11:10:51 +0200
Subject: Re: Running code (Was: I-D Action: draft-ietf-6man-ipv6only-flag-03.txt)
To: ipv6@ietf.org
References: <CAFU7BASO_ByzbanhLKnWV280O_fASd-8W+ujpj3sN6d2-whw2w@mail.gmail.com> <CACWOCC-u7aAPwAOcixYvt2On=-o_8X25GhqdXTfA+tWRC1o2XA@mail.gmail.com> <3beca72e-19c5-10af-02e5-c21a90d77100@gmail.com> <20181019.223739.271916573.sthaug@nethelp.no> <4f58643c-272e-507e-3282-c87befd42395@gmail.com> <0927741c-4e8e-fcf7-ddd6-3ba500ba4c3d@si6networks.com> <7B48A11D-31DE-443C-B73A-14642EA0A397@jisc.ac.uk> <7526af75-4359-6fc6-e39b-eb94024a04de@si6networks.com> <E1BB1232-C1A2-496A-8157-0682D91EED42@steffann.nl> <5E75F3CA-F1D2-4F4F-9CF7-EEEE59634C1E@gmail.com> <C46C990E-0A4F-4731-8CB1-FD204858935E@consulintel.es>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <76b4f0c5-a628-1b20-0583-7de825a91457@gmail.com>
Date: Wed, 24 Oct 2018 11:10:49 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <C46C990E-0A4F-4731-8CB1-FD204858935E@consulintel.es>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/AEuWavE5OyS-XKnhOLhMlO50vlA>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2018 09:10:58 -0000


Le 23/10/2018 à 20:33, JORDI PALET MARTINEZ a écrit :
> Hi,
> 
> I don't think this can be enforced and even less for a specific ID
> or WG.
> 
> And this will be discriminatory also if applied to all the IETF 
> work.
> 
> There are many authors that don't have time, resources, access to
> the source code from vendors, or even knowledge, among many many
> many other possible reasons, to implement an ID they submit.

An additional reason is the following: it can be a waste of time
implementing something whose spec gets scrapped.

This reason typically applies when implementing an individual proposal 
Internet Draft.

Alex

> Also, there will be IDs which are not "implementable", etc., and
> clearly that doesn't disqualify that it may be a perfectly valid
> work.
> 
> I guess this is a discussion that should be held at the general area 
> list.
> 
> Regards, Jordi
> 
> 
> 
> -----Mensaje original----- De: ipv6 <ipv6-bounces@ietf.org> en 
> nombre de Suresh Krishnan <suresh.krishnan@gmail.com> Fecha: martes, 
> 23 de octubre de 2018, 20:26 Para: Sander Steffann 
> <sander@steffann.nl> CC: Fernando Gont <fgont@si6networks.com>, 
> "ipv6@ietf.org" <ipv6@ietf.org> Asunto: Re: Running code (Was: I-D 
> Action: draft-ietf-6man-ipv6only-flag-03.txt)
> 
> 
>> On Oct 23, 2018, at 2:05 PM, Sander Steffann <sander@steffann.nl> 
>> wrote:
>> 
>> Hi,
>> 
>> Changed the subject because this discussion is now moving away
>> from any specific draft.
>> 
>>> That's kind of my take, as well However, I think that asking for 
>>> an implementation of the ipv6-only flag is a requirement that I 
>>> have never seen for taking new work or publishing it, so it
>>> would be unfair to ask that to the authors of this particular
>>> I-D.
>> 
>> I'd like that to become the norm though. Having a running
>> prototype can help enormously when writing specifications. My
>> preference would be to move back to a base principle of running
>> code and rough consensus, instead of only rough consensus.
> 
> If the WG decides to go on this path, I will be fully supportive of 
> that. This model has worked out well for idr (see 
> https://trac.ietf.org/trac/idr/wiki#ImplementationRequirement). What 
> I am uncomfortable with is that criterion being *selectively*
> applied to this draft as a prerequisite for progress.
> 
> Thanks Suresh
> 
> --------------------------------------------------------------------
>  IETF IPv6 working group mailing list ipv6@ietf.org Administrative 
> Requests: https://www.ietf.org/mailman/listinfo/ipv6 
> --------------------------------------------------------------------
> 
> 
> 
> 
> ********************************************** IPv4 is over Are you 
> ready for the new Internet ? http://www.consulintel.es The IPv6 
> Company
> 
> This electronic message contains information which may be privileged 
> or confidential. The information is intended to be for the exclusive 
> use of the individual(s) named above and further non-explicilty 
> authorized disclosure, copying, distribution or use of the contents 
> of this information, even if partially, including attached files, is 
> strictly prohibited and will be considered a criminal offense. If
> you are not the intended recipient be aware that any disclosure,
> copying, distribution or use of the contents of this information,
> even if partially, including attached files, is strictly prohibited,
> will be considered a criminal offense, so you must reply to the
> original sender to inform about this communication and delete it.
> 
> 
> 
> --------------------------------------------------------------------
>  IETF IPv6 working group mailing list ipv6@ietf.org Administrative 
> Requests: https://www.ietf.org/mailman/listinfo/ipv6 
> --------------------------------------------------------------------
>