Summary

  • Jordi Palet Martinez authored LAC-2022-1 versions 1 and 2, which moved rules applying across IPv4, IPv6 and ASN resources into a new general section of the LACNIC Policy Manual.
  • The proposal described its changes as editorial, yet its before-and-after text replaced a 90-day announcement rule with maximum periods of three months for IPv4, twelve months for IPv6 and six months for ASN resources; the public record does not measure what that wording changed in practice.

A sentence in the wrong place

Imagine a member looking for the rule that explains what evidence a registry may request before allocating more number resources. In LACNIC’s Policy Manual v2.16, the documentation clause was numbered 2.3.2.5 and sat inside the IPv4 chapter. Its first sentence referred to IPv4 addresses that an Internet Registry had received and to the justification for each IPv4 assignment. That placement made sense if a reader arrived through the IPv4 chapter. It was less intuitive if the same expectation applied to IPv6 address space or Autonomous System Numbers.

That mismatch between a rule’s location and its reach is the starting point for LAC-2022-1, “Unify Texts That Apply to Both IPv4 and IPv6.” The LACNIC Policy System names Jordi Palet Martinez as the author of versions 1 and 2. The proposal argues that some text located in the IPv4 section also applied to IPv6 and ASN resources, so rules shared across resource types should be collected in a general section rather than repeated or buried in one protocol’s chapter.

The proposal’s title names IPv4 and IPv6. Its rationale and proposed text go further: they explicitly include ASN resources. The title is therefore a useful clue to the problem, but a poor boundary for the proposal’s full scope. A reader who sees “IPv4 and IPv6” and stops there would miss the third resource family that appears in the body.

From definitions to general rules

Version 2 of the proposal created a new section called “General Rules” and moved the existing definitions section down to section 0. The distinction matters. Definitions tell a reader what the manual’s terms mean. General rules state obligations or procedures that can apply across several resource types. The proposal was trying to give each kind of text a more suitable address in the document.

LACNIC staff’s published interpretation lists eight subjects moved into the shared area: documentation; principles for proper administration and stewardship; resource requests; security and confidentiality; equal processing of applications; non-guaranteed routability; RPKI ROAs with origin ASN 0; and geolocation. This is not one technical protocol rule. It is a set of clauses with different jobs. Some concern what members must document. Some concern how LACNIC handles applications. Others describe routability expectations or the publication of assignment information.

The old layout could encourage a reader to treat a paragraph’s chapter as part of its scope. The proposed layout makes a different claim: where a rule sits should reflect the resources and procedures it governs. Moving text does not make IPv4, IPv6 and ASNs technically interchangeable. It makes a visible statement about which policy obligations the manual treats as common.

Documentation illustrates the point. In v2.16, the rule referred to IPv4 addresses and IPv4 assignments. In version 2’s proposed text, it referred to Internet resources and to allocations or assignments. The listed examples—engineering plans, subnetting and aggregation plans, network topology, routing plans, equipment-investment receipts and other relevant documents—remained familiar. The change was in the breadth of the subject to be documented as much as in the paragraph’s position.

For a member, this distinction can affect the first question asked when preparing an application: “Which chapter should I consult?” A shared section lowers the chance that someone reads the IPv4 clause as irrelevant to an IPv6 or ASN request. But the publication of a broader sentence does not tell us whether members searched differently, submitted different evidence or faced fewer follow-up questions. The public record provides no such before-and-after measurement.

The deadline that complicates the editorial story

There is a second detail that deserves more than a passing mention. The v2.16 manual’s general non-guaranteed-routability language said allocated or assigned resources had to be announced within a maximum of 90 days, unless a justified exception applied. Version 2 of LAC-2022-1 proposed a different formulation: a maximum of three months for IPv4 resources, twelve months for IPv6 resources and six months for ASN resources.

The proposal calls its changes “minor editorial changes” and says they are not intended to change operational aspects. LACNIC staff’s interpretation says the proposal does not affect the registry system. Those statements are important evidence of stated intent and of staff’s implementation assessment. They do not erase what is visible in the before-and-after text. A single 90-day sentence became three resource-specific periods. Three months is close to 90 days, though not always identical by calendar arithmetic; twelve months and six months are plainly longer intervals than 90 days.

That does not, by itself, prove how LACNIC or its members treated the rule, whether another provision already supplied a different operational deadline, or whether network announcements changed as a result. It does mean that the policy record contains a timeline distinction alongside the chapter reorganization. The careful account is therefore neither “only a formatting change” nor “a proven operational reform.” It is a published text change whose declared editorial purpose and differentiated deadlines should be read together.

The proposal also changed how documentation was described. Its broader phrase—Internet resources, rather than only IPv4 addresses—could make the obligation’s reach clearer. Yet clarity is an outcome to test, not an effect to assume. The policy system can confirm that a version was ratified and implemented. It cannot tell us whether a member in a particular country understood the new wording, whether staff requested more or less documentation, or whether one resource class encountered a different compliance burden.

A policy contribution, not a personal veto or mandate

The official record attributes versions 1 and 2 to Jordi Palet Martinez. That is a meaningful, documentable role. It is not evidence that he alone decided the text, controlled the policy forum, directed the board or implemented the rule. A proposal enters a community process; a submission is not the same thing as consensus or institutional authority.

The listed process shows several distinct stages. Version 1 was presented at LACNIC 37 on 4 May 2022, and version 2 at LACNIC 38 on 4 October. The system records a discussion period from 14 September to 8 November 2022, a first consensus assessment through 22 November, a last call for comments through 20 December and a second consensus assessment through 27 December. It records board ratification on 22 December, a ratified status dated 23 January 2023 and implementation on 8 February 2023. The record does not supply a vote count in the displayed timeline, so none should be inferred from it.

The status page marks the proposal as implemented and 100% complete. LACNIC’s Policy Manual history lists LAC-2022-1 among the changes added in version 2.17; the current index is version 2.21. These are strong records of procedural completion and documentary incorporation. They are not operational outcome data. Completion answers “Was the approved text incorporated?” It does not answer “Did application quality improve?” or “Did the new time periods change routing behavior?”

A dated RIPE NCC event biography describes Jordi as contributing to IETF and RIR policies since 2001 and working on IPv6 deployment. APNIC’s 2018 author page identified him at that time as CEO/CTO of The IPv6 Company. This background situates the proposal in a broader record of policy and technical participation, but it does not establish his present job title or explain the motivations of other participants in LACNIC’s process.

What a chapter can and cannot tell a reader

Policy manuals are operational maps as well as archives. A clause placed under IPv4 suggests a relationship to that resource even when its underlying principle may span IPv6 or ASNs. Consolidating common rules can make the map more faithful to the actual reach of the text. It can also create a new risk: a general section may look universal even when the details differ by resource type.

LAC-2022-1’s proposed announcement periods show why a shared heading should not be mistaken for a single shared deadline. The text makes a common home for rules while specifying different clocks for different resources. The better reading is “common placement, differentiated application.” That distinction preserves both sides of the design: one policy framework can state general expectations while still recognizing that resource types do not follow identical operational timelines.

The policy record leaves several practical questions open. How does the published Spanish text express the scope of “Internet resources”? What evidence establishes that a resource has been announced? How are justified exceptions recorded? Do application systems and member guidance present the same deadlines as the manual? How does LACNIC distinguish a resource that is allocated from one assigned? The source record available for this article does not answer all of them.

Those questions are not reasons to discount the proposal. They define what an impact evaluation would need to examine. A stronger post-implementation account would compare the prior and current policy text, the application guidance used by members, staff procedures and representative cases across IPv4, IPv6 and ASN resources. It would also separate the documentation change from the announcement timeline. Without that evidence, a claim that the proposal reduced ambiguity or changed operations would outrun the public record.

The result: scope made explicit, effect still unmeasured

Jordi Palet Martinez’s LAC-2022-1 contribution is best understood as a policy-architecture intervention with a textual complication. It addressed a mismatch between where cross-resource rules were stored and the resources to which they applied. It brought a collection of rules into a general section and clarified that documentation language could address Internet resources more broadly than IPv4 assignments alone.

At the same time, the new text replaced one announcement period with different periods by resource type. The proposal’s editorial framing and staff’s no-system-impact assessment are part of the evidence; so is the wording itself. The record establishes ratification, implementation and later incorporation into the policy manual. It does not establish whether those changes reduced administrative burden, altered member decisions or affected routing in practice.

That separation is the lasting lesson of the case. The address of a rule in a manual can shape how readers interpret its reach. The words inside the rule can still carry a distinct obligation. And a completed policy process, even one marked 100% implemented, is not the same as a measured outcome. The document shows what LACNIC decided to publish and when. It does not show what changed on the network.

Sources