Re: [v6ops] Please review the No IPv4 draft

Ted Lemon <ted.lemon@nominum.com> Wed, 16 April 2014 19:05 UTC

Return-Path: <Ted.Lemon@nominum.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 A24EA1A02ED for <v6ops@ietfa.amsl.com>; Wed, 16 Apr 2014 12:05:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level:
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 O-DMCGBQET_g for <v6ops@ietfa.amsl.com>; Wed, 16 Apr 2014 12:05:13 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id 4BDBE1A0291 for <v6ops@ietf.org>; Wed, 16 Apr 2014 12:05:13 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 1CF8D1B803F for <v6ops@ietf.org>; Wed, 16 Apr 2014 12:05:10 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id DF06519005C; Wed, 16 Apr 2014 12:05:09 -0700 (PDT)
Received: from [192.168.146.119] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 16 Apr 2014 12:05:09 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <534EC1DB.4010902@foobar.org>
Date: Wed, 16 Apr 2014 14:05:07 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <575F73AC-8DA5-4E04-B2CF-4875B729C7D3@nominum.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>
To: Nick Hilliard <nick@foobar.org>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/3CRuhgjVXDKZwODDl2C_HUTWTe4
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:05:17 -0000

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.

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.