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

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Tue, 23 October 2018 18:33 UTC

Return-Path: <prvs=1834938bf9=jordi.palet@consulintel.es>
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 EF310130EB3 for <ipv6@ietfa.amsl.com>; Tue, 23 Oct 2018 11:33:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es
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 FN_SLsRsU1yz for <ipv6@ietfa.amsl.com>; Tue, 23 Oct 2018 11:33:05 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30BF6130E4D for <ipv6@ietf.org>; Tue, 23 Oct 2018 11:33:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1540319583; x=1540924383; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:CC:Message-ID:Thread-Topic:References: In-Reply-To:Mime-version:Content-type:Content-transfer-encoding; bh=XkjqfDz5GYNfPG23r47L1AsEH6uQ3uks5kzwqRRCsig=; b=mJh3Aak2i3lrd cXwzhuw4Jcdgk78Z6zZMrEOq6b2WYWkiaQlOUGAuPnf/DvE7RknLSv/gVvkOGlyw c03ggFUssc6YwPGdrxOLX2kszfY+eUMfTN2JuyFCvmaX8tHLtss+tpS0amtQ9BM3 RLcrMByWmMDY9JWEL16nxfkgf3yHzs=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Tue, 23 Oct 2018 20:33:03 +0200
X-Spam-Processed: mail.consulintel.es, Tue, 23 Oct 2018 20:33:03 +0200
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50005921333.msg for <ipv6@ietf.org>; Tue, 23 Oct 2018 20:33:01 +0200
X-MDRemoteIP: 2001:470:1f09:495:e029:6e39:5a:1318
X-MDHelo: [10.10.10.99]
X-MDArrival-Date: Tue, 23 Oct 2018 20:33:01 +0200
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1834938bf9=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ipv6@ietf.org
User-Agent: Microsoft-MacOutlook/10.10.3.181015
Date: Tue, 23 Oct 2018 20:33:01 +0200
Subject: Re: Running code (Was: I-D Action: draft-ietf-6man-ipv6only-flag-03.txt)
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: Suresh Krishnan <suresh.krishnan@gmail.com>, Sander Steffann <sander@steffann.nl>
CC: Fernando Gont <fgont@si6networks.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Message-ID: <C46C990E-0A4F-4731-8CB1-FD204858935E@consulintel.es>
Thread-Topic: Running code (Was: I-D Action: draft-ietf-6man-ipv6only-flag-03.txt)
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>
In-Reply-To: <5E75F3CA-F1D2-4F4F-9CF7-EEEE59634C1E@gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/cNCqudesEwZSZ70EaBxMFd9-Icg>
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: Tue, 23 Oct 2018 18:33:07 -0000

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. 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.