[135372] in North American Network Operators' Group
Re: Using IPv6 with prefixes shorter than a /64 on a LAN
daemon@ATHENA.MIT.EDU (Carlos Martinez-Cagnazzo)
Mon Jan 24 09:36:45 2011
In-Reply-To: <20110124142607.GA54584@macbook.catpipe.net>
Date: Mon, 24 Jan 2011 12:35:17 -0200
From: Carlos Martinez-Cagnazzo <carlos@lacnic.net>
To: Phil Regnauld <regnauld@nsrc.org>
Cc: bmanning@vacation.karoshi.com, nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Doing a little introspection, I found myself realizing that one of the
most bothersome aspects of the /64 boundary (for me, just speaking for
myself here) is exactly that, the tendency to the hardcoding of boundaries.
C.
On Mon, Jan 24, 2011 at 12:26 PM, Phil Regnauld <regnauld@nsrc.org> wrote:
> bmanning@vacation.karoshi.com (bmanning) writes:
>> =A0as a test case, i built a small home network out of =A0/120. works ju=
st fine.
>> my home network has been native IPv6 for about 5 years now, using a /96 =
and IVI.
>>
>> some thoughts. =A0disable RD/RA/ND.
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 none of the DHCPv6 code works like DHCP, so =
I re-wrote
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 client and server code so th=
at it does.
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 static address assignment is a good thing fo=
r services like DNS/HTTP
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 secure dynmaic update is your friend
>>
>> summary - its not easy, vendors don't want to help. =A0but it can be don=
e.
>
> =A0 =A0 =A0 =A0Right - /64 is an assumption that's hardcoded many places.
>
> =A0 =A0 =A0 =A0But it does work.
>
>
>
