Transferring InterNIC space from ARIN Database to other RIR databases

Hi,

I may not have had my attention in focus when this was discussed the
last time around, so I hope you will excuse me for asking some simple
questions which may already have been given their reply.

I understand that what is happening is that the "master source" for
the affected registrations is being moved from (in our case) ARIN to
the RIPE NCC.

 o I suppose this means that in-addr.arpa updates will after this
   change be done only against the RIPE database for those pieces of
   address space which is transferred?

 o Can the RIPE NCC shed some light on how the in-addr.arpa zone
   generation will happen "behind the scenes" after this change?  E.g.
   what would the typical latency be between "update of registration
   data in the RIPE DB" to "visibility in the DNS"?

 o After the move of the authority for the data, what information will
   the ARIN database return when queried via whois?  A pointer to the
   RIPE NCC (as happens now for the larger RIPE address blocks), or a
   "slave" copy of of the data from the RIPE database?

I think this looks otherwise fine -- I suspect some of us will have to
do some tidy-up work in the aftermath of the move no matter what.

Regards,

- Håvard