Attributes of APNIC Whois Database as-set objects

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.

as-set template

To view the as-set object, see APNIC Whois Database object templates.

as-set attributes

The following describe the mandatory and optional attributes in an as-set object.

Mandatory attributes
Optional attributes

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
as-set*	Technical	The name of a set of aut-num objects. The as-set attribute may take two forms: 1. Non-hierarchical A non-hierarchical as-set attribute must begin with 'AS-'. Non-hierarchical as-set names should only be used to create as-set objects that can be used across many networks, for example, unallocated AS numbers. Example: AS-UNALLOCATED ASNs 2. Hierarchical 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-'. Hierarchical as-set names should be used when creating sets of AS numbers specific to your own, your customers', or your peers' networks. APNIC recommends the following format to allow you to manage multiple as-set objects for your network: <origin-as-number>:AS-CUSTOMERS <origin-as-number>:AS-PEERS Example: AS1:AS-CUSTOMERS
descr	Administrative	A short description related to the object's purpose. Example: Peers for AS1 ExampleNet
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.

Top

Optional attributes

Attribute	Function	Description
country	Administrative	Two letter code of the country where the admin-c is based. Details of country codes are specified in ISO3166.
members*	Technical	Explicitly lists members of the as-set. Members of an as-set can be: AS numbers AS sets If this attribute is used, the aut-num or as-set objects referred to should not include a reference to this as-set object in their own member-of attributes. Attempts to do so will result in an authorisation failure.
mbrs-by-ref	Technical/ administrative	The identifier of a registered mntner object that can be used to add members to the as-set indirectly. To include an aut-num or as-set object as a member in this as-set, the mntner specified in the mbrs-by-ref attribute must refer to this as-set in the appropriate aut-num or as-set object's member-of attribute. This allows the maintainer to choose which of the objects they maintain should be part of the set. If the maintainer chooses not to list the set in the member-of attribute of an object, that object will not be included in the set. To allow any aut-num or as-set to be a member of this as-set, use the keyword ANY. If the mbrs-by-ref attribute is not used, the as-set will only include objects specified the members attribute.
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.