Summary

  • The NRO published its 2026-Q3 RIR Comparative Policy Overview on 9 October as a quarterly reference, not as a policy statement by the five registries.
  • Its ASN section shows why the document is a map: the table groups regional criteria under one heading, but each RIR’s reported eligibility test differs and must be checked against the current regional policy before action.

A comparison table is most useful when it tells an operator where to look next. The NRO’s 35-page Q3 overview does that across AFRINIC, APNIC, ARIN, LACNIC and RIPE NCC. It ranges from membership and resource transfers to IPv4, IPv6, autonomous system numbers, database registration, abuse contacts, reverse DNS and experiments. The breadth is valuable for teams whose work crosses regional boundaries. The date on the cover is just as important as the scope: this is version 2026-3, published on 9 October 2026.

The NRO is careful about what the document is. Its overview page calls it a reference for the Internet community, not a policy statement by the RIRs. It also says the comparison is accurate on its publication date but may become outdated when a policy is implemented later. The NRO directs readers to the policy sections of each registry for official documents. That warning is not a footnote to the comparison; it defines how to use it.

The ASN section gives a concrete example. As the Q3 overview reports the rules, AFRINIC ties eligibility to membership and an interconnection, routing-policy or technical-need test, with a limited path for an applicant planning to meet the condition. APNIC describes direct and sponsored routes and tests for current or planned interconnection under RFC 1930 guidance. ARIN’s table says an organization may receive one ASN on request, while additional numbers require a routing-policy or other technical justification.

LACNIC asks for a current or near-term need to interconnect and details of the intended routing policy; RIPE NCC’s entry requires multihoming and a new unique external routing policy.

Those are not interchangeable versions of one form. The table’s shared row label makes comparison possible, while the criteria beneath it show why a network planner cannot infer that an ASN request accepted in one region will meet another region’s test. Nor should this article turn the snapshot’s entries into present-tense instructions: the NRO itself marks the document as time-bounded. The point is that a common topic does not imply a common rule.

For an application, transfer or compliance review, use the overview as an index. First identify the resource, applicant, region and decision date. Then open the current policy text at the relevant RIR, note its version and implementation date, and verify any related procedure or membership requirement. If the NRO table and a later regional document differ, the later official text is the next document to check; the comparison alone cannot resolve the discrepancy.

Heng Lu’s Note 73 supplied only a narrow editorial question: participation in a policy process and authority to decide are not the same thing. The article’s factual boundary comes from the NRO’s own disclaimer, not from that note. The decision useful to operators is straightforward: keep the snapshot’s date attached whenever it enters a ticket, procurement memo or approval pack.

Sources