{"id":31579,"date":"2025-10-30T13:31:53","date_gmt":"2025-10-30T13:31:53","guid":{"rendered":"https:\/\/blog.lacnic.net\/?p=31579"},"modified":"2025-10-30T16:41:15","modified_gmt":"2025-10-30T16:41:15","slug":"a-new-nro-resource-for-network-operators-working-across-multiple-rirs","status":"publish","type":"post","link":"https:\/\/blog.lacnic.net\/en\/a-new-nro-resource-for-network-operators-working-across-multiple-rirs\/","title":{"rendered":"A new NRO resource for network operators working across multiple RIRs"},"content":{"rendered":"\n

By Sof\u00eda Sofia Silva Berenguer<\/a><\/p>\n\n\n\n

The Number Resource Organization (NRO) has published a new reference page to help network operators and other members of the Internet technical community learn how to create Route Origin Authorizations (ROAs) through each of the five Regional Internet Registries (RIRs). The process of creating ROAs through each RIR portal<\/a> brings together links to each RIR\u2019s official ROA documentation, support contacts, and a high-level summary of differences across RIRs.<\/p>\n\n\n\n

It\u2019s a small but meaningful step toward making the Resource Public Key Infrastructure (RPKI) ecosystem easier to navigate, more transparent, and ultimately more consistent across RIR regions.<\/p>\n\n\n\n

Why this matters for routing security<\/h2>\n\n\n\n

RPKI is a critical building block for improving the security and resilience of the Internet routing system. It helps prevent route hijacking and misorigination, situations where Internet traffic is accidentally (or intentionally) routed through the wrong network.<\/p>\n\n\n\n

ROAs are a key component of RPKI. A ROA is a digitally signed statement that authorizes a specific Autonomous System Number (ASN) to originate routes for a given set of IP prefixes. When network operators create ROAs for their prefixes, other networks can validate the corresponding Border Gateway Protocol (BGP) routes and make better decisions about which ones to accept.<\/p>\n\n\n\n

Despite RPKI\u2019s importance, adoption is still a work in progress. A common challenge for operators who interact with multiple RIRs is navigating operational differences. Each RIR has its own member portal, terminology, and process for creating and managing ROAs. These differences can be confusing and time-consuming for newcomers and multi-region operators. That\u2019s where the NRO reference page<\/a> helps.<\/p>\n\n\n\n

Beyond convenience, this initiative supports a broader goal: enhancing consistency in RPKI service provision across the RIR system. The five RIRs collaborate closely on RPKI, yet natural variations exist, shaped by regional policies, historical systems, and member needs.<\/p>\n\n\n

Additional reading:<\/div><\/div><\/div>
RPKI best practices and lessons learned<\/a><\/div><\/div><\/section>\n\n\n

A single reference point for all RIRs<\/h2>\n\n\n\n

The new NRO page doesn\u2019t attempt to replace or rewrite any of the RIRs\u2019 existing documentation. Instead, it acts as a trusted index, providing direct pointers to where each process is explained in detail by the RIR itself.<\/p>\n\n\n\n

This approach keeps each RIR\u2019s website as the source of truth, while reducing friction for anyone asking, \u201cWhere do I go to create a ROA?\u201d<\/p>\n\n\n\n

The page includes links to:<\/p>\n\n\n\n