1 / 10

Whois DB Operational Update

Whois DB Operational Update. Database SIG APNIC-15, Taipei 26 February 2003. Overview . Database Usage Statistics Objects Statistics Changes Since Last DB-SIG Meeting Operational Plan Future Development. Database Usage. when using whois v2 many spikes indicates spam

ernst
Download Presentation

Whois DB Operational Update

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Whois DB Operational Update Database SIG APNIC-15, Taipei 26 February 2003

  2. Overview • Database Usage Statistics • Objects Statistics • Changes Since Last DB-SIG Meeting • Operational Plan • Future Development

  3. Database Usage when using whois v2 many spikes indicates spam grazing activities after upgrading to whois v3 spam grazers are blocked (green) Real load is only 50%

  4. Database Usage

  5. Database Usage

  6. Database Usage • Procedure to get bulk access (for research and non-spam use only) • Send e-mail to helpdesk@apnic.net • Sign agreement form • Send signed form to APNIC • APNIC will allow your nominated server to do bulk access

  7. Objects Statistics (end Jan 03)

  8. Latest Changes • Integration of routing registry function • previously under APIRR project • now both resource and routing information is available in whois.apnic.net • Deprecation of MAIL-FROM authentication

  9. Operations Plan • Installation of whois servers in multiple location for improved lookup service and availability • Requirement specification for large members to run their own whois servers (proposal to be presented later in this DB-SIG)

  10. Future Development • Upgrade to version 3.1.1 • allows synchronous update via web interface (either through MyAPNIC or APNIC public website) • implementation of MD5 authentication • Investigate the use of X.509 certificate for authentication • Ongoing liaison with RIPE on whois development

More Related