inet-rtr

Object Template

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

               Status       Instance     Search Status

inet-rtr:      [mandatory]  [single]     [primary/lookup key]
descr:          [mandatory]  [multiple]   [ ]
alias:          [optional]   [multiple]   [ ]
local-as:       [mandatory]  [single]     [inverse key]
ifaddr:         [mandatory]  [multiple]   [lookup key]
interface:      [optional]   [multiple]   [lookup key]
peer:           [optional]   [multiple]   [ ]
mp-peer:        [optional]   [multiple]   [ ]
member-of:      [optional]   [multiple]   [inverse key]
remarks:        [optional]   [multiple]   [ ]
admin-c:        [mandatory]  [multiple]   [inverse key]
tech-c:         [mandatory]  [multiple]   [inverse key]
notify:         [optional]   [multiple]   [inverse key]
mnt-by:         [mandatory]  [multiple]   [inverse key]
last-modified:  [generated]  [single]     [ ]
source:         [mandatory]  [single]     [ ]

Attribute status

Mandatory

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

Attribute	Description
inet-rtr	The valid DNS name of the router described. EXAMPLE inet-rtr: rtr.example.net
descr	A short description related to the object’s purpose. EXAMPLE descr: Border router for Sparkynet descr: Beijing - China
local-as	Specifies the AS number of the Autonomous System that operates the router. EXAMPLE local-as: AS1
tech-c	The NIC-handle of a technical contact ‘person’ or ‘role’ object. 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.
admin-c	The NIC-handle of an on-site contact ‘person’ object. 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.
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’.
last-modified	It is a time stamp that is generated by the system to reflect when the object was last modified. last-modified: 2018-08-30T07:50:19Z
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
alias	Alternative canonical DNS names for the router.
ifaddr	Describes all the inter-router serial port interfaces for all the line cards. The interface address (ifaddr) attribute must be in the format: <ipv4-address> masklen <integer> [action <action>] EXAMPLE ifaddr: 147.45.0.17 masklen 32 For more information, see RFC 2622 – Routing Policy Specification Language (RPSL), section 9.
interface	This attribute performs the same function as the ‘ifaddr’ attribute above. The difference is that interface allows both IPv4 and IPv6 address families to be specified. Describes all the inter-router serial port interfaces for all the line cards. The interface address (interface) attribute must be in the format: afi <afi> <ipv4-address> masklen <integer> [action <action>] or afi <afi> <ipv6-address> masklen <integer> [action <action>] [tunnel <remote-endpoint-address>, <encapsulation>] For more information, see RFC 4012 – Routing Policy Specification Language next generation (RPSLng), section 4.5.
peer	Specifies the protocol used to peer with another router. EXAMPLE peer: BGP4 RTRS-IBGP-PEERS ASNO(AS3333), flap_damp() peer: BGP4 PRNG-EBGP-PEERS ASNO(PeerAS), flap_damp() For more information, see RFC 2622 – Routing Policy Specification Language (RPSL), section 9.
mp-peer	This attribute performs the same function as the ‘peer’ attribute above. The difference is that mp-peer allows both IPv4 and IPv6 address families to be specified. Specifies the protocol used to peer with another router. EXAMPLE <protocol> afi <afi> <ipv4- or ipv6- address> <options> \| <protocol> <inet-rtr-name> <options> \| <protocol> <rtr-set-name> <options> \| <protocol> <peering-set-name> <options> For more information, see RFC 4012 – Routing Policy Specification Language next generation (RPSLng), section 4.5.
remarks	General remarks. May include a URL or instructions on where to send abuse complaints.
notify	The email address to which notifications of changes to this object should be sent. IMPORTANT! Do NOT send spam or hacking complaints to this address.

Generated

Attribute value is generated by the database.

Updating

You will soon be able to updated this object 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.

Using inet-rtr objects

An inet-rtr can be used by automated tools to determine to which AS a router belongs. It can also be used to register information about peering relationships.

The inet-rtr object can also be useful if you are using RPSL to configure your internal network. It allows you to keep track of internal routing configurations.

For more information, see RFC 2622 – Routing Policy Specification Language (RPSL), section 9.