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] changed: [mandatory] [multiple] [ ] source: [mandatory] [single] [ ]
Attribute must be included in the object. Failure to do so will result in errors.
|peering-set||The name of the filter set. The peering-set must begin with ‘PRNG-‘.
|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.
|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.
|mnt-by||Lists a registered ‘mntner’ used to authorize and authenticate changes to this object.
|changed||The email address of who last updated the database object and the date it occurred.
changed: firstname.lastname@example.org 20010921
IMPORTANT! This is NOT to be used as a contact address.
|source||The database where the object is registered.
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.
|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:
EXAMPLE AS2 at 126.96.36.199
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:
|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.|
Attribute value is generated by the database.
You will soon be able to updated this object in MyAPNIC.
Instances of attribute allowed
|Attribute must appear only once in the object.|
|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 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.|
|Attribute can be queried in the database to return the object. Please note, however, that a lookup key does not uniquely identify an object.|
|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),