Re: [v6ops] IPv4 trajectory
Alexandru Petrescu <alexandru.petrescu@gmail.com> Thu, 02 April 2015 18:09 UTC
Return-Path: <alexandru.petrescu@gmail.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 2832D1A0056 for <v6ops@ietfa.amsl.com>; Thu, 2 Apr 2015 11:09:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level:
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 xuIB3HQb0qLd for <v6ops@ietfa.amsl.com>; Thu, 2 Apr 2015 11:09:35 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D04731A002D for <v6ops@ietf.org>; Thu, 2 Apr 2015 11:09:34 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t32I9WxM009310; Thu, 2 Apr 2015 20:09:32 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 00C892076BA; Thu, 2 Apr 2015 20:10:28 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id E6F4D2074AC; Thu, 2 Apr 2015 20:10:27 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t32I8xOF016069; Thu, 2 Apr 2015 20:09:32 +0200
Message-ID: <551D85B7.5030406@gmail.com>
Date: Thu, 02 Apr 2015 20:08:55 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Mark Andrews <marka@isc.org>
References: <63C03012-C7DD-497E-A1EF-019711E95FD0@cisco.com> <551BFBA9.5070103@gmail.com> <4A8F9E83-B481-44FC-AD70-BFFF43EC2614@lists.zabbadoz.net> <551CE36A.50706@gmail.com> <BAE229DE-22AC-4E64-8E70-CA182104364B@lists.zabbadoz.net> <551D8001.8060901@gmail.com> <20150402180046.4F6E52C5011F@rock.dv.isc.org>
In-Reply-To: <20150402180046.4F6E52C5011F@rock.dv.isc.org>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/P0vl7nhrRkYV1ueF4BR9gzzslEg>
Cc: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>, v6ops@ietf.org
Subject: Re: [v6ops] IPv4 trajectory
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: Thu, 02 Apr 2015 18:09:37 -0000
Le 02/04/2015 20:00, Mark Andrews a écrit : [...] >> And Windows' hosts file containing 127? > > Do you want to rip all the A records out of the DNS as well? Right. That is necessary in order to obtain IPv6-only. But it looks like a huge task to remove all A records from DNS. This makes think about removing all 500k IPv4 routes from the DFZ - also a huge task. > If the getaddrinfo() is properly written the IPv4 addresses will be > filtered from the responses with AI_ADDRCONFIG set so it shouldn't > matter if it is still there. That would still be IPv4 taking space on disk; taking bandwidth on network up to Client (AI_ filtering is local, right?). >>>>> so it=92s not a big deal anymore). >>>> >>>> I beg to differ, as I see it this is still far away from an >>>> ideal where only IPv6 were present in the computer. >>> >>> >>> Well, better start living it today and we can have a lot better >>> operational discussions on the end-node (client/server systems) >>> side. I have 7 IPv4 addresses left in use in total for all my >>> infrastructure (and could condense it to 2 or 3 if I wanted >>> really badly). And the only reason I keep those is for the >>> ipv4-only world to reach NS/MX/Web. But that=92s just me. >>> Leave a /27 for a SMB and be good ;-) >> >> Congratulations. >> >> I have no BSD here, except for the proprietary derivatives (ios, >> windows, etc). For all code that I can modify it's linux. Given >> that I can't turn off IPv4 until linux gives a means to. > > You have a editor, a compiler and the source. You have the means to > do it. Whether you have the skill / inclination to do it is another > matter. Ressource may be there, and the pleasure of removing; but reticence worrying doing it too early is there too. Maybe someone somewhere still needs this little IPv4 and it will break otherwise; wouldnt touch it yet. Alex > >> Do you know whether ios has such a means to turn off fully IPv4? >> >> Alex >> >>> >>> =97 Bjoern A. Zeeb Charles >>> Haddon Spurgeon: "Friendship is one of the sweetest joys of >>> life. Many might have failed beneath the bitterness of their >>> trial had they not found a friend." >>> >>> >>> >> >> >> _______________________________________________ v6ops mailing list >> v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
- [v6ops] IPv4 trajectory Fred Baker (fred)
- Re: [v6ops] IPv4 trajectory Alexandru Petrescu
- Re: [v6ops] IPv4 trajectory Lee Howard
- Re: [v6ops] IPv4 trajectory Erik Nygren
- Re: [v6ops] IPv4 trajectory Ackermann, Michael
- Re: [v6ops] IPv4 trajectory Templin, Fred L
- Re: [v6ops] IPv4 trajectory Fred Baker (fred)
- Re: [v6ops] IPv4 trajectory Brian E Carpenter
- Re: [v6ops] IPv4 trajectory Fred Baker (fred)
- Re: [v6ops] IPv4 trajectory Fred Baker (fred)
- Re: [v6ops] IPv4 trajectory Brian E Carpenter
- Re: [v6ops] IPv4 trajectory Fred Baker (fred)
- Re: [v6ops] IPv4 trajectory Brian E Carpenter
- Re: [v6ops] IPv4 trajectory joel jaeggli
- Re: [v6ops] IPv4 trajectory Ca By
- Re: [v6ops] IPv4 trajectory Bjoern A. Zeeb
- Re: [v6ops] IPv4 trajectory James Woodyatt
- Re: [v6ops] IPv4 trajectory Alexandru Petrescu
- Re: [v6ops] IPv4 trajectory Alexandru Petrescu
- Re: [v6ops] IPv4 trajectory Bjoern A. Zeeb
- Re: [v6ops] IPv4 trajectory Alexandru Petrescu
- Re: [v6ops] IPv4 trajectory Alexandru Petrescu
- Re: [v6ops] IPv4 trajectory Mark Andrews
- Re: [v6ops] IPv4 trajectory Alexandru Petrescu
- Re: [v6ops] IPv4 trajectory James Woodyatt
- Re: [v6ops] IPv4 trajectory Brian E Carpenter
- Re: [v6ops] IPv4 trajectory George, Wes
- Re: [v6ops] IPv4 trajectory Fred Baker (fred)
- Re: [v6ops] IPv4 trajectory Ackermann, Michael
- Re: [v6ops] IPv4 trajectory Xing Li
- Re: [v6ops] [sunset4] IPv4 trajectory George, Wes