nanog mailing list archives
Re: Another v6 question
From: Per Carlson <pelle () hemmop com>
Date: Fri, 28 Jan 2011 10:10:00 +0100
Hi Owen.
The downside is that it doesn't provide enough bits for certain kinds of auto-topology management that are being considered by CE vendors. I highly recommend /48 instead.
I've seen this claim (you need a /48) from your side several times, but never seen any explanation why a /56 won't work. Is there any requirement that sub-delegations must happen on 8-bit boundaries? AFAICS there is at least nothing in the RFC. Wouldn't for example a nibble boundary work equally well (splitting a /56 into 16 /60s, each containing 16 /64s)? I don't challenge the claim, I'm just trying to understand the rationale behind it. -- Pelle RFC1925, truth 11: Every old idea will be proposed again with a different name and a different presentation, regardless of whether it works.
Current thread:
- Re: Another v6 question, (continued)
- Re: Another v6 question Roland Dobbins (Jan 26)
- Re: Another v6 question Max Pierson (Jan 27)
- Re: Another v6 question Mark Smith (Jan 30)
- Re: Another v6 question Jared Mauch (Jan 27)
- Re: Another v6 question Owen DeLong (Jan 27)
- /64 is "enough" until 2021 for 90% of users (was Re: Another v6 question) Jared Mauch (Jan 27)
- Re: /64 is "enough" until 2021 for 90% of users (was Re: Another v6 question) Mark Smith (Jan 30)
- Re: Another v6 question Valdis . Kletnieks (Jan 27)
- Re: Another v6 question Mikael Abrahamsson (Jan 27)
- Re: Another v6 question Owen DeLong (Jan 27)
- Re: Another v6 question Per Carlson (Jan 28)
- Re: Another v6 question Mark Andrews (Jan 28)
- Re: Another v6 question Jimmy Hess (Jan 27)
- Re: Another v6 question Jack Bates (Jan 27)