Whois Database Upgrade Maintainer Administration APNIC Database SIG

Whois Database Upgrade Maintainer Administration APNIC Database SIG September 3 rd, 2002 sanjaya@apnic. net

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

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%)

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

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

Outcome • Impact to APNIC – 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

Questions?