Good to see they're responding to the criticism so fast. Handing out /116's seems a bit of a weird choice, but that's not really a problem.
I'd be interested in hearing how they handle the routing within the data centers. Is it all just ethernet, and whoever uses ND (IPv6's ARP) to announce an address gets data to that address routed, or is are there some kind of subnets in between? How do they avoid someone stealing an address in your pool?
> My guess is that they're routing a /64 to each physical machine, and then /116s to the virtual systems.
That doesn't really work, as the /116 is shared among all nodes in the same DC. It also doesn't explain how SLAAC works, as all nodes in the DC get an address from the same pool (2600:3c01::/64 for instance).
The two most important updates since the original announcement are that Newark, NJ is now IPv6 enabled and that you can now get more than one IPv6 address for free.
"No forced migrations here" and the timing of this suggest to me that it's a competitive response to the bungled attempt by Rackspace to end-of-life Slicehost. Good for them.
(In their announcement, Rackspace rather listed IPv6 as the primary rationale for shutting down Slicehost.)
12 comments
[ 4.2 ms ] story [ 31.5 ms ] threadI'd be interested in hearing how they handle the routing within the data centers. Is it all just ethernet, and whoever uses ND (IPv6's ARP) to announce an address gets data to that address routed, or is are there some kind of subnets in between? How do they avoid someone stealing an address in your pool?
4096 addresses is much nicer than just one, so I'm thrilled to see this change. Switching over from a tunnel right now.
(In their announcement, Rackspace rather listed IPv6 as the primary rationale for shutting down Slicehost.)