LACNIC Case Study

Project overview

LACNIC wishes to offer an IRR service to its stakeholders

Architecture & RPKI-to-IRR conversion

A key principle of the LACNIC IRR service is that it will not contain any route or route6 objects that cover space not managed by LACNIC. Another expectation is that only the Internet Number Resource holder themselves can influence the route objects (aka avoiding 'the RADB model').

LACNIC generates a RPSL formatted dump from the myLACNIC environment which is imported into IRRd v4 and redistributed to the world using NRTM and WHOIS.

Software used

IRRd v4.1.x (currently in beta, pending additional testing)

Testing correct functioning

XXX TODO: document what tests we use to conclude the service works correctly