Summary
- RIPE planned a staffed centre because its volunteer forum could not reliably carry routine regional recordkeeping, maps, DNS checks and network contacts.
- The 1991 proposal sought 720,000 ECU for three years; the RIPE NCC began work on 1 April 1992 and acted as a delegated number registry from 1 May.
Analysis
The first regional Internet registry was a staffing problem before it was an address desk. RIPE’s September 1990 proposal said its community worked well on development, but routine administration needed dedicated staff. The proposed Network Coordination Centre would keep that work going between meetings. It would support network operators; it would not run their networks or provide end-user support.
The job description was bigger than maintaining a list of addresses. RIPE’s 1991 activity plan included a database of European networks and responsible contacts, checks for consistency, exchanges with coordination centres outside Europe, maps of connectivity, NOC contact details, DNS software and nameserver checks, traffic statistics, documents and meeting support. The plan said regular work of this kind had proved difficult to sustain through voluntary effort. “Coordination” meant people, reporting cycles and a place to keep records.
The setup paper then put a price on that routine. Its estimate was 240,000 ECU a year and it asked for three years of funding: 720,000 ECU. Staff accounted for 180,000 ECU in the annual plan; equipment, office space and travel filled out the rest. The paper treated the total as a target to secure, not a receipt. RARE had accepted the job of providing a legal environment for the centre, but said it had no resources to finance it centrally. RIPE invited organisations inside and outside its community to contribute.
The legal shell, the money and the work therefore sat in different hands. The RIPE community defined the NCC’s tasks and was meant to review its operation. RARE offered the legal framework. The centre would employ people and maintain the information. Local NICs and NOCs would handle assignments closer to the networks. That was a governance design with a practical bill attached.
Address allocation was part of the proposal, but it did not begin as the only job. RIPE NCC’s later activity plan says the centre had been working since 1 April 1992. The number-registration procedure says that from 1 May it acted as a delegated registry for European network numbers. It sent blocks to service providers and NICs/NOCs; individual organisations were directed to their network service provider. The centre could maintain the record without becoming the operator of every network in Europe.
That boundary mattered. The NCC’s database was supposed to make regional information consistent and usable; local operators still made their networks run. The plan’s maps, contact records and DNS checks supported operations without taking operational control. In January 1998, the RIPE NCC became a legal entity in its own right. The recurring coordination job had outlasted its first legal arrangement.
The surviving setup papers establish a funding target, not who ultimately paid every ECU. A final contribution schedule or audited account for the first three years would show whether the full 720,000-ECU target was raised and how actual spending compared with the estimate.
Sources
- RIPE-019 — RIPE Network Coordination Centre
- RIPE-035 — RIPE NCC Activity Plan
- RIPE-039 — Procedures To Set Up the RIPE NCC
- RIPE-065 — RIPE NCC Internet Numbers Registration Procedures
- RIPE-110 — RIPE NCC Activity Plan, Version 4
- RIPE-207 — RIPE NCC Annual Report 1999, Foreword
- RIPE NCC — The History of RIPE
Member Briefing
Deeper Profile Context
Sign in with the right membership level to unlock the full briefing and source notes.
Only for Strategic Circle
Strategic Circle
Open to all readers. Unlock profile briefings after joining and signing in.
Join Strategic CircleOnly for Leadership Alliance
Leadership Alliance
For qualified IP-asset owners and management; sign in to unlock alliance briefings.
Join Leadership Alliance





