Summary

  • LACNIC lists LAC-2025-5, on IPv4 sub-assignment to third parties, as Ratified; its chronology shows Board ratification on 9 March 2026 and ratification on 24 March.
  • The final text calls for each qualifying sub-assignment to be linked to the recipient ASN in WHOIS and for a public log of the address block, recipient ASN, date and start-or-end event.
  • LACNIC’s Policy Development Process places implementation after ratification. The checked sources do not identify a live log entry, a particular block, a sub-assignment, a breach or an implementation date.

A policy state is not an event record

LAC-2025-5’s public history preserves a route through discussion, consensus assessments, Board ratification and final ratification. That is a public institutional result. It is not a reason to invent a named transaction, a live service or an outcome for any holder.

The intended record is concrete. The final text limits the mechanism to IPv4 sub-assignments, places conditions around recipient identity, scale and stated need, and says that each qualifying sub-assignment should be recorded in LACNIC WHOIS with the recipient ASN. It also calls for a public movement log carrying the block, recipient ASN, date and whether the observed event is a start or an end. Those fields would make a later record useful because they bind a claim to a bounded object and time.

LACNIC’s own PDP separates ratification from implementation. Its diagram places implementation after Board ratification, and LACNIC’s policy-development overview describes the Policy Manual as the document containing policies implemented in the region. That sequence does not nullify ratification. It prevents the opposite error: treating a policy-status label as proof that a particular log entry exists, that a particular organization used the mechanism, or that a particular address block was lawfully sub-assigned.

The proportionate remedy is an operating receipt beside each public event: policy and version, implementation state, stable entry identity, event type, address block, recipient ASN, publication time, source-system label, correction lineage and a coverage statement. It does not expose contracts or decide disputes. It lets a reader distinguish a policy promise from an observed event without turning the registry record into a title deed or verdict.

Sources checked