On 2010-12-15, at 16:36, John Russell wrote:
So, I'm looking at this ipv6 assignment from the
good folks at APNIC, and I'm also looking at my current, aging, not-very-scalable IP
Management system, and I'm not liking where I see this going.
I'm interested to hear NZNOGs suggestions about decent, scalable, software
(preferably off-the-shelf) to handle v4 and v6 IP management. Open source stuff welcome,
though commercial, supported software is also fine.
I'm just wondering what you cool kids are using to manage their address space these
Acquaintances who run ISPs here in Canada have dealt with the problem of v6 assignment a
little differently than they did with v4, and have generally not looked for a unified
v4/v6 assignment tool.
For example, suppose you've been assigned 2001:db8::/32, you don't expect to have
to handle more than 61,440 customers (and if you do wind up with more you can get another
/32), and you want to assign each customer, regardless of residential/business
distinction, with a /48. Further suppose that each customer has an identifier that can be
reduced to an integer, i, starting at 0x1000.
Then assign 2001:db8:i::/48 to customer i.
Everything between 2001:db8::/64 and 2001:db8:0fff::/64 (inclusive) can be used for Other
For internal bits and pieces I am partial to 2001:db8:<site>:<vlan>::/64
schemes which mean that your full documentation requirement reduces to a list of site
numbers and things that don't fit in vlans (e.g. loopback address, anycast addresses).
In my experience that's such a small amount of stuff that it can happily live in a
text file in subversion, or on a single internal neteng wiki page, or something similar.