Whois DB Operational Update

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

description

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 - PowerPoint PPT Presentation

Transcript of Whois DB Operational Update

Page 1: Whois DB Operational Update

Whois DB Operational Update

Database SIG

APNIC-15, Taipei

26 February 2003

Page 2: Whois DB Operational Update

Overview

• Database Usage Statistics

• Objects Statistics

• Changes Since Last DB-SIG Meeting

• Operational Plan

• Future Development

Page 3: Whois DB Operational Update

Database Usage

when using whois v2many spikes indicates spam grazing activities

after upgrading to whois v3spam grazers are blocked (green)Real load is only 50%

Page 4: Whois DB Operational Update

Database Usage

0

2,000,000

4,000,000

6,000,000

8,000,000

10,000,000

12,000,000

14,000,000

16,000,000

18,000,000

Sep Oct Nov Dec Jan

Queries

Blocked

Web Queries

Page 5: Whois DB Operational Update

Database Usage

0

10,000

20,000

30,000

40,000

50,000

60,000

70,000

80,000

Sep Oct Nov Dec Jan

Updates

Page 6: Whois DB Operational Update

Database Usage

• Procedure to get bulk access (for research and non-spam use only)– Send e-mail to [email protected]– Sign agreement form– Send signed form to APNIC– APNIC will allow your nominated server

to do bulk access

Page 7: Whois DB Operational Update

Objects Statistics (end Jan 03)

inetnum 173,145

in-addr 47,258

inet6num 934

ip6.int/arpa 1,217

aut-num 2,415

mntner 6,590

person/role 116,010

as-block 7

as-set 29

route 627

Page 8: Whois DB Operational Update

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

Page 9: Whois DB Operational Update

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)

Page 10: Whois DB Operational Update

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