Summary

  • Hernán Moguilevsky authored both versions of LAC-2020-10. LACNIC implemented the policy on 27 April 2023.
  • The adopted clause gives the recipient of a registered IPv4 sub-assignment the right to create and manage ROAs for that prefix while it remains in LACNIC WHOIS.

Picture a technician at a network exchange waiting for someone upstairs to sign a slip before a route can receive its origin authorization. The technician has the sub-assigned addresses and operates the network; the address holder has the ROA pen. Hernán Moguilevsky knew the operating side of that arrangement. LACNIC's biography records his years running networks at Argentina's CABASE exchange and later work in PIT Chile's networking team. LAC-IX lists him in its policy working group.

His LAC-2020-10 proposal took aim at one stubborn permission. A provider could sub-assign an IPv4 block while the recipient still had to depend on the holder to sign the ROA. Moguilevsky proposed placing the signing and management right with the recipient for the duration of the delegation. The adopted sentence sits inside section 2.3.2.13, where ISPs must register assignments of /29 or larger in LACNIC WHOIS within seven days. That placement matters. Registration names the operating recipient and sets the condition for the ROA right.

The drafting history has a useful correction of its own. Version 1 used “exclusive” and “customer,” and spoke of ROA certificates. In version 2, the sentence became the recipient's right to create and manage Route Origin Authorizations while the prefixes are registered. LACNIC staff explicitly recorded the removal of “customer” and “certificates.” The current policy manual retains the leaner text. It gives a named party an operational action under a visible registry condition; it does not need an ornamental crown on that party's head.

LACNIC's staff analysis also describes what happens when the registration ends: associated ROAs are revoked. For delegated certificate systems, staff discussed child certificates and synchronized cancellation. Those details reveal why a one-line permission has a long tail. A ROA still sitting in the system after the underlying sub-assignment disappears is a stale instruction about who may originate a route. The policy makes the WHOIS entry a practical hinge between an operator's authority and its expiry.

The board ratified the proposal in August 2022; LACNIC implemented it on 27 April 2023. The pen moved, but it did not float away. Its holder is the registered recipient, and its paper trail is the assignment record.