Creating Routing Registry Objects

1. The first thing you will need to do is create a Maintainer Object. A Maintainer Object links all your other types of objects together. 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:
---------------------- CUT HERE -------------------

For an example please click here


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 -------------------

For an example please click here


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 -------------------

For an example please click here


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 -------------------

For an example please click here


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 -------------------

For more information using PGP key instead of CRYPT_PW see here


Return to Routing Registry Overview

[mandatory]    [single]

the maintainer object is named by the mntner field. In the NTTCOM Route Registry, maintainer names start with MAINT- and contain just letters, digits, and hyphens. There can be only one mntner field per maintainer object, and only one maintainer with a given name. Case is not significant when it comes to comparison.

[mandatory]    [single]

The descr field is a textual description of the maintainer object, for people to read. There can only be one descr field, but it can continue across multiple lines if the second and subsequent lines begin with whitespace. The lines of the descr should be no longer than 60 characters, to avoid line folding by email clients.

[mandatory]    [multiple]

The admin-c is the administrative contact for the maintainer. In the NTTCOM Route Registry, the admin-c is considered the true owner of all objects registered to the maintainer. The admin-c is identified by a nic handle, and nic handles are normally assigned by the registrar who provided the address space. The nic handle for the admin-c must be available for lookup, and contain an email address for use in contacting the administrative contact.

The admin-c approves resetting the password for the maintainer object (the only route object change that the DB Admin performs after the maintainer has been created). There can be more than one admin-c, in which case any of them can approve a password reset.

The admin-c is also responsible for responding to general issues with objects owned by the maintainer, so the admin-c must refer to someone who will monitor their email and respond promptly and authoritatively. If there is more than one admin-c listed, they must all be responsive to email.

[mandatory]    [multiple]

The admin-c is the administrative contact for the maintainer. In the NTTCOM Route Registry, the admin-c is considered the true owner of all objects registered to the maintainer. The admin-c is identified by a nic handle, and nic handles are normally assigned by the registrar who provided the address space. The nic handle for the admin-c must be available for lookup, and contain an email address for use in contacting the administrative contact.

A "nic handle" is a short identifier which can be looked up with the whois program. Normally, RIRs assign nic handles to contacts when IP space is assigned.

An example of a nic handle is JH636-ARIN, which can be found on whois.arin.net:

whois -h whois.arin.net JH636-ARIN
[optional]     [multiple]

The tech-c field names the technical contact. The tech-c refers to a responsive party, because some people will contact the tech-c instead of, or in addition to, the admin-c, but the tech-c cannot approve changes to the maintainer. There can be more than one tech-c, each identified by a nic handle.

The admin-c and tech-c may be the same.

<email-address>    [mandatory]    [multiple]

the upd-to email address receives email when an unauthorized update attempt fails.

<email-address>    [optional]     [multiple]

the mnt-nfy email address receives mail whenever any object owned by the maintainer is added, changed, or deleted.

[mandatory]    [multiple]

The auth field specifies how changes to objects owned by this maintainer are authenticated. In the NTTCOM Route Registry, its value can be either CRYPT-PW, MD5-PW or PGPKEY.

CRYPT-PW information in the maintainer object must be provided in the form of a UNIX encrypted password, MD5-PW information as an MD5 encrypted password. Clear text passwords will not be accepted. If you are unable to encrypt passwords locally you can use the appropriate crypt calculator below. An object using MAIL-FROM will not be accepted.

Click here for Crypt Password Generator provided by Merit.

Look here for more information on PGP authentication.

<free-form>    [optional]     [multiple]

The remarks field is optional, and there may be more than one of them.

Typically used for information related to the object.

<email-address>    [optional]     [multiple]

When this object is changed, email is sent to the notify address.

list of <mntner-name>    [optional]     [multiple]

The object is owned by the maintainer listed in mnt-by.

<email-address> <date>    [mandatory]    [multiple]

When the object is changed, that fact is documented by the changed: field that has the syntax <email-address> <yyyymmdd>

NTTCOM    [mandatory]    [single]

The source field defines the registry that the object belongs to. For objects registered in the NTTCOM Route Registry, the source is "NTTCOM". Objects from other registries are also present in the NTTCOM Route Registry, showing their original source

<as-number>    [mandatory]    [single]
<object-name>    [mandatory]    [single]
<see rfc2622, 6.1>    [optional]    [multiple]

import: from <peering-1> [action <action-1>]
   . . .
   from <peering-N> [action <action-N>]
   accept <filter>

<see rfc2622, 6.2>    [optional]    [multiple]

export: to <peering-1> [action <action-1>]
   . . .
   to <peering-N> [action <action-N>]
   announce <filter>

<see rfc2622, 6.5>    [optional]    [multiple]

default: to <peering> [action <action>] [networks <filter>]

list of <as-set-names>    [optional]    [multiple]
<object-name>    [mandatory]    [single]
list of <as-numbers> and/or <as-set-names>
[mandatory]    [multiple]
<address-prefix>    [mandatory]    [single]

A route object needs to be created for each prefix needing to be announced.

<as-number>    [mandatory]    [single]

This will identify which ASN is originating this prefix.

list of <route-set-names>    [optional]    [multiple]
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
            
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 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 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