irt

Object Template

The object template includes information on how to complete the attribute values.

                Status       Instance     Search Status

irt:            [mandatory]  [single]     [primary/lookup key]
address:        [mandatory]  [multiple]   [ ]
phone:          [optional]   [multiple]   [ ]
fax-no:         [optional]   [multiple]   [ ]
e-mail:         [mandatory]  [multiple]   [lookup key]
abuse-mailbox:  [mandatory]  [multiple]   [inverse key]
signature:      [optional]   [multiple]   [ ]
encryption:     [optional]   [multiple]   [ ]
admin-c:        [mandatory]  [multiple]   [inverse key]
tech-c:         [mandatory]  [multiple]   [inverse key]
auth:           [mandatory]  [multiple]   [inverse key]
remarks:        [optional]   [multiple]   [ ]
irt-nfy:        [optional]   [multiple]   [inverse key]
notify:         [optional]   [multiple]   [inverse key]
mnt-by:         [mandatory]  [multiple]   [inverse key]
changed:        [mandatory]  [multiple]   [ ]
source:         [mandatory]  [single]     [ ]

Example

inetnum:        192.168.1.0 - 192.168.1.255
netname:        EXAMPLENET-AP
descr:          Example net Pty Ltd
country:        AP
admin-c:        DE345-AP
tech-c:         DE345-AP
status:         ASSIGNED PORTABLE
mnt-by:         MAINT-EXAMPLENET-AP
mnt-irt:        IRT-EXAMPLENET-AP
changed:        johndoe@examplenet.com/*  */ 20101231
source:         APNIC

irt:            IRT-EXAMPLENET-AP
address:        123 Example st.
address:        20097 Exampletown
address:        Australia
phone:          +12 34 567890 000
fax-no:         +12 34 567890 010
abuse-mailbox:  abuse@examplenet.com/*  */
admin-c:        DE345-AP
tech-c:         DE345-AP
auth:           PGPKEY-80FFBF15
remarks:        emergency phone number +12 34 567890 333
remarks:        timezone GMT+10 (GMT+2 with DST)
remarks:        https://www.examplenet.com
remarks:        This is a TI accredited CSIRT/CERT
irt-nfy:        notify@examplenet.com/*  */
mnt-by:         MAINT-EXAMPLENET-AP
source:         APNIC

Attribute status

Mandatory

Attribute must be included in the object.  Failure to do so will result in errors.

Attribute Description
irt Specifies the name of the irt object.

  • The name should start with the prefix “IRT-“, which is reserved for this type of object.
address Full postal address of a contact.

  • You can use any combination of alphanumeric characters.
  • More than one line can be used.
EXAMPLE
address: 2 Pandora St Boxville
address: Wallis and Futuna Islands

e-mail A contact email address for non-abuse/technical incidents.

abuse-mailbox Specifies the email address to which abuse complaints should be sent.
admin-c The NIC-handle of an on-site administrative contact. As more than one person often fulfills a role function, there may be more than one admin-c listed.

  • In the web interface, the admin-c attribute contains a link to the ‘person‘ object the NIC-handle belongs to.
  • An administrative contact (admin-c) must be someone who is physically located at the site of the network.
tech-c The NIC-handle of a technical contact. As more than one person often fulfills a role function, there may be more than one tech-c listed.

  • In the web interface, the tech-c attribute contains a link to the ‘person’ or ‘role’ object to which the NIC-handle belongs to.
  • A technical contact (tech-c) must be a person responsible for the day-to-day operation of the network, but does not need to be physically located at the site of the network.
auth Defines the authentication scheme to be used to link resources (aut-num, inetnum, inet6num) to this irt object. Authentication options available are:

CRYPT-PW
PGP-KEY
MD5 

EXAMPLE:
auth: PGPKEY-80FFBF15

For information on how to use these authentication options see:

arrow-blue Authentication options for mntner objects

mnt-by Lists a registered ‘mntner’ used to authorize and authenticate changes to this object.

  • A ‘mntner’ object is a database object used to authorize updates to the APNIC database.
  • When your database details are protected by a ‘mntner’ object, then only persons with access to the security information of that ‘mntner’ object will be able to change details.
  • In the web interface, the mnt-by attribute contains a link to the specified ‘mntner’.
changed The email address of who last updated the database object and the date it occurred.

  • Every time a change is made to a database object, this attribute will show the email address of the person who made those changes.
  • All APNIC delegated IP addresses will initially record an APNIC email address in this attribute, as APNIC creates the first database object.
  • Please use the address format specified in RFC 822 – Standard for the Format of ARPA Internet Text Message and provide the date format using one of the following two formats: YYYYMMDD or YYMMDD.
changed: hostmaster@sparkynet.com.wf/*  */ 20010921

IMPORTANT! This is NOT to be used as a contact address.

source The database where the object is registered.

  • Use APNIC for objects in the APNIC Database.
  • Please use UPPERCASE letters.

Optional

Attribute may be deleted from the object. To delete an optional attribute you must also remove the attribute from the object template.  Failure to do so will result in errors.

Attribute Description
phone A contact telephone number.

+ <international code> <area code> <phone #>
+ <international code> <area code> <phone #> ext. <#>
EXAMPLE
phone: +681 368 0844 ext. 32

fax-no A contact fax number.

+ <international code> <area code> <fax #>

 

EXAMPLE
fax-no: +681 367 1797

signature References a ‘key-cert‘ object representing a CSIRT public key used by the team to sign their correspondence.
encryption References a ‘key-cert‘ object representing a CSIRT public key used to encrypt correspondence sent to the CSIRT.
remarks Information about the object that cannot be stated in other attributes.
irt-nfy The email address to be notified when a reference to the irt object is added or removed.
notify The email address to which notifications of changes to this object should be sent.

Generated

Attribute value is generated by the database.

Updating

This object can be created and updated in MyAPNIC.

Instances of attribute allowed

Single
Attribute must appear only once in the object.
Multiple
Attribute may appear multiple times in the object. For example, you may wish to include more than one admin-c attribute.

 

Attribute search status

Primary key
Primary keys distinguish an object from all other objects in the database. To update a primary key, you must delete the entire object and them create a new object with the updated information.
Lookup key
Attribute can be queried in the database to return the object.  Please note, however, that a lookup key does not uniquely identify an object.
Inverse key
Attribute can be used when performing an inverse query using the -i flag. For example, the query

-i mntner <MNTNER-NAME>

will return all objects with the specified maintainer in the mnt-by attribute.