You say that you are an "ISP", but then say that you need to go to "your ISP" to get IPv6 from them!? Confusing a bit that is ;) Nevertheless; there are several ways to get IPv6 address space: - From the RIR's - by becoming an LIR and then requesting a /32 (A /32 for 100 /48's is a bit overkill IMHO though) - (soon possible in RIPE region) by becoming an end-site and getting a contract with RIPE and then getting a /40 or /44 allocation from them depending on how much you will really need. In both cases you mean you need to manage your own ASN, do BGP, arrange and pay for transit etc. - From an upstream ISP (which means you are "locked" to them, unless you never swap upstream ISP or you don't mind renumbering everything) - Get a /40, /42 or /44 or so IPv6 allocation from them routed to you. In both cases you will most likely be paying for the bits sent anyway, thus the main difference there is if you need to pay either your ISP for the address space or the RIR and how much you wil have to pay for transit and equipment fees (a router at an IX, links there etc) or the ISP fees. Everything comes with a price. You didn't explain the model of your ISP though, thus how you hook up to your upstream ISP, or you hook up the downstream users (DSL, flat-ethernet?). If you can reach those WRTs natively then you can indeed easily ask your end-users to upgrade them to eg OpenWRT Kamikaze which has excellent support for IPv6 and then give them an IPv6 address on the link between them and you and then route them the /48. DHCPv6 and especially DHCPv6-PD (Prefix Delegation) is not installed per standard on routers yet unfortunately, also in most cases you will be giving out static allocations anyway (easier in management, administration, accounting, abuse-tracking etc etc) thus one won't need the PD part; which is also a bit horrible on the end-user end when the mechanism just changes the prefix all of a sudden, giving them a prefix when they ask for it is a much better option (and thus also why SixXS does it that way ;) Note that /48 for end-users has been discussed, and there are proposals for /56 for end-users (not end-sites like companies though). In the ARIN region this is already the case for some time, in RIPE region not yet, there we still calculate with /48s.