Re: [v6ops] Please review the No IPv4 draft

Philip Homburg <pch-v6ops-3a@u-1.phicoh.com> Tue, 22 April 2014 13:50 UTC

Return-Path: <pch-bBB316E3E@u-1.phicoh.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 C35111A0441 for <v6ops@ietfa.amsl.com>; Tue, 22 Apr 2014 06:50:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.9
X-Spam-Level:
X-Spam-Status: No, score=-3.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2] 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 EduTw45_boeA for <v6ops@ietfa.amsl.com>; Tue, 22 Apr 2014 06:50:52 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) by ietfa.amsl.com (Postfix) with ESMTP id 4E5561A040D for <v6ops@ietf.org>; Tue, 22 Apr 2014 06:50:52 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #76) id m1Wcb5y-0000FMC; Tue, 22 Apr 2014 15:50:46 +0200
Message-Id: <m1Wcb5y-0000FMC@stereo.hq.phicoh.net>
To: "George, Wes" <wesley.george@twcable.com>
From: Philip Homburg <pch-v6ops-3a@u-1.phicoh.com>
Sender: pch-bBB316E3E@u-1.phicoh.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> <20140416155714.GB64039@ricotta.doit.wisc.edu> <alpine.DEB.2.02.1404162310050.10236@uplift.swm.pp.se> <B21C1073-ABBE-44FE-964F-65AD7849CD31@delong.com> <alpine.DEB.2.02.1404170658440.10236@uplift.swm.pp.se> <4EABCE38-7CBA-4C95-84EE-686A2300F26E@delong.com> <8E450CDC-FFC5-4649-89FE-387836C8E40B@nominum.com> <CAEmG1=oNyotn6tcKyxUuLCW0of-MxVrvUB08jsygjo8kidgt0g@mail.gmail.com> <CF7BDD91.1911D%wesley.george@twcable.com>
In-reply-to: Your message of "Tue, 22 Apr 2014 09:00:32 -0400 ." <CF7BDD91.1911D%wesley.george@twcable.com>
Date: Tue, 22 Apr 2014 15:50:36 +0200
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/giTH9wD8RldnkmxeeGfc2U2RZqg
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: Tue, 22 Apr 2014 13:50:55 -0000

In your letter dated Tue, 22 Apr 2014 09:00:32 -0400 you wrote:
>    WG] I think that there's a need for clarification here. A lot
>    of this discussion has focused almost exclusively on the full-on
>    disabling of IPv4. Part of what the draft discusses is that
   there are differing things that can be signaled to the local
>    devices from the network based on the bit set in the proposed
>    option. There is an option that simply signals "there is no IPv4
>    support on this network" and makes attendant recommendations
>    that the device decide on its own what to do for any local IPv4
>    traffic on the LAN, including doing nothing, configuring 169
>    addresses, etc. but that it should disable IPv4 on the upstream
>    interface facing the network that provided the signal (I.e.
>    Stop forwarding IPv4 traffic and stop sending DHCPv4).

I'm really curious about the resistance of putting the no-ipv4 option in
DHCPv4. As far as I can tell that can be done safely, with almost no 
drawbacks.

Instead, an endless amount of effort seems to be invested in defending the
current choice for DHCPv6 and RA.

Maybe there is document the describes why putting the no-ipv4 option in
DHCPv4 is such a horrible idea. It is just that I can't find it.

Does anyone have a link to that document? (Assuming it exists)