Attributes of APNIC Whois Database peering-set objects

Using peering-set objects

Use peering-set objects to simplify peering statements in the import and export attributes of aut-num objects.

For more information, see RFC 2622, section 5.6.

To view the peering-set object, see APNIC Whois Database object templates.

The following describe the mandatory and optional attributes in a peering-set object.

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

Attribute	Function	Description
peering-set*	Technical	The name of the filter set. The peering-set must begin with 'PRNG-'. Example: PRNG-EXAMPLENET
descr	Administrative	A short description related to the object's purpose. Example: Peering at IX123
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 mnt-by 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. Every time a change is made to a database object, this attribute will show the email address of the person who made those changes. This is not to be used as a contact address.
source	Administrative	The name of the database from which the data was obtained.

Attribute	Function	Description
peering*	Technical	Peering is used for importing or exporting IPv4 routes. Although the peering attribute is optional, at least one peering or mp-peering must be present in the peering-set object. The peering attribute can specify: Other peering sets Example: PRNG-XAM Peering statements Example: AS2 at 9.9.9.1 For more information, RFC 2622, section 5.6.
mp-peering*	Technical	This attribute performs the same function as the peering attribute above. The difference is that mp-peering allows both IPv4 and IPv6 address families to be specified. Although the mp-peering attribute is optional, at least one peering or mp-peering must be present in the peering-set object. Peerings used for importing or exporting IPv4 and IPv6 routes. The mp-peering attribute can specify: Other peering sets Example: PRNG-XAM6 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 will be sent. When this attribute contains dbmon@apnic.net, it means APNIC staff are notified of changes to the object.
mnt-lower	Administrative	Sometimes there is a hierarchy of maintainers. In these cases, mnt-lower is used as well as mnt-by. New in Whois v3.2.