nanog mailing list archives
Re: IPv6, multihoming, and customer allocations
From: Owen DeLong <owen () delong com>
Date: Tue, 16 Mar 2010 09:17:02 -0700
On Mar 16, 2010, at 7:38 AM, Rick Ernst wrote:
Regurgitating the original e-mail for context and follow-up. General responses (some that didn't make it to the list): - "There really is that much space, don't worry about it." - /48s for those that ask for it is fine, ARIN won't ask unless it's a bigger assignment - /52 (or /56) on smaller assignments for conservation if it makes you feel better - Open question on whether byte/octet-boundary assignment (/56 vs /52) is better for some reason
Octet boundary, not really. Nibble boundary, yes. Both for DNS delegation convenience and for human factors issues.
I haven't seen anything on the general feel for prefix filtering. I've seen discussions from /48 down to /54. Any feel for what the "standard" (widely deployed) IPv6 prefix filter size will be?
So far, mostly it's /48 with a few select providers trying to hold the line at /32. Owen
Current thread:
- IPv6, multihoming, and customer allocations Rick Ernst (Mar 13)
- Re: IPv6, multihoming, and customer allocations Antonio Querubin (Mar 13)
- Re: IPv6, multihoming, and customer allocations Owen DeLong (Mar 13)
- Re: IPv6, multihoming, and customer allocations Rick Ernst (Mar 16)
- IPv6 filtering practices (Was: IPv6, multihoming, and customer allocations) Jeroen Massar (Mar 16)
- Re: IPv6, multihoming, and customer allocations Owen DeLong (Mar 16)
- Re: IPv6, multihoming, and customer allocations Joel Jaeggli (Mar 16)
- Re: IPv6, multihoming, and customer allocations Steve Bertrand (Mar 16)
- Re: IPv6, multihoming, and customer allocations Steve Bertrand (Mar 16)
