[116744] in North American Network Operators' Group
RE: IPv6 Addressing Help
daemon@ATHENA.MIT.EDU (Skeeve Stevens)
Sun Aug 16 03:57:23 2009
From: Skeeve Stevens <Skeeve@eintellego.net>
To: Jeroen Massar <jeroen@unfix.org>, Chris Gotstein <chris@uplogon.com>
Date: Sun, 16 Aug 2009 17:56:59 +1000
In-Reply-To: <4A85800A.6020703@spaghetti.zurich.ibm.com>
Cc: Nanog <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Really? You just say 'Gimme v6 please' to APNIC and they do.
--
Skeeve Stevens, CEO/Technical Director
eintellego Pty Ltd - The Networking Specialists
skeeve@eintellego.net / www.eintellego.net
Phone: 1300 753 383, Fax: (+612) 8572 9954
Cell +61 (0)414 753 383 / skype://skeeve
www.linkedin.com/in/skeeve ; facebook.com/eintellego
--
NOC, NOC, who's there?
> -----Original Message-----
> From: Jeroen Massar [mailto:jeroen@unfix.org]
> Sent: Saturday, 15 August 2009 1:18 AM
> To: Chris Gotstein
> Cc: Nanog
> Subject: Re: IPv6 Addressing Help
>=20
> Chris Gotstein wrote:
> > We are a small ISP that is in the process of setting up IPv6 on our
> > network. We already have the ARIN allocation and i have a couple
> > routers and servers running dual stack. Wondering if someone out
> > there would be willing to give me a few pointers on setting up my
> > addressing scheme?
>=20
> Strange, I recall that you had to submit one when requesting address
> space from ARIN. Why don't you use that one?
>=20
> > I've been mulling over how to do it, and i think i'm making it more
> > complicated than it needs to be. You can hit me offlist if you wish
> > to help. Thanks.
>=20
> It all depends on your network and how you want to set it up, but for
> the sake of internal aggregation:
> * Determine the expected amount of IPv6 customers at a certain
> location for the next X years, making X > 2 (though 10 is probably a
> better idea, just in case, if don't want to do it again ;) )
> * Take that number round it up to a power of 2
> * Every customer gets a /48, you know the number, which is a power of
> 2, thus root it, and you know how many bits you need at that site
>=20
> eg expect 200 customers, round to power of 2 thus 256, which is 2^8,
> thus you will need a /48 + 8 bits =3D /40 at that location.
>=20
> You now know how much address space you need at that location for the
> next X years.
>=20
> Repeat that for all your locations / routing areas, basically the PoPs
> or termination points of your customers; or if you are really big do
> that per city/town/suburb. Keep enough space (the rounding helps there
> quite a bit, especially with numbers like 50k customers ;)
>=20
> Now you have an overview of what you expect to be allocating at each
> and every site. To add a little growth/future proof and to make live
> easy, you could either opt at this stage to round everything off to
> 'nice'
> numbers, eg only use /40's or /36's per PoP. Thus making everything the
> same, or doing things like grouping smaller PoPs together.
>=20
> Then when you have done that, take those blocks, and try to squeeze
> them a bit together. You should now have arrived to the address plan
> that you originally submitted to ARIN.
>=20
> Fill those blocks into a nice database, roll a PHP/shell/perl/whatever
> script to spit out your router configuration and presto: you are done.
>=20
> Enjoy the weekend ;)
>=20
> Greets,
> Jeroen
>=20
