RIPE NCC board elections look modest if they are viewed as association housekeeping. Members register for a General Meeting, candidates gather nominations, ballots are cast, resolutions are counted, and several seats on the Executive Board are filled for another term. That is the ordinary furniture of a Dutch not-for-profit membership association. It is also an inadequate description of what the vote now means.
In the post-exhaustion IPv4 economy, the board of a Regional Internet Registry sits above a scarce operational ledger. It does not own the Internet. It does not route packets. It does not set bilateral market prices for IPv4 blocks. But it governs the institution whose records, contracts, fees, transfer processes, RPKI services, reverse-DNS delegations, sanctions controls, legal posture and implementation culture influence how scarce number resources are recognised and moved. That makes election legitimacy a form of market infrastructure.
Legitimacy here does not mean ceremonial approval. It means that members and market participants can treat later registry actions as the output of a constrained, accountable institution rather than the preference of a self-protecting gatekeeper. If an election is credible, the board can make difficult budget, fee, compliance and strategic choices at a lower trust cost. If the election is thin, opaque or captured by insiders, every later decision carries a governance discount. A transfer delay looks less like process and more like discretion. A fee rise looks less like cost recovery and more like extraction. A policy implementation choice looks less like stewardship and more like control.
RIPE NCC is the mature test case because it is not a crisis registry. It is a long-established, technically competent and well-documented membership association based in the Netherlands, serving Europe, the Middle East and parts of Central Asia. Its public materials describe a Regional Internet Registry that distributes and registers IPv4, IPv6 and AS Number resources, maintains the RIPE Database, supports transfers, operates RPKI and reverse DNS, runs information services such as RIPE Atlas, RIPEstat and RIS, and supports meetings, training, community work and public engagement. That breadth is precisely why board elections matter.
Official RIPE NCC materials are useful factual exhibits. The Executive Board page says members elect the board, which consists of seven people; the board represents the membership, guides senior management, oversees the financial position, approves the Activity Plan and Budget, appoints management and calls General Meetings. The General Meetings page says members discuss operations, vote on resolutions and elect board members, with the spring meeting normally used for Executive Board elections and charging-scheme decisions. The Articles of Association, voting pages, budget documents and charging schemes provide the institutional map.
They do not provide the economic conclusion. Institutions naturally describe their own governance through accountability, transparency, service and community. The harder question is whether the member election actually disciplines the power RIPE NCC has acquired because IPv4 is scarce. Market-side critics of registry power ask that question in harsher language: records, votes, fees, transfer recognition and registry-layer exposure have become economically consequential because number resources are no longer merely administrative entries. These arguments are not neutral. Their value is that they focus attention on the gap between corporate form and capital-like effect.
The board election is where that gap is either narrowed or widened. It is the formal moment when members can convert concern into institutional direction.
A board above a scarce ledger
The RIPE NCC Executive Board is not a parliament. It is the governing board of a private membership association. That distinction matters. The board cannot plausibly claim the authority of a public legislature, telecom regulator or court. It can claim the authority granted by the Articles of Association, the members, applicable Dutch law, contracts and RIPE NCC's institutional role as an RIR. That authority is narrower than public sovereignty. It is still economically powerful.
The power comes from the ledger. A number-resource registry is valuable because it makes uniqueness and recognised holdership legible. Networks need to know that an IPv4 prefix, IPv6 allocation or AS Number is not duplicated. Buyers and sellers need a recognised change path. Operators need usable contacts. RPKI relies on a registered relationship between resources and certificate authority. Reverse DNS depends on registry-managed delegations. Inter-RIR transfers require coordinated approval. Sanctions screening can become a closing condition. The registry record is not the whole asset, but it is part of the confidence structure around the asset.
Before IPv4 exhaustion, this ledger was tied to distribution from a pool. RIPE NCC's IPv4 run-out page records the familiar sequence: for much of its history, LIRs could receive IPv4 addresses as needed if they supplied documentation; after the final /8 was reached in 2012, policy limited each LIR to one /22; in November 2019, the remaining IPv4 pool was exhausted; the current waiting-list model permits eligible LIRs that have not received an IPv4 allocation to request one /24 from future recovered space. The facts are technical. The consequence is economic.
Once exhaustion arrived, RIPE NCC's central position shifted. It no longer sat mainly in front of a pool of new supply. It sat above the recognised record for resources already embedded in customer networks, hosting platforms, cloud operations, enterprise systems, merger documents, lease contracts, routing-security settings and reputational histories. IPv4 blocks became productive capital because they enable revenue, continuity and optionality. The registry did not create that value. Scarcity and use did. But the registry can lower or raise the cost of trusting the value.
This is why a board election prices risk. A board that treats RIPE NCC as a narrow ledger will ask different questions from a board that treats the institution as a broad steward of market behaviour. A ledger board will want accurate records, clear authority checks, reliable transfers, bounded sanctions compliance, RPKI continuity, reverse-DNS stability and measured fees. A gatekeeper board will be more comfortable with broad institutional discretion, wider service bundling, thicker compliance posture and public language that turns community process into expansive authority.
Every real board will sit between those poles. RIPE NCC must prevent fraud. It must obey applicable law. It must keep systems secure. It must maintain records. It must finance staff and infrastructure. It must support the RIPE community. The question is proportionality. How much power is necessary to protect the ledger, and how much is institutional convenience?
Election legitimacy matters because the board is where this proportionality is supposed to be disciplined.
Corporate accountability is not community consensus
RIPE has two legitimacy layers that are often treated as if they automatically reinforce each other. One is the open RIPE community, where policies are discussed through working groups, mailing lists and meetings. The other is RIPE NCC corporate accountability, where members vote at General Meetings, elect the Executive Board, approve financial reports, vote on charging schemes and discharge the board. Both matter. They are not the same.
RIPE policy development is open beyond the membership. A person does not need to be a RIPE NCC member to propose or discuss policy. That openness is a strength. It allows operators, researchers, critics, customers, consultants and non-members to shape rules that affect number resources. It also means policy consensus is not identical to member consent. The active policy community may include people who do not pay the fees, do not hold resources, do not depend on RIPE NCC services and do not carry the same operational risk as members.
Member governance has the opposite limit. RIPE NCC members elect the board and vote on association resolutions. But members are not the whole affected economy. A member may be the recognised holder while customers, lessees, subsidiaries, downstream networks, lenders, public-sector users or hosted clients depend on the resources. A buyer in a corporate transaction may price registry risk without having a vote. A firm using leased address space may depend on RPKI and reverse DNS managed by a holder, without being visible as a member voice. A consumer, hospital, school, enterprise or public agency may rely on services supported by RIPE-region resources without knowing RIPE NCC exists.
This is not a criticism of the RIPE model by itself. No registry association can give every downstream user a ballot. The point is narrower: neither the community nor the membership should be used as a magic word. Community consensus can help legitimate policy text. Member voting can help legitimate the corporate layer. Neither automatically authorises all economic consequences imposed by registry discretion.
The distinction matters most after scarcity. A policy mailing list may produce a rule affecting transfers, temporary use, RPKI or reverse DNS. RIPE NCC staff may implement it. The board may allocate the budget and risk appetite behind implementation. Members may fund the institution. The market may bear the cost. If something goes wrong, responsibility can become diffuse. The community made the policy. The association implemented it. The board approved the budget. Staff followed process. The affected party was absent or silent.
A mature election culture should make these boundaries explicit. Board candidates should be asked how they understand the relationship between RIPE community policy and RIPE NCC corporate accountability. They should explain whether they see the board as a passive implementer of community output, a guardian of member money, a risk manager for a Dutch association, a steward of the RIR system, or a narrow supervisor of registry reliability. The answer matters because each theory produces different conduct under stress.
If the board treats community process as sufficient legitimacy, it may underestimate member cost. If it treats member voting as sufficient legitimacy, it may underestimate non-member dependency. If it treats legal compliance as sufficient legitimacy, it may underestimate market friction. If it treats technical stability as sufficient legitimacy, it may underestimate capital-allocation effects. A legitimate board must hold all four in view without collapsing them into one comforting word.
RIPE NCC's election system can support that kind of accountability. It can also dilute it if elections become a low-salience ritual in which candidates are judged mainly by reputational familiarity rather than by their theory of registry power.
What the board actually controls
The board's economic significance is visible in RIPE NCC's own governance documents. The Executive Board page lists duties that go beyond ceremonial oversight: representing membership, guiding senior management, supervising the financial position, approving the Activity Plan and Budget, appointing management and calling General Meetings. The Articles of Association add more detail. The board consists of at least three and at most seven natural persons, acting in a personal capacity and not required to be members. It appoints the Management Team. The Management Team receives operational decisions concerning Standard Service Agreements, including authority to suspend a member that does not fulfil obligations. The articles provide for arbitration around Management Team decisions regarding those agreements.
These powers sit close to the registry relationship. Standard Service Agreements define the contractual environment for members. Suspension can affect access to services. The Management Team handles operational decisions, but the board appoints that team, determines remuneration and can lay down regulations about duties. The board approves budgets that determine how much capacity exists for registry services, legal work, data quality, member support, RPKI, information security, engagement and process improvement. The board calls the meetings where members vote on resolutions and elections.
This is not day-to-day packet routing. It is the institutional architecture that determines how the registry behaves when something important happens.
Consider transfers. RIPE NCC's transfer pages say transfers are free of direct charge, but parties must satisfy policy, documentation, authority and, where relevant, sanctions screening. Scarce resources face a 24-month restriction after receipt or certain updates. Inter-RIR transfers require coordination with another registry and compatibility with both policy regimes. The board does not personally approve every transfer. But it controls the organisation's tolerance for transparency, performance measurement, staffing, legal conservatism and investment in smoother process. If the board demands aggregate reporting on transfer delays and abandoned requests, market confidence improves. If it does not, transfer friction remains partly anecdotal.
Consider fees. The Charging Scheme 2026 sets a EUR 1,800 annual contribution per LIR account, separate charges for independent assignments and ASNs, and a sign-up fee. Members vote on charging schemes, but the board and management shape the proposals, cost base and explanation of scope. A fee is not merely a membership subscription when the membership relationship is tied to registry recognition and services. It is a price on continued access to the official ledger.
Consider data quality and review. The Activity Plan and Budget 2026 says RIPE NCC planned to check registration data for around 20,000 End Users with independent resources and conduct 2,400 Assisted Registry Checks. That may be valuable ledger maintenance. It is also a large contact point between the institution and members or End Users. The board's budget and risk posture determine whether such programmes feel cooperative and evidence-based, or broad and intimidating.
Consider RPKI. The Activity Plan and Budget includes work on RPKI infrastructure, security, audit and related standards. RPKI is no longer a peripheral service. It is part of routing-security practice. A board that understands RPKI as operational control will demand careful notice, recovery paths, continuity planning and clear limits on certificate-related leverage.
Board power is therefore indirect but real. It is not the power to write every policy clause. It is the power to set the institutional conditions under which policy, contracts, fees and services are applied. That is why elections matter.
Election mechanics are necessary, not sufficient
RIPE NCC's election mechanics are more open than many nonprofit systems. The Articles of Association say board members act in a personal capacity and need not be members. A nomination requires written support from at least five RIPE NCC members. The 2026 candidate page states that candidates do not need to be RIPE NCC members, but must gather five nominations from members who are registered LIR contacts in the LIR Portal. It also lists useful experience such as senior management, financial management, compliance and risk, strategic management, Internet governance knowledge, legal understanding, technical expertise and communication ability.
There are conflict and eligibility constraints. The legal-requirements page explains restrictions involving employment, shared ownership, controlling interests and affiliations with current board members, as well as exclusions connected to boards of other RIRs, ICANN, ISOC and the ASO AC under the Articles. Nominees must submit identity materials and statements. There is a candidate Code of Conduct. These controls are designed to protect the board from conflicts, fraud and personal misconduct. They are useful.
The voting process is also structured. The May 2026 General Meeting took place in person and online from 20-22 May 2026 in Edinburgh. The election filled three seats for terms ending in May 2029. The voting report says 3,421 members registered to vote and 3,049 cast ballots. The election used instant run-off voting. The voting report also records two-factor access using two voting codes, a voting period from 20 May to 22 May, reminders to voters who had not voted, a one-hour registration extension due to LIR Portal login issues, 27 assistance requests and an independent observer from ARIN. These are the details of a serious voting operation.
Mechanics, however, are not the same as political economy. A clean voting platform can produce a weak mandate if the electorate is small relative to the affected base, if candidates do not discuss the real economic issues, if small operators cannot evaluate the stakes, if nominations favour familiar insiders, or if the board role is framed as institutional service rather than control over scarce registry infrastructure.
The participation figures show both strength and limit. More than 3,000 ballots is not trivial. It reflects real member engagement. But the Activity Plan and Budget 2026 says RIPE NCC budgeted on the basis of 20,000 contributing LIRs aligned with the number of members. If roughly 3,000 members cast ballots in a consequential GM, the election is representative enough to be valid under the rules, but not broad enough to be treated as full member attention. The silent majority may be content. It may also be busy, underinformed, fee-fatigued, language-constrained, or unaware that board choices now affect capital-like infrastructure.
This is the central election-economics problem: the cost of voting is not only clicking a ballot. It is the cost of knowing why the ballot matters. A member must track candidate statements, understand the difference between RIPE community policy and RIPE NCC corporate governance, read charging-scheme options, understand budget categories, evaluate RPKI and registry-risk priorities, interpret board discharge and financial reports, and decide whether a candidate's background matches the scarcity-era problem. A small operator may have little time for that work.
Election mechanics reduce fraud and procedural error. They do not automatically produce informed control over gatekeeping power. That requires a stronger campaign culture.
Voting trust is registry trust
Voting systems in an ordinary association can be treated as internal administration. In a registry association, they are part of the same trust architecture as the registry. The reason is simple: both systems ask members to believe that an institutional record reflects the right actor's authority. In a transfer, RIPE NCC must know who is allowed to move or receive a resource. In a General Meeting, it must know who is allowed to cast a vote. In a candidate nomination, it must know whether five member supports are real. In a proxy, it must know whether one person is entitled to act for another. These are different processes, but the credibility problem is shared.
This has an important implication. The quality of the election is not only a matter of fairness to candidates. It is evidence of institutional competence in authority management. If members see a clear, secure and well-observed voting process, they have more reason to believe the association can manage other high-consequence authority questions. If voting access is confusing, if candidate materials are thin, if eligibility and proxy rules are hard to understand, or if technical issues are poorly explained, members may generalise that uncertainty to the wider registry relationship.
The May 2026 voting report is useful because it gives operational detail: registration numbers, ballots cast, voting method, timing, reminders, assistance requests, a technical login issue and independent observation. That is the right instinct. A registry should publish the audit trail of its own authority processes. The same instinct should extend to economic processes: transfer timing, documentation cycles, sanctions-related delays where disclosure is lawful, RPKI incidents, reverse-DNS support, ARC outcomes and member-service response.
Voting trust also depends on intelligibility. A member can trust the cryptographic or procedural integrity of a ballot and still lack a clear view of what the vote is choosing. The ballot must be secure, but the agenda must also be economically meaningful. Members should know not only who the candidates are, but what theories of the institution they represent. A candidate who promises stability may mean stable fees, stable institutional scope, stable staff culture, stable community process or stable registry service. These are not the same. A candidate who promises change may mean cost discipline, more reporting, lower discretion, more member support, sharper sanctions process or a broader strategic role. These too are not the same.
The election system therefore needs to make the choice visible. Voting mechanics protect the ballot. Candidate specificity protects the mandate.
Candidate access and the acceptable boundaries of dissent
The five-nomination threshold is low enough to avoid a closed slate. Anyone who can secure written support from five members can become a candidate if they meet the legal and conduct requirements. Candidates do not have to be members. In a region with thousands of members, this is a modest threshold. It is a meaningful openness feature.
But candidate access is not only a threshold question. It is also a question of acceptable dissent. A candidate who challenges RIPE NCC's institutional scope, fee structure, transfer transparency or gatekeeping posture must do so in a culture that prizes stability. That culture has reasons. A registry must avoid reckless governance. Board members need financial literacy, legal caution, technical understanding and trustworthiness. A candidate promising disruption without understanding Dutch association law, registry services, RPKI, sanctions or member contracts would be a real risk.
The problem is that stability can become a filter against legitimate reform. A candidate who says that RIPE NCC should remain trusted, stable and community-driven will sound safe. A candidate who says that RIPE NCC's compulsory fee bundle should be narrowed around ledger functions, transfer friction should be measured, and policy-based gatekeeping should be treated as capital control may sound adversarial even if the analysis is institutionally conservative. In a scarcity economy, the second candidate may be more relevant to long-term legitimacy.
The election system therefore needs room for informed dissent. Legal requirements should screen conflicts and misconduct, not economic viewpoint. Candidate materials should allow serious discussion of fees, reserves, transfer friction, sanctions risk, RPKI governance, small-operator burden, RIPE NCC Middle East, external engagement and the boundary between community support and core registry work. The Code of Conduct should prevent abuse, not turn sharp institutional critique into a procedural liability.
The 2026 election pages include candidate videos, biographies, an online session and supporting materials. Those are useful. The next step is economic specificity. A board candidate statement should not be a biography plus a declaration of support for the Internet. It should answer what the candidate believes RIPE NCC is for in a post-exhaustion market. Is the association primarily a ledger operator funded by members? A broader Internet-development institution? A community secretariat with registry duties? A European-rooted compliance body serving a multi-region membership? A routing-security infrastructure provider? The answer determines budget and risk posture.
Candidate access is legitimate when members can choose among real theories of the institution, not merely among resumes.
Fees, reserves and institutional scope
Fees are where board elections become immediate economics. RIPE NCC's charging scheme is voted on by members, but the board and management shape the financial frame. They decide which activity plan is proposed, how budgets are presented, how services are bundled, how reserves are explained, how inflation and staffing are handled, and how costs are divided between core registry work and wider activity.
The Charging Scheme 2026 is based on an annual contribution per LIR account, with separate charges for independent and legacy Internet resources as defined in the document, plus a sign-up fee for new members or additional LIR registrations. For 2026 the annual LIR contribution remained EUR 1,800, with EUR 75 per independent Internet number resource assignment, EUR 50 per ASN assignment and a EUR 1,000 sign-up fee. The scheme says members vote every year at the GM to return excess paid fees or address shortages through redistribution.
Those facts are not alarming by themselves. A registry needs money. Skilled staff, secure systems, legal compliance, data quality, member support, RPKI operations, reverse DNS, K-root, audits and resilience all cost money. The economic question is scope. Which costs are unavoidable ledger costs? Which are broader public goods? Which benefit active community participants more than ordinary members? Which support government engagement or regional outreach? Which are optional but desirable? Which should be financed through compulsory fees attached to registry recognition?
The Activity Plan and Budget 2026 sharpens this question. It budgets income of about EUR 41.140 million, costs of about EUR 41.125 million and a small operating surplus, with a budgeted FTE count rising to 202.1. It divides spending across the Registry, Information Services, External Engagement and Community, Organisational Sustainability, and bad debts and depreciation. It presents the budget as a way for members to learn about plans and influence direction, and says member feedback is sought through the Membership Discussion list and the RIPE NCC Services Working Group before the final version is approved by the board.
This is transparent, but transparency is not the same as discipline. A member still has to ask whether the cost base is aligned with the registry's core purpose. The budget includes ledger-like services such as registration, member services, registry monitoring, the RIPE Database, the LIR Portal, RPKI, DNS and K-root. It also includes information services, research, public policy, Internet governance, community building, training and engagement. Many of these are useful. The issue is not usefulness. It is compulsion.
A compulsory association relationship tied to scarce number-resource recognition should be modest unless members actively choose otherwise with clear cost separation. This does not mean every wider activity should be cut. Measurement systems, training and engagement may produce public value. But a member should be able to tell whether a euro paid to preserve registry standing is funding the ledger, member support, security, community infrastructure, public-policy engagement, institutional presence or reserves. If that distinction is blurred, fees become a quiet tax on recognition.
Board elections are the member mechanism for testing that modesty. Candidates should be asked which services they regard as core ledger functions, which as public goods, which as member benefits and which as mission expansion. They should explain how reserves should be sized and justified. They should explain whether fee stability matters more than programme breadth. They should explain how small members in lower-income or politically exposed parts of the region should experience the cost of a euro-denominated flat charge.
Without that debate, fees become financial governance without economic accountability.
Board accountability over policy implementation
The RIPE community develops policy; RIPE NCC implements it. This division is a strength when it keeps policy from being written unilaterally by staff. It is a weakness if the board hides behind the community when implementation creates costs.
The board does not need to second-guess every working-group consensus. It should not turn policy development into board rulemaking. But it is responsible for the institution that implements policy, finances the work, supervises management and handles risk. That gives the board an accountability role even where policy originates outside the corporate layer.
Consider a transfer rule. If community policy creates or preserves a 24-month restriction, RIPE NCC must apply it. But the board can ask whether members and market participants receive clear guidance, aggregate timelines, categories of delay, data on abandoned requests and evidence that the rule is proportionate. It can ask whether the rule pushes legitimate activity into leasing. It can ask whether small operators are disproportionately affected. It can ask staff to distinguish anti-fraud checks from business-model judgement.
Consider delegated RPKI. RIPE NCC's policy implementation material for 2025-02 says accepted policy allows revocation of certificates associated with long-term non-functional delegated CAs after notice, with updated terms published and a 90-day non-functionality period. That may be technical hygiene. It is also operationally consequential. The board should ask whether certificate-state changes are communicated clearly, whether recovery paths are usable, whether smaller operators understand the consequences and whether RPKI service governance is treated as critical infrastructure rather than ordinary account administration.
Consider Assisted Registry Checks. The Activity Plan's target of 2,400 ARCs indicates a large data-quality operation. Accurate registry data is a ledger function. But member experience matters. Are checks cooperative? Are escalation paths clear? Are errors separated from fraud? Are sanctions or banking issues treated narrowly? Does a small ISP know that an ARC is data-quality work rather than a threat to continuity? The board should require that line to remain visible.
This is where ledger versus gatekeeper becomes practical. The board should not ask only whether RIPE NCC can implement policy. It should ask whether implementation keeps the gate narrow. A ledger protects uniqueness, accuracy, authorised changes, RPKI, reverse DNS, transfer recording and dispute isolation. A gatekeeper judges broader commercial legitimacy and creates uncertainty around resources. Policies may require some gatekeeping. The board's job is to keep it evidenced, proportionate and measured.
If a board candidate cannot explain this distinction, they may be qualified in ordinary nonprofit governance but underprepared for scarcity-era registry oversight.
Transfers, leasing and the board's market signal
RIPE NCC does not operate the IPv4 market, but it sends market signals. Every transfer rule, performance metric, sanctions note, legacy-resource update, RPKI service condition and fee decision changes how participants perceive RIPE-region resources. The board is responsible for whether those signals are predictable.
Transfers are the obvious case. RIPE NCC says all resource transfers are free of charge. That is good. But the economic cost of a transfer is not the invoice. It is the total friction: documentation, timing, uncertainty, restrictions, inter-RIR dependence, sanctions screening, legal counsel, broker reliance and the risk of unexpected questions. A board that publishes only successful transfers leaves the market to infer friction from anecdotes. A board that demands aggregate process data lowers the risk premium.
Leasing is the less visible case. Leasing grows when address holders want income and users want capacity without permanent purchase, or when transfer friction makes direct acquisition less attractive. It can be efficient. It can also hide operational risk. A lessee may depend on the holder for ROAs, reverse DNS, abuse response and renewal. The holder remains exposed to registry obligations. The registry may see the holder but not the user. A board that ignores leasing will miss part of the scarcity economy. A board that moralises leasing may push it into opacity. A board that recognises leasing as a normal market response can ask how RIPE NCC should support accurate operational facts without becoming a lease regulator.
Sanctions compliance is another signal. RIPE NCC is a Dutch association subject to applicable Dutch and EU law. It cannot ignore sanctions. But how sanctions checks are explained, timed and bounded affects market confidence. A board should want clear legal boundaries, aggregate transparency where lawful, and procedures that separate unavoidable law from discretionary caution. In a region that includes sensitive jurisdictions, this is not a side issue. It is part of transfer-market architecture.
Legacy resources also matter. Historical resources may have unusual documentation and contractual status. A board that seeks to normalise every legacy relationship into current membership logic may increase resistance. A board that leaves legacy ambiguity unresolved may discount market confidence. The ledger-first path is to reduce factual uncertainty without using modern services as pressure points beyond necessity.
The board's market signal should be boring. Boring does not mean passive. It means predictable, narrow, measurable and service-focused. The market should know what RIPE NCC will check, how long it usually takes, what law may block, what documents matter, how RPKI and reverse DNS are maintained, what happens during disputes and what fees fund. When the official path is boring, workarounds become less attractive. When the official path is opaque, intermediaries sell protection from the registry layer.
An election is therefore a vote on the signal RIPE NCC sends to the scarcity market.
Discharge, liability and the accountability gap
The General Meeting does more than elect board members. It votes on resolutions, adopts financial reports, decides charging schemes and considers discharge of the Executive Board. The discharge mechanism is important because it reveals a deeper accountability gap.
RIPE NCC's discharge explainer says discharging the board typically releases board members from potential liability for actions taken during their term, as described in the Annual Report and Financial Report, toward the association as a whole. It also says discharge does not cover actions outside board duties, matters not clearly stated in the reports, liability toward external parties including individual members, or gross negligence, wilful misconduct or absence of good faith.
This is corporate governance, not market compensation. It helps members assess whether the board damaged the association. It does not solve the problem of registry discretion causing harm to a member, a buyer, a lessee or downstream network. If a policy implementation delays a transfer, if an RPKI decision disrupts routing, if a sanctions process creates uncertainty, if an ARC escalates in a way that affects continuity, the cost may be borne outside the association's own balance sheet. The board may have acted properly from the association's perspective while external parties experience significant loss.
This is the power-liability gap. RIPE NCC can affect economically valuable resources, but its formal accountability mechanisms are mostly association mechanisms. Members can vote, object, ask questions, use arbitration for certain agreement-related disputes, or litigate where legal claims exist. But the everyday market cost of uncertainty is not easily captured. It appears as discounts, broker fees, lease premiums, legal diligence, delayed transactions and operational fear.
Board elections are one way to reduce that gap before harm occurs. A board that understands the gap can require RIPE NCC to publish process metrics, clarify remedies, narrow discretion, distinguish data correction from punishment, and budget for member support. A board that does not understand it may sincerely believe that corporate transparency and community process are enough.
The legitimacy test is not whether RIPE NCC can avoid all liability. No infrastructure institution can. The test is whether it reduces the need for liability claims by making official behaviour predictable and proportionate. A board discharge vote looks backward. Election legitimacy must look forward.
Agenda control in a membership association
Agenda control is the quiet form of election power. Members vote at GMs, but the board and management shape what is placed before them, how early documents are published, how options are framed, what data are supplied, how charging models are described and how candidates are introduced.
The Articles of Association require convocations, agenda subjects, proposed-resolution text and, where relevant, draft activity plan and budget material to be sent to members before the meeting. They allow member groups with at least one-tenth of possible votes to require a General Meeting. They allow members to attend, vote electronically and use proxy arrangements subject to rules, including a one-percent cap on proxies. These are meaningful constraints. They keep the board from being wholly self-sufficient.
Yet agenda power remains real. A charging-scheme vote can be framed as a choice among models selected by RIPE NCC. A budget can be presented in a way that makes broad service scope appear natural. A candidate debate can focus on civility and experience rather than transfer-market risk. A discussion of strategy can emphasise resilience, public engagement and external threats while giving less attention to the cost of the compulsory registry relationship. None of that requires bad faith. It is how organisations defend their own centre of gravity.
Members need countervailing data to make agenda control accountable. How much does each core ledger service cost? How much of the EUR 1,800 fee funds registry operations versus information services, external engagement or organisational overhead? How much transfer friction is created by policy rather than staff capacity? How often are ARCs completed without material issue? How often do sanctions checks delay legitimate transactions? How often do members need help voting or updating authority? How many small operators participate in GMs relative to large incumbents?
The May 2026 voting report includes valuable process details: registration numbers, ballot counts, voting method, timing, technical-access issue, assistance requests and independent observation. This is good governance practice. The same spirit should be extended to economic governance. Publish the equivalent of a voting report for registry friction.
Agenda control is not illegitimate. Hidden agenda control is.
Legitimacy as market infrastructure
Markets do not trust institutions because those institutions call themselves trusted. They trust them when official processes reduce uncertainty at a tolerable cost. For RIPE NCC, legitimacy is therefore not a reputational luxury. It is an input into the price and usability of number resources.
An IPv4 buyer wants to know whether a RIPE-region block can be transferred predictably. A seller wants to know whether documentation will be accepted. A lessor wants to know whether operational delegation can be supported without risking recognised holdership. A lessee wants stable RPKI, reverse DNS and abuse response. A small ISP wants address capacity without hiring counsel for every registry interaction. A legacy holder wants historical status handled without coercion. A member in a sensitive jurisdiction wants legal compliance to be narrow, clear and non-political. A downstream customer wants continuity without learning registry law.
Board legitimacy affects all of this indirectly. A board with a clear mandate can demand performance transparency. It can ask whether budget categories match member needs. It can set expectations for member support. It can insist that public language not outrun legal authority. It can appoint management that understands market reliance. It can separate essential registry work from broad institutional ambition. It can support community processes without treating them as full economic consent.
Conversely, a board elected through low-salience participation and broad institutional consensus may drift toward self-protection. It may approve budgets because staff recommend them. It may defend scope because every activity can be described as valuable. It may preserve transfer friction because caution is safer than error. It may discuss small-operator inclusion while leaving fixed costs unchanged. It may treat member silence as satisfaction.
That drift is slow and respectable. It does not look like capture. It looks like continuity. But in a scarcity economy, continuity can be a form of gatekeeping if it preserves allocation-era habits in a transfer-market world.
The market will not announce its judgment in a resolution. It will discount RIPE-region risk, rely more on brokers, structure around restrictions, lease rather than buy, avoid direct registry exposure, keep records minimally updated, or pay specialists to interpret the institution. Those behaviours are market votes on legitimacy.
The board election is the formal vote. The market response is the informal one. RIPE NCC should want the two to point in the same direction.
What a legitimate board election should test
A legitimate RIPE NCC board election in the post-exhaustion economy should test institutional theory, not only candidate character.
It should test the candidate's view of RIPE NCC's core. Is the core the narrow ledger: uniqueness, records, transfers, RPKI, reverse DNS, member support, security and continuity? Or is the core a broad regional Internet-development institution funded through the registry relationship? Both views can be defended, but they imply different fee and budget choices.
It should test the candidate's understanding of IPv4 scarcity. Does the candidate see transfer and leasing markets as normal adaptations to scarcity, or as regrettable deviations from an allocation-era ideal? Does the candidate understand that policies affecting mobility can function as capital controls even if RIPE NCC avoids property language?
It should test accountability for implementation. How should RIPE NCC publish aggregate transfer timing? How should it measure abandoned or delayed requests? How should ARCs be made cooperative and bounded? How should RPKI changes be communicated? How should reverse-DNS and database changes protect operational continuity?
It should test fee discipline. What portion of the annual fee should be visibly tied to essential ledger functions? How should broader services be justified? What is the proper role of reserves? How should the board weigh training, meetings, fellowships, research and public-policy work against the burden on small members?
It should test member participation. How should RIPE NCC reduce the cost of informed voting? Should candidate questions be standardised around budget, transfer friction, RPKI, sanctions, small operators and institutional scope? Should voting participation be reported by country, member type or size in aggregated form where lawful? How should proxy and electronic voting remain secure without becoming cumbersome?
It should test the candidate's distinction between RIPE community and RIPE NCC membership. A candidate should be able to explain where open policy consensus ends and corporate accountability begins. They should not use one to evade the other.
It should test humility. The best board member for a scarcity-era registry is not necessarily the person with the largest vision. It may be the person who knows where the institution should stop.
These tests would not politicise the election in a harmful way. They would make explicit the politics already embedded in fees, transfers, RPKI, sanctions and scope. A board election that does not discuss these issues is not apolitical. It is merely quiet.
Watchpoints: where election legitimacy will become visible
The first watchpoint is turnout relative to economic exposure. The May 2026 GM recorded 3,421 registered voters and 3,049 ballots cast. That is a meaningful electorate, but it is much smaller than the contributing LIR base described in the budget. Future elections should be judged not only by ballot integrity but by whether participation grows among small operators, lower-income markets, members outside the usual policy centres and resource holders directly exposed to transfer and fee decisions. A formally valid vote can still be economically thin.
The second watchpoint is candidate specificity. If candidates speak mainly about stability, community, experience and trust, the election will not test the scarcity problem. Watch whether candidates answer concrete questions about transfer friction, fee scope, ARCs, RPKI, reverse DNS, sanctions, leasing, legacy resources and small-member costs. Vague stewardship language is no longer enough.
The third watchpoint is charging-scheme politics. The board and members will keep facing pressure over flat fees, independent-resource charges, ASNs, sign-up fees, redistribution, reserves and the cost of broader services. If fee debates remain framed as administrative necessity, members will miss the central issue: the fee funds an institution whose recognition layer supports scarce capital. Watch whether future charging models show clearer separation between core ledger costs and broader activity.
The fourth watchpoint is budget presentation. The 2026 budget provides useful detail on registry, information-services, external-engagement and organisational categories. The next step is economic accountability: which spending reduces member risk, which reduces market friction, which supports wider public goods, and which mainly strengthens institutional presence? A legitimate board should make that distinction easier, not harder.
The fifth watchpoint is registry-friction reporting. Election legitimacy will be stronger if the board requires regular aggregate reporting on transfer timing, document cycles, inter-RIR delays, sanctions-related blocks where disclosure is lawful, ARC outcomes, RPKI incidents, reverse-DNS support and member-service response. Without such data, members vote in the dark about the cost of discretion.
The sixth watchpoint is the board's treatment of policy implementation. Community policy should remain open and bottom-up, but board accountability begins when implementation imposes cost. Watch whether the board asks for market-impact analysis when policy touches scarce IPv4 resources, routing-security state or operational control. Watch whether it treats implementation as a ledger function or as a chance to expand institutional leverage.
The seventh watchpoint is small-operator dependency. If the official path is easy for large operators and hard for small ones, RIPE NCC legitimacy will erode from the bottom. Watch whether board candidates and budgets address fixed costs: paperwork, English-language burden, meeting time, legal uncertainty, voting attention, sanctions complexity and technical automation requirements.
The eighth watchpoint is discharge culture. Members should not treat discharge as a rubber stamp. The vote releases liability toward the association for reported actions, with limits. It is not a substitute for evaluating whether board decisions lowered or raised external risk. Watch whether members use discharge debates to ask concrete questions about fees, reserves, service performance, transfer transparency and management oversight.
The ninth watchpoint is the candidate pipeline. The five-nomination threshold is open, but serious dissent must be culturally acceptable. Watch whether reform candidates can argue for a narrower, ledger-first RIPE NCC without being framed as anti-community or destabilising. A mature election can contain disagreement about institutional scope.
The final watchpoint is whether RIPE NCC keeps the official ledger cheaper than the workaround. If members and market participants believe that the elected board disciplines fees, narrows discretion, measures friction and protects operational continuity, they will trust the official path. If they believe elections simply refresh a broad institution whose costs and gates are hard to change, they will price RIPE NCC as a risk layer and buy protection elsewhere.
Board election legitimacy is therefore not an annual governance accessory. It is the mechanism by which members can tell a scarce-resource registry what kind of institution it is allowed to become. In the abundance era, a stable board could plausibly be judged by continuity and competence. In the IPv4 scarcity era, competence must include economic restraint. The board should make RIPE NCC more boring, not more grand: accurate records, predictable transfers, clear fees, bounded compliance, reliable RPKI, stable reverse DNS, measurable service, and a narrow line between ledger protection and gatekeeping power.