Summary

  • Raúl Echeberría’s 2011 LACNIC essay treated members as both principals of a membership organisation and recipients of operational services. A new customer-service department was meant to make resource requests and contact with the registry easier to navigate while encouraging members to participate in policy discussion and elections.
  • His parallel service as Chair of the Internet Society Board was created under a separate institutional process. The records support a story about distinct authorities and practical responsibilities, not a claim that Echeberría represented every user in Latin America and the Caribbean or personally controlled Internet number allocation.

The public record of Raúl Echeberría’s work contains a deceptively simple pairing. He was a senior executive at LACNIC, the Regional Internet Registry serving Latin America and the Caribbean, and for several years he chaired the Internet Society’s Board of Trustees. Both roles placed him in conversations about the Internet’s institutions. Both involved people who described the Internet as global and open. Yet the offices were constituted by different organisations, had different constituencies, and carried different kinds of authority.

That distinction matters because institutions that supply operational services can also depend on member participation for legitimacy. A registry receives resource requests, maintains records, and supports its members. Those members may also elect directors, attend meetings, pay fees, and contribute to policy discussions. The same organisation can therefore encounter a customer at one point in a service workflow and a member-principal at another. If leaders blur those roles, a smooth support channel can be mistaken for democratic consent, or a payment can be mistaken for a vote.

If they separate them too sharply, the institution may deliver a technically correct service while failing to hear from the people whose participation sustains its rules.

Echeberría’s 2011 account of LACNIC’s strategic planning placed that tension in unusually direct terms. He argued that LACNIC’s members were both the organisations that mandated the non-profit and the organisations receiving its services. The same customers, he wrote, requested IP resources, paid membership fees, attended LACNIC meetings, and voted. His phrasing was not a legal ruling or a survey result. It was an executive’s description of how the organisation should understand the relationships passing through its doors.

The proposal that followed was practical. LACNIC had chosen a stronger customer orientation as one of its main lines of work. A new Customer Service Department would make contact more coherent, improve the process for requesting resources, shorten response times, and help members track requests. The first focus was the registry system through which IPv4, IPv6, and autonomous system number resources were requested. In the department head’s contemporaneous account, the registry system was both the organisation’s core service and a first point of contact with a customer.

A separate task was to strengthen member participation in public-policy discussions and institutional elections. This was not merely another feature of customer support. It was a different relationship with a different consequence. Resolving a request is a service outcome. Voting in a board election is an exercise of formal membership authority. Joining a policy discussion may influence the rules under which a resource is used or transferred, but attendance by itself does not prove that a view was broadly authorised.

Echeberría’s description put the service channel and the governance channel in the same frame, while the institutional design still required them to remain distinguishable.

That boundary is the centre of this article. Echeberría’s record does not show that a customer-service programme caused a measurable rise in participation, that every stated service improvement was implemented, or that members felt a particular way about the programme. It does show an executive naming a structural problem, proposing an organisational mechanism, and connecting service quality to member engagement without treating the two as identical.

The accompanying ISOC records show him serving as a Board Chair within another body, where the authority of the role is visible in agendas, committee work, Board meetings, and the relationship with a separate President and CEO.

The work before the titles

LACNIC’s retrospective of 2014 places Echeberría in the organisation’s early history. It says he was part of the group that began working on LACNIC’s creation in 1998 and formally joined its Interim Board in June 2002. He chaired that interim Board until November of the same year. The retrospective then says that he resigned as CEO on 30 June 2014 after twelve years in the position. These dates do not provide a complete biography, and they do not by themselves establish what decisions he personally made. They do establish that his executive tenure was tied to a long period of institutional formation rather than a brief public appointment.

For a regional registry, institutional formation is not an abstract project. The work sits where technical operations, membership, and policy touch. A registry has to process requests for number resources, maintain data, communicate requirements, support organisations, and participate in a wider system whose rules are developed through procedures involving the regional Internet community. The registry’s operational reliability is visible in whether users can complete tasks and whether its records can be used.

Its legitimacy is visible in a different set of questions: who participates, how rules are decided, and what authority a participant actually holds.

Those questions became more concrete around 2011. LACNIC’s official account of the central IPv4 pool’s exhaustion describes Echeberría as Executive Director and NRO Chair at the moment when the final central IPv4 blocks were transferred to the five Regional Internet Registries. It says he symbolically received the block corresponding to Latin America and the Caribbean during a ceremony in Miami.

The post situates that ceremony within a coordinated transfer to AFRINIC, APNIC, ARIN, LACNIC, and RIPE NCC and notes that the remaining address space had been distributed according to a global policy approved by the regional communities and ratified by ICANN.

The careful reading is important. A ceremony can make a moment legible to a broad public; it does not turn the person accepting an object on stage into the author of the allocation policy. The source describes a symbolic receipt of the region’s block. The policy was a separate product of community processes and ratification. Echeberría’s public position made him a visible participant in an institutional transition, but the factual record does not make him a sovereign over the address pool. The difference between visibility and authority is one of the recurring lines in his public career.

A service strategy with a governance edge

In April 2011 Echeberría published an essay titled “Closer to our Customers, Providing Better Services.” He wrote in the first person as LACNIC’s Executive Director and said that the latest strategic-planning process had selected stronger customer orientation as a principal line of work. His argument began by holding two descriptions together: LACNIC was a membership-based non-profit mandated by its members, and those same members received services from LACNIC. Therefore, he said, members were also customers.

The statement is easy to compress into a slogan: members are customers. That would lose the more interesting part. Echeberría did not replace membership with customer status. He said the same organisations appeared in both relations. They requested number resources and paid membership fees; they also attended meetings and voted. The organisation should understand the whole relationship rather than treat each contact channel as an isolated encounter. The claim was about how staff should see a person or organisation moving through LACNIC’s work, not about erasing the distinction between using a service and exercising membership rights.

This framing addressed a common operational risk. When an organisation has several teams and contact points, a member can experience the institution as a series of disconnected desks. A resource request may have one owner, a fee question another, an event a third, and a policy discussion a fourth. In such a structure, a person may need to retell the same context or may be unable to find out who is responsible for the next step. A shared view of the customer promises coordination across those points. It treats the interaction as a relationship with the institution, not a queue item that disappears when it leaves one team.

The proposal also carried a governance risk. The more capable a support system becomes at understanding users, the easier it is to mistake the service department’s view of demand for the membership’s collective judgment. A request log can show where people encounter friction. It cannot, on its own, establish which policy the community has authorised. A satisfaction survey can indicate reported experience if designed and interpreted carefully. It cannot replace an election. Attendance can signal interest, but it does not necessarily show who was absent, whose interests were represented, or whether a proposal won procedural approval.

A customer orientation can strengthen trust and reduce operational exclusion, but it does not create a mandate by itself.

Echeberría’s 2011 essay did not spell out all those safeguards. It did, however, place both kinds of relationship in the same explanation. That creates a useful standard for assessing the organisational move: did it make service easier while preserving members’ separate opportunities to deliberate and decide? The first-party record supports the design question. It does not provide a complete evaluation against it.

A department, not just a promise

A few months later, LACNIC published an interview with Luisa Villa y Battenberg, identified as the head of the Customer Service Department. The interview is important because it shows that customer orientation had moved beyond an executive essay into an organisational unit. It also provides an independent institutional voice about the intended work, even though it remains LACNIC’s own account and is not an external audit.

Villa described a broad programme. The department intended to make the website more user-friendly, simplify resource requests, improve response times, and develop services as new needs were detected through closer contact. It planned to make email and telephone communication more efficient and, when possible, visit customers during seminars in their countries. Centralising points of contact was expected to make it possible to track requests regardless of status. The stated priority was satisfaction with LACNIC services, with attention to service quality and functionality.

The initial focus on the registry system gave the plan a concrete operating surface. That system handled requests for IPv4, IPv6, and ASN resources. Villa described it as the first point of contact and as the core of LACNIC’s services because it was tied to resource allocation. A better interface there could matter to an organisation trying to plan a network deployment, receive a resource, update records, or understand why a request had not progressed. The source does not give a measured before-and-after response-time series. It does identify which process the department chose first and why.

The interview also points to a feedback loop. The department proposed surveys to learn how satisfied customers were and to collect suggestions for improvements. At the same time, it planned to encourage more participation in discussion lists, the upcoming Board elections, and the annual members’ assembly. This is more than a list of tasks. It reveals how the department understood its place: it would handle service interactions while also trying to make organisational participation more accessible.

The two tracks should not be collapsed. A survey is a way to collect feedback about an experience. A discussion list is a forum where a proposal can be tested and contested. An election selects representatives according to the relevant rules. An assembly is a formal member venue with its own procedures. The department could help people find those channels and understand how to join them. Whether the resulting participation was broad, representative, influential, or decisive would require evidence about the channels themselves and the decisions they produced.

The distinction also clarifies what leadership can and cannot claim. Echeberría could set a strategic direction, organize an executive function, and explain why service and participation mattered. The department’s head could define priorities and methods. Staff could implement a new interface or handle requests. Members could use the service, join a discussion, vote, or decline to participate. A public article by the executive and an interview with the department head document the first two layers of that chain; they do not, without further records, establish the full result at the last layer.

Why the same member appears in several roles

LACNIC’s member identity joins functions that are easy to separate in a diagram but difficult to separate in a person’s working day. A network organisation may request addresses, pay a fee, attend a technical meeting, contribute to policy discussion, and vote. Some organisations will do all of these. Some will do only one or two. Each interaction has different stakes and rules.

The service relationship is often individual and time-sensitive. An organisation needs an answer about a request or a record. It may care about clarity, predictability, and the time required to resolve a problem. These are not trivial matters. In a technical environment, uncertainty around resources or records can affect planning and operations. A registry that cannot explain its process creates costs even when its allocation policy is formally sound.

The membership relationship is collective and procedural. It concerns who qualifies as a member, what rights membership confers, how elections work, and how a decision becomes valid. A member may be simultaneously a customer in one workflow and a principal in a governance workflow. But the two roles are not interchangeable. A service ticket does not cast a ballot. A fee receipt does not show how a member voted. A high support rating does not prove that a rule has community consent.

This is why Echeberría’s formulation matters. He described a single organisation as moving through several interfaces with LACNIC. The intended benefit was institutional memory: staff would recognise that a service recipient was also connected to meetings, membership, and voting. That could help staff route questions, explain processes, and keep communication consistent. It could also make it easier for the organisation to invite members into formal processes rather than treating them as a list of addresses to be served.

There is a corresponding design obligation. If a registry maps people across service and governance channels, it needs to preserve purpose. Information gathered to resolve a resource request should not quietly become a proxy for political preference. A staff member should not infer a member’s election position from a service interaction. A process designed for efficient support should not determine whose voice counts. The public records here do not show that LACNIC crossed those lines; nor do they provide a privacy or data-governance audit of the department.

These are risks inherent in combining a comprehensive institutional view with separate forms of authority, not allegations about what Echeberría or LACNIC did.

The design question is therefore not whether service and governance should be connected. They inevitably meet in a member organisation. The question is whether each connection is transparent and bounded. A customer-service department can signpost the election calendar, clarify how to submit a policy comment, or report that members cannot find a form. It cannot decide what the membership intends. An assembly can debate and vote. It should not be judged by ticket closure rates. A good institutional architecture allows each channel to inform the others without pretending they measure the same thing.

A second institution, a different office

The Internet Society records make Echeberría’s second office visible in another way. Its 2010 Annual Review lists him as a trustee and Chair, with a term running from 2008 to 2011. The 2011 Annual Review contains a message signed by Echeberría as Chair of the Board and a separate message from Lynn St. Amour as President and CEO. The separation was not a nuance in title. It distinguished the Board’s leadership from the chief executive’s operational role.

The Board meeting records show the chair’s work in practice. Minutes from an Executive Committee teleconference in March 2010 list Echeberría among those present. They record him presenting the proposed agenda for the Board meeting, proposing that the CEO’s performance review be completed in the first part of the year, and offering to work on the evaluation with the Treasurer and another trustee. The minutes also note discussion of a working group on the Board’s governance role. The page marks the minutes unconfirmed, so they should be read with that status in view.

Still, they offer a specific record of agenda-setting and oversight responsibilities rather than a ceremonial portrait of the chair.

At the June 2010 Board meeting, the resolution establishing the Executive Committee included Echeberría as Chair alongside the President and CEO, Treasurer, Secretary, and other trustees. The arrangement makes one institutional boundary legible: the chair had a role in a committee that included the chief executive, while the CEO remained a distinct office. In 2011 the Board again established an Executive Committee and named Echeberría as its Chair. A separate resolution appointed him chair of the Compensation Committee. Those were Board decisions, not powers inherent in being a prominent figure in the regional Internet community.

The records show routine governance as well as high-level symbolism. The chair opens meetings, works with the agenda, coordinates committee responsibilities, and participates in Board oversight. In the March 2012 minutes, Echeberría is listed among the trustees present at a meeting where the Board discussed the relationship between ISOC and ICANN in closed session. The minutes then record a transition to an open session. Without a public resolution or fuller account, no conclusion should be invented about what the closed discussion decided.

In 2012, the Board thanked him for his service as Chair and identified him as a member of the By-Laws Review Committee.

This record does not prove that one office influenced the decisions of the other institution. LACNIC and ISOC may have shared interests, and Echeberría’s experience may have helped him understand both. The sources cited here do not establish that LACNIC directed ISOC, that ISOC directed LACNIC, or that the Board Chair spoke on behalf of all RIR members. The significance is more modest and more useful: one person could hold roles in both organisations, but the authority for each role was institution-specific. At LACNIC he was an executive.

At ISOC he was a trustee elected or appointed within ISOC’s own process and selected by that Board as Chair. Each role had its own principals, records, boundaries, and accountability routes.

The difference between representation and presence

A public leader often stands before cameras, speaks at a meeting, or receives an award on behalf of an organisation. Such moments can make a person look like the organisation itself. They do not eliminate the organisation’s internal procedures or turn one spokesperson into the authorised voice of every stakeholder.

The IPv4 handover ceremony is a clear example. LACNIC’s account places Echeberría in front of the final allocation moment for the region. The same account says that the blocks were distributed under a global policy developed and approved through regional community processes. The official description allows both facts to coexist: Echeberría was the visible executive who received a block symbolically, and he was not the sole author of the policy that made the transfer possible.

The same distinction applies to the Internet Society chairmanship. LACNIC called Echeberría the first Latin American to chair ISOC and described the appointment as recognition of LACNIC’s work. That is an institutional interpretation from LACNIC. The records independently establish that the ISOC Board had appointed or elected him to its Board and that its officers selected him as Chair. Those records make his office real; they do not give him a mandate to represent every person or organisation in Latin America and the Caribbean.

In February 2014, LACNIC reported that Echeberría and Demi Getschko had been appointed co-chairs of the Executive Committee preparing the Global Multistakeholder Meeting on the Future of Internet Governance in São Paulo. The committee was responsible for agenda, format, and invitations to stakeholder groups. The assignment is evidence of a convening role. It is not evidence that he could speak for every stakeholder group, choose participants without constraints, or decide the meeting’s eventual principles.

The distinction between convening and representation matters precisely because conveners influence what can be discussed, by whom, and in what format, while still lacking authority to dictate what each constituency believes.

A person-centered history should therefore describe observable decisions and their institutional paths. The records show Echeberría advocating for a customer-oriented service strategy, participating in ISOC Board and committee work, and accepting public assignments associated with LACNIC. They show him leaving the LACNIC CEO role in 2014 after twelve years. They do not provide access to his private motives, the internal deliberations behind every decision, or the voices of every member served by LACNIC. Keeping those limits in view is not a way to diminish his work. It prevents the story from confusing reputation with documented performance.

What can be said about results

The strongest evidence in the 2011 service story concerns the design and launch of an organisational function. The department existed; its head described it; its priorities were published. That is meaningful. Establishing a department creates an owner for a set of service problems. It can make improvements easier to coordinate and give the organisation a place to collect user feedback.

The public sources available for this commission do not show a complete series of service metrics before and after the department’s creation. They do not report how many requests were processed through the registry system, how much response time changed, what fraction of cases were resolved at first contact, or whether the new centralised tracking reduced repeat requests. They do not publish the survey design, sample, response rate, or results. Without these measures, it would be inaccurate to say that the department improved service quality, even if that was its stated aim.

The right conclusion is narrower. LACNIC’s leadership identified a need to orient the organisation around the member’s whole relationship with the registry. It created a department to coordinate service and gather feedback. It placed the registry system first because that was where organisations requested core number resources and first encountered the institution. It also described participation in policy discussions, elections, and the member assembly as goals. The evidence shows the organisational choices and the intended mechanisms. It does not prove their effects.

This distinction helps explain why service and accountability should be measured separately. A service dashboard might report time to first response, time to resolution, reopen rates, completeness of explanations, and the share of requests whose status can be tracked. A participation record might report who received notice, which classes of members could join, how many submitted comments, how voting eligibility was applied, turnout by eligible members, and how the final decision followed the published procedure.

These are examples of what a future public record could make visible; they are not claims that LACNIC used these exact indicators in 2011.

Likewise, a satisfaction score would not be a complete governance measure. People might value a rapid answer and still oppose a policy. A member could be satisfied with one service and inactive in institutional elections. A network operator could participate in policy debate without being a customer of a particular service during that period. Any one metric would capture a limited view. A more credible assessment would preserve the differences and show how the organisation interpreted them.

Echeberría’s own rhetoric can be read as an invitation to such a broader view. He urged LACNIC staff to see the same member across the service channels, meeting life, and voting process. That is a statement about organisational attention. It is not enough to establish institutional accountability. For that, the organisation would need records showing how service requests were handled, how participation channels were opened, how decisions were made, and how members could question or appeal the outcomes. The available material starts to show the shape of this agenda; it does not complete the audit trail.

The executive’s leverage and its limits

A chief executive can influence what an institution notices. A strategic plan can elevate service quality from a back-office concern into an organisational priority. A department can give that priority a named owner. A public explanation can set expectations for staff and members. Each is a real form of executive leverage, but none is equivalent to unilateral authority over community policy.

The record of LACNIC’s member-service initiative shows this mix. Echeberría described the direction and rationale. The department head translated them into operational priorities. The registry system became the initial focus. Member participation was encouraged through distinct channels. The Board election and annual assembly were not replaced by the new customer interface. The strategy sought to make LACNIC’s relationships more coherent, while the formal member process still mattered for institutional decisions.

This is an important constraint on executive storytelling. A leader may say that a programme is intended to make an organisation more responsive. That statement does not certify that all recipients experienced it as more responsive. An executive may say that members are also customers. That does not transform every member preference into an instruction, nor does it make every customer a member. A leader may speak at a global forum. That does not confer an unlimited mandate to represent the entire region.

Public narratives often turn an institution’s work into a personal story because people remember names more easily than committees. The risk is that a founder or chief executive becomes the explanation for every organisational result. The opposite mistake is also possible: treating the executive’s role as empty because formal authority belongs to members, a board, or a policy forum. Echeberría’s record suggests a more accurate account. Executive leadership can define problems, propose structures, convene people, and execute decisions within assigned authority.

The public evidence should then be used to identify what others decided, what staff implemented, and what remains unmeasured.

This approach preserves human interest without inventing a private psychology. Echeberría’s career intersected a pivotal shift in Internet number resources, an organisation’s effort to redesign how members experienced its services, and an international governance body where he carried board responsibilities. Those are concrete stakes. They affect the organisations that request resources, the members who govern a registry, and the wider community that depends on rules being credible. The story can be about the choices visible in the record, not about an imagined inner motive.

A leadership test for member-based infrastructure

The practical test emerging from these records is not whether a registry should think of members as customers. LACNIC’s own 2011 account says that it should do so because members were both principals and service recipients. The harder test is how an organisation preserves that duality without collapsing it.

First, service processes need clear responsibility. A member should know where to submit a resource request, how to track it, what information is needed, and who explains a delay. The 2011 department plan directly addressed these friction points through a user-friendly website, simpler request processes, faster response, and consolidated tracking. If such commitments are made, later reporting should show which were implemented and what changed.

Second, governance channels need their own visibility. A support department can tell members how to reach discussion lists, elections, and assemblies. The organisation should also make clear which channel makes which decision. A policy discussion is not an election; an election is not a service ticket; a satisfaction response is not necessarily a formal member position. Clear process descriptions help members choose the right route and reduce the risk that an institution cites the easiest metric as evidence of consent.

Third, feedback should lead to an accountable response. Collecting suggestions is only the first step. A useful feedback loop would identify recurring issues, state who owns a remedy, explain what the organisation changed, and preserve the right to disagree with the remedy. If the institution cannot address a complaint, it should say why and identify any review path. The 2011 interview described surveys and tracking as intended instruments; it did not show the final publication of such an accountability loop.

Fourth, role boundaries need to be explicit when one person holds positions across institutions. A LACNIC executive’s participation in an ISOC Board role can create experience and connections. It does not merge the institutions. Each decision should be attributable to the body that made it, each chair should be accountable under that body’s rules, and each public claim should state the capacity in which the person is speaking. The records from ISOC offer a model of visible role differentiation: Chair, President and CEO, Treasurer, and Secretary are identified separately in Board documents.

Finally, the institution should make absence legible as well as participation. A list of attendees or voters cannot by itself show whether all eligible groups had access, whether barriers prevented participation, or whether a result was accepted. That does not make participation meaningless; it means the denominator and process matter. For a membership organisation, the question is not only who spoke but also who could speak, how a view was registered, and what converted it into a decision.

These tests are useful because they turn broad claims about openness into operational questions. Can a member obtain a clear status for a resource request? Can a member find the next election or policy process? Can observers distinguish a staff decision from a board decision and a community policy decision? Can the organisation show what happened after feedback arrived? Such questions do not imply that LACNIC failed them. They identify what a complete public assessment would need to know.

The end of a tenure is not the end of the institution

When Echeberría left the CEO role in June 2014, LACNIC’s retrospective placed his twelve years in the context of an organisation whose creation work had begun before he formally joined its Interim Board. The same 2014 roundup described activity in several domains: community meetings, Internet governance, IPv4 policy changes, FRIDA awards, and the launch of a regional incident-response coordination centre. Those institutional events do not all belong to the departing executive, and the post does not claim that he personally produced them. It does show the breadth of the environment in which a regional registry operated.

This is a useful check against the founder narrative. Institutions outlast their founders and executives. Their operations depend on staff, boards, members, working groups, technical systems, budgets, and external relationships. An executive may be a central figure in a period of growth, but successors inherit rules and operational structures that require their own decisions. The 2011 customer-service programme should therefore be judged neither as a personal triumph by default nor as an unfulfilled promise simply because the public sources are incomplete.

Its traceable legacy is that LACNIC named a member-service problem and built a department with a defined initial focus. Evaluating long-term results would require additional primary records.

The transition also clarifies the distinction between institutional and personal continuity. Echeberría’s work in LACNIC and ISOC overlapped in time, but the appointments and responsibilities were not one continuous office. His LACNIC executive role ended; his ISOC Board service followed its own term and committee structure. Public institutions rely on handovers precisely because no one person should be identical with the organisation. The sources establish the duration and end date of his LACNIC tenure, but they do not document every succession decision or internal handover detail.

The analysis should stop there rather than invent a seamless transfer.

What his record can and cannot prove

There is enough evidence to describe Echeberría as an institutional builder and executive who publicly connected service design with membership participation. There is enough to trace a concrete service department, its stated priorities, and its focus on the registry system. There is enough to document parallel Board responsibilities at ISOC, including committee chairmanship and work on agendas and CEO evaluation. There is enough to situate his tenure around the creation and growth of LACNIC, the 2011 IPv4 pool transition, and his 2014 departure.

There is not enough in these sources to quantify service improvements, infer the opinions of all members, attribute every LACNIC outcome to Echeberría, prove that customer orientation caused more democratic participation, or treat an ISOC board position as regional representation. Nor is there evidence here of conflict between his roles, misconduct, or improper influence. The prudent story is narrower than either a hero narrative or a suspicion narrative: a leader worked across service and governance settings, named the dual identity of LACNIC members, and occupied a separate board role within ISOC.

The institutional boundaries remain visible in the records.

That account also leaves room for a better future evidence trail. LACNIC could publish a longitudinal service dashboard tied to the registry system, with definitions for request time, response time, resolution, reopened cases, and the fraction of cases with a visible status. It could publish survey methods and an explanation of how member feedback informed changes. It could connect participation notices to the actual election and policy outcomes without implying that participation volume alone proves legitimacy. And it could preserve decision records that show which body acted, what authority it used, and where members could seek review.

Those suggestions are not a claim about missing or inadequate records beyond the limited package reviewed for this article. They are a way to make the original 2011 design measurable. If the strategic objective was a more coherent relationship with members, a public record of service, feedback, and governance would let members see the difference between an intention and an outcome. It would also prevent one success measure from being made to carry more authority than it has.

A portrait of bounded authority

Echeberría’s two offices are interesting because they show how a person’s influence can cross institutions without erasing their boundaries. At LACNIC, the executive could organise service priorities and represent the registry in regional and international settings. The members remained the organisation’s principals, and policies depended on procedures broader than the executive’s authority. At ISOC, he chaired the Board and performed Board work alongside a separate President and CEO. The Board’s authority belonged to ISOC’s constitutional and procedural framework.

This is not a story about one person standing above Internet governance. It is a story about the work required to keep an infrastructure institution responsive while preserving who has the right to decide. Service is one way institutions earn trust. Membership is one way they distribute authority. Public representation is one way they make their work legible. None substitutes for the others.

The most durable detail in the record may be the sentence Echeberría wrote in 2011: the organisation that requested resources, paid fees, attended meetings, and voted was often the same organisation. The point was not that each action meant the same thing. The point was that LACNIC needed to see the whole relationship. A mature governance design takes the next step: it remembers the person across channels while keeping the consequences of each channel distinct.

Sources