Privacy of customer assignments

  1. Why are customer assignments being made private?
  2. What will happen when this policy is implemented?
  3. What if I want to keep my Whois records as they are?
  4. Can I update private records via an email to auto-dbm?
  5. Can the Whois update form on the public website see private records?
  6. How can I move objects between the APNIC Whois database and the private database?
  7. What if I don’t want to use MyAPNIC?
  8. Will related objects be affected?
  9. Can an inetnum that is referenced by a route object be removed from the database? Why?
  10. Can a route object creation refer to a private inetnum?

Why are customer assignments being made private?

At APNIC 16, there was consensus to adopt a policy proposal intended to protect the privacy of end users. Under the amended registration policy, LIRs are now able to decide whether or not their customer registration details should be publicly visible in whois.

What will happen when this policy is implemented?

The migration of database objects will take place on 30 September 2004. From this date, only those non-portable objects designated ‘public’ will be visible in the APNIC Whois Database, meaning that all non-portable objects (customer assignments) will cease to be visible in the database. Database queries on customer-assigned address space will be directed to the upstream provider’s registration information.

Portable allocations and assignments will be unaffected.

What if I want to keep my Whois records as they are?

If you would like your customer assignments to remain visible in the APNIC Whois Database, you will have to make them ‘public’ after the migration date. You can do this using MyAPNIC, or by contacting the APNIC helpdesk.

Can I update private records via an email to auto-dbm?

No. auto-dbm is a public tool, and does not allow you to access private objects. APNIC will provide an alternative tool to manage private objects through an automated process, but the implementation schedule for this tool has not yet been finalised.

Can the Whois update form on the public website see private records?

No. Only the Whois update form on MyAPNIC can see private records.

How can I move objects between the APNIC Whois database and the private database?

You can change the status of your resource records using MyAPNIC.

What if I don’t want to use MyAPNIC?

APNIC recommends that members use MyAPNIC to manage their resources; however, those not using MyAPNIC can contact APNIC helpdesk and have all of their resources restored to ‘public’ status. The resources can then be managed as usual.

This project is concerned with inetnum and inet6num objects. Related objects such as route objects, maintainer objects, and nic-handles will not be affected.

It is up to the member to delete related objects (e.g. maintainers, nic-handles) if they are no longer needed. APNIC also has a regular data cleaning process to remove unreferenced objects in the APNIC Whois Database.

Can an inetnum that is referenced by a route object be removed from the database? Why?

Yes, because a route object only refers to an inetnum during creation of the route object itself (in order to check maintainer authorisation). Once created, the route object no longer refers to the inetnum.

Can a route object creation refer to a private inetnum?

No. When you create a route object it must refer to a publicly viewable inetnum.