Attributes of APNIC Whois Database filter-set objects
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, section 5.4.
filter-set template
To view the filter-set object, see APNIC Whois Database object templates.
filter-set attributes
The following describe the mandatory and optional attributes in a filter-set object.
Note: Attributes marked with an asterisk (*) now support four-byte AS number syntax. For more information see the ASN resource guide.
Mandatory attributes
Attribute |
Function |
Description |
filter-set* |
Technical |
The name of the filter set. The filter-set must begin with 'FLTR-'. Example: FILTR-EXAMPLENET |
descr |
Administrative |
A short description related to the object's purpose. Example: Filter local community routes |
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. |
Optional attributes
Attribute |
Function |
Description |
filter* |
Technical |
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, section 5.4. |
mp-filter* |
Technical |
Logical expression which when applied to a set of IPv4 or IPv6 routes returns a subset of these routes. For more information, see RFC 4012, section 2.5.2. The filter and mp-filter attributes cannot appear together within the same object. 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. |
See also
- Whois v3.2 upgrade guide
- Attributes of APNIC Whois Database objects
- APNIC Routing Registry resource guide
- Updating information in the APNIC Whois Database
- RFC 2622 - Routing Policy Specification Language (RPSL)
- RFC 2650 - Using RPSL in Practice
- RFC 4012 - Routing Policy Specification Language next generation (RPSLng)


