----- Original Message ----- From: "Gert Doering" <gert@space.net>
Our products may issue max N addresses per link from dhcp defined by the product specifications. Can I allocate 10 IPv6 addresses to a customer from our own pool, or does the customer need its own record in the DB ? If so, _must_ this allocation be a /64 even though the customer will only use 10 addresses?
[ ] Yes. [ ] No. [ ] Don't know.
The IPv6 end user assignment policies are pretty strict in that regard.
There is no option to give "10 addresses" to a user - period. When becoming LIR, you've signed that you'll follow the RIPE policies - and this is established RIPE policy.
So the whole question is moot.
I apologise if this is moot, but an answer would really be appreciated. This becomes a problem with private users as it already is today. We can't store data about every single private user into a public database, and there might also be issues regarding the privacy act. It breaks the "true spirit of IPv6"; "have enough addresses, and no questions asked". So basically we have a policy that is no or little different to the existing IPv4 policy, and private end-users can still only get one single address? Or am I totally wrong? How can I give 10, and only 10, addresses to a private customer without allocating the customer its own /64 ? Joergen Hovland