Creating an IPv6 implementation plan

[Christian Hahn]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Petra Zeidler schrieb:
> Thus wrote Iljitsch van Beijnum (iljitsch at muada.com):
> 
>> On 22-aug-2007, at 18:25, Iljitsch van Beijnum wrote:
>>
>>>>   a. Can't find consensus on BCP for numbering this network.  It  
>>>> doesn't
>>>> help that we don't follow BCP for numbering in IPv4, but this  
>>>> might be an
>>>> opportunity to do things "right" - if I could figure out what that  
>>>> means.
>>> Set aside the all-zeros subnet for your servers,
>> I meant /48 block, not "subnet". This means you can give your DNS  
>> server 2001:db8::53 or something like that.
> 
> One added advice for the addressing plan: don't get too complicated.
> KISS is a great principle - eg for Iljitsch's advice "Allocation::/48
> is ourselves" is simple.
> Trying to code the make of the device into the address is not.
> 
> And don't attempt to conserve addresses as hard as you would with IPv4. :)
> Simple should win over less address use while you still manage to keep
> about a quarter of your allocation as planning reserve for changes.

Regarding your address planning you should consider reading
http://www.ietf.org/internet-drafts/draft-ietf-v6ops-addcon-05.txt
which contains also two case studies in addressing an IPv6 network.

best regards,
Christian
> 
> regards,
> 	Petra

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGzUgE6kMW7HW8620RAhacAJ9t+zyjhIx3lUfLE1h9fWOKDpeRMQCfSifm
JhrylTyR3l1rQwnAJtca1ts=
=4YbQ
-----END PGP SIGNATURE-----