Summary

  • Raúl Echeberría recalled that LACNIC’s founders invited 30 guests to celebrate its recognition in Shanghai on 31 October 2002. More than 100 arrived, and the organizers pooled personal cash and credit cards to settle the bill. His joke about an oversubscribed bar sits beside a first-year annual report that records four people working in a 13-square-metre Montevideo office.
  • LACNIC’s first operating year drew on US$146,985.31 in ARIN transfers, technical and staffing support from NIC Brasil, training and policy support from NIC México, and a supervised transfer of records and authority. Echeberría moved from Board chair and interim executive to CEO in November. The paperwork and borrowed labor made the new registry work before the new title could do much on its own.

The guest list was a governance document of sorts

The founders of LACNIC had reason to celebrate on 31 October 2002. ICANN had recognized a regional Internet registry for Latin America and the Caribbean. Raúl Echeberría later told the story of what happened in the hotel bar in Shanghai. They invited 30 people. More than 100 came. When the bill arrived, the hosts quietly worked out how much cash they had between them and how many credit cards could help. His tenth-anniversary speech gives the episode a comic finish and a serious beginning: the new institution had won a place in global coordination before it had the money, staff or room of an established registry.

There is a temptation to turn every founding story into a fable about heroic improvisation. Echeberría supplied a better detail. He described the founders sometimes presenting an image of greater capacity than they actually had. In the same speech, he named the organizations and people that made the project possible. That combination is more useful than an origin myth. LACNIC had convinced others it could take responsibility for a region’s number resources. It still had to hire, build systems, pay bills, migrate records and answer requests from network operators. Recognition was a public verdict on a plan.

The plan had to survive Monday morning.

Echeberría was already deep in that work. He had chaired LACNIC’s Board while the institution was being assembled. The Board made him the interim executive in April 2002 and formally appointed him Executive Director and CEO from 15 November, according to its first annual report. The famous Shanghai evening fell between those dates. He was the public face of a newly recognized registry, and the year’s records show how much of its operating capacity had to come from elsewhere. A bar tab tells us nothing about the organization’s accounts. It does tell us why its first accounts deserve to be read.

Four people, 13 square metres

LACNIC’s 2002 annual report describes its work as largely virtual until May. Engineering and registration tasks were already being carried out with NIC Brasil in São Paulo. Meetings in Montevideo sometimes used space at Uruguay’s academic network. In May, LACNIC sublet a small part of a technology company’s office in Montevideo: roughly 13 square metres, shared facilities, its own telephone line and a decent Internet connection. At times, four people worked in that space. Those are the room dimensions behind a regional institution’s name.

The figure is funny until it becomes a floor plan. Four adults, desks, documents and telephones in 13 square metres leave little room for an impressive launch photograph. The annual report says the original plan was to stay there until March or April 2003. Savings during 2002 let the Board approve a move ahead of schedule. On 19 December, LACNIC opened a leased office of about 140 square metres with four work areas and a meeting room. Its space grew more than tenfold in seven months. The job had expanded with it: the address registry was handling operations, members, accounts and policy meetings across a large region.

The sequence is worth pausing over. The first office arrived in May, registration service began under ARIN supervision in July, ICANN recognition came at the end of October, and the larger office opened in December. At every stage, the institution's public promise was bigger than its physical address. Echeberría's task was to keep those clocks aligned: the desk where a member asked for service, the engineers adapting the registry database, the Board approving expenditure, and the partners lending capacity. The office move followed seven months of work that had already made LACNIC useful.

The extra space gave those functions a place to meet; it was the result of an operating year, not the beginning of one.

The tiny room matters because it makes a plain business point. Institutions carry their obligations at full size even when their budgets and premises are still small. A request for address space has to be processed according to the applicable rules whether the staff sit in 13 square metres or 140. A member whose record is moving between registries needs the correct record, not a photograph of the opening ceremony. The new office was useful. The prior months proved that the work could start before the furniture caught up.

The first budget had neighbors

LACNIC’s Board approved a 2002 spending budget of US$150,411.75 on 7 April. The annual report records that ARIN transferred US$146,985.31 during the year under an agreement sharing income from the emerging LACNIC region. Total annual income reached US$225,201.31. These figures describe cash flows and approved spending. The report places another set of numbers beside them: estimates of operating help supplied by partners. NIC Brasil’s contribution was valued at about US$175,000; NIC México’s at about US$70,000.

The in-kind estimates cover people, equipment, hosting, software, travel, training and policy work. A reader who adds those estimates to the cash budget and announces a new revenue figure has changed the accounting story. The striking fact is simpler. LACNIC’s first year depended on capacity that had a price even when LACNIC did not write the cheque. NIC Brasil was running key technical work and lending facilities. NIC México paid for much of the LACNIC III meeting in November and helped design training and policy processes. The registry’s budget was a plan for its own expenditure; the operating system around it was wider than that line.

The annual report names the providers, describes the arrangements and says executive management and the Board retained control of the outsourced functions. That statement had work to do. Members would meet LACNIC at its own door, yet parts of the service ran through another organization’s engineers, servers and rooms. A credible regional registry had to know which work it directed, which partner performed it and which record showed the transfer. Its early strength lay in making those assignments visible.

For Echeberría, that meant management in the literal sense of the word. Until the first budget employee arrived, administrative tasks had been handled jointly by the Board, especially by its chair. Accountant Irene Suffia joined in April to take charge of finance. Adriana Rivero joined in July for member services and temporary secretariat duties. Technical employee Pablo Allietti arrived in November. The year-end staff list contains six named people, two of them based in the São Paulo facilities that NIC Brasil lent to LACNIC.

An organizational chart could make the enterprise look finished; the report shows it being hired one function at a time.

ARIN’s supervised handoff

The human and financial story ran alongside a technical transfer. Before LACNIC began independent operations, ARIN had been handling number-resource requests for the region. A joint transition plan dated 25 June 2002 described how applications, current and archived records, reverse-DNS administration, business files and accounting responsibility would move. It was signed by ARIN’s Ray Plzak and LACNIC Board Chair Raúl Echeberría. Its pages are full of dates and handoffs because the address book could not be moved by a ceremonial vote.

At one stage, applicants still used ARIN forms and sent requests to ARIN. LACNIC evaluated them, then ARIN reviewed that evaluation and made the allocation decision. The revised procedure brought applications directly to LACNIC and let its team make the determination, while ARIN supplied a second opinion before LACNIC completed the registration. The plan set that supervised stage to begin in July and the second-opinion requirement to end with the full operational transfer in November. The annual report records 30 July as the date LACNIC began directly handling the registration service under ARIN supervision.

The difference between supervised practice and final authority matters. On 31 October, ICANN recognized LACNIC. On 11 November, ARIN and LACNIC signed documents confirming the transfer. The annual report places the effective transfer of authority on 18 November. These were stages in one build, each changing a specific part of the arrangement. October’s public recognition attracted the crowd in the bar. July’s supervised work and November’s signed records kept the registry’s operations intelligible to the organizations whose addresses were involved.

The transition plan gave the records their own paperwork. Electronic files were to be identified by name and date, with checksum material. Paper records were to be numbered and copied; ARIN kept originals while LACNIC received copies. Letters recorded the movement of official registration and accounting records. Reverse-DNS administration required identification of the relevant zones and serial numbers. That is less photogenic than a Shanghai announcement and vastly more helpful when someone later asks which registry held a particular record on a particular day.

The borrowed engine had named engineers

NIC Brasil’s part went beyond a friendly promise to lend a server. LACNIC’s annual report says its engineering department effectively served as LACNIC’s engineering team from the beginning. Frederico Neves led that group and acted as LACNIC’s chief technical officer. NIC Brasil supplied equipment, hosted applications, adapted the registration system it already used and provided staff for registration services and the website. The report valued the 2002 contribution at about US$175,000.

This is where the founding story gets practical. A regional registry requires more than a policy declaration. It needs a database that can receive old records and new requests, a service that can answer operators, reverse-DNS arrangements, membership and billing information, and a public website that tells users what to do. NIC Brasil provided a running technical base. LACNIC adapted it, rather than waiting for a pristine system to be written while its members waited for service. That decision gave the emerging institution an operating engine; the Board and executive management still carried responsibility for the destination and the rules.

The report says the engineering team and ARIN had to resolve differences between database structures. Decisions about data format or quality brought in finance and membership staff as well as engineers and registration management. That is the real shape of a migration. A field in a database can become an invoice, a member entitlement or a Whois answer. Treating it as a purely technical column would leave the next department to discover the error. Echeberría’s name appears in the plan because an executive had to connect the parts while the specialists made them work.

The reported operational outcome was concrete. LACNIC said its engineering preparations were ready for the 30 July start and that the new work proceeded without major user disruption. The registration service itself was thin: Ricardo Patara was its sole dedicated worker for most of 2002, with help on particular tasks. The report lists 79 approved IPv4 applications amounting to the equivalent of 2,581 /24 blocks, two IPv6 /32 blocks and 86 ASNs. Each number is a service result, tied to the year in which the staff and systems were still being assembled.

NIC México paid for the public room

NIC México’s contribution was different and equally revealing. The annual report describes help with training programs, travel and policy development, and says it paid for practically all of LACNIC III, the November meeting in Mexico City. The report estimated that support at about US$70,000 for the year. The first set of LACNIC’s own policies was approved at that meeting after work by four groups. Roughly 100 people attended. The number echoes the Shanghai bar story, but the tasks were different: one gathering celebrated recognition; the other helped make the new registry governable.

Policy and membership services were part of the operating model. Adriana Rivero worked on member information and organized the first public election of regional representatives to the ASO Address Council. The website moved from telling the story of LACNIC’s creation to serving organizations that needed forms, procedures and status information. The annual report says updates went online in Spanish, English and Portuguese at nearly the same time. In a region spanning many countries and network operators, three-language service was a daily operating task, not a flourish for the conference stage.

The 2002 report also records a decision about members whose resources had been assigned under ARIN. As LACNIC received the related records, it recognized their membership rights alongside those of organizations receiving new resources. That sounds like a back-office line until one imagines being an operator on the other side of the transfer. The address record, the service path and the membership relationship had to arrive together. LACNIC’s public claim to operate for the region acquired substance when those organizations could find their entries and exercise the rights attached to them.

The title changed after the work started

Echeberría’s own offices shifted during the year. He had chaired the Board while the six founding organizations built LACNIC. In April 2002, the Board assigned him interim executive duties. He signed the June transition letter as Board Chair. The Board then asked him to take the Executive Director and CEO roles permanently from 15 November. Oscar Messano became Board Chair, and Hartmut Glaser took Messano’s former treasurer role. The annual report records the changes as part of the same operating year.

Those dates make a compact portrait of a founder becoming an executive. Echeberría did not arrive after the registry was finished. He was there while its data, staff, budget and delegated work were being assembled. His responsibilities crossed meetings in Las Vegas, Bucharest and Shanghai, the July service start, and the November signatures. By the time he formally became CEO, much of the job was already being done. The title caught up with the workload.

His later anniversary speech remembered the moment with warmth, including the successful party that almost outran its hosts’ wallets. The annual report supplies the less festive parallel: a first budget, a borrowed technical workforce, a small room and a transfer schedule. Together, they make the recognition ceremony more interesting. A new regional registry was built by people who could explain precisely which files, functions and funds would move, even as they were still measuring their office in square metres.

A registry cannot open for business on a single date

The founding year offers a useful cure for the phrase “LACNIC launched in 2002.” On 13 June, ARIN and LACNIC staff met in Montevideo to settle the final service steps. The annual report says LACNIC began handling the registration service directly on 30 July, with ARIN still supervising. The engineers had made the systems ready; the organization had to put forms, policies and explanations online in three languages at once. By late October, the people answering requests were already carrying a live workload. Shanghai put a public date on a transition that was already serving operators.

The 25 June plan reads like the checklist behind that sentence. It scheduled a database snapshot from ARIN, entry of records into LACNIC’s database, changes to the handling of new applications and a move of reverse-DNS service in stages. It gave current registration records one timetable and archived records another. Accounting files had their own dates. The point was to leave a trail that a later operator could follow. When an address holder asks why a record appears in one system and a payment in another, a named file and a dated acknowledgement are considerably more useful than the word “transition.”

The plan also separated technical operation from administrative authority for reverse DNS. Servers could be configured and tested before the final transfer letters took effect. The letters were to name the zones and their serial numbers; the CEOs of the two registries would sign their respective transfer and receipt portions. This is the sort of detail that earns no applause in a hotel bar. It is exactly the detail an operator needs if a technical question arises while ownership of a task is changing. The public milestone was a date; the operational milestone was an answerable question.

ARIN and LACNIC signed the final documents on 11 November in Mexico City, and the annual report places the effective authority change on 18 November. Echeberría’s permanent CEO appointment took effect on 15 November, between those two steps. It is a delightful piece of institutional timing: the chair who had signed the June plan as chair became chief executive just as the last signatures moved the registry’s duties into their new home. The calendars of people, files and authority crossed, then continued on different paths.

The address book came with members attached

LACNIC was assuming responsibility for organizations that had already received resources through ARIN, as well as for future applicants. The annual report says the new registry recognized the membership rights of those organizations when the related records moved. That decision joins the technical and the institutional sides of the transfer. An operator could see its resources in a new database and deal with a new office; it also had a standing relationship with that office. A registry that migrates addresses and forgets members would have built an impressive filing cabinet with a locked customer entrance.

Member services demanded their own worker and procedures. Adriana Rivero joined in July, took charge of the information about member organizations and their representatives, worked on website content and helped run LACNIC III. The same area conducted the first public election of regional representatives to the ASO Address Council. These jobs sound scattered when listed as staff duties. They were one problem seen from different desks: who belongs to the institution, how that person or organization receives information, and how it takes part in a process the institution organizes.

The report’s three-language website rule also belongs here. LACNIC served Latin America and the Caribbean, where the same form had to reach applicants across several languages. Staff made new information available in Spanish, English and Portuguese at nearly the same time. A form has to be current when an applicant uses it; a membership notice has to be intelligible before a deadline passes. Translation was a daily part of the registry’s customer service, sustained by a webmaster in São Paulo and a small team whose other duties filled the office in Montevideo.

The registration volume gives that service a measurable outline. Ricardo Patara’s area approved 79 IPv4 applications, representing the equivalent of 2,581 /24 blocks, plus two IPv6 /32 blocks and 86 ASNs in 2002. The annual report records those approvals for the year. The figures show that the young institution was doing registry work while the transition was under way. Echeberría’s staff list and the output list belong on the same page. One tells us who did the work; the other tells us what the work produced.

The bill behind the little office

The 13-square-metre office was an economical choice with a clear sequel. LACNIC planned to remain there into spring 2003, but the year’s savings allowed it to open the 140-square-metre leased premises in December 2002. The annual report states both the plan and the early move. It also says the Board approved the necessary expenditure. An office expansion became possible because the Board watched costs during a year of uncertain transition. That is a more concrete story about institutional growth than a photograph of a ribbon being cut.

The annual accounts offer another small surprise. Spending came in at 100.07% of the approved budget, while total income was above the original estimate. The report says a professional auditor reviewed the year-end accounts without observations and that LACNIC’s own control body gave a favorable assessment. Echeberría’s personal bar bill was settled privately by the celebrants, according to his later account; the registry’s spending and income were reported through its institutional books. His anecdote works because the contrast is real and the categories stay in their lanes.

It is easy to romanticize austerity when the support bill sits on someone else’s desk. The report makes that harder by valuing NIC Brasil’s 2002 help at about US$175,000 and NIC México’s at about US$70,000. The former included equipment and engineering labor; the latter included training, policy work and much of a major meeting’s cost. The reported LACNIC spending budget was about US$150,000. These are different types of figures, but they put a scale on the cooperative work that held the registry up. The founders had a tiny office because their allies supplied other offices, systems, people and expertise.

Echeberría’s later telling of the Shanghai party lands differently beside these numbers. More than 100 guests were a social success, with a bill that the hosts had to improvise. A registry working for a region with many countries needed the opposite financial habit: state the budget, name the contributions, record the transfers, audit the accounts and keep the service running. LACNIC’s first annual report did precisely that. The joke survived because the institution learned to turn scarce resources into a working schedule rather than a permanent excuse.