Re: [v6ops] Please review the No IPv4 draft

Ted Lemon <ted.lemon@nominum.com> Tue, 15 April 2014 15:37 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 3A2541A0476 for <v6ops@ietfa.amsl.com>; Tue, 15 Apr 2014 08:37:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.772
X-Spam-Level:
X-Spam-Status: No, score=-0.772 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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 jqCA1xGI1_4j for <v6ops@ietfa.amsl.com>; Tue, 15 Apr 2014 08:37:29 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id A47AE1A01E2 for <v6ops@ietf.org>; Tue, 15 Apr 2014 08:37:23 -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 228C21B8055 for <v6ops@ietf.org>; Tue, 15 Apr 2014 08:37:21 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (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 1BF7519005C; Tue, 15 Apr 2014 08:37:21 -0700 (PDT)
Received: from [172.16.0.175] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 15 Apr 2014 08:37:20 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <82E804C3-725D-415A-87C3-512073774C6F@delong.com>
Date: Tue, 15 Apr 2014 10:37:19 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <C3DC2027-A532-4A2C-852E-A1329098B080@nominum.com>
References: <534BF5A5.5010609@viagenie.ca> <534BFA08.3030404@foobar.org> <49EA8AC9-D5C5-4FE5-9A10-0CD574782F0F@nominum.com> <534C07FC.8000907@foobar.org> <F08AF14D-22C6-4F4C-9388-670EB4CD8453@nominum.com> <534C17B8.8030209@foobar.org> <534C27C9.80701@viagenie.ca> <20140414194824.GY43641@Space.Net> <534C3F7D.3040406@viagenie.ca> <20140414201231.GZ43641@Space.Net> <23F575A3-E00D-410E-9929-7377B7CAA623@nominum.com> <82E804C3-725D-415A-87C3-512073774C6F@delong.com>
To: Owen DeLong <owen@delong.com>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/N63sXAZHk2wIrE9euGGkrWn4VaA
Cc: 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: Tue, 15 Apr 2014 15:37:34 -0000

On Apr 14, 2014, at 11:51 PM, Owen DeLong <owen@delong.com> wrote:
> Calling it the wrong thing while advocating an even more wrong thing is equally absurd.

When I call it the wrong thing, I mean that it doesn't work well (and I explained that).  In practice, not in theory.   You are claiming that adding the capability to shut off DHCPv4 is even more wrong, but you haven't explained why.   So when we weigh the two considerations next to each other, one of which is substantiated by everybody's daily experience of Linux networking, and the other of which is purely speculative and not substantiated by any reasoning that would lead us to think it is true, then despite the fact that, if it were true, it would be worse, we should, logically, weigh the other consideration more heavily.

For comparison, suppose you were to assert that there's a significant risk of giant bunnies leaping out into the road when driving on any interstate highway in the U.S.  We could definitely say that if such a statement were true, it would require us to change our driving habits.   And yet we likely would not change our driving habits, because you have given us no reason to think it's true.

(Happy Easter!)