Summary

  • Buenos Aires Province’s 1992 satellite message network was formally province-wide, but its builders later reported links to only 35 of 124 municipalities.
  • A project team moved from mainframe terminals and SDLC to IP over X.25, using Linux mail relays and proxies; the team reported 35 municipalities on TCP/IP in 1994 and 102 in 1995.

A single service on paper, 35 municipalities in the account

The decree described a unified provincial service for sending and receiving government messages. The network remembered by its builders was smaller. In a 2020 history, Sandra D’Agostino and Rodolfo Cozzi say that the leased satellite links then in use covered 35 of the province’s 124 municipalities, plus two tax offices and the Casa de la Provincia. The network linked IBM terminals to a government mainframe; it was a message service, not a public Internet connection.

That gap between administrative scope and installed reach is the story’s starting point. A rule could designate one route for the provincial administration without making the route available at every municipal office. The same retrospective quotes the decree’s network as the sole, non-redundant means for authorized terminals to communicate. It does not supply a failure log or an independent inventory of working sites, so “non-redundant” describes the stated design, not a documented outage.

IP arrived through a change in layers

The province’s information office had been established in 1991, according to the paper. A 1993 decree then supported centralized coordination of software, hardware and wider IT planning. The authors say a team that included people from the National University of La Plata used that opening to plan what they called a provincial Internet.

The proposed network did not begin by replacing every satellite circuit. The team reports moving the carrier links from SDLC to X.25, then carrying IP over X.25 through Cisco 2501 routers. Their account places Linux servers at access points, where sendmail relayed mail and a proxy reduced repeated external requests over satellite links of 9,600 or 19,200 bits per second. The physical path remained a leased satellite service; the data and application layers changed around it.

Addressing followed the same split between a common plan and local systems. The project registered gba.gov.ar, requested a class-B network on 30 May 1994, and says it received 170.155 four days later. The paper reproduces images labelled as the request and allocation. It also says the team used private 10/8 space for separate provincial areas in June 1994, a month after RFC 1597 described private address blocks. That RFC establishes the address-space context; it does not verify this installation.

What 35 and 102 count

The builders’ chronology reports 35 municipalities on the TCP/IP architecture in 1994 and 102 the following year. Those figures should not be merged with the earlier 35/124 satellite count: one describes the old terminal service, the other a stage in the new architecture. They are not counts of residents, households, active users, traffic or equal service quality.

The paper also describes a 1995 link for one rural school in Bolívar, routed through the municipality using an 800 MHz spread-spectrum connection that the authors put at 2 Mbit/s. It is a revealing example of a local endpoint joining a provincial network, not proof that rural schools across the province had comparable access. Likewise, a later legal record says the province established one data network for its public administration in 2003 and repealed the 1992 decree; that later decision does not independently confirm how many sites were operational in 1994 or 1995.

The central achievement was therefore narrower than a province “coming online” in one moment. A government team adapted an existing low-bandwidth satellite service so IP could be deployed in stages, with a mail relay and proxy at the edge. The evidence is a participant retrospective, not independent telemetry. It supports a specific migration path and two reported rollout counts. It leaves unresolved which municipal offices had live service on any given day, what failed, and whether the paths had operational backups.

The account is D’Agostino and Cozzi’s history of the provincial communications network. The official 2003 provincial decree is later legal context. RFC 1597 and RFC 877 describe address space and IP-over-X.25 context; neither documents the provincial rollout.

Sources

The participant team’s retrospective is available as the repository record and full paper; deployment figures and technical details above are attributed to its authors. The paper cites Buenos Aires Decree 21/91, Decree 2272/92, and Decree 4015/93. These links preserve its legal references. The 2272/92 page timed out during this research, so its contents are attributed to the retrospective rather than presented as independently verified. The later Decree 1204/2003, RFC 1597, and RFC 877 provide legal and protocol context, not independent evidence of the rollout.