5 ms·
It's a protocol layer thing, mostly down to "what prefix sizes can I reasonably expect other providers to accept?" For IPv4 the answer was a /24; for IPv6 the
by namecast 11y ago
It's a protocol layer thing, mostly down to "what prefix sizes can I reasonably expect other providers to accept?"
For IPv4 the answer was a /24; for IPv6 the answer seems to
be a /64 at this point, and burning an entire /64 to get a couple of DNS servers (the typical use case for anycast) to resolve slightly faster is overkill. It's also probably a great way to annoy your RIR when they ask 'how the hell did you burn through your initial IPv6 delegation with only two hosts' ;)
EDIT: I meant /48, not /64! Whoops-a-doodle.
- detaro 11y agoIt's also probably a great way to annoy your RIR when they ask 'how the hell did you burn through your initial IPv6 delegation with only two hosts' Since /56 seems to become the "easily available standard size" for allocations, using a /64 doesn't seem like to much of an issue, especially since larger orgs should easily get /48s? (But are /64 really accepted as routes? I would have imagined that to be also limited to /56 or /60 or so)
- namecast 11y agoDepends on who's doing the accepting ;) I actually meant a /48, mea culpa! I'll leave this here: https://labs.ripe.net/Members/dbayer/visibility-of-prefix-lengths https://labs.ripe.net/Members/dbayer/visibility-of-prefix-le... It's from 2010-ish but still sadly relevant.
- detaro 11y agoOk, yes, "wasting" a /48 is a problem ;)