Support Center
Create Routing Registry Objects
1. The first thing you will need to do is create a Maintainer Object and Person Object. A Maintainer Object links all your other types of objects together, a Person Object provides contact details for each object and is referenced through the admin-c/tech-c attributes. Cut and paste template into your email and fill out each field appropriately. Mouse over for directions. Note: if you do not fill in an optional field then remove field completely. A submitted template with a blank field will automatically be rejected.
---------------------- CUT HERE ------------------- mntner: descr: admin-c: tech-c: upd-to: mnt-nfy: auth: remarks: notify: mnt-by: changed: source: person: address: phone: e-mail: nic-hdl: mnt-by: changed: source: ---------------------- CUT HERE -------------------
Example Maintainer Object
mntner: MAINT-NTTCOM-BB
descr: Global IP Network (GIN) maintainer
admin-c: NCGE-VRIO
tech-c: NCGE-VRIO
upd-to: ip-eng-reports@us.ntt.net
mnt-nfy: ip-eng-reports@us.ntt.net
auth: CRYPT-PW feiubf2iubf2
remarks: contacts per RFC2142:
remarks: Abuse / UCE reports abuse@ntt.net
remarks: Security issues security@ntt.net
notify: ip-eng-routing@us.ntt.net
mnt-by: MAINT-NTTCOM-BB
changed: boudreat@us.ntt.net 20190701
source: NTTCOM
Example Person Object
person: Global IP Network (GIN) Engineering address: 8300 E Maplewood Ave. Suite 400 Greenwood Village, CO 80111 US phone: +1 877-688-6625 e-mail: ip-eng@us.ntt.net nic-hdl: NCGE-VRIO remarks: For security issues contact security@ntt.net mnt-by: MAINT-NTTCOM-BB changed: chowser@us.ntt.net 20180823 source: NTTCOM
2. You will need an *AS (aut-num) Object*. This object lets others know others about the ASN such as POC information and routing policy.
---------------------- CUT HERE ------------------- aut-num: as-name: descr: import: export: default: member-of: admin-c: tech-c: remarks: notify: mnt-by: changed: source: ---------------------- CUT HERE -------------------
Example as (aut-num)
aut-num: AS2914
as-name: NTTC-GIN-AS
descr: Global IP Network
admin-c: VP8-ARIN
tech-c: VP8-ARIN
import: from as93 accept AS93
import: from as3727 accept AS-HEAS
import: from as103 accept as103
import: from as10368 accept as10368
[... many import lines deleted ...]
export: to as93 announce AS-NTT
export: to as3727 announce ANY
export: to as103 announce as-ntt
export: to as10368 announce as-ntt
[... many export lines deleted ...]
remarks: peers should accept as-ntt
mnt-by: MAINT-NTTCOM-BB
changed: boudreat@us.ntt.net 20060518
source: NTTCOM
3. If you have BGP customers yourself, you will need an *AS-set Object*. The NTTCOM Registry will then look for objects for each ASN listed in the AS-set in order to add their prefixes to your BGP prefix filter.
---------------------- CUT HERE ------------------- as-set: descr: members: admin-c: tech-c: remarks: notify: mnt-by: changed: source: ---------------------- CUT HERE -------------------
as-set example
as-set: AS2914:AS-GLOBAL
descr: Global IP Network transit customers
members: AS2914, AS3949,
AS2914:AS-US, AS2914:AS-ASIA, AS2914:AS-EUROPE
admin-c: NCGE-VRIO
tech-c: NCGE-VRIO
remarks: contacts per RFC2142:
remarks: Abuse / UCE reports abuse@ntt.net
remarks: Security issues security@ntt.net
mnt-by: MAINT-NTTCOM-BB
changed: boudreat@us.ntt.net 20060825
source: NTTCOM
person: Global IP Network Engineering
address: NTT
8005 S Chester St Ste 200
Centennial, CO 80112-3523
US
phone: +1 303 6451900
fax-no: +1 303 7082490
e-mail: ip-eng@us.ntt.net
nic-hdl: NCGE-VRIO
remarks: contacts per RFC2142:
remarks: Abuse / UCE reports abuse@ntt.net
remarks: Security issues security@ntt.net
mnt-by: MAINT-NTTCOM-BB
changed: boudreat@us.ntt.net 20060824
source: NTTCOM
4. You will need to add a *Route Object* for each specific prefix your ASN plans to announce (originate).
---------------------- CUT HERE ------------------- route: descr: origin: member-of: remarks: notify: mnt-by: changed: source: ---------------------- CUT HERE -------------------
route example:
route: 129.250.0.0/16
descr: NTTCOM bb
origin: AS2914
remarks: this is non-portable space, no exceptions
mnt-by: MAINT-NTTCOM-BB
changed: heas@shrubbery.net 19990619
source: NTTCOM
v6 route example:
route6: 2001:418::/32
descr: NTT
origin: AS2914
remarks: this is non-portable space, no exceptions
remarks: contacts per RFC2142:
remarks: Abuse / UCE reports abuse@ntt.net
remarks: Security issues security@ntt.net
mnt-by: MAINT-NTTCOM-BB
changed: boudreat@eng.verio.net 20070728
source: NTTCOM
This is the “Key-Cert Object” template for those who want to use PGP key instead of Crypt-PW (see mouse-over for “auth:” at top of page).
---------------------- CUT HERE ------------------- key-cert: [mandatory] [single] [primary/look-up key] method: [generated] [single] [ ] owner: [generated] [multiple] [ ] fingerpr: [generated] [single] [ ] certif: [mandatory] [single] [ ] remarks: [optional] [multiple] [ ] notify: [optional] [multiple] [inverse key] mnt-by: [mandatory] [multiple] [inverse key] changed: [mandatory] [multiple] [ ] source: [mandatory] [single] [ ] ---------------------- CUT HERE -------------------
Get More Information
Get Started
To find out which solutions will best benefit your business, contact one of our Account Managers.
Stay Connected
Contact the Global IP Network Team
Thank you for your interest in the Global IP Network.
Please click the button below and fill out the form, and a representative will contact you shortly.
NTT DATA | Global IP Network
NTT DATA is a global leader in all Internet-related businesses. Our Tier 1 Global IP Network, consistently ranked among the top networks worldwide, spans the Americas, Europe, Asia and Oceania, providing a premier environment for content, data and video transport through a single Autonomous System Number (AS2914).
© 2025 NTT DATA | Global IP Network
