On 9-mei-2005, at 12:46, Gert Doering wrote:
I ponder wether it would make sense to write up an example addressing plan for a /32 standard allocation which people can use as a template...
It would definitely be a nice thing to have.
This is what I came up with for two customers who are beginning IPv6 deployment. It works both for DSL and colocation. - assign each customer a 16-bit number (starting at 20 or so) - for each customer, use a dedicated /64 for between your/their stuff, like 2001:db8:a:<cust-id>::/64 - use the ...1 address on your end, such as 2001:db8:a:<cust-id>::1 - route a /48 to the ...2 address, such as 2001:db8:<cust-id>::/48 to 2001:db8:a:<cust-id>::2 - send router advertisements so hosts in the /64 can autoconfigure Customers can now either use just the /64 with autoconfiguration or the /48 but then they need to set up an IPv6 router. This is not as transparent as I'd like it to be, and it's also kind of wasteful because it uses up a /48 for every customer even if they're not going to use it. But I think simplicity is key here, at least at this point in time when the stuff isn't as automatic as it could be. Having a / 64 per customer is useful because that way you know which address goes with which customer. If you set up a shared /64 on a shared subnet you don't know which customer has which address.