[189931] in North American Network Operators' Group
Re: Netflix banning HE tunnels
daemon@ATHENA.MIT.EDU (tim@pelican.org)
Fri Jun 10 02:19:26 2016
X-Original-To: nanog@nanog.org
Date: Fri, 10 Jun 2016 07:19:22 +0100 (BST)
From: "tim@pelican.org" <tim@pelican.org>
To: nanog@nanog.org
In-Reply-To: <0e36af3e-9781-4f2b-1080-af915fff3755@blakjak.net>
Errors-To: nanog-bounces@nanog.org
=0A=0AOn Friday, 10 June, 2016 05:48, "Mark Foster" <blakjak@blakjak.net> s=
aid:=0A=0A> Router-jockeys and purists often cite this. I've done it myself=
.=0A> But there are a lot more moving parts in most service providers than=
=0A> simply the ones and zeros.=0A> Bandwidth Accounting, Billing, Provisio=
ning systems in particular - and=0A> the developers/maintainers of these wh=
o have little or no knowledge of=0A> IPv6 and perhaps not a lot more than t=
hat of IPv4, except that it's more=0A> easily human-read and digested?=0A=
=0A+1. (Actually, +lots)=0A=0AMaking the packet-shifting tin shift v6 pack=
ets is not that complex, certainly not in the normal cycle of equipment upg=
rades, and assuming you started thinking about it years ago.=0A=0AAll the b=
usiness systems that sit around it? Not so much. $DAYJOB has plenty of co=
de, 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 m=
ake-the-field-bigger time. IT departments seem reluctant to provide that r=
esource, unless you've got people at the very top of the business bought in=
to the fact that you *need* to do IPv6. In my experience, the IT part of t=
he business, even within an ISP, tends to be the part that loves their NAT =
=3D=3D security and private addressing for everything[0], so just doesn't s=
ee what all the fuss is about...=0A=0AEven putting that aside, there are de=
cisions to be made as a business around how you present IPv6 to the custome=
r. Someone in Sales or Finance will want to be charging per /64 (or worse,=
per address). Support will want good canned answers to the "I have a publ=
ic address now - where is my NAT?" calls. Tech Pre-Sales will need upskill=
ing to think in networks, not addresses. Probably a whole bunch more.=0A=
=0ARegards,=0ATim.=0A=0A[0] In fairness, this is at least in part due to a =
decade of beatings from checklist-monkey auditors, but that's a different r=
ant.
