Re: [v6ops] Please review the No IPv4 draft

Ray Hunter <v6ops@globis.net> Tue, 15 April 2014 06:08 UTC

Return-Path: <v6ops@globis.net>
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 07B7B1A0743 for <v6ops@ietfa.amsl.com>; Mon, 14 Apr 2014 23:08:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.173
X-Spam-Level:
X-Spam-Status: No, score=-2.173 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] 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 LyDnxOpuicZ9 for <v6ops@ietfa.amsl.com>; Mon, 14 Apr 2014 23:08:21 -0700 (PDT)
Received: from globis01.globis.net (mail.globis.net [IPv6:2001:470:1f15:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id D7BD41A06C9 for <v6ops@ietf.org>; Mon, 14 Apr 2014 23:08:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id B5890870074; Tue, 15 Apr 2014 08:08:17 +0200 (CEST)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m04tDYRGRn4S; Tue, 15 Apr 2014 08:08:17 +0200 (CEST)
Received: from Rays-iMac.local (unknown [IPv6:2001:470:1f15:73a:7daa:d497:b80b:8b11]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPSA id 7901187006F; Tue, 15 Apr 2014 08:08:17 +0200 (CEST)
Message-ID: <534CCCCF.9040000@globis.net>
Date: Tue, 15 Apr 2014 08:08:15 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.9 (Macintosh/20140129)
MIME-Version: 1.0
To: Ted Lemon <ted.lemon@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> <F2A0EC2F-6B41-4560-88BA-CEBF3E921B61@delong.com> <CAEmG1=oK8iHAms2_uVBsCtpCG7xBdhRfh9QQrd+JXUXgjBPqPA@mail.gmail.com> <0901D65B-EA79-4E20-987D-9BA01CEDDAB3@delong.com> <B3942C2F-C08E-42F2-9038-92C3C63E0023@nominum.com> <534C432D.3060700@globis.net> <51F06435-CA02-4B65-8484-51687A35CB29@nominum.com>
In-Reply-To: <51F06435-CA02-4B65-8484-51687A35CB29@nominum.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/HrsWdTDTMyC1UTLT4THkpcDg8sM
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 06:08:26 -0000

> Ted Lemon <mailto:ted.lemon@nominum.com>
> 15 April 2014 05:17
>
> The network is mismanaged or under attack. Fix it.
>
See Homenet Architecture 3.2.2.2.  B: Two ISPs, Two CERs, Shared subnet. 
http://tools.ietf.org/html/draft-ietf-homenet-arch-13#page-18

What when one ISP says "No IPv4 Service" whilst the other ISP says "Yes 
IPv4, and here's your address"?

This is NOT a misconfiguration IMHO, but a weakness in the assumptions 
lying behind this draft i.e. that all routers on a link are managed by 
one self-consistent management entity for both IPv6 and IPv4.
> Ray Hunter <mailto:v6ops@globis.net>
> 14 April 2014 22:21
>
>
>
>
> That we are discussing turning off IPv4 in both RA and DHCPv6 just 
> highlights to me how ridiculous host configuration has become.
>
> To me this proposal just introduces all sorts of horrible race 
> conditions and inconsistencies, and I'm not convinced it's any better 
> than just configuring up IPv4 via DHCPv4 with either a self assigned 
> address or an RFC 1918 address and saying nothing about remote 
> connectivity (given that most OSes already have IPv4 detection 
> mechanisms in place to work out whether they are on a corporate 
> network with proxies or the Internet or on an isolated island or 
> whatever.)
>
> e.g. what does a host do if RA says turn off IPv4, but DHCPv4 replies 
> either before or after a host receives that RA advertisement?
> Does the host have to then disable IPv4 once it is already up? For how 
> long?
>
> What if DHCPv6 and RA are not consistent (given they may not even be 
> the same router or device responding)?
>
> What if one router is IPv4 only and the other IPv6 only? And they're 
> from 2 different ISP providers connected to a common L2 LAN? That's a 
> perfectly valid configuration in my opinion.
>
> Can an absence of "turn off IPv4" message be taken as a "turn on IPv4"?
>
> How would this be implemented consistently given RA is generally ICMP 
> (kernel space) and DHCPv6 user space (daemon)?
>
> Given the O and M bit saga, what makes anyone think that this 
> additional signalling will be any better?
>
> Why would any end host trust this message?
>
> IMHO the place to turn off or signal limited IPv4 connectivity is in 
> DHCPv4 (if we ever even attempt to do that).
>
> ------------------------------------------------------------------------


-- 
Regards,
RayH