[address-policy-wg] Registration of IPv6 DHCPv6-PD pools

Hi,

the current IPv6 Address Allocation and Assignment Policy (RIPE-481)
states:

http://www.ripe.net/ripe/docs/ripe-481.html#registration_assignment
=======================================================================
5.5. Registration

When an organisation holding an IPv6 address allocation makes IPv6
address assignments, it must register assignment information in a
database, accessible by RIRs as appropriate. (Information registered by
an RIR/NIR may be replaced by a distributed database for registering
address management information in future). Information is registered at
the granularity of End Site assignments. [...]
=======================================================================

Let's assume a residential eyeball network with $BIGNUM customers
provides a dynamic /56 via DHCPv6-PD to each customer by default,
from a large pool of /56s.

I'm not sure what the implications of above policy is, especially in
regards to the last sentence, "Information is registered at
the granularity of End Site assignments.". Given that the End Site
identity changes dynamically in a relatively high frequency, and
considering $BIGNUM in the 6 to 7 figure range, it certainly won't be
sensible pumping a $BIGNUM count of /56 inet6nums into the RIPE DB, all
with "descr: dynamic end site network". Unfortunately it seems that this
is actually required ny the policy though, wether in the RIPE DB or a DB
operated by the LIR in question, accessible to the NCC.

Providing dynamic networks to end sites instead of only single addresses
is something new to the community. I'm looking for clarification on how
we're going to handle those kind of deployments in regard of assignment
registration.

Best regards,
Daniel

-- 
CLUE-RIPE -- Jabber: dr at cluenet.de -- dr at IRCnet -- PGP: 0xA85C8AA0