1. Whois Database Upgrade
Maintainer Administration
APNIC Database SIG September 3rd, 2002

2. Maintainer Administration
Whois v2
‘mnt-by’ attribute optional in ‘inetnum’ object
Many ‘inetnum’ objects have no maintainer
These objects are unprotected and at risk of unauthorised change
Whois v3
‘mnt-by’ attribute is mandatory
Upgrade from whois v2 to v3 creates need for database policy

3. Upgrade Status – Version 3
On all assignment and allocation ‘inetnum’ objects where no ‘mnt-by’ protection exists
‘maint-null’ has been inserted
Offers no protection
Temporary solution
Affected objects (as of 25 Aug 02)
7,736 out of 135,141 (6%)
scope problem
When was the last update
How many objects

4. Future Plan
Add maintainers automatically to all unmaintained ‘inetnum’ objects
Copy maintainer from encompassing object
These maintainers may belong to ISPs (APNIC Members) or APNIC
If unmaintained, take next level up
Implement immediately

5. Decision Process inetnum object range Maintainer APNIC-HM MAINT-MEMBER
APNIC range
APNIC-HM
last choice
APNIC member range
MAINT-MEMBER
1st choice
customer range
MAINT-NULL

6. Outcome Impact to APNIC Impact to APNIC Member
Additional workload for APNIC
Legal implications
AUNIC and ERX has same implications
Impact to APNIC Member
APNIC member maintainer will be added to many customer assignment records
Member will need to update customer records on behalf of the customer
May make ongoing changes, or add new maintainers for customers

7. Questions?