[189932] in North American Network Operators' Group
Re: Netflix banning HE tunnels
daemon@ATHENA.MIT.EDU (Valdis.Kletnieks@vt.edu)
Fri Jun 10 04:32:31 2016
X-Original-To: nanog@nanog.org
To: "tim@pelican.org" <tim@pelican.org>
From: Valdis.Kletnieks@vt.edu
In-Reply-To: <1465539562.450519746@apps.rackspace.com>
Date: Fri, 10 Jun 2016 04:32:25 -0400
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
--==_Exmh_1465547545_2073P
Content-Type: text/plain; charset=us-ascii
On Fri, 10 Jun 2016 07:19:22 +0100, "tim@pelican.org" said:
> All the business systems that sit around it? Not so much. $DAYJOB has
> plenty of code, database structures etc that are built around "an IP address is
> no more than 15 characters long and matches
> '[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}'". To fix that, you need
> development time - typically expensive analyst time to work out *what* you need
> to change, not just code-grinder make-the-field-bigger time. IT departments
> seem reluctant to provide that resource, unless you've got people at the very
> top of the business bought into the fact that you *need* to do IPv6.
Some of us had those very same challenges - but managed to deploy IPv6 last
century *anyhow*. Seriously - none of your code has been untouched for the 16
years so far in this century (if it in fact hasn't, you probably have bigger
problems). You should have been doing incremental changes for IPv6 as you
revisit code, so you didn't have a big pile of stuff left.
And quite frankly, those of you who dragged their feet have really missed the
boat. 10 years ago, you could have done an incremental deploy of IPv6, knowing
that only people clued enough to manually enable it would be using it. So
it was safe to put out a "It's sort of there, use at your own risk, let us
know what you manage to break" mode. SLAAC only because you don't have the
business infrastructure for DHCP6? Back then it was OK.
That's long gone. Now every smart phone and laptop - pretty much everything
that isn't a smart TV or a game console is going to try to use it, so you need
to get it 100% right on the first try or your support center is going to catch
fire.
--==_Exmh_1465547545_2073P
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Exmh version 2.5 07/13/2001
iQIVAwUBV1p7GQdmEQWDXROgAQKQeRAArZNhPORTUbLj2ylu0oSK7yTF1T8VZ8v6
IVjBSOJaiER3ZBTXt8uhe6YFDgMDbeuwgiW9rYz+iz1+CuDa19hBuYG66QxgnIqH
5dHDn+SQzbBYsZJSf3tbqDeIArN91XytJxTd8ss/wFQbzxCQ2nd57HScfAno1SsL
ETv1GE4pSj49vWZ2ifQ3Ej2lS74g8tfpEksAGWewDMkJC7+yWPSwMWYc4iQrXkKk
84+G5350u3JsQWilLsyoPHKqd+cTaleh9ffo1uHLXxYj/W7//FqHdKqrvbFawgYP
8FmrTjG0tGecRWvruntU++HJfvWM/tEJAAKR1jA8JvkeNsgC6Hn2T7PlVz6HT8JT
vGJSd3vwj5A3/Vsp49XZUo4nyIOYQEAEPnkx3jQ9FuNeuFuTrCCYd/HpK/j/gVT/
E1R0pNFbb62ly3xx8yTfCON7nm0abY5WTtysJsYUoIGgjsHTKgQeRtRxykIPSrR0
8eeZpOStqAaDAJUzaHj9z+tBYgGnHBAmbdSFnwGjtSGWaNdtHIkOO0el9sDQS7X+
1lY4zX0kfy6kKhix4RNJET5AnsryepkSJDXRawTHTuCtuvkpbWkQ/T8XeY8rXQTK
KdmNe+BufxhyN4MSI0xg3A8NrwWBosnajcP2auCOZydKwhmVjTXTY6U84Fn4fBqe
AqJrSbCduRc=
=4lxl
-----END PGP SIGNATURE-----
--==_Exmh_1465547545_2073P--
