filter-set
Object Template
The object template includes information on how to complete the attribute values.
Status Instance Search Status filter-set: [mandatory] [single] [primary/lookup key] descr: [mandatory] [multiple] [ ] filter: [optional] [single] [ ] mp-filter: [optional] [single] [ ] 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 |
---|---|
filter-set | The name of the filter set.
The filter-set must begin with ‘FLTR-‘. EXAMPLE FILTR-EXAMPLENET For IPv6 reverse delegations, use the format x.x.x.x.ip6.arpa. |
descr | A short description related to the object’s purpose.
EXAMPLE Filter local community routes |
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.
|
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.
|
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 |
---|---|
filter | The policy filter of the set.
The policy filter is a logical expression which, when applied to a set of routes, returns a subset of those routes. EXAMPLE filter: (AS1 or fltr-foo) and <AS2> Important: The filter and ‘mp-filter’ attributes cannot appear together within the same object. For more information, see RFC 2622 – Routing Policy Specification Language (RPSL), section 5.4. |
mp-filter | Logical expression which when applied to a set of IPv4 or IPv6 routes returns a subset of these routes.
|
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 filter-set objects
The filter-set object is an advanced routing object that can be used by more complex networks to filter imported and exported routes.
For more information, see RFC 2622 – Routing Policy Specification Language (RPSL), section 5.4.