Module set

A set’s name is an rpsl word with the following restrictions: All as-set names start with prefix “as-”. All route-set names start with prefix “rs-”. All rtr-set names start with prefix “rtrs-”. All filter-set names start with prefix “fltr-”. All peering-set names start with prefix “prng-”. For example, as-foo is a valid as-set name.

Set names can also be hierarchical. A hierarchical set name is a sequence of set names and AS numbers separated by colons “:”. At least one component of such a name must be an actual set name (i.e. start with one of the prefixes above). All the set name components of an hierarchical name has to be of the same type. For example, the following names are valid: AS1:AS-CUSTOMERS, AS1:RS-EXPORT:AS2, RS- EXCEPTIONS:RS-BOGUS.

https://www.rfc-editor.org/rfc/rfc2622#section-5.

Constants

ANY

The keyword ANY matches all routes.

ASN

AS number.

AS_SET

The as-set attribute defines the name of the set. It is an RPSL name that starts with “as-”.

AS_SET_BASE

Base AS Set name, including peeras.

AS_SET_BASE_OR_ASN

FILTER_SET

The filter-set attribute defines the name of the filter. It is an RPSL name that starts with “fltr-”.

FILTER_SET_BASE

Base Filter Set name.

FILTER_SET_BASE_OR_ASN

OBJECT_NAME

RPSL object name, without restriction on first letter.

PEERAS

The keyword PeerAS can be used instead of the AS number of the peer AS. PeerAS is particularly useful when the peering is specified using an AS expression.

PEERING_SET

The peering-set attribute defines the name of the set. It is an RPSL name that starts with “prng-”.

PEERING_SET_BASE

Base Peering Set name.

PEERING_SET_BASE_OR_ASN

ROUTE_SET

The route-set attribute defines the name of the set. It is an RPSL name that starts with “rs-”.

ROUTE_SET_BASE

Base Route Set name.

ROUTE_SET_BASE_OR_ASN