Support Center

Registry Use Policy

The data found on and/or mirrored by NTTCOM Registry servers is strictly for Internet operational purposes only. It may not be used for any other purposes, such as advertising.

Background

The Global IP Network applies filters to routes advertised by customer BGP peers. These filters are built from the Internet Routing Registries (IRRs). Every route wished to be announced by a customer requires an exact prefix to be registered. This is a safeguard to help protect the Global IP Network (and the rest of the Internet) from accidental announcement of prefixes which do not belong to the ASN or similar errors which have caused other ISPs to have (multi-day) outages/instability. Once a customer registers a prefix, they can announce the prefix or any specifics covered by that prefix.

The routing registry whois server used by Global IP Network is the same software in use by the RADB. It conforms to RPSL syntax (see RFC2280, RFC2622, and ISC’s list of Tutorial Materials).

Thus, syntax of objects and operations are almost entirely the same. The only differences are the address for object submission, the hostname for queries, the source: is NTTCOM, and MAIL-FROM authentication is not accepted.

Service Expectations & Policy

Use of the NTTCOM Registry is being made available to Global IP Network customers (and their customers) free of charge. However, the following disclaimers apply:

• Mail to db-admin@rr.ntt.net and any other issues requiring manual intervention are handled Monday-Friday approximately 1700-0100 UTC. It may take up to 48 hour before the issue can be addressed. Automatic updates to auto-dbm@rr.ntt.net are normally immediate. Actual response time is likely to be better
• Although maintenance of the routing registry is done on a best-effort basis; the Global IP Network will not be responsible for lost data, lost service, etc. resulting from any failure of this service.
• Abuse this service will not be tolerated.
• You are responsible for the email addresses that you place in the NTT Commuications Global IP Network Routing Registry. Updates to NTTCOM Registry data result in email being sent to those addresses, and bad addresses produce bounced mail. The Global IP Network will make a reasonable effort to resolve errors, after which the failing address will be moved to a remark in the registry and will not be used in processing updates.
• The Global IP Network reserve the right to modify this policy at any time without notice.
• Customers who leave the Global IP Network will have 1 month to move their objects to another routing registry.
• The NTT Network Operations Center does not provide assistance with utilizing the NTTCOM Registry or setting up route objects, aut-num objects, and so on

Filter Updates

Filter updates (extraction of routes from the NTTCOM Registry and loading new filters onto the routers) are done by an automated process. PLEASE plan your changes ahead of time based on the timeline for update processing outlined in the rest of this section.

• Route lists are built at 0100 UTC. If there is an email address listed in the NTTCOM Registry, unix style uni-diffs will be emailed depicting any changes from the last build of the route list plus a copy of the full list and any errors encountered while expanding your as-set.
• Updated filters are loaded onto the routers and peers are soft-cleared at 0400 UTC.

Getting Started

The first step in making use of the NTTCOM Registry (like using the RADB) is to register a maintainer object (mntner). This object will be referenced by several other objects (including itself) for authentication and other purposes.

To register a maintainer object complete a maintainer object template and email it to the database administrator (db-admin@rr.ntt.net). The database administrator will insert the object in the NTTCOM Registry database and you will receive an acknowledgement.

Once the maintainer object is registered, all other object additions/changes can be done by using the automatic registry processor. You can add/delete/modify objects by emailing the completed template(s) to email address of the automatic registry processor: auto-dbm@rr.ntt.net.

Add an object:
Complete a template and email it.

Delete an object:
Use the existing object and add a “delete: reason” field to end and email it.

Modify an object:
Modify the existing object and email it.

Multiple adds/deletes/modifies may appear in one email message. Please click here for an example.

Time to create your objects.

Example

How to verify your Objects (making Queries)

Use whois and/or the IRRToolSet (version 4.7 or greater) to query the database for registered objects.

The Global IP Network maintains two servers. rr.ntt.net is the primary server (authoritative for the NTTCOM Registry database) and rr1.ntt.net is a backup.

For example, here is the Global IP Network as-set:

Mirroring the NTTCOM Registry database

NSPs wishing to mirror the NTTCOM Registry database should contact the db-admin@rr.ntt.net.