Summary

  • RIPE-866 governs both sponsorship accepted by RIPE NCC and support distributed by it. The same ineligibility rules therefore apply to incoming sponsors and outgoing recipients.
  • Section 4.1 places litigation, court cases, arbitration, public arguments and other conflicts in one clause, and extends it to a party merely associated with someone involved.
  • The guideline identifies RIPE NCC as final decision-maker and reserves sole discretion, but it does not publicly define the association, argument or relevance threshold, identify a case, or promise reasons and reconsideration.
  • A private affected-party receipt and a smaller public aggregate could preserve confidentiality while making direction, relationship, conflict class, evidence date, authority, duration and correction reviewable.

The consequential word in RIPE-866 is not sponsorship. It is associated.

Section 4.1 says RIPE NCC will neither accept incoming sponsorship nor provide outgoing sponsorship when the sponsor or recipient is involved in, or associated with a party involved in, litigation, court cases, arbitration, public arguments or other conflicts with RIPE NCC, its management or another RIR. The line begins with recognisable formal processes and ends with two categories that have no public edge: public arguments and other conflicts. It then adds a second join. The party asking to give or receive support need not itself be the party conducting the dispute.

That sentence sits inside a serious institutional purpose. The guideline is meant to protect RIPE NCC's neutrality, independence, reputation and the trust of the RIPE community. It says sponsorship buys acknowledgement, not influence. It excludes relationships that could compromise independence and parties that seek, or could reasonably be perceived as seeking, influence over policy, community process, governance or operations. An infrastructure institution should not let an event package become a private route into its agenda.

But a preventive rule can be legitimate in purpose and still need a decision boundary. A court case has a filing and parties. Arbitration ordinarily has an agreement and a defined process. A public argument may have none of those things. Association can describe ownership, employment, a commercial contract, professional advice, a shared director, membership in a coalition or nothing more than proximity. RIPE-866 does not say which of these relationships is relevant, how close it must be, or when it stops mattering.

The correct conclusion is not that RIPE NCC has excluded a critic. The checked public record names no rejected sponsor, no recipient denied support and no decision under the new document. The conclusion is that the published rule leaves its most elastic joins to case-level judgement. If that judgement is to be trusted, each use needs to leave more than a yes or no.

One rule, two directions of value

The first discipline is to keep the direction visible. RIPE-866 defines its scope as sponsorships received or distributed by RIPE NCC: incoming and outgoing sponsorships. Section 4 repeats that the organisation will not accept support in one direction or provide support in the other when an ineligibility condition applies.

The distinction is more than accounting. An incoming sponsor offers money or in-kind value to an institution that controls the event, programme and brand. The familiar risk is influence: visibility may be converted into access, and access may be mistaken for authority. An outgoing recipient is in a different position. It may be an event, activity or organisation seeking support from RIPE NCC. Withholding that support can protect RIPE NCC from entanglement, but it can also impose a cost on an external party whose relationship to a dispute may be indirect.

A common principle can cover both directions. A common explanation should not erase them. The decision record should begin with incoming or outgoing, identify whether the subject is sponsor or recipient, and state what RIPE NCC is accepting, withholding or ending. Otherwise the reader cannot tell whether the institution was protecting itself from purchased influence or deciding where its own support could safely travel.

The older article in BTW's archive, The Sponsor's Logo on the Agenda, examined the first risk: money buying visibility, hospitality and social access around Internet-governance meetings. RIPE-866 creates a different question. It gives the organiser an exclusion test. The analytical task is not to prove that sponsors shape an agenda; it is to make the organiser's use of association and conflict classifications inspectable.

Five conflict classes do not carry the same evidence

The drafting of Section 4.1 moves from relatively formal to radically open-ended categories.

Category named in RIPE-866 Publicly observable starting point Missing decision question
Litigation Pleadings, parties, jurisdiction or another recorded dispute What stage and relevance bring it within sponsorship review?
Court cases A court, case and party relationship may be identifiable Does any case count, or only a case tied to RIPE NCC neutrality and risk?
Arbitration A structured but often confidential process What may be verified without exposing protected material?
Public arguments No definition or required forum appears in RIPE-866 What separates sustained conflict from criticism, debate or ordinary advocacy?
Other conflicts A residual category What limiting principle prevents the residual from swallowing the list?

The article cannot fill these blanks by decree. Public arguments may be narrower than public disagreement or broader than formal controversy. The document does not decide. Other conflicts may be intended to catch a factual pattern that formal labels miss. It may also be a drafting safety valve. Neither possibility tells an affected party why its own situation crossed the line.

This is where a relevance finding matters. The receipt need not publish the argument or adjudicate who is right. It should say which conflict class was used, which institution was its target—RIPE NCC, its management or another RIR—and why that relationship mattered to a named principle such as neutrality, independence, community trust, reputation or legal risk.

Without that join, a formal label does too much work. A minor procedural case can appear more serious than a sustained informal campaign; an intense policy disagreement can be mistaken for a sponsorship conflict despite being part of a healthy open community. A reasoned finding allows RIPE NCC to distinguish them without turning the guideline into an exhaustive code.

Association needs a factual edge

The direct-party branch is comparatively simple. The sponsor or recipient is involved in the stated conflict. The association branch is where institutional memory can spread.

Corporate groups share directors and brands. Consultants act for several clients. Event organisers have venue, media, programme and financial partners. Community organisations have members who disagree with one another. A former officer may retain no current authority. A service provider may know little about a customer's dispute. Conversely, a nominally separate body may be controlled by the same people and used to route the same benefit.

A rule designed only around formal identity would be easy to evade. RIPE NCC has a legitimate reason to look through an artificial intermediary. Yet the answer cannot be to treat every relationship as attributable conduct. A reviewable record needs three separate statements: what the relationship is, what relevant conduct or control moves through it, and why that connection matters in this sponsorship context.

Roles can operate as evidence triggers without becoming automatic verdicts. Shared ownership, management, agency or funding may justify closer review. The final decision still needs a case-specific relevance finding. That approach lets RIPE NCC address evasion while protecting a venue, adviser, affiliate or coalition member from inheriting an indefinite conflict merely because a name can be connected.

Time is part of the edge. An association may end. Management can change. Litigation can settle. An argument can cool. An outgoing activity can have a different purpose from a prior incoming package. Section 6 already acknowledges changing circumstances by permitting review after acceptance. A decision record should therefore include its evidence cut-off, context and next review trigger. Otherwise a temporary relationship can become an informal permanent label.

Discretion is strongest when it leaves a reason

Section 5 allows RIPE NCC to consider community feedback where appropriate and says expressions of concern will be weighed in good faith. It also states that RIPE NCC retains responsibility for the final decision. Section 6 goes further: RIPE NCC reserves sole discretion to accept or decline incoming sponsorship and to provide or withhold outgoing sponsorship or financial support.

Sole discretion does not mean arbitrary action. It identifies the institutional owner and preserves room to handle facts that cannot be reduced to a mechanical checklist. That flexibility can be necessary when legal risk, confidentiality, event timing and community trust intersect.

The price of flexibility is an intelligible record. Community concern should be evidence to consider, not an invisible plebiscite. A legal dispute should be a fact, not a proxy for wrongdoing. Reputation should be connected to a foreseeable mechanism, not invoked as a free-standing veto. The affected party should be able to understand what RIPE NCC decided without receiving every private communication or internal legal assessment.

A bounded receipt could contain:

  • the RIPE document and version;
  • incoming or outgoing direction;
  • sponsor or recipient and contractual role;
  • direct-involvement or association branch;
  • relationship type and relevant conduct where association is used;
  • conflict class and institutional target;
  • principle engaged and case-specific relevance;
  • evidence classes and cut-off date;
  • treatment of community feedback, if material;
  • decision authority, date, reason code and scope;
  • duration or context limit; and
  • changed-circumstance review and correction channel.

This would not create a right to sponsorship. It would create a right-sized explanation of why discretion produced this result at this time.

Public accountability can remain aggregate

Publishing case files would be destructive. Litigation and arbitration can contain confidential or privileged material. A small technical community makes supposedly anonymous descriptions easy to reverse-engineer. Sponsors and recipients may also have legitimate commercial and personal interests in a private decision.

The public layer should therefore be smaller than the affected-party receipt. RIPE NCC could report counts by incoming and outgoing direction, broad reason class and result: accepted, declined, withheld, withdrawn, reconsidered or corrected. It could distinguish direct involvement from association when the number is large enough, suppress cells that risk identification, state the document version and publish zero counts instead of silence.

Those aggregates would answer important questions without naming anyone. Is the new clause used? Does it operate mainly on incoming or outgoing decisions? Is association exceptional or routine? Do changed circumstances ever lead to correction? A report of zero would be evidence about use, not proof about hidden motives.

The 194th Executive Board meeting minutes make this expectation particularly reasonable. They say the Board asked for criteria to justify sponsor decisions. They also record a deliberate choice to make the document available to the community as a RIPE Document, partly for version control, while keeping approval internal rather than requiring Board approval.

Versioned publication solves one problem: readers can know what the institution says. A reason-and-review record solves the next: affected parties and overseers can know which part of that document did the work.

What is not in the record

No checked source identifies a party excluded under RIPE-866. No source says a public mailing-list message, press article, lawsuit, criticism of an RIR or policy disagreement counts as a public argument. No source says that ownership, employment, advice, family, customer status or membership is enough to establish association.

The public guideline does not say RIPE NCC keeps no internal record. It simply does not expose a standard reason contract. Nor does it say that an ineligible sponsorship affects RIPE NCC membership, Internet number resources, registry services, voting, policy participation or attendance. Sponsorship is the decision surface. Expanding the article beyond it would convert a document analysis into an allegation.

RIPE-866 is also not a community-adopted number-resource policy. The public page lists RIPE NCC as author and RIPE NCC Management as approver. The Board minutes describe a request, advance review and internal approval route. That governance history may invite oversight questions, but it does not justify rewriting the approval record.

The risk analysed here is conditional. An undefined association can increase diligence and interpretation cost. A broad reference to public arguments can create apprehension about how disagreement will be classified. Neither mechanism proves actual chilling, retaliation, inconsistent decisions or financial loss. The document supplies the control design; observation must wait for implementation evidence.

Sources