[172370] in North American Network Operators' Group
Re: Credit to Digital Ocean for ipv6 offering
daemon@ATHENA.MIT.EDU (Grzegorz Janoszka)
Tue Jun 17 15:56:00 2014
X-Original-To: nanog@nanog.org
Date: Tue, 17 Jun 2014 21:55:50 +0200
From: Grzegorz Janoszka <Grzegorz@Janoszka.pl>
To: nanog@nanog.org
In-Reply-To: <35DBEB1C-BCFD-4778-963C-208BF77219E6@virtualized.org>
Errors-To: nanog-bounces@nanog.org
On 2014-06-17 21:46, David Conrad wrote:
>>>> No, 8 individual IPv6 addresses.
>>> Wow. Harsh. I burn more than that just in my living room.
>> I don't think that is too harsh as all 8 are assigned to a single server. So if I have three VPS's, I have 24 total addresses.
> In the case of my 3 VPS's, I've received /64s from both RootBSD.net and Arp Networks or 55,340,232,221,128,654,848 addresses. I'm not sure I see a rationale for assigning 8 addresses. That is, I could understand assigning a single address or a /64 but 8 addresses? I'd think that'd be more complicated/error prone than either the /128 or /64 options. A bit odd.
There are still applications that break with subnet smaller than /64, so
all VPS providers probably have to use /64 addressing.
/64 for one customer seems to be too much, on the other side 8 IP's can
be not enough in some cases. I think 65536 out of shared /64 for one
server can be enough. You can easily automate provisioning and reverse
DNS assuming you assign /112 for each server.
If you block SLAAC and provide connectivity to only the static IP's,
your abuse folks should appreciate it (yes, I know you can spoof v6).
--
Grzegorz Janoszka
