Object Class types

Each Object class has a number of attributes associated with it. These attributes are also documented here - Object Attributes. For a full reference on the standard, please refer to RFC 2622: Routing Policy Specification Language.

Purpose:
Defines a named group of AS numbers or other as-sets. Commonly used to simplify import/export filters or build hierarchical groupings of autonomous systems.

Typical Usage:

• To define all ASNs used by a customer, peer, or organization.

• To reference in routing policy (e.g., in import/export statements).

Required attributes:

• as-set

• members

• mnt-by

• changed

• source

Example:

Purpose:
Defines routing policy for an Autonomous System (AS). Describes how the AS interacts with upstream, downstream, and lateral peers.

Typical Usage:

• To register your AS and define BGP policies.

• Referenced in route/route6 objects via origin.

Required attributes:

• aut-num

• as-name

• import

• export

• mnt-by

• changed

• source

Example:

Purpose:
Represents a reusable named filter for route expressions, such as IP prefixes, as-paths, or communities.

Typical Usage:

• To define custom routing filters in a reusable object.

• Used in import/export policies or tools like bgpq3.

Required attributes:

• filter-set

• filter

• mnt-by

• changed

• source

Example:

Purpose:
Describes a specific router (by name), its interfaces, local AS, and BGP peerings.

Typical Usage:

• To define router-level configuration in RPSL.

• Used in network documentation or router grouping (rtr-set).

Required attributes:

• inet-rtr

• local-as

• mnt-by

• changed

• source

Example:

Purpose:
Publishes a public PGP key used to cryptographically sign object submissions for authentication.

Note: The RADb Web Portal currently does not support key-cert–based updates.

You will need to upload the key-cert object via email (auto-dbm) or API

Typical Usage:

• For securing updates to RADb using PGP/GPG.

• Required for PGP/GPG-based authorization on maintained objects.

Required attributes:

• key-cert

• method

• owner

• fingerpr

• certif

• mnt-by

• changed

• source

Example:

Purpose:
Defines who has authorization to update, delete, or create objects in RADb.

Typical Usage:

• Every object must be protected by at least one mntner.

• Typically tied to an organization or network's AS.

Required attributes:

• mntner

• descr

• auth

• mnt-by

• changed

• source

Example:

Purpose:
Represents a group of BGP peerings. Used for routing policy automation.

Typical Usage:

• Define all peerings for a particular region, IXP, or customer.

• Referenced in policy statements or BGP templates.

Required attributes:

• peering-set

• peering

• mnt-by

• changed

• source

Example:

Purpose:
Describes an individual contact person responsible for networking operations.

Typical Usage:

• Referenced in admin-c or tech-c of other objects.

• Must be registered before being used as a contact.

Required attributes:

• person

• address

• phone

• e-mail

• nic-hdl

• mnt-by

• changed

• source

Example:

Purpose:
Describes a group role (e.g., NOC, abuse desk), used as a contact point.

Typical Usage:

• Referenced in admin-c or tech-c.

• Preferred over person for general/shared contacts.

Required attributes:

• role

• address

• phone

• e-mail

• nic-hdl

• mnt-by

• changed

• source

Example:

Purpose:
Registers an IPv4 route announcement and origin ASN.

Typical Usage:

• Required to allow ASNs to propagate prefixes via IRR filters.

• Used by upstreams and peers for routing validation.

Required attributes:

• route

• origin

• mnt-by

• changed

• source

Example:

Purpose:
Registers an IPv6 route and origin ASN.

Typical Usage:

• Same use as route, but for IPv6.

• Included in IRR-based prefix lists.

Required attributes:

• route6

• origin

• mnt-by

• changed

• source

Example:

Purpose:
Defines a set of route prefixes or other route-sets.

Typical Usage:

• Used to group prefixes for easier policy management.

• Often used in large import/export policies.

Required attributes:

• route-set

• members

• mnt-by

• changed

• source

Example:

Purpose:
Groups routers by hostname or IP address.

Typical Usage:

• Used with inet-rtr objects for modeling BGP peering or configuration templates.

Required attributes:

• rtr-set

• members

• mnt-by

• changed

• source

Example: