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

神明達哉 <jinmei@wide.ad.jp> Tue, 23 October 2018 20:01 UTC

Return-Path: <jinmei.tatuya@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 08112130E1B for <ipv6@ietfa.amsl.com>; Tue, 23 Oct 2018 13:01:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.42
X-Spam-Level:
X-Spam-Status: No, score=-0.42 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, FROM_EXCESS_BASE64=0.979, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 IAXFYYMlTJDC for <ipv6@ietfa.amsl.com>; Tue, 23 Oct 2018 13:01:48 -0700 (PDT)
Received: from mail-lf1-f47.google.com (mail-lf1-f47.google.com [209.85.167.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3AB0B12426A for <ipv6@ietf.org>; Tue, 23 Oct 2018 13:01:48 -0700 (PDT)
Received: by mail-lf1-f47.google.com with SMTP id w16-v6so33115lfc.0 for <ipv6@ietf.org>; Tue, 23 Oct 2018 13:01:48 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=AecxOlHgj7ZBojq6j1WMKT0DFcluMRv1UZqOdUUwe/A=; b=e6SMGA/lTOJfVj8cU42iDG+bm9U7WmQyDi/um3gZTgmWF282247KUQtLF899bb10yn qAjNKiGWgdBjIgy3ji5pe5gMtEHtSXkPY6Es46eOjOachn4dUuNkYWZSebYXSJHpBlWG RLiAf0X3DCJs5khdlsxpoXh/ikncQ6IMQvGFpiCwJ45gjJpMPLtD0jQmLAPfy6D/u9Ld fAuegCV4brtXVTExEcaFXv6Lc3e3tP539ROXxtJG3BMicLZLQCIzjkoDgcBFT3NuMWMZ b+pA66ThidwAYHIY3U9qF9t40x+PAlof5nI90RRGe5MS/nCbv6hHIxs4apnJyxN+dPuq PZ3Q==
X-Gm-Message-State: ABuFfohOoXTsD05TQO8Gqq3m/4XdOpsZvs5yMNVFq4heMq8oAkx+RW1r Z/4cUka7uhMkPW0rQSlf5K/fP+tUTF5VqHiXFSw=
X-Google-Smtp-Source: ACcGV626km5Sw/XbGx4px5LysYqCRgeinyTzTioiYQdsaDNilfkHzuYDaxyiZftvhC1EN4n+SNVdii+hZ8vDDFG7Gno=
X-Received: by 2002:a19:5e5d:: with SMTP id z29mr8734051lfi.105.1540324905877; Tue, 23 Oct 2018 13:01:45 -0700 (PDT)
MIME-Version: 1.0
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>
From: 神明達哉 <jinmei@wide.ad.jp>
Date: Tue, 23 Oct 2018 13:01:34 -0700
Message-ID: <CAJE_bqeLYHFgJaQVyNqxc0PQM7OrAgGeCKh5rfcR5OswQNO1XA@mail.gmail.com>
Subject: Re: Running code (Was: I-D Action: draft-ietf-6man-ipv6only-flag-03.txt)
To: Suresh Krishnan <suresh.krishnan@gmail.com>
Cc: Sander Steffann <sander@steffann.nl>, Fernando Gont <fgont@si6networks.com>, IPv6 IPv6 List <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000da87800578ead660"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/SQwuws-BeW31iSh0D5SqmIFyTLg>
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 20:01:50 -0000

At Tue, 23 Oct 2018 14:26:28 -0400,
Suresh Krishnan <suresh.krishnan@gmail.com> wrote:

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

I agree as a general statement, but I believe we should carefully look
into the context for this particular case.  I supported the idea of
seeing an implementation of this draft in my own comment because the
draft has been controversial and there has not even been an interest
in (let alone an attempt of) implementing it even if host implementors
should be a primary beneficiaries of this proposal.  Given these I
believe it's reasonable and fair to suggest to hold off a while and
see if there's someone at least trying to have a prototype
implementation and if we can learn from it.  My general impression of
this thread is that others who supported the idea did so more or less
for the same reason, i.e, taking into account the situation instead of
abruptly raising the bar just because they didn't like the proposal.

Whether we should generally/always require an implementation as a wg
is a different topic.  I personally support at least the sense of the
idea (how strictly it should apply would still be a different
question), but I understand different people will have different
opinions on that point.

--
JINMEI, Tatuya