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.

Download Report

Transcript 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.

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
grazing activities
after upgrading to whois v3
spam grazers are blocked (green)
Real load is only 50%
Database Usage
18,000,000
16,000,000
14,000,000
12,000,000
10,000,000
Queries
Blocked
Web Queries
8,000,000
6,000,000
4,000,000
2,000,000
0
Sep
Oct
Nov
Dec
Jan
Database Usage
80,000
70,000
60,000
50,000
40,000
Updates
30,000
20,000
10,000
0
Sep
Oct
Nov
Dec
Jan
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
Objects Statistics (end Jan 03)
inetnum
in-addr
inet6num
ip6.int/arpa
aut-num
mntner
person/role
as-block
as-set
route
173,145
47,258
934
1,217
2,415
6,590
116,010
7
29
627
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
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)
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