Customer Zone
Global IP Network Map
The Looking Glass
Routing Policy
Get More Information
Product Collateral
Case Studies
White Papers
Audio & VideoGet Started
To find out which solutions will best benefit your business, contact one of our Account Managers.
Click Here to Get Connected
Call us at 1-877-868-8638
Stay Connected
Follow Us on Twitter
Friend Us on Facebook
Join Us on LinkedInRouting Registry
- Registry Use Policy
- Background
- Service Expectations & Policy
- Filter Updates
- Getting started
- Object Templates
- PGP authentication
- Queries
- Mirroring the routing registry database
The scope of this document is limited to the routing registry maintained by the NTT Communications Global IP Network. Please see Merit's RADB site for more complete information about routing registries in general.
Attn: On Saturday, March 31, 2007, the NTT / Verio Routing Registry was replaced with the NTT Communications Global IP Network Routing Registry, all data with source: Verio was converted to source NTTCOM. All route objects submitted after March 31, 2007, need to reference source: NTTCOM.
The IP addresses of the route registry servers did not change. They were renamed to rr.ntt.net and rr1.ntt.net.
Registry Use Policy
The data found on and/or mirrored by NTT Communications Global IP Network Routing Registry servers is strictly for Internet operational purposes only. It may not be used for any other purposes, such as advertising.Background
The NTT Communications 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 NTT Communications Global IP Network (and the rest of the Internet) from accidental announcement of prefixes which do not belong to the ASN, accidental announcement of every /32 within an IPv4 prefix, and similar errors which have caused other ISPs to have (multi-day) outages/instability.The routing registry whois server used by NTT Communications 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 NTT Communications Global IP Network Routing Registry is being made available to NTT Communications 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 NTT Communications 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 NTT Communications Global IP Network Routing Registry data result in email being sent to those addresses, and bad addresses produce bounced mail. The NTT Communications 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 NTT Communications Global IP Network reserve the right to modify this policy at any time without notice.
- Customers who leave the NTT Communications Global IP Network will have 1 month to move their objects to another routing registry.
- The NTT Communications Network Operations Center does not provide assistance with utilizing the NTT Communications Global IP Network Routing Registry or setting up route objects, aut-num objects, and so on
Filter Updates
Filter updates (extraction of routes from the NTT Communications Global IP Network Routing 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 objects registered in the other registries must be completed by 0000 UTC to insure they are mirrored in the NTT Communications Global IP Network server by the time the route lists are built. Use of the CANET and SAVVIS registries is discouraged due to the mirroring process these two registries use.
- Route lists are built at 0100 UTC. If there is an email address listed in the NTT Communications Global IP Network Routing 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.
Using PGP authentication
To use PGP with the NTT Communications Global IP Network Routing Registry, each user expecting to submit object updates authenicated by PGP must provide a PGP public key (RSA or DSS). These keys have to be registered in the database (source:) via a key-cert object (see Object Templates). A maintainer object (mntner) must be registered first, followed by the key-cert(s) and then PGP auth can be added to the maintainer.To register a key-cert, extract a copy your public key. Here is an example using PGP 2.62 on a unix-like system (e.g. Linux, FreeBSD and others):
% pgp -kxa heas /tmp/pubkey
Pretty Good Privacy(tm) 2.6.2 - Public-key encryption for the masses.
(c) 1990-1994 Philip Zimmermann, Phil's Pretty Good Software. 11 Oct 94
Uses the RSAREF(tm) Toolkit, which is copyright RSA Data Security, Inc.
Distributed by the Massachusetts Institute of Technology.
Export of this software may be restricted by the U.S. government.
Current time: 2000/09/29 03:49 GMT
Extracting from key ring: '/home/heas/.pgp/pubring.pgp', userid "heas".
Key for user ID: John Heasley <heas@shrubbery.net>
1024-bit key, Key ID 7A774C09, created 1996/12/20
Transport armor file: /tmp/pubkey.asc
Key extracted to file '/tmp/pubkey.asc'.
The key-cert: value is PGPKEY-<key ID>, PGPKEY-7A774C09 in this example.
The content of /tmp/pubkey.asc is:
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.6.2
mQCNAjK6S8cAAAEEAM4de4EPalJsDOsaSlOBRhDGLlSxRetZz532lPRL9rx0wkvL
4U0mzSI2jppKjJJhvkwIkMsHd3yz3Vbpm/4HydPtCZc3/+kjC//myjdOMCK44ED4
E42pt6Wgg8Ik0cOTqYexZ0qV/ci2aOMyXK+VbVGG1ZTK4SvsbEsr3VJ6d0wJAAUR
tCFKb2huIEhlYXNsZXkgPGhlYXNAc2hydWJiZXJ5Lm5ldD6JAJUDBRA4UBPSD28L
lepPzu8BAaN7A/9Q5FXm/WimNUe+iPBX/zznfUBkUpxpIy4yFApIKI68zslmxwdV
975YT0t/ftVJtCCNjrhPD/4RI9kqDQqJMlh0hwYFTV+t/DFTvZ33wsklt/+Q4qLb
4/AEdKpveG00seNt4R5UymD+NVK2fpmx2SJuHLQoh1tDo09KafmjOyCrmYkAlQMF
EDhOvbTSMEkkdQ6DSQEBcbwD/jnrwtXpMPQmWYb12FLdmlMNGbV4ESxt8QXfgVra
w14KQJ4P9lToT9Tmqe9Q4NFcKRs/00Q4xlRWwdPuFF4QGOJxBLnE1Xv60rY9eY2Q
i3DRbRiDw0YgK1xgscRHeRq1giTc2NWFb11KlzV5qciWWDjpx6t01v9Vn59xCCbW
kEdziQCVAwUQNWRxjfay2HvjD8wlAQGZlAP/SenlqYAfmSVZ/s5st9zA43hXQnNR
oJeXvFW5kutGAuGOGXZInXB/q9HtoLrngA9PlWHNs+kDP3ipFh9+jyeojQm5fQ94
R7yMRgupGZJ9WfUQRA1nvB+HmXfRg9bZ5FNoewrCO6aawhEnZ8D7HIrHRz+sH9Mi
mufkPEARFgZ6F4GJAJUDBRA3eUEYT5ggX09IZTEBARGSBACZrW+GXCFHG5gPmeVX
cOKcKCE18NyYlah0Pd72y15sJy8GyGIFTpDEDRRE//mQwIWaLV4eehuzHz0ygMm5
HI4k7FlrHpJqq5/g6pM1zQohvqY53imUbhf4WBzgrvPrfTM/2jaWCb8OBNBCHpiT
oKWkTqqvK99ScKkf+F+HJMa4ookAdQMFEDNaCL+6FAGUXCurYQEBLp4C/26hjz7e
5gtlvfM+rdHNAZY+HUhZRty6kOyWJsMu1s9PDlTbljwdTz7cJ141jww6F8JCYGt4
SfbeT1Mz7MDzgz8jXO710KOwzmOIqupUUUnuw0bMhIMZzhPm6+0OeZgCSYkAlQMF
EDXVCFcImkdUx0QebQEBjf0EAKyDniKogR5CPn3zIUHAmroHMKiDdMEFsZv4Ih0m
ERymLH0m2YLePS2lBnwg4ZsIlj0OVksJLgoSb8V3TM1a2ykBkldySha3dHRE0g8J
QDQ1c2QgGd5SHdBFZY0FNbKj1XbCqxN0ZdmRay5l7UxD532xXA+TZ0LZwkaYcamP
fjW1iQCVAwUQNBUPkPTPnXJdMaXhAQECgwP/f39qTwHAQEj/fxtbH4wmmsDjo8d0
FJ/MZsSMSiF0PDbAkvb/krY4Xr4MI1MNNosUJ6f4ZHMGLIzYGYeLyy1jD8KLMDjZ
DdJI+eKG46iHHLpcAlYeKhfZqEB16+t44mGW6cKyUellk0cUd7nK2ZPj+/u/4ziN
JekadG1899vuHzSJARUDBRAzTJh364x/pH7NgKUBAZrkB/4sDhJ54578Ze+ci9wM
OaaTlIsH8YGWskZ1Y+Hj8XiLX4euUXDqd9SFs9RBrzMx7edlE8Q1N9cLAPVCKr8d
swhb2K7Tgmpwrhe6KpNUa6PSCv6t11gc17QiFzJGoYSAAl7UnJjx9zFAMjfeo+id
O0clhPMWC6pvB2rNoBMNt+vRXpq7ApWF8CSudwWf277BrKGC8TbwC/ntMtS4ZcjR
S9Tl/5EMdHgMKqQt+wJx/g1o6g2d0xz65IoNDhpScetkSQXjFh20olcts0ZnQRhp
W7J9kAEFG9/Yr8GIB7eUjsOr1XIlhMNqwOkqfu9px3eM3ntBjJOZM/WbHWm1KYc4
2/hciQCVAwUQMrtgE0sr3VJ6d0wJAQFisgP/TDmqElXnB+h9MldnsnnZ7VgDLhHY
+hv8EP9aVd/w2oOR3ZKhYYFcbBnmOvPp34SxaBMf3KSqhEQ22tAfOoQkhIDQs0oj
DtB4mTmtlQNHFVlbD914eHxIYEznrr7Nw2xqo/GgA+lEC0hrZx2itrIHcZgojE3q
T42/v4ja9lTNq1OJAJUDBRAyu0Gn+8I/jbEzFDkBAarXA/99R9ATMI8NSVIX3V0z
Js2oIjC/jKbvstVhR7E+yx49hqRWBtVDCT65IiR2pyf4rl9M+tekbKununIBhjny
yXcMkK96fbBrFQA3c2pqSLKhXNFrEdapV0874VgwVfW4938xi5oCfV/nPT6lYgdo
H6/eLL6MCx9ga0q87NGUdh0naw==
=OlpC
-----END PGP PUBLIC KEY BLOCK-----
The contents of /tmp/pubkey.asc becomes the value of certif: in
the key-cert object. Since the public key is greater than one
line, the line continuation character (+) must be prepended to
the beginning of each line following the first. Be sure that you do not
supply any of the [generated] tokens, as noted in the
key-cert template. Therefore, the object submitted to register this
key-cert is:
key-cert: PGPKEY-7A774C09
certif:
+-----BEGIN PGP PUBLIC KEY BLOCK-----
+Version: 2.6.2
+
+mQCNAjK6S8cAAAEEAM4de4EPalJsDOsaSlOBRhDGLlSxRetZz532lPRL9rx0wkvL
+4U0mzSI2jppKjJJhvkwIkMsHd3yz3Vbpm/4HydPtCZc3/+kjC//myjdOMCK44ED4
+E42pt6Wgg8Ik0cOTqYexZ0qV/ci2aOMyXK+VbVGG1ZTK4SvsbEsr3VJ6d0wJAAUR
+tCFKb2huIEhlYXNsZXkgPGhlYXNAc2hydWJiZXJ5Lm5ldD6JAJUDBRA4UBPSD28L
+lepPzu8BAaN7A/9Q5FXm/WimNUe+iPBX/zznfUBkUpxpIy4yFApIKI68zslmxwdV
+975YT0t/ftVJtCCNjrhPD/4RI9kqDQqJMlh0hwYFTV+t/DFTvZ33wsklt/+Q4qLb
+4/AEdKpveG00seNt4R5UymD+NVK2fpmx2SJuHLQoh1tDo09KafmjOyCrmYkAlQMF
+EDhOvbTSMEkkdQ6DSQEBcbwD/jnrwtXpMPQmWYb12FLdmlMNGbV4ESxt8QXfgVra
+w14KQJ4P9lToT9Tmqe9Q4NFcKRs/00Q4xlRWwdPuFF4QGOJxBLnE1Xv60rY9eY2Q
+i3DRbRiDw0YgK1xgscRHeRq1giTc2NWFb11KlzV5qciWWDjpx6t01v9Vn59xCCbW
+kEdziQCVAwUQNWRxjfay2HvjD8wlAQGZlAP/SenlqYAfmSVZ/s5st9zA43hXQnNR
+oJeXvFW5kutGAuGOGXZInXB/q9HtoLrngA9PlWHNs+kDP3ipFh9+jyeojQm5fQ94
+R7yMRgupGZJ9WfUQRA1nvB+HmXfRg9bZ5FNoewrCO6aawhEnZ8D7HIrHRz+sH9Mi
+mufkPEARFgZ6F4GJAJUDBRA3eUEYT5ggX09IZTEBARGSBACZrW+GXCFHG5gPmeVX
+cOKcKCE18NyYlah0Pd72y15sJy8GyGIFTpDEDRRE//mQwIWaLV4eehuzHz0ygMm5
+HI4k7FlrHpJqq5/g6pM1zQohvqY53imUbhf4WBzgrvPrfTM/2jaWCb8OBNBCHpiT
+oKWkTqqvK99ScKkf+F+HJMa4ookAdQMFEDNaCL+6FAGUXCurYQEBLp4C/26hjz7e
+5gtlvfM+rdHNAZY+HUhZRty6kOyWJsMu1s9PDlTbljwdTz7cJ141jww6F8JCYGt4
+SfbeT1Mz7MDzgz8jXO710KOwzmOIqupUUUnuw0bMhIMZzhPm6+0OeZgCSYkAlQMF
+EDXVCFcImkdUx0QebQEBjf0EAKyDniKogR5CPn3zIUHAmroHMKiDdMEFsZv4Ih0m
+ERymLH0m2YLePS2lBnwg4ZsIlj0OVksJLgoSb8V3TM1a2ykBkldySha3dHRE0g8J
+QDQ1c2QgGd5SHdBFZY0FNbKj1XbCqxN0ZdmRay5l7UxD532xXA+TZ0LZwkaYcamP
+fjW1iQCVAwUQNBUPkPTPnXJdMaXhAQECgwP/f39qTwHAQEj/fxtbH4wmmsDjo8d0
+FJ/MZsSMSiF0PDbAkvb/krY4Xr4MI1MNNosUJ6f4ZHMGLIzYGYeLyy1jD8KLMDjZ
+DdJI+eKG46iHHLpcAlYeKhfZqEB16+t44mGW6cKyUellk0cUd7nK2ZPj+/u/4ziN
+JekadG1899vuHzSJARUDBRAzTJh364x/pH7NgKUBAZrkB/4sDhJ54578Ze+ci9wM
+OaaTlIsH8YGWskZ1Y+Hj8XiLX4euUXDqd9SFs9RBrzMx7edlE8Q1N9cLAPVCKr8d
+swhb2K7Tgmpwrhe6KpNUa6PSCv6t11gc17QiFzJGoYSAAl7UnJjx9zFAMjfeo+id
+O0clhPMWC6pvB2rNoBMNt+vRXpq7ApWF8CSudwWf277BrKGC8TbwC/ntMtS4ZcjR
+S9Tl/5EMdHgMKqQt+wJx/g1o6g2d0xz65IoNDhpScetkSQXjFh20olcts0ZnQRhp
+W7J9kAEFG9/Yr8GIB7eUjsOr1XIlhMNqwOkqfu9px3eM3ntBjJOZM/WbHWm1KYc4
+2/hciQCVAwUQMrtgE0sr3VJ6d0wJAQFisgP/TDmqElXnB+h9MldnsnnZ7VgDLhHY
++hv8EP9aVd/w2oOR3ZKhYYFcbBnmOvPp34SxaBMf3KSqhEQ22tAfOoQkhIDQs0oj
+DtB4mTmtlQNHFVlbD914eHxIYEznrr7Nw2xqo/GgA+lEC0hrZx2itrIHcZgojE3q
+T42/v4ja9lTNq1OJAJUDBRAyu0Gn+8I/jbEzFDkBAarXA/99R9ATMI8NSVIX3V0z
+Js2oIjC/jKbvstVhR7E+yx49hqRWBtVDCT65IiR2pyf4rl9M+tekbKununIBhjny
+yXcMkK96fbBrFQA3c2pqSLKhXNFrEdapV0874VgwVfW4938xi5oCfV/nPT6lYgdo
+H6/eLL6MCx9ga0q87NGUdh0naw==
+=OlpC
+-----END PGP PUBLIC KEY BLOCK-----
mnt-by: MAINT-HEAS
changed: heas@shrubbery.net 20000928
source: NTTCOM
password: foo
Note the use of the CRYPT-PW authentication password for the maintainer
MAINT-HEAS. Then, the PGP authentication information must be
added to the maintainer object. For example:
mntner: MAINT-HEAS
descr: shrubbery maintainer
admin-c: JH636
tech-c: JH636
upd-to: heas@shrubbery.net
mnt-nfy: heas@shrubbery.net
auth: CRYPT-PW za/0jxyxoQNJQ
auth: PGPKEY-7A774C09
notify: heas@shrubbery.net
mnt-by: MAINT-HEAS
changed: heas@shrubbery.net 20000928
source: NTTCOM
password: foo
Once the server has acknowleged the maintainer object update, further object updates can be authenticated with PGP. For example:
% cat /tmp/mntner
mntner: MAINT-HEAS
descr: shrubbery.net maintainer
admin-c: JH636
tech-c: JH636
upd-to: heas@shrubbery.net
mnt-nfy: heas@shrubbery.net
auth: CRYPT-PW za/0jxyxoQNJQ
auth: PGPKEY-7A774C09
notify: heas@shrubbery.net
mnt-by: MAINT-HEAS
changed: heas@shrubbery.net 20000928
source: NTTCOM
% pgp -sta /tmp/mntner
Pretty Good Privacy(tm) 2.6.2 - Public-key encryption for the masses.
(c) 1990-1994 Philip Zimmermann, Phil's Pretty Good Software. 11 Oct 94
Uses the RSAREF(tm) Toolkit, which is copyright RSA Data Security, Inc.
Distributed by the Massachusetts Institute of Technology.
Export of this software may be restricted by the U.S. government.
Current time: 2000/09/29 04:11 GMT
A secret key is required to make a signature.
You need a pass phrase to unlock your RSA secret key.
Key for user ID "John Heasley <heas@shrubbery.net>"
Enter pass phrase: Pass phrase is good.
Key for user ID: John Heasley <heas@shrubbery.net>
1024-bit key, Key ID 7A774C09, created 1996/12/20
Just a moment....
Clear signature file: /tmp/mntner.asc
% more /tmp/mntner.asc
-----BEGIN PGP SIGNED MESSAGE-----
mntner: MAINT-HEAS
descr: shrubbery.net maintainer
admin-c: JH636
tech-c: JH636
upd-to: heas@shrubbery.net
mnt-nfy: heas@shrubbery.net
auth: CRYPT-PW za/0jxyxoQNJQ
auth: PGPKEY-7A774C09
notify: heas@shrubbery.net
mnt-by: MAINT-HEAS
changed: heas@shrubbery.net 20000928
source: NTTCOM
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQCVAwUBOdQW1Esr3VJ6d0wJAQE3ZQP+NOb3XY0fCa0Icfn99bLn25pHDdEBGdmh
T0dbvf9znD3kKE5ZETswluA/LRiO5NW0sjKvOxXJrNX6+Vmf1ueP3TvGjhZXl2Fl
1c8iRFul1gWIlqBU+C8GD8yRJ+7XysfAHjYj5wIlISRVL6aWCCp2RCFlsgrB3TnC
Zd8L4dX7Bi8=
=nbPN
-----END PGP SIGNATURE-----
The contents of /tmp/mntner.asc (in it's entirety) sent via electronic mail to the email address of registry automatic procesor. Note the options to PGP; -sta to sign a plaintext file with your secret key (see your implementation's documentation for more information).
PLEASE do not send email with MINE attachments to the registry for processing. MIME attachements will be NOT be processed. Many mail clients that include PGP support use MIME attachments by default.
For more information on PGP authentication with IRRs, see RFC2726..Getting Started
The first step in making use of the NTT Communications Global IP Network Routing 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 NTT Communications Global IP Network Routing Registry database and you will receive an acknowledgement.
Your maintainer object MUST use CRYPT-PW (or PGP-FROM authentication when it becomes available). An object using MAIL-FROM will not be accepted. Look here for more information on PGP authentication.
The CRYPT-PW information in the maintainer object must be provided in the form of a UNIX encrypted password. Clear text passwords will not be accepted. If you are unable to encrypt passwords locally you can use this crypt calculator provided by Merit.
Once the maintainer object is registered, all other 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
Complete a template and email it.
DeleteUse the existing object and add a delete: reason field to end and email it.
ModifyModify the existing object and email it.
Multiple adds/deletes/modifies may appear in one email message. Here is an example, where password: is the cleartext password for the maintainer MAINT-BEARD, the route: is a new route object, the as-set is being modified to include AS64999, and the aut-num object is being deleted.
To: auto-dbm@rr.ntt.net
From: manchu@foo.com
Subject: multiple mods
password: seeTheWizard
route: 192.168.0.0/16
descr: dixie athletic cups
1000 South Front Ave
Too Cold, North Dakota 12345-6789
origin: AS65000
remarks: this is non-portable space, no exceptions
notify: manchu@foo.com
mnt-by: MAINT-BEARD
changed: manchu@foo.com 19990401
source: NTTCOM
as-set: AS-BEARD
descr: ASes to which we provide transit (+ our AS)
members: AS65000, AS-BIGCUST, AS-STARSHIP, AS-ITSABUST,
AS65001, AS64999
tech-c: VP0-ARIN
admin-c: VP0-ARIN
notify: manchu@foo.com
mnt-by: MAINT-BEARD
changed: manchu@foo.com 19990401
source: NTTCOM
aut-num: AS65000
as-name: UNSPECIFIED
descr: something
remarks: ----------- Customers --------------
import: from AS65001
action pref=10;
accept AS65001 AND NOT {0.0.0.0/0}
export: to AS65001
announce ANY AND NOT {0.0.0.0/0}
admin-c: VP0-ARIN
tech-c: VP0-ARIN
notify: manchu@foo.com
mnt-by: MAINT-BEARD
changed: manchu@foo.com 19990401
source: NTTCOM
delete: unused aut-num
Database Queries
Use whois and/or the IRRToolSet (version 4.7 or greater) to query the database for registered objects.
The NTT Communications Global IP Network maintains two servers. rr.ntt.net is the primary server (authoritative for the NTT Communications Global IP Network routing registry database) and rr1.ntt.net is a backup.
For example, here is the NTT Communications Global IP Network as-set:
eng% whois -h rr.ntt.net AS2914:AS-GLOBAL
as-set: AS2914:AS-GLOBAL
descr: NTT Communications 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 20070413
source: NTTCOM
person: NTT Communiations Global IP Network Engineering
address: NTT America
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 20070413
source: NTTCOM
Object templates
Object fields which are optional but are unused by a particular object, must be omitted when submitted to the NTT Communications Global IP Network Routing Registry automatic processor. Failure to do so will produce errors.
Maintainer (mntner) Template
---------------------- CUT HERE -------------------
mntner:
descr:
admin-c:
upd-to:
mnt-nfy:
mnt-by:
auth:
changed:
source: NTTCOM
---------------------- CUT HERE -------------------
mntner: [mandatory] [single]
descr: [mandatory] [single]
admin-c: [mandatory] [multiple]
tech-c: [optional] [multiple]
upd-to: [mandatory] [multiple]
mnt-nfy: [optional] [multiple]
auth: [mandatory] [multiple]
remarks: [optional] [multiple]
notify: [optional] [multiple]
mnt-by: [optional] [multiple]
changed: [mandatory] [multiple]
source: [mandatory] [single]
Maintainer Example
mntner: MAINT-NTTCOM-BB
descr: NTT Communications Global IP Network maintainer
admin-c: JH636-ARIN
tech-c: JH636-ARIN
upd-to: ip-eng-reports@us.ntt.net
mnt-nfy: ip-eng-reports@us.ntt.net
auth: CRYPT-PW bbc5fU3MWR5xA
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 20060824
source: NTTCOM
PGP key (key-cert) Template
---------------------- CUT HERE -------------------
key-cert:
certif:
mnt-by:
changed:
source: NTTCOM
---------------------- 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] [ ]
key-cert Example
key-cert: PGPKEY-7A774C09
method: PGP
owner: John Heasley <heas@shrubbery.net>
fingerpr: F4 56 93 93 3A CD 4C C1 C7 D5 6C B2 A7 F4 E0 FD
certif:
+-----BEGIN PGP PUBLIC KEY BLOCK-----
+Version: 2.6.2
+
+mQCNAjK6S8cAAAEEAM4de4EPalJsDOsaSlOBRhDGLlSxRetZz532lPRL9rx0wkvL
+4U0mzSI2jppKjJJhvkwIkMsHd3yz3Vbpm/4HydPtCZc3/+kjC//myjdOMCK44ED4
+E42pt6Wgg8Ik0cOTqYexZ0qV/ci2aOMyXK+VbVGG1ZTK4SvsbEsr3VJ6d0wJAAUR
+tCFKb2huIEhlYXNsZXkgPGhlYXNAc2hydWJiZXJ5Lm5ldD6JAJUDBRA4UBPSD28L
+lepPzu8BAaN7A/9Q5FXm/WimNUe+iPBX/zznfUBkUpxpIy4yFApIKI68zslmxwdV
+975YT0t/ftVJtCCNjrhPD/4RI9kqDQqJMlh0hwYFTV+t/DFTvZ33wsklt/+Q4qLb
+4/AEdKpveG00seNt4R5UymD+NVK2fpmx2SJuHLQoh1tDo09KafmjOyCrmYkAlQMF
+EDhOvbTSMEkkdQ6DSQEBcbwD/jnrwtXpMPQmWYb12FLdmlMNGbV4ESxt8QXfgVra
+w14KQJ4P9lToT9Tmqe9Q4NFcKRs/00Q4xlRWwdPuFF4QGOJxBLnE1Xv60rY9eY2Q
+i3DRbRiDw0YgK1xgscRHeRq1giTc2NWFb11KlzV5qciWWDjpx6t01v9Vn59xCCbW
+kEdziQCVAwUQNWRxjfay2HvjD8wlAQGZlAP/SenlqYAfmSVZ/s5st9zA43hXQnNR
+oJeXvFW5kutGAuGOGXZInXB/q9HtoLrngA9PlWHNs+kDP3ipFh9+jyeojQm5fQ94
+R7yMRgupGZJ9WfUQRA1nvB+HmXfRg9bZ5FNoewrCO6aawhEnZ8D7HIrHRz+sH9Mi
+mufkPEARFgZ6F4GJAJUDBRA3eUEYT5ggX09IZTEBARGSBACZrW+GXCFHG5gPmeVX
+cOKcKCE18NyYlah0Pd72y15sJy8GyGIFTpDEDRRE//mQwIWaLV4eehuzHz0ygMm5
+HI4k7FlrHpJqq5/g6pM1zQohvqY53imUbhf4WBzgrvPrfTM/2jaWCb8OBNBCHpiT
+oKWkTqqvK99ScKkf+F+HJMa4ookAdQMFEDNaCL+6FAGUXCurYQEBLp4C/26hjz7e
+5gtlvfM+rdHNAZY+HUhZRty6kOyWJsMu1s9PDlTbljwdTz7cJ141jww6F8JCYGt4
+SfbeT1Mz7MDzgz8jXO710KOwzmOIqupUUUnuw0bMhIMZzhPm6+0OeZgCSYkAlQMF
+EDXVCFcImkdUx0QebQEBjf0EAKyDniKogR5CPn3zIUHAmroHMKiDdMEFsZv4Ih0m
+ERymLH0m2YLePS2lBnwg4ZsIlj0OVksJLgoSb8V3TM1a2ykBkldySha3dHRE0g8J
+QDQ1c2QgGd5SHdBFZY0FNbKj1XbCqxN0ZdmRay5l7UxD532xXA+TZ0LZwkaYcamP
+fjW1iQCVAwUQNBUPkPTPnXJdMaXhAQECgwP/f39qTwHAQEj/fxtbH4wmmsDjo8d0
+FJ/MZsSMSiF0PDbAkvb/krY4Xr4MI1MNNosUJ6f4ZHMGLIzYGYeLyy1jD8KLMDjZ
+DdJI+eKG46iHHLpcAlYeKhfZqEB16+t44mGW6cKyUellk0cUd7nK2ZPj+/u/4ziN
+JekadG1899vuHzSJARUDBRAzTJh364x/pH7NgKUBAZrkB/4sDhJ54578Ze+ci9wM
+OaaTlIsH8YGWskZ1Y+Hj8XiLX4euUXDqd9SFs9RBrzMx7edlE8Q1N9cLAPVCKr8d
+swhb2K7Tgmpwrhe6KpNUa6PSCv6t11gc17QiFzJGoYSAAl7UnJjx9zFAMjfeo+id
+O0clhPMWC6pvB2rNoBMNt+vRXpq7ApWF8CSudwWf277BrKGC8TbwC/ntMtS4ZcjR
+S9Tl/5EMdHgMKqQt+wJx/g1o6g2d0xz65IoNDhpScetkSQXjFh20olcts0ZnQRhp
+W7J9kAEFG9/Yr8GIB7eUjsOr1XIlhMNqwOkqfu9px3eM3ntBjJOZM/WbHWm1KYc4
+2/hciQCVAwUQMrtgE0sr3VJ6d0wJAQFisgP/TDmqElXnB+h9MldnsnnZ7VgDLhHY
++hv8EP9aVd/w2oOR3ZKhYYFcbBnmOvPp34SxaBMf3KSqhEQ22tAfOoQkhIDQs0oj
+DtB4mTmtlQNHFVlbD914eHxIYEznrr7Nw2xqo/GgA+lEC0hrZx2itrIHcZgojE3q
+T42/v4ja9lTNq1OJAJUDBRAyu0Gn+8I/jbEzFDkBAarXA/99R9ATMI8NSVIX3V0z
+Js2oIjC/jKbvstVhR7E+yx49hqRWBtVDCT65IiR2pyf4rl9M+tekbKununIBhjny
+yXcMkK96fbBrFQA3c2pqSLKhXNFrEdapV0874VgwVfW4938xi5oCfV/nPT6lYgdo
+H6/eLL6MCx9ga0q87NGUdh0naw==
+=OlpC
+-----END PGP PUBLIC KEY BLOCK-----
mnt-by: MAINT-HEAS
changed: heas@shrubbery.net 20000928
source: NTTCOM
as (aut-num) object
---------------------- CUT HERE -------------------
aut-num:
as-name:
descr:
import:
export:
default:
member-of:
admin-c:
tech-c:
remarks:
notify:
mnt-by:
changed:
source: NTTCOM
---------------------- CUT HERE -------------------
aut-num: [mandatory] [single]
as-name: [mandatory] [single]
descr: [mandatory] [single]
import: [optional] [multiple]
export: [optional] [multiple]
default: [optional] [multiple]
member-of: [optional] [multiple]
admin-c: [mandatory] [multiple]
tech-c: [mandatory] [multiple]
remarks: [optional] [multiple]
notify: [optional] [multiple]
mnt-by: [mandatory] [multiple]
changed: [mandatory] [multiple]
source: [mandatory] [single]
as (aut-num) example
aut-num: AS2914
as-name: NTTC-GIN-AS
descr: NTT Communications 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
as-set object
---------------------- CUT HERE -------------------
as-set: AS-
descr:
members:
tech-c:
admin-c:
notify:
mnt-by:
changed:
source: NTTCOM
---------------------- CUT HERE -------------------
as-set: [mandatory] [single]
descr: [mandatory] [single]
members: [mandatory] [multiple]
tech-c: [mandatory] [multiple]
admin-c: [mandatory] [multiple]
remarks: [optional] [multiple]
notify: [optional] [multiple]
mnt-by: [optional] [multiple]
changed: [mandatory] [multiple]
source: [mandatory] [single]
as-set example
as-set: AS2914:AS-GLOBAL
descr: NTT Communications 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: NTT Communications Global IP Network Engineering
address: NTT America
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
route object:
---------------------- CUT HERE -------------------
route:
descr:
origin:
notify:
mnt-by: MAINT-
changed:
source: NTTCOM
---------------------- CUT HERE -------------------
route: [mandatory] [single]
descr: [mandatory] [single]
origin: [mandatory] [single]
member-of: [optional] [multiple]
remarks: [optional] [multiple]
notify: [optional] [multiple]
mnt-by: [optional] [multiple]
changed: [mandatory] [multiple]
source: [mandatory] [single]
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 Communications
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
Mirroring the NTT Communications Global IP Network routing registry database
NSPs wishing to mirror the NTT Communications Global IP Network routing registry database should contact the db-admin@rr.ntt.net.