Summary
- LACNIC's register entry for LAC-2024-4 prints "Ratificación del directorio 19/12/2024" in one field and a separate "Ratificada 21/01/2025" in another; the Board's approved minutes record the ratification once, unanimously, on 21 January 2025.
- The earlier Board date falls inside the second-consensus window the same page prints, no Board record of that date was located in the documents reviewed, and the procedure's printed clock arrives at 21 January without it.
One policy, five dated lines, and a disagreement inside the page that keeps them.
The policy is LAC-2024-4, Bitácora de asignaciones de la reserva especial de direcciones IPv4 para infraestructura crítica — a log of assignments, recoveries and returns from the IPv4 pool LACNIC holds back for critical infrastructure. Its entry in LACNIC's policy system reads as a railway timetable: last call 18/11/2024 - 16/12/2024, then Evaluación segundo consenso 16/12/2024 - 23/12/2024, then Ratificación del directorio 19/12/2024, then Ratificada 21/01/2025, then Implementada 25/04/2025, with the status line reading Implementada at 100 per cent (register entry, Spanish).
Read those two middle lines again. Ratificación del directorio — board ratification — is dated 19 December 2024. Ratificada — ratified, feminine, the policy named as the thing acted on — is dated 21 January 2025. The English version of the same page keeps the split in English: Ratification by the board 19/12/2024, Ratified 21/01/2025, Implemented 25/04/2025 (register entry, English). Two fields, two labels, two dates, one decision.
Neither language version obtained for this review says what distinguishes the first field from the second. That is not an inference. It is what the page does not print.
Now put the deciding body's own record beside it. The Board met on 21 January 2025 at 17:00 UTC. Item 2.2 on the agenda was Ratificación de política LAC-2024-4 v1, and the resolution reads: El Directorio procede a la ratificación de la Política LAC-2024-4 v1: Bitácora de asignaciones de la reserva especial de direcciones IPv4 para infraestructura críticas, de los autores Hernán Arcidiacono, Ricardo Patara y Edwin Salazar Ordoñez y la aprueba por unanimidad (approved minutes, 21 January 2025). Unanimous, named authors, one sitting. No ratification dated 19 December 2024 appears in the text of those minutes obtained here.
Then the clock. LACNIC's Policy Development Process, version 8, dated 11 July 2024, prints the sequence with its durations: a last call of four weeks for any proposal that reaches consensus; within a maximum of one week after the last call, the moderators confirm whether consensus is maintained, and if it is, the proposal pasa a la ratificación por el Directorio; and at its first meeting after those four weeks the Board may accept the proposal, work out the implementation date with staff and announce it, or reject it (Policy Development Process v8).
The last call closed on 16 December 2024. The first sitting in the 2025 calendar the Board had approved is 21 January — thirty-six days later, which is my subtraction, not a figure any of these pages prints. Two independent routes converge on the January date: the body that voted, and the rule that told it when to.
What the page prints against itself is the other date. 19 December 2024 sits inside the second-consensus window of 16/12/2024 to 23/12/2024 that the same register entry prints — that is, inside the period whose whole purpose is to decide whether consensus survived, and before the step that sends a proposal to the Board at all. The distance between the page's two Board dates is thirty-three days, again my arithmetic from printed dates.
The minutes chain does not close the gap either. The approved minutes of 2 December 2024 record the Board approving the 2025 meeting calendar, whose first confirmed date is 21 January (minutes, 2 December 2024). The approved minutes of 21 February 2025 record the Board approving the minutes of 2 December 2024 and of 21 January 2025 (minutes, 21 February 2025). No minutes of any 19 December sitting appear in either document read for this piece.
So state the boundary as a boundary. No Board act, minute, notice or resolution dated 19 December 2024 was located in the documents reviewed here. Whether one exists outside that set is not established by this review, and nothing in these pages explains the field that carries the date. A reader who wants to know which day the Board acted can get to 21 January 2025 from the minutes and from the procedure's own clock. A reader who wants to know what the register's first Board field means has no route at all.
Implementation is the one milestone where the page and the record agree without strain. On 25 April 2025 a message on LACNIC's policy list announced that the policy had been implemented that month: durante este mes de abril quedó implementada la política LAC-2024-4 (policy list, 25 April 2025) — ninety-four days after the minutes, by my count. The procedure requires exactly that notification: implementation of Board-ratified proposals is to be communicated through the Policy List as soon as it occurs (Policy Development Process v8, PDF).
Entry into force is a question the dated page does not settle either. The procedure obtained here prints no fixed rule for when a ratified policy takes effect; implementation timing is analysed by the Board with staff and announced. The consolidated Policy Manual is labelled version 2.21, and in the portions of its PDF obtained for this review no general entry-into-force clause appears (Manual of Policies v2.21, PDF) — a scope, not a verdict, since the document was not read page by page. The Manual's web page is explicit about which copy governs: if the web version and the PDF conflict, the PDF prevails (Manual, web version). And in March 2026 a director was still asking the question in a Board meeting — whether ratified policies take effect from implementation or retroactively — and the legal adviser answered that the general principle applies, a partir de su aprobación e implementación (minutes, 24 March 2026).
One further wobble sits in the same file, reported here because it is printed and not because it means anything more: the 2 December 2024 minutes date their own meeting in the header, then close with the formula Siendo las 12 horas del miércoles 4 de diciembre. Header, 2 December. Closing, Wednesday 4 December.
None of this is a finding about anyone's conduct. A policy that cleared its comment periods, was ratified unanimously and was implemented on schedule is not a scandal, and the arithmetic above does not allege that a step was skipped or a meeting held in secret. What it shows is narrower and more useful: a public register that functions as the outside world's clock — the page an operator, a national registry or a lawyer opens to ask when this rule became real — prints two Board dates for one decision and defines neither.
For anyone holding the same pages, the recomputable answer is January. For the record to be recomputable on its own terms, one of two things has to change: the page prints what Ratificación del directorio records, or a Board record dated 19 December 2024 is published and named. Until then, cite the minutes for the vote and the register for the implementation, and say which document you relied on. Anything else is guessing at a column heading.
Member Briefing
Read the full trend briefing
Members read the full briefing with the source notes behind every finding.
Strategic Circle
A daily briefing in your language, built from changes we have verified.
Join for USD 20/monthCancel anytime.
Members also get the full research library, a daily briefing on the networks they follow and the private forum.






