Protecting your contact information
Registering contact information
Administrative and technical contact persons must be registered.
The registered administrative contact (admin-c) must be someone who is physically located at the site of the network except for:
- Residential networks of users: The IRs technical contact may be registered as the admin-c.
- Networks in exceptional circumstances where it is impractical to maintain an onsite administrative contact. In such circumstances, an off-site person may be registered as the admin-c.
The technical contact (tech-c) need not be physically located at the site of the network but must be a person who is responsible for the day-to-day operations of the network.
Protecting your contact information
The APNIC Whois Database is an important source of information for the Internet community. Therefore, it is important that the information in the database is accurate and not vulnerable to unauthorized changes or additions. To protect objects, the APNIC Whois Database uses maintainer objects.
Authorization model
The APNIC Whois Database is based on a hierarchical structure. When objects are submitted to the APNIC Whois Database, the software checks that the person submitting the objects has the authority to update existing objects or create new objects within a hierarchical structure, such as hierarchical route or inetnum objects.
Registering authentication information
Authentication occurs when the database software checks the password or private key given in a submission against the password or public key lodged in the database. If the two match, the person making the email submission is authenticated.
Authorization occurs after the submission has been authenticated. The database checks that you are authorized to create or modify the object you submitted.
For objects to be changed, the email submission must include the authentication method of the maintainer object protecting the object. Hierarchical objects can only be created if you include the authentication method of the maintainer object or objects controlling the creation of objects within that hierarchy. If the object is associated with a hierarchy of objects (for example, hierarchical allocation and assignment inetnum objects), the software will check that you have permission to create, update, or delete objects within that hierarchy. Usually, this will be determined by the inclusion of higher objects maintainer objects' authorization methods in the submission.