Summary

  • LACNIC says IRR route objects help organizations share routing policy and build BGP filters, often automatically.
  • BTW analysis: automation is safer when operators know which system generated each object and how recently consumers refreshed it.

Sources: LACNIC’s IRR design, RPKI and IRR FAQ, and the operational progress report.

LACNIC describes an Internet Routing Registry as a database of route objects through which organizations publish routing-policy information. Other networks can consume those objects to construct BGP filters, and that construction is often automated.

The important detail is how LACNIC populates the view. Its design uses RPKI ROAs to generate route and route6 objects, while registry information supplies other object classes. LACNIC’s FAQ lists AUT-NUM, ROUTE, ROUTE6, AS-SET, MNTNER and PERSON as supported objects. It says AS-SET is created by the resource holder, while the other listed objects are generated automatically.

That makes “the IRR” less like a single declaration channel and more like a public projection with multiple provenance paths. LACNIC says the objects are available through FTP, web interfaces and WHOIS. Availability helps automation, but it does not by itself show when a downstream network last rebuilt its filters or whether every relevant object is complete.

The first-party sources do not establish that all consumers refresh on one schedule, that an IRR-derived filter prevents every route leak or hijack, or that every supported object class is complete at all times. A filter built from the data is therefore operational evidence, not proof of route legitimacy.