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

Suresh Krishnan <suresh.krishnan@gmail.com> Tue, 23 October 2018 21:26 UTC

Return-Path: <suresh.krishnan@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 34293130DC7 for <ipv6@ietfa.amsl.com>; Tue, 23 Oct 2018 14:26:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 PMdYKPn_TSQX for <ipv6@ietfa.amsl.com>; Tue, 23 Oct 2018 14:26:04 -0700 (PDT)
Received: from mail-yw1-xc33.google.com (mail-yw1-xc33.google.com [IPv6:2607:f8b0:4864:20::c33]) (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 A3180130D7A for <ipv6@ietf.org>; Tue, 23 Oct 2018 14:26:04 -0700 (PDT)
Received: by mail-yw1-xc33.google.com with SMTP id x7-v6so1178619ywf.9 for <ipv6@ietf.org>; Tue, 23 Oct 2018 14:26:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=tayVjBzV786q96tQSRdYwt11AWC8lBGsSxPZ/PBSMSc=; b=FVTjf1wlMh+B9B6JN6o1KsyP+oRqqnsxcKk+IlBGfsNF/sfz7kjkJKD0AlXs+RuqrA HMmt5Jpvac/RlCXHBvhHSm0a+YI4udJbl9iLUcqL3L9AGRizCJ0i8K9xlQEujQh1sP9A Xd5ea0Tfkxjn11zF4LfCx8kjxU2XPIbviqaJ0I8mG70ojU0bichgHOCrvv+VIhTF4S5Z W5ov7ul2C3HMlOqc5tcQ8/rSo0I02jC5YPerVNHejy6Ux5gvFqzDbEw2D2mLtrnBqeRM urzbWnoeLfw3rUFlJrsYM1EjQ/VbSC1Su5gLwxKH2vU93AK2lAaiBD1qZa8Czws51YG2 rbjg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=tayVjBzV786q96tQSRdYwt11AWC8lBGsSxPZ/PBSMSc=; b=HQfF4X5lix8IO1GoyHBVwX/VZCchZgMEVlnhaxB7QszE96a5ah0NYJOD85IqRnX4+i nWalMoNOG1FSNicdPzvZWdaxo4FA0pwR8ePy2RopUMjn46n1/MGa3iqiBAJhMwUe5j8/ lT49upFIPSVVmSoubbaqDZm9y6kI6m1N1vbmjIqn4j5IYq/DNVmXvkHcDk2l/6MC3D/W PMDOXcVlyIT2fE0+Vl2JoDrEqIQaFxYA0STSlccXlKYVskCQFmTvs0G5PXqt20YXV2dN v0mPYK7muW2EzCsvawvdM4Tf7pdoNm4izInDJ6E7G06iNaXTmt/SQPeibMIf5xk8VpUH Dnyg==
X-Gm-Message-State: AGRZ1gIjpWIUhEiZ6N0WNdTa42Kx99PMZREpLEU6Iyx5gNb4RyFSSF27 wayWj2eUgUjiBDWN1Dx8HC4R0t/+
X-Google-Smtp-Source: AJdET5eVkaKnMkEhWv9OB0xYfUh/qaIoJVU7rjFs3jkLbgeXphO5b1emFZR15c8ANmOGFPQw5ulx8Q==
X-Received: by 2002:a81:a002:: with SMTP id x2-v6mr2174004ywg.293.1540329963662; Tue, 23 Oct 2018 14:26:03 -0700 (PDT)
Received: from [10.0.0.18] (45-19-110-76.lightspeed.tukrga.sbcglobal.net. [45.19.110.76]) by smtp.gmail.com with ESMTPSA id w188-v6sm542029ywf.59.2018.10.23.14.26.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 23 Oct 2018 14:26:02 -0700 (PDT)
From: Suresh Krishnan <suresh.krishnan@gmail.com>
Message-Id: <2FF42917-97F7-47FC-B004-3B7FB2626CC1@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_CB6821A3-7AC3-4387-BD54-0EA747C95BDC"
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
Subject: Re: Running code (Was: I-D Action: draft-ietf-6man-ipv6only-flag-03.txt)
Date: Tue, 23 Oct 2018 17:26:01 -0400
In-Reply-To: <CAJE_bqeLYHFgJaQVyNqxc0PQM7OrAgGeCKh5rfcR5OswQNO1XA@mail.gmail.com>
Cc: Sander Steffann <sander@steffann.nl>, Fernando Gont <fgont@si6networks.com>, IPv6 IPv6 List <ipv6@ietf.org>
To: 神明達哉 <jinmei@wide.ad.jp>
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> <CAJE_bqeLYHFgJaQVyNqxc0PQM7OrAgGeCKh5rfcR5OswQNO1XA@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.100.39)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/HwxZbrFh_C9I6FO0v_33lBqtFSg>
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 21:26:07 -0000

Hi Jinmei-san,

> On Oct 23, 2018, at 4:01 PM, 神明達哉 <jinmei@wide.ad.jp> wrote:
> 
> At Tue, 23 Oct 2018 14:26:28 -0400,
> Suresh Krishnan <suresh.krishnan@gmail.com <mailto: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 <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. 

And in fact, I found your response to be most helpful in the way of how this can be implemented. Thanks for that! I think the crux of the issue is about what to do on a host implementation. e.g. installing iptables entries to filter IPv4 may or may not be acceptable to some of the people who commented on this thread. 

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

Yep. Agree.

Thanks
Suresh