- Billing & Accounting
- Service Level Agreements
- Policies & Procedures
If your company plans to establish a BGP connection to the NTTCOM network, you will need to have the appropriate objects registered in either the NTTCOM route registry or a registry that we mirror (see https://us.ntt.net/support/policy/routing.cfm#RR for list mirrored IRRs) for your connection to work properly. It is your responsibility to setup and maintain their route registry objects.
If your company has "downstream" BGP customers, those customers will need to have route objects created for their networks if they want to transit your NTTCOM connection.
The NTTCOM route registry is offered free of charge to NTT Communications customers. Customers are welcome to use whatever registry they prefer, as long as it is one that we mirror (see https://us.ntt.net/support/policy/routing.cfm#RR for list mirrored IRRs).
NTTCOM strongly encourages customers who rely on proxy objects (objects registered by a 3rd party) to duplicate their objects in the NTTCOM Route Registry to avoid any unforeseen downtime due to 3rd party manipulation or deletion of proxy objects.
NTTCOM advises customers who already use an IRR to duplicate their objects in the NTTCOM Route Registry to avoid any unforeseen downtime due to unexpected changes to objects registered in another IRR.
A maintainer-object links all other types of objects that may be registered in the route registry pertaining to a specific customer and their objects.
The maintainer-object contains several fields pertaining to the customer's company and the individuals in control of the route-policy (typically the network administrator). The field mntner: contains the maintainer ID. This maintainer ID is contained in the mnt-by: of all other object types (route-object, AS-Macro, aut-num) associated to the customer and their route-policy.
A route object is an object that specifies the network that a particular AS plans to announce. NTTCOM ACLs are built from these objects. NTTCOM only accepts "exact match" announcements, so route objects should be registered to match the customer announcements and AS Number. NTTCOM advises customers to aggregate announcements whenever possible.
An AS-SET object is used by NTTCOM customers that have downstream AS customers. This object allows NTTCOM to build ACLs based upon objects registered to all member ASes contained in the AS-SET, including the NTTCOM customer ASN.
Member ASes must have route objects registered in the NTTCOM registry or a registry NTTCOM mirrors for the ACLs to be updated.
Nested AS-SETs are permitted (eg. Downstream AS may have an AS-SET registered, this should be included in NTTCOM customer AS-SET).
- Command (where AS = 3727): server$ whois -h rr.ntt.net \!gas3727 - Response: A49 22.214.171.124/24 126.96.36.199/23 188.8.131.52/27 C
- Command (where network = 184.108.40.206/24): server$ whois -h whois -h rr.ntt.net 220.127.116.11 - Response: route: 18.104.22.168/23 descr: shrubs origin: AS3727 notify: email@example.com mnt-by: MAINT-HEAS changed: firstname.lastname@example.org 19991028 source: NTTCOM
A web based query tool can be found here:
- NTTCOM updates filters daily at 0000 UTC. Route objects submitted prior to 0000 UTC are included in this daily ACL build and are usually active on the network around 0600 UTC.
- Common errors to avoid:
BGP Advertisements must be an EXACT MATCH to route object entries.
Route Object: 22.214.171.124/24
Route Object: 126.96.36.199/16