Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>doma<strong>in</strong></strong>: <strong>Objects</strong><br />
<strong>in</strong> <strong>the</strong><br />
<strong>RIPE</strong> <strong>Database</strong><br />
Peter Koch<br />
<br />
DB WG, <strong>RIPE</strong> 57<br />
Dubai, 30-OCT-2008<br />
<strong>RIPE</strong> 57 DB WG <strong>RIPE</strong> DB <strong>doma<strong>in</strong></strong> objects 1 of 5
Time for a review<br />
• Bug <strong>in</strong>itiated closer look at all non-reverse <strong>doma<strong>in</strong></strong>: objects<br />
• Most ccTLDs had a s<strong>in</strong>gle object with refer: attribute<br />
• Few ccTLDs had additional material<br />
– <strong>in</strong>complete subset of all SLD registrations<br />
– some random 3LD entries<br />
– <strong>in</strong>consistent and/or outdated<br />
– ma<strong>in</strong>ta<strong>in</strong>ed by o<strong>the</strong>r mntner:s but <strong>the</strong> TLD registry<br />
• Only few ccTLDs seem to actively ma<strong>in</strong>ta<strong>in</strong> <strong>the</strong>ir entries<br />
<strong>RIPE</strong> 57 DB WG <strong>RIPE</strong> DB <strong>doma<strong>in</strong></strong> objects 2 of 5
How refer: works<br />
• Query for SLD.TLD will be proxied to given whois server<br />
• Queries (appear to) orig<strong>in</strong>ate from <strong>RIPE</strong> NCC’s proxy server<br />
• Orig<strong>in</strong>al client’s address optionally <strong>in</strong>cluded <strong>in</strong> proxied query<br />
• Query volumes average at 4 q/s <strong>in</strong> 2008<br />
<strong>RIPE</strong> 57 DB WG <strong>RIPE</strong> DB <strong>doma<strong>in</strong></strong> objects 3 of 5
Input from <strong>the</strong> DNS WG<br />
• CENTR members understand that <strong>the</strong> refer: attribute was a<br />
migration aid and those present had no objections aga<strong>in</strong>st remov<strong>in</strong>g<br />
<strong>the</strong>ir ccTLD <strong>doma<strong>in</strong></strong>: object from <strong>the</strong> <strong>RIPE</strong> database<br />
• Cleanup of <strong>the</strong> rema<strong>in</strong><strong>in</strong>g objects is seen as a matter of database<br />
hygiene and left to <strong>the</strong> discretion of <strong>the</strong> <strong>RIPE</strong> community<br />
• The DNS WG – pend<strong>in</strong>g confirmation on <strong>the</strong> list – did not see any<br />
cont<strong>in</strong>ued benefit <strong>in</strong> keep<strong>in</strong>g <strong>doma<strong>in</strong></strong>: objects<br />
• However, TLDs rely<strong>in</strong>g on <strong>the</strong> service should receive proper<br />
consideration and assistance<br />
<strong>RIPE</strong> 57 DB WG <strong>RIPE</strong> DB <strong>doma<strong>in</strong></strong> objects 4 of 5
Proposal to deal with <strong>doma<strong>in</strong></strong>: objects<br />
• Forward <strong>doma<strong>in</strong></strong>: objects to be phased out<br />
• Ask <strong>RIPE</strong> NCC to draft a schedule<br />
• Expect ma<strong>in</strong>ta<strong>in</strong>ers to remove <strong>the</strong>ir objects<br />
• Cleanup after deadl<strong>in</strong>e<br />
• Coord<strong>in</strong>ate early and actively with those ccTLDs us<strong>in</strong>g <strong>the</strong> <strong>RIPE</strong> DB as<br />
<strong>the</strong>ir whois data repository<br />
<strong>RIPE</strong> 57 DB WG <strong>RIPE</strong> DB <strong>doma<strong>in</strong></strong> objects 5 of 5
Change language