[162643] in North American Network Operators' Group
Re: IPv6 and HTTPS
daemon@ATHENA.MIT.EDU (Jima)
Sun Apr 28 01:55:13 2013
Date: Sat, 27 Apr 2013 23:55:41 -0600
From: Jima <nanog@jima.us>
To: North American Network Operators Group <nanog@nanog.org>
In-Reply-To: <05CD8F9B-46DD-4069-9EBE-2C92FFFF210E@delong.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 2013-04-27 11:01, Owen DeLong wrote:
> On Apr 26, 2013, at 9:55 PM, Jima wrote:
>> On 2013-04-26 01:29, Don Gould wrote:
>>> I agree with others that there is still way to much XP and other non
>>> supporting platforms and I suspect that by the time we get those out of
>>> the system we'll be most of the way there for IPv6 access.
>>
>> And heck, you don't even need to get rid of XP for IPv6 -- just enable the stack. (It's not the greatest implementation, but `ipv6 install` is still an easier sell than "replace your computer.")
>
> This will work until you no longer have an IPv4 resolver available for DNS. After that, XP fails miserably.
I could only wish the biggest software barrier to disabling IPv4 on
local networks was XP's DNS resolver path.
Doing away with IPv4 isn't a sane short-term goal for anyone carrying
along software as old as XP anyway; I'd focus on getting IPv6 to all of
the things and marginalizing IPv4 destinations to the point that CGN is
of reduced impact and concern.
Oh, and a pony.
Jima
