Internet Routing Registry
An Internet Routing Registry (IRR) is a database of Internet route objects for determining, and sharing route and related information used for configuring routers, with a view to avoiding problematic issues between Internet service providers.
The Internet routing registry works by providing an interlinked hierarchy of objects designed to facilitate the organization of IP routing between organizations, and also to provide data in an appropriate format for automatic programming of routers. Network engineers from participating organizations are authorized to modify the Routing Policy Specification Language (RPSL) objects, in the registry, for their own networks. Then, any network engineer, or member of the public, is able to query the route registry for particular information of interest.
Relevant objects
Status of implementation
In some RIR regions, the adoption/updates of for e.g. AUT-NUM[7] (Represents for e.g. Autonomous system (Internet)) is only done when the record is created by the RIR, and as long nobody complains about issues, the records remain unreliable/original-state. Most global ASNs provide valid information about their resources in their e.g. AS-SET[8] objects. Peering networks are highly automated, and it would be very harmful for the ASNs.
See also
References
- ↑ "4.2.1 Description of the AUT-NUM Object". https://www.ripe.net/manage-ips-and-asns/db/support/documentation/ripe-database-documentation/rpsl-object-types/4-2-descriptions-of-primary-objects/4-2-1-description-of-the-aut-num-object. Retrieved 28 January 2016.
- ↑ "4.2.3 Description of the INET6NUM Object". https://www.ripe.net/manage-ips-and-asns/db/support/documentation/ripe-database-documentation/rpsl-object-types/4-2-descriptions-of-primary-objects/4-2-3-description-of-the-inet6num-object. Retrieved 28 January 2016.
- ↑ "4.2.5 Description of the ROUTE Object". https://www.ripe.net/manage-ips-and-asns/db/support/documentation/ripe-database-documentation/rpsl-object-types/4-2-descriptions-of-primary-objects/4-2-5-description-of-the-route-object. Retrieved 28 January 2016.
- ↑ "4.2.4 Description of the INETNUM Object". https://www.ripe.net/manage-ips-and-asns/db/support/documentation/ripe-database-documentation/rpsl-object-types/4-2-descriptions-of-primary-objects/4-2-4-description-of-the-inetnum-object. Retrieved 28 January 2016.
- ↑ "4.2.6 Description of the ROUTE6 Object". https://www.ripe.net/manage-ips-and-asns/db/support/documentation/ripe-database-documentation/rpsl-object-types/4-2-descriptions-of-primary-objects/4-2-6-description-of-the-route6-object. Retrieved 28 January 2016.
- ↑ "4.2.7 Description of the AS-SET Object". https://www.ripe.net/manage-ips-and-asns/db/support/documentation/ripe-database-documentation/rpsl-object-types/4-2-descriptions-of-primary-objects/4-2-7-description-of-the-as-set-object. Retrieved 28 January 2016.
- ↑ "4.2.1 Description of the AUT-NUM Object". https://www.ripe.net/manage-ips-and-asns/db/support/documentation/ripe-database-documentation-1.7.5/rpsl-object-types/4-2-descriptions-of-primary-objects/4-2-1-description-of-the-aut-num-object. Retrieved 13 April 2015.
- ↑ "4.2.7 Description of the AS-SET Object". https://www.ripe.net/manage-ips-and-asns/db/support/documentation/ripe-database-documentation-1.7.5/rpsl-object-types/4-2-descriptions-of-primary-objects/4-2-7-description-of-the-as-set-object. Retrieved 13 April 2015.
- Representation of IP Routing Policies in a Routing Registry (ripe-81++)
- Internet Routing Registry Tutorial
External links
- RFC 2622, Routing Policy Specification Language
- RFC 2650, Using RPSL in Practice
- IRR LIST, A list of routing registries with links to databases and general information
- IRR accuracy, BGPmon.net - How accurate are the Internet Route Registries (IRR)
 |  |
