Attributes of the APNIC Whois Database router (inet-rtr) object

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, section 9.

inet-rtr template

To view the inet-rtr template, see APNIC Whois Database object templates.

inet-rtr attributes

The following describe the mandatory and optional attributes in an inet-rtr object.

Mandatory attributes
Optional attributes

Note: Attributes marked with an asterisk (*) now support four-byte AS number syntax. For more information see the ASN resource guide.

Mandatory attributes

Attributes	Function	Description
inet-rtr*	Technical	The valid DNS name of the router described. Example: inet-rtr: rtr.example.net
descr	Administrative	A short description related to the object's purpose. Example: descr: Border router for Sparkynet descr: Beijing - China
local-as*	Technical	Specifies the AS number of the Autonomous System that operates the router. Example: local-as: AS1
tech-c	Administrative	The NIC-handle of a technical person or role object. In the web interface, the tech-c attribute contains a link to the person or role object to which the NIC-handle belongs.
admin-c	Administrative	The NIC-handle of an on-site contact person or role object. In the web interface, the admin-c attribute contains a link to that person or role object to which the NIC-handle belongs.
mnt-by	Administrative	The identifier of a registered mntner object used for authorisation and authentication. In the web interface, the mntner attribute contains a link to the specified mntner.
changed	Administrative	The email address of who last updated the database object and the date it occurred. The changed attribute is not a network contact address, as it merely records who made the most recent change to the registration information. All APNIC addresses will initially record an APNIC address in this field, as APNIC creates the first database object.
source	Administrative	The name of the database from which the data was obtained.

Optional attributes

Attributes	Function	Description
alias	Technical - advanced	Alternative canonical DNS names for the router.
ifaddr*	Technical	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, section 9.
interface*	Technical - advanced	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, section 4.5. New in Whois v3.2.
peer*	Technical - advanced	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 section 9.
mp-peer*	Technical - advanced	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, section 4.5. New in Whois v3.2.
remarks	Administrative	General remarks. May include a URL or email address.
notify	Administrative	The e-mail address to which notifications of changes to an object should be sent.