Whois Update Guangliang Pan

Overview Differences between APNIC and RIPE Whois Databases Change mnt-by from member’s maintainer to APNIC-HM for aut-num object Create route objects for foreign AS numbers

Differences between APNIC and RIPE Whois Databases APNIC shares RIPE Whois database code APNIC modifies the code to meet our own policy requirements and have our own features For example: –APNIC policy requires a mandatory reference to an IRT (Incident Response Team) object in inetnum, inet6num and aut-num objects, but RIPE seems more prefer to use abuse-c in the organisation object now.

IRT vs abuse-c APNIC Whois - IRT is mandatory in inetnum object inetnum:... mnt-irt: [mandatory] … source: APNIC RIPE Whois – IRT is optional in inetnum object inetnum: … mnt-irt: [optional] … source: RIPE

How abuse-c work in RIPE Whois

Upgrade APNIC Whois APNIC Whois technical version is on v1.69 and RIPE Whois is on v1.81 We are planning to have a technical upgrade for APNIC Whois There are some new features for our consideration. We will post the details on the mailing list for comments. You can provide your feedback on whether APNIC should adopt those features.

Some new features for consideration Dry-run updates Pending Route Authorisation New query flags (--valid-syntax and --no-valid-syntax) New Attributes, eg: –Introduces the new attributes "created:" and "last-modified:" New role syntax Allow change the name of a person or role object

Change aut-num maintainer The aut-num object for an AS number is mnt-by member’s maintainer in APNIC whois to allow members to easily change their routing policy. From time to time, members accidentally deleted their aut- num and not able to put it back by themselves. Suggested to change the mnt-by from member’s maintainer to APNIC-HM. Members can easily update their aut-num via MyAPNIC if they changed their routing policy or contact person, but they are not able to delete the aut-num object.

Create route objects for foreign AS numbers Members can only create a route object when the inetnum (IP address range) and aut-num (AS Number) are both in APNIC Whois database. However, in some cases, your IP address range might need to be routed by an ASN which is not in APNIC whois. In such case, you can contact APNIC helpdesk. We will evaluate your request case by case and help you to create a route object if approved. For IP address ranges not under APNIC management, we suggest you contact the relevant RIR to get your route object created.

Questions? Thank you !