APNIC Home

peering-set

Object Template

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

               Status       Instance     Search Status

peering-set:   [mandatory]  [single]     [primary/lookup key]
descr:          [mandatory]  [multiple]   [ ]
peering:        [optional]   [multiple]   [ ]
mp-peering:     [optional]   [multiple]   [ ]
remarks:        [optional]   [multiple]   [ ]
tech-c:         [mandatory]  [multiple]   [inverse key]
admin-c:        [mandatory]  [multiple]   [inverse key]
notify:         [optional]   [multiple]   [inverse key]
mnt-by:         [mandatory]  [multiple]   [inverse key]
mnt-lower:      [optional]   [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
peering-set The name of the filter set. The peering-set must begin with ‘PRNG-‘.

EXAMPLE
PRNG-EXAMPLENET
descr A short description related to the object’s purpose.

EXAMPLE
Peering at IX123
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
peering 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, see RFC 2622 – Routing Policy Specification Language (RPSL), section 5.6.
mp-peering 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
remarks General remarks. May include a URL or email address.
notify The email address to which notifications of changes to this object will be sent.
mnt-lower Sometimes there is a hierarchy of maintainers. In these cases, mnt-lower is used as well as mnt-by.

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 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 – Routing Policy Specification Language (RPSL),
section 5.6.