An Internet Routing Registry (IRR) is a distributed routing information database that is maintained collaboratively for the purpose of ensuring the integrity of Internet routing. IRR objects are defined using Routing Policy Specification Language (RPSL). Internet service providers can use the information available in the IRR to develop routing plans and create access control lists, among other things, to filter the traffic on their networks.
LACNIC's IRR is characterized by the fact that the information it contains can be managed through the MiLACNIC platform. The objects currently available are mntner, person, aut-num, route, route6 and as-set.
With the exception of as-set, all objects are automatically generated when you start using RPKI and can be modified by the organization's administrative contact. Exceptionally, person objects can be updated by the corresponding user through MiLACNIC.
Note that all objects generated in LACNIC’s IRR are public. LACNIC makes them available on its ftp servers and allows them to be queried using different web interfaces and the whois service available at irr.lacnic.net
Start using IRR from MI LACNIC
The following considerations should be taken into account:
- In the LACNIC IRR, the mntner, person, aut-num, route, and route6 objects are automatically generated based on pre-existing information in the LACNIC database (ROAs). These objects cannot be deleted while the organization is using the IRR.
- As-set objects are explicitly declared by the organization's administrative contact. If you wish to delete an as-set object, go to the as-set tab.
To begin using the IRR, generate objects based on existing information, and enable the creation of as-set objects, select the [Services] / [IRR] option in the organization's context menu:
Then, select the option "Generate objects and enable the creation of as-set":
Object definitions:
- mntner: An mntner object represents the entity responsible for managing the objects in the IRR. It shows general information about the organization and its related contacts (person). In the LACNIC IRR, this object is automatically generated based on the organization's data.
- person: A person object contains information about each of the administrative, technical, and abuse contacts included in the various IRR objects. In LACNIC’s implementation, this object is automatically generated based on the information of the users associated with the organizations, IP addresses, and ASNs registered with LACNIC.
- aut-num: An aut-num object contains information about autonomous system numbers. In the LACNIC IRR, this object is automatically generated based on the ASNs assigned to the organization.
- route and route6: These objects allow specifying the Autonomous System Number that originates a BGP announcement with its corresponding IPv4 and IPv6 networks. In LACNIC's implementation, these objects are automatically generated based on the ROAs created by the organization.
- as-set: This object allows grouping Autonomous Systems into sets. In the LACNIC IRR, this object must be explicitly created by the organization's administrative contact.
Comments
0 comments
Article is closed for comments.