Re: [v6ops] Please review the No IPv4 draft

Owen DeLong <owen@delong.com> Wed, 16 April 2014 19:43 UTC

Return-Path: <owen@delong.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 853161A030E for <v6ops@ietfa.amsl.com>; Wed, 16 Apr 2014 12:43:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.263
X-Spam-Level:
X-Spam-Status: No, score=-1.263 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=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 lA4eZGNCwxwH for <v6ops@ietfa.amsl.com>; Wed, 16 Apr 2014 12:43:45 -0700 (PDT)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id D31041A021D for <v6ops@ietf.org>; Wed, 16 Apr 2014 12:43:45 -0700 (PDT)
Received: from owens-mbp.meeting.arin.net (unknown.servercentral.net [50.31.214.180] (may be forged)) (authenticated bits=0) by owen.delong.com (8.14.2/8.14.2) with ESMTP id s3GJg9qI032181 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 16 Apr 2014 12:42:11 -0700
X-DKIM: Sendmail DKIM Filter v2.8.3 owen.delong.com s3GJg9qI032181
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=delong.com; s=mail; t=1397677333; bh=IxJJOAlYBaoKfrwkMTGQuRKiXbg=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc: Content-Transfer-Encoding:Message-Id:References:To; b=xgCRFWh60fEWThFsoDFmvpru9OStFaosP8GZqrk0tjz4yYuqej7PxFDxsF4/IA7Cz zEMVhSymSJYVApkZlZnDgKrX3pPHx5KXRNW1M4GKblCvjIA5524VEsLH6QILHmRJde Uc3HILLr5cMMIVK1qtznKGWmmMxn7LwJ/ujG6InI=
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Owen DeLong <owen@delong.com>
In-Reply-To: <575F73AC-8DA5-4E04-B2CF-4875B729C7D3@nominum.com>
Date: Wed, 16 Apr 2014 12:42:06 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <B4B17FC0-01E1-448B-8683-83917953544A@delong.com>
References: <534BF5A5.5010609@viagenie.ca> <20140415083615.GB43641@Space.Net> <534D3672.3060702@viagenie.ca> <3446106.k0lm12lQ8b@linne> <alpine.DEB.2.02.1404161034220.10236@uplift.swm.pp.se> <CAKD1Yr2D+ZMi-UctuvrMzyqoHqgBy5O26GODT=bRwq0PsvLgLw@mail.gmail.com> <alpine.DEB.2.02.1404161053110.10236@uplift.swm.pp.se> <m1WaMBx-0000BSC@stereo.hq.phicoh.net> <E772899C-8505-4436-8594-380799F91BA0@nominum.com> <CAKD1Yr2KFOi_hW3CCSbcT-uPQSwsUyE06cY3r8=CuunSbnz_xw@mail.gmail.com> <D701ADC0-EA9F-48DD-933F-9E02ACF3EBD4@nominum.com> <534EAB83.1070906@foobar.org> <70739713-281A-41E6-93ED-5EE1BC4B7FAB@nominum.com> <534EC1DB.4010902@foobar.org> <575F73AC-8DA5-4E04-B2CF-4875B729C7D3@nominum.com>
To: Ted Lemon <ted.lemon@nominum.com>
X-Mailer: Apple Mail (2.1874)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0rc1 (owen.delong.com [192.159.10.2]); Wed, 16 Apr 2014 12:42:13 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/tZi9vqFJOXCDTlRLKuCIruJqNtg
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>
Subject: Re: [v6ops] Please review the No IPv4 draft
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 19:43:50 -0000

On Apr 16, 2014, at 12:05 PM, Ted Lemon <ted.lemon@nominum.com> wrote:

> On Apr 16, 2014, at 12:46 PM, Nick Hilliard <nick@foobar.org> wrote:
>> Process exists to serve the ietf, not the other way around.  Several people
>> in both v6ops and homenet have expressed serious concern about the choice
>> to use dhcpv6 and ra instead of dhcpv4.  If you want to invoke process to
>> close the discussion on this topic, then that's your prerogative, but given
>> the previous lack of discussion about it, I would view this as a very poor
>> idea.
> 
> That's fine.   The working group is amenable to useful discussion, as far as I know.   What concerns me is that a lot of objections have been raised that are simply opinions, and that are addressed in the current document.   And motivations have been stated that do not match my personal experience of the state of the art in host configuration stacks.
> 
> So I raise process not because I think process should trump technical contribution, but because process is the only way to deal with disputes over matters of opinion.   There's no way everyone can win on a matter of opinion, and while there's clearly some support for a DHCPv4 solution, there's substantially more support for a DHCPv6/RA solution.   That's also why I asked people who object whether they had objections which were of the form "this won't actually work because FOO."   Nobody provided any values of FOO with respect to the current proposal.

Please explain how “substantially more support” was established in this context.

It sounds like there was very limited discussion mostly in relation to other drafts in working groups outside of v6ops.

There’s definitely been substantial objection to doing it in DHCPv6/RA and significant support for doing it either in DHCPv4 or ICMPv4.

> You may get the impression that I feel strongly about this proposal and think it's a good idea.   I do support the work, and I think the choice that's been made is a good one, but I really don't feel strongly about it—I'd be just as happy if the conclusion of the process was "just filter IPv4 at the access points if you want it to go away," and I'd like to see more discussion on that topic.   But what I really do feel strongly about is that discussions should be productive, and that's why you see me participating in this discussion in the way that I have been doing.

In which case, I would suggest it would be more productive to look for ways to take the feedback received and apply it in a useful way rather than simply attempt to unilaterally declare it out of scope for the review and that the issues raised are “settled” and immutable by this process.

Owen