Re IPv6 adoption (Was Re: IPv10 (Temp. name IPmix) (draft-omar-ipv10-00.txt).)

Steve Crocker <> Thu, 29 December 2016 01:12 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 843F312952E for <>; Wed, 28 Dec 2016 17:12:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -5
X-Spam-Status: No, score=-5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.1, SPF_HELO_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id UbgKhw4ZBiLi for <>; Wed, 28 Dec 2016 17:12:16 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 5881A1294C9 for <>; Wed, 28 Dec 2016 17:12:16 -0800 (PST)
Received: from; Thu, 29 Dec 2016 01:12:15 +0000
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re IPv6 adoption (Was Re: IPv10 (Temp. name IPmix) (draft-omar-ipv10-00.txt).)
From: Steve Crocker <>
In-Reply-To: <049f01d2613f$c5431ef0$4fc95cd0$>
Date: Wed, 28 Dec 2016 20:12:14 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <049f01d2613f$c5431ef0$4fc95cd0$>
To: Tony Hain <>
X-Mailer: Apple Mail (2.3124)
Archived-At: <>
Cc: IETF <>
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 29 Dec 2016 01:12:17 -0000


I’ve been trying to understand the dynamics of IPv6 adoption.  Your note fills in part of the puzzle.  Nice!



> On Dec 28, 2016, at 2:22 PM, Tony Hain <> wrote:
> [Regarding the problem of legacy IPv4 hosts in the enterprise environment that will not migrate, [it has been] demonstrated fact that [administrators of legacy hosts] are unwilling to make the well documented changes to deploy IPv6 because they simply refuse to make a change, or to  learn something new. 
> In the beta version of Windows XP I made sure IPv6 was ON-BY-DEFAULT, with no knob to turn it off, because I knew that given the option enterprise administrators would turn it off. I lost the battle in the shipping version though, and sure enough the first things that showed up on search engines were instructions for how to turn IPv6 off. The lack of deployed end systems limited the willingness of app developers to bother making their changes, which in turn fed the resistance to change by the intermediate network administrators. Fast forward to the point where IPv6 is required, and forcing the changes outward from the middle is proving to be as difficult as predicted.
> Tony