Shane Kerr. RIPE 45, May 2003, Barcelona. 1 Contact Data in the RIPE Database Shane Kerr RIPE NCC

Shane Kerr. RIPE 45, May 2003, Barcelona. 2 Background & Goal Certain kinds of data have caused problems –Domain objects (heavy use by ccTLD’s) –Person objects (heavy use by ccTLD’s, etc.) Cleanups have been made in the past –Consistency fixes –Deletions of unnecessary data, one-time and ongoing Small numbers of “inconsistencies” not a problem Perform some measurement of data quality

Shane Kerr. RIPE 45, May 2003, Barcelona. 3 Contact Data Contacts are: –Referenced by resources recorded in the Database –Administrative or technical Contacts have: –Name –Postal address –Phone number – address

Shane Kerr. RIPE 45, May 2003, Barcelona. 4 Focus on Name impossible to check Postal address/phone number difficult to check possible –Sadly optional for person objects

Shane Kerr. RIPE 45, May 2003, Barcelona. 5 Checking the addresses 1.Unique extracted (about 500,000 in all) 2.Syntax check to remove garbage and bad TLD 3.Unique domains extracted (about 280,000 in all) 4.DNS checked Algorithm from RFC 2821 MX lookups, with fallback to A lookups 5.SMTP checked VRFY unreliable Use RSET, MAIL, RCPT for each Minimise connections (only 140,000 unique IP’s)

Shane Kerr. RIPE 45, May 2003, Barcelona results

Shane Kerr. RIPE 45, May 2003, Barcelona. 7 “Refusal” Codes

Shane Kerr. RIPE 45, May 2003, Barcelona. 8 Interpreting the Results 20% of addresses can never be reached 80% may still fail –Depends on mail software and configuration –Impossible to check further without delivering mail –Even delivered mail may never be read

Shane Kerr. RIPE 45, May 2003, Barcelona. 9 aut-num results

Shane Kerr. RIPE 45, May 2003, Barcelona inetnum results A significant percentage of inetnum objects have no valid address. A much smaller percentage of actual IP addresses has no valid e- mail address, but still a significant amount. Most of these are because the “ ” attribute is optional in the person object. objects IP addresses reachable non-reachable no

Shane Kerr. RIPE 45, May 2003, Barcelona Conclusions & Questions Many networks have no reachable contacts “ ” being optional is a significant reason Is this a problem? If so, how big of a problem? Possible actions: –Make “ ” mandatory –Check reachability on person creation/update –Put a “remark:” on networks with unreachable contacts –Return parent networks if contacts unreachable