Summary

  • Six LACNIC policy-register entries print Jordi Palet Martinez in an Authors field: LAC-2016-4, LAC-2018-14, LAC-2019-1, LAC-2023-7, LAC-2025-4 and LAC-2026-5. Two are recorded Implemented at 100 %; three print "Did not reach consensus" on the date of a first consensus assessment; one is recorded Abandoned.
  • The register records outcomes and never grounds. The drafted texts do the explaining: the adopted pair grant a transfer or an assignment, while the three that closed condition space an entity already holds — an end date, a queue position, a recovery route.

The field itself

The entry for LAC-2019-1 prints "Jordi Palet Martinez" in the Authors field for Version [1], beside Edwin Salazar and Edmundo Cazarez. The same entry records the proposal as Implemented at 100 %, in discussion from 28 February 2019, ratified by the board on 20 June 2019 and implemented on 21 July 2020 (LAC-2019-1). That single record already shows what the register is good for and what it is not: it dates every step of an adoption with a precision a meeting report cannot match, and it says nothing at all about why anyone voted the way they did.

LAC-2016-4 carries the same author name across Versions [1, 2], is recorded Implemented at 100 % and was ratified by the board on 20 June 2016. Its title is a single line of policy engineering: "Modify direct IPv6 address assignments to end users" (LAC-2016-4). The English rendering read here prints no implementation date; 1 August 2016 appears on the Spanish-language rendering of the same entry.

The three that carry the sentence

LAC-2023-7 prints its Authors field as "Jordi Palet Martinez - Version [1, 2, 3, 4, 5]" and records the status as Withdrawn with "0 %". The dates are laid out without commentary: last modified 13/08/2025, in discussion from 14/08/2025, first consensus assessment 09/10/2025 - 23/10/2025, Did not reach consensus 23/10/2025, Withdrawn 22/04/2026 (LAC-2023-7).

Its operative text is where the substance sits. "Both temporary and permanent IPv4 address transfers will be allowed between LIRs and/or end users (hereinafter “entities”), under the conditions below." Then two narrowing sentences follow. "However, temporary transfers will only be allowed within the region (temporary intra-RIR transfers)." And: "However, in the case of temporary transfers, a specific recipient may only receive (in total) a maximum of a /20." The clause that ties the mechanism to a clock reads: "In the case of permanent transfers, the end date of the transaction will be left blank.

For temporary transfers, the specific end date of the transfer will be specified."

The proposal opened a door — temporary and permanent transfers between entities — and then wrote a date into the transaction. That is the whole architecture of the text in three sentences: permission at the front, an expiry at the back.

LAC-2025-4 prints "Jordi Palet Martinez - Version [1]", records Abandoned with "0 %", and lays out its own calendar: last modified 02/09/2025, in discussion from 02/09/2025, first consensus assessment 28/10/2025 - 11/11/2025, Did not reach consensus 12/11/2025, Abandoned 13/11/2026 (LAC-2025-4). Its operative sentence distributes advantage inside a queue: "Those included on the IPv4 Waiting List under the provisions above will advance their position if they can justify that they have effectively deployed IPv6 and will take precedence over those who have not yet deployed IPv6." A queue position is not a new resource. It is a rank held inside a list the registry already keeps.

LAC-2026-5 prints "Jordi Palet Martinez - Version [1]", records Did not reach consensus with "0 %", and prints: last modified 15/09/2026, in discussion 16/09/2026 - 11/11/2026, first consensus assessment 11/11/2026 - 25/11/2026, Did not reach consensus 11/11/2026 (LAC-2026-5). Its operative text keeps legacy resources inside the registry's service envelope — on terms and conditions established by the Board of Directors, provided stated conditions are met — and adds that where those requirements are not met, the Board of Directors may initiate recovery procedures. Read plainly, the draft says: stay, on our terms, or the Board may come for the space. No new allocation appears anywhere in it; the subject is what happens to space someone already holds.

What the contrast is, and what it is not

The observation is textual, not psychological. Each of the three closed texts attaches a consequence to a resource relationship that already exists: an end date on a temporary transfer, a rank inside the waiting list, an administrative route by which legacy space can be recovered. Each of the two adopted texts creates a transaction or an assignment that did not exist before — inter-RIR IPv4 transfers including legacy space, and direct IPv6 assignments to end users. That is my reading of the printed clauses, offered as a reading, because the register itself is silent on grounds.

The asymmetry matters for anyone who has ever argued that policy outcomes track merit. They may track the object of the clause instead. A draft that gives something away is a draft everyone can price at zero risk; a draft that puts a condition on what a holder already has asks specific people to accept a specific loss, and those people are in the room.

The one record that comes closest to naming grounds is not a ground at all. LAC-2018-14, authored by the same three names across Versions [1, 2], sought a mechanism for transfers of IPv4, IPv6 and ASN resources between different regions, and its rationale argued that IPv6 deployment may require small IPv4 blocks for transition mechanisms or may significantly increase costs where such blocks are unavailable (LAC-2018-14). It is recorded Abandoned on 13 May 2019, with discussion beginning 30 October 2018, and its entry carries a last-modified date of 27 February 2019 sitting before the abandonment it describes.

Three defects of form worth naming

The retained text of the three closed entries prints "0 %" beside each status and does not state what the percentage measures. It is not described here as a support level, because the register does not say it is one.

All three closed entries print a "Last modified" date no later than their own "In discussion" start date: 13/08/2025 against 14/08/2025, 02/09/2025 against 02/09/2025, and 15/09/2026 against 16/09/2026. Whether that is a field-ordering convention or a stale stamp cannot be settled from the pages read; it is recorded, not interpreted.

And two LACNIC policy-list renderings disagree with the detail entries: one still calls LAC-2026-5 "Under discussion" with a current-state window of 16/09/2026 - 11/11/2026, while the detail entry prints Did not reach consensus at 11/11/2026; another calls LAC-2025-4 "Did not reach consensus" at 12/11/2025, while the detail entry prints Abandoned 13/11/2026. Both readings carry their own dates and neither reconciles the other.

The name on the record, and where it is not

A LACNIC blog post dated 30 May 2019 names Jordi Palet Martinez, Edwin Salazar and Edmundo Cazarez as promoters of a proposal authorising IPv4 resource transfers between LACNIC and other RIRs, reports consensus at the LACNIC 31 Public Policy Forum and on the policy list, and places the text in its final comments period (LACNIC, 30 May 2019). The post prints no policy identifier, so it names no proposal; the LAC-2018-14 entry's own abandonment on 13 May 2019 falls before the post, and LAC-2019-1's discussion from 28 February 2019 and board ratification on 20 June 2019 fall on either side of it.

The AFRINIC-28 Public Policy Meeting minutes, held 9 May 2018 in Dakar, associate Jordi Palet Martinez with four IPv6 proposals — AFPUB-2018-V6-001-DRAFT01, -002-DRAFT01, -003-DRAFT01 and -004-DRAFT01 — as named presenter, and record that -001-, -003- and -004- reached Last Call at that meeting (AFRINIC-28 minutes). Presenter is the role the minutes assign. They do not assign authorship, and this article does not either.

What can be checked, and what is not here

The register prints a name in an Authors field and prints no biography; the six entries are matched by that printed name, not by an independent identity check. LAC-2019-1 and LAC-2018-14 each print two co-authors beside him, so the adopted inter-RIR transfer clause cannot be laid at one person's door.

LAC-2019-1's requirement that LACNIC keep a public inter-RIR transfer log recording the transaction date, the source and destination organisations, the transferred addresses and the two RIRs comes from the entry's account of the proposal text rather than from a verbatim excerpt, and it is the most directly auditable thing in this whole file.

The APNIC proposal records that a cross-registry comparison would need were not obtained, so the second-registry layer rests on the AFRINIC-28 minutes alone, where the printed role is presenter. That is a gap in the record, named as a gap.

What survives is smaller and firmer than a verdict. One author's name appears on six registry entries; two of the texts he is printed beside became binding policy and three did not; and the difference between them is legible in the clauses, not in the outcomes. Anyone who wants the reason will have to go to the mailing lists and the forum minutes, because LACNIC's register — which dates every step with a bureaucrat's precision — has decided not to say.

Sources