Randy Bush wrote:
You are right, we are moving only domain objects. The person objects will remain in the RIPE Database for several months.
and how will person:s work? in general, i am confused about this. e.g.
whois -h whois.ripe.net dom.ain
causes a referral to a domain: object with a tech-c: of <handle>-RIPE, or is it <handle>-DENIC?
<handle>-RIPE. This is a transition state which will last for several months.
if the former, <handle>-RIPE then it would seem that either o all the person:s stay at ripe database, or
All person objects will stay in the RIPE Database until moved to DENIC one (with different suffix).
o the person:s are mirrored from denic database to ripe database
if the latter, <handle>-DENIC, then it would seem that either o all the person:s are mirrored in the ripe database, or o the above whois query will not be able to show the requestor the person:s
in general there is a problem of duplication (or lack thereof as ripe seems uninclined to mirror any data except radb and apnic) as oposed to referral for handles. i am trying to understand the best practice we can muster now and what we might do in the future.
Current setup of the RIPE database requires that the database (source) should be self consistent - that is no external references are allowed. Referral mechanism for domains is different. I agree, duplication of handles is a problem, but so far it cannot be solved without violating referential integrity.
for the curious, i run the RGNET database at whois.rg.net. the purpose is twofold, referree for some cctlds and my routing data. radb mirrors these data but ripe does not. i am confused whether i am rb366 or rb366-arin, and in how many databases i need to maintain the person:s.
randy
Reagrds, Andrei Robachevsky DB Group Manager RIPE NCC