Re: [v6ops] IPv4 trajectory
Alexandru Petrescu <alexandru.petrescu@gmail.com> Thu, 02 April 2015 06:36 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 0CC9D1B2B29 for <v6ops@ietfa.amsl.com>; Wed, 1 Apr 2015 23:36:55 -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 8T-UIjiIWprt for <v6ops@ietfa.amsl.com>; Wed, 1 Apr 2015 23:36:53 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 027721B2B28 for <v6ops@ietf.org>; Wed, 1 Apr 2015 23:36:52 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t326aoeC027338; Thu, 2 Apr 2015 08:36:50 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id AA09C205BE6; Thu, 2 Apr 2015 08:37:45 +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 9D016200DF0; Thu, 2 Apr 2015 08:37:45 +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 t326aQUJ021228; Thu, 2 Apr 2015 08:36:50 +0200
Message-ID: <551CE36A.50706@gmail.com>
Date: Thu, 02 Apr 2015 08:36:26 +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: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
References: <63C03012-C7DD-497E-A1EF-019711E95FD0@cisco.com> <551BFBA9.5070103@gmail.com> <4A8F9E83-B481-44FC-AD70-BFFF43EC2614@lists.zabbadoz.net>
In-Reply-To: <4A8F9E83-B481-44FC-AD70-BFFF43EC2614@lists.zabbadoz.net>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/_IWFNoGxC8IZ5DRqvq9N4HBkkbk>
Cc: 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 06:36:55 -0000
Sorry to insist on this, just as side note. Le 01/04/2015 19:54, Bjoern A. Zeeb a écrit : >> On 01 Apr 2015, at 14:07 , Alexandru Petrescu >> <alexandru.petrescu@gmail.com> wrote: >> >> It is customary to see current computers having both an IPv6 stack >> and an IPv4 stack on them. But some computers only have IPv4, >> whereas the rest have IPv4 and IPv6 stacks. There are no >> computers (to my knowledge) which have only IPv6 stacks. > > One of my desktop systems does (not have IPv4 support anymore; In general I can agree with you, in a sense where maybe a computer is not reachable on IPv4 from another computer; maybe part of IPv4 support is no more there. > and to my knowledge you can just disable it on Windows as well, Right - uncheck the IPv4 box, and check IPv6 on a computer Windows 7's "Properties" of the network interface - it works. But, after this, one can still ping 127.0.0.1, the routing table still contains pure IPv4 entries, the domain name (which only exists in IPv4) is still showing in ipconfig /all, the computer is still receiving TCP and TLSv1 re-transmissions from its earlier connections. Worse, the IPv4-only applications report errors which are not explicitely telling there is no such address family. I guess even netsh interface ipv4 add address will work ok. (compared to an IPv4-only computer: routing table does not show anything making think IPv6, etc.) I guess unchecking the IPv4 box simply removes IPv4 addresses from interfaces and stops the DHCP client, maybe puts the interface down; but it will not remove the IPv4 stack from the kernel, will not ARP inform the router it has no more IPv4, will not recompile the apps to remove the IPv4-only socket interfaces, will not forbid adding manually IPv4 addresses. > so it’s 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. Alex > > — 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] 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