Object Attributes

Below is a list of the various types of object attributes that can be used with RADb Objects

If you are unsure about which attributes are optional and which are mandatory for a RADb Object, you can use a WHOIS query against RADb WHOIS to list the attributes. The query flag is -t <object> where <object> is one of route, route6, etc.

Example:

The postal address of a person or role in the RADB.

The administrative contact for the object. Can be a person's name or a NIC handle.

Note:

• You can only use admin-c and tech-c if the NIC handle you reference already exists in a person or role object in RADb.

• If the NIC handle doesn’t match, the object won’t be accepted.

• RADb also shows the linked contact information when someone views your record.

Defines the set of Autonomous Systems (ASes) that form a boundary for route aggregation.
If not specified, only the origin AS acts as the boundary. Within the boundary, more specific routes are shared. Outside the boundary, only the aggregate route is shared.

Specifies how an aggregate route is created. Can be either "inbound" (routes are combined when received) or "outbound" (routes are combined before sending).

An optional attribute for routers that specifies the canonical DNS name of the router.

A descriptive name for an Autonomous System (AS), consisting of uppercase letters, numbers, and dashes. Must start with a letter and not include spaces.

Indicates the authentication method for updating RADB objects. Commonly uses BCRYPT-PW, which stores a hashed version of the maintainer’s password.

Contains the public key certificate in a secure, encoded format. Used for verifying the authenticity of a maintainer.

Specifies who last updated the object and the date of the update.
Format:

Lists the individual routes that make up an aggregated route.

Specifies default routing policies when a router lacks a more specific route. Defines the AS or router that will be used as a fallback.

A brief description of the object, typically the organization or business name.

An email address for contacting a person or role associated with the object.

Defines the routing policy for sending routes to other networks. Specifies which routes will be shared with peers.

Lists more specific routes that are allowed to be shared outside of an aggregation boundary.

A fax number for contacting a person or role.

Defines criteria for filtering routes based on attributes like IP addresses, AS paths, or communities.

A unique identifier that verifies the authenticity of a key certificate. Displayed as a hexadecimal code.

While the GEOIDX attribute can be placed in the RADb (and other IRRs) route/6 objects, the use of this attribute type remains experimental and it is unlikely to resolve any geolocation errors. We follow the recommendations in the presentation linked here: NANOG IRR Additions. It is also helpful to include one line each for ISO 3166 Alpha-2, ISO 3166 Alpha-3, and ISO_3166-2:US Subdivision Codes, and UN M.49 geocodes. Many service providers do not query an IRR for this information. Instead, they use the country code information listed with the RIR WHOIS and commercial GeoIP databases.

• IPLocation.net aggregates much of the data from ARIN and databases such as:

• DP-IP.com

• Google

• IPInfo.io

• IP2location

• IPligence

• MaxMind - GeoIP Demo

• MaxMind - Correction

• Netflix Email

The use of GEOIDX attribute is encouraged but ensuring ARIN's WHOIS service is up-to-date and correcting these databases is the best practice.

Specifies IP address ranges within an aggregated route that are not reachable.

Defines an IP address and subnet mask for a router interface.
Format:

Defines routing policies for receiving routes from other networks. Specifies which routes will be accepted from peers.

Specifies how and when aggregated routes are generated and applied. Can include conditions for when to update routing information.

The AS number of the router’s owner or operator. Mandatory for inet-rtr objects.

Indicates which route sets, AS sets, or router sets the object belongs to. Defines group membership.

Note:

• The max size of the member-of field is 4096 characters.

• Add an additional member-of attributes if more ASNs are needed

Lists the individual members of a set object, such as routes, ASes, or routers.

Note:

• The max size of the members field is 4096 characters.

• Add an additional members attributes if more ASNs are needed

Specifies the maintainer responsible for the object. Used for authentication when making updates.

Email address to notify when updates to the object are successfully made.

Indicates the method used for digital signature verification, such as PGP.

A unique identifier for a person or role object in the RADB. Used as a reference or contact handle.

Note:

• You can only use admin-c and tech-c if the NIC handle you reference already exists in a person or role object in RADb.

• If the NIC handle doesn’t match, the object won’t be accepted.

• RADb also shows the linked contact information when someone views your record.

An email address that receives notifications when the object is updated.

Specifies the AS number that announces a specific route.
Example:

The owner attribute is defined for the key-cert object. This is a generated attribute containing a description of the owner of the key. For a PGP key, the owners are the user id's associated with the key.

The peer attribute, if present, specifies a protocol peering with another router. It is an optional attribute of the inet-rtr object. The syntax is as follows:

The phone attribute is defined for person and role objects. It provides a contact phone number for the given entity.

General remarks. Can include an URL or RFC822 address (if preceeded by mailto:).

Identifier of the database containing authoritative data for this object. Use RADB for objects in the RADB Database.

A technical contact. In the RADB, either a person's name or a NIC handle may be specified.

Note:

• You can only use admin-c and tech-c if the NIC handle you reference already exists in a person or role object in RADb.

• If the NIC handle doesn’t match, the object won’t be accepted.

• RADb also shows the linked contact information when someone views your record.

The trouble attribute is defined for the role object. It is an e-mail contact address for problem/abuse reports.

The upd-to attribute is specific to the mntner class object. It specifies the e-mail address to notify in the case of an unsuccessful update attempt to an object maintained by the given mntner object.