The object template includes information on how to complete the attribute values.
Status Instance Search Status as-set: [mandatory] [single] [primary/lookup key] descr: [mandatory] [multiple] [ ] country: [optional] [single] [ ] members: [optional] [multiple] [ ] mbrs-by-ref: [optional] [multiple] [inverse key] 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] [ ]
as-set: AS12345: AS-EXAMPLENET descr: EXAMPLENET-AS-SET country: AU members: AS6789, AS9876 remarks: Peering AS tech-c: DE345-AP admin-c: DE345-AP notify: firstname.lastname@example.org mnt-by: MAINT-EXAMPLENET-AP changed: email@example.com 20101231 source: APNIC
Attribute must be included in the object. Failure to do so will result in errors.
|as-set||The name of a set of aut-num objects. The as-set attribute may take two forms:
A non-hierarchical as-set attribute must begin with ‘AS-‘.
EXAMPLE AS-UNALLOCATED ASNs
A hierarchical as-set attribute consists of as-set names and AS numbers separated by colons ‘:‘. There must be at least one ‘set-name‘ within the hierarchical name that starts with ‘AS-‘.
<origin-as-number>: AS-CUSTOMERS <origin-as-number>: AS-PEERS EXAMPLE AS1: AS-CUSTOMERS
|descr||A short description related to the object’s purpose.
EXAMPLE Peers for AS1 ExampleNet
|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.
|country||Two letter ISO 3166 code of the country or economy where the admin-c is based.
Please use UPPERCASE letters.
EXAMPLE country: WF
|members||Explicitly lists members of the as-set. Members of an as-set can be: AS numbers; or AS sets
|mbrs-by-ref||The identifier of a registered ‘mntner’ object that can be used to add members to the as-set indirectly.
|remarks||Information about the object that cannot be stated in other attributes. 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 as-set objects
The as-set object allows you to group AS numbers with similar properties.
For example, instead of referring to many individual AS numbers in the import and export attributes of the aut-num object, you can refer to a single as-set object.
For example, by using the following as-set object:
as-set AS1:AS-CUSTOMERS members: AS2, AS3, AS4, AS5
… instead of using this long import statement:
import: from AS2 accept AS2 import: from AS3 accept AS3 import: from AS4 accept AS4 import: from AS5 accept AS5
… you could replace it with this simple import statement:
import: from AS1:AS-CUSTOMERS accept AS1:AS-CUSTOMERS
If you use automated tools used to configure routers, the aut-num objects associated with the as-set object will be returned, and all individual routes that originate from the AS numbers will be injected into your configuration files.
For more information, see RFC 2650 – Using RPSL in Practice.