Summary

  • RIPE-791 extended a restriction to applications on behalf of natural persons who had acted as contact persons or representatives of a former member. RIPE-863 instead covers applications submitted by or for a person who supplied fraudulent or misleading data or was involved in supplying it.
  • The checked documents do not say whether the change broadens, narrows or clarifies the affected population. RIPE-863 does not define involved or publish a threshold for attributing participation.
  • The duration did not change. The restriction ends five years after the fraudulent documentation was submitted or, for a former member, five years after the Standard Service Agreement was terminated; a verified acquittal or dismissal can end it earlier.
  • A protected involvement-and-expiry receipt should identify the operative document, person-to-application relationship, attributed conduct, evidence classes, decision authority, start event, calculated end date, consequence and correction path without publishing private allegations.

The old sentence was built from organisational position. A person appeared in a later application, and the earlier record asked whether that person had been a contact or representative of the former member. The new sentence is built from conduct. It asks whether a person provided the data or was involved in its provision, and whether the current application was submitted by or for that person.

That is not a cosmetic edit. Role and conduct answer different questions. A named contact may have had no part in the disputed material. Someone without a formal title may have prepared, transmitted, directed or authenticated it. RIPE-863 makes conduct or involvement central, but the document does not enumerate which actions count, how close the connection must be or what evidence is sufficient.

The safe conclusion is therefore narrow. The wording changed. The five-year consequence remains. Its application now requires an attributable relationship among a prior data event, a person and a current request. The sources do not supply a real case through which to observe how RIPE NCC performs that attribution.

The predicate changed; the clock did not

RIPE-863 is a published RIPE document dated 20 July 2026, authored by RIPE NCC and approved by its Executive Board. It updates RIPE-791, the 4 April 2023 predecessor now marked obsoleted. RIPE’s own comparison page displays the former role sentence as deleted and the new provision-or-involvement sentence as inserted.

Around that edit, the main temporal rule is stable. Both texts say the restriction ceases five years after one of two events. For fraudulent documentation, the date of submission starts the clock. For a former member, termination of the Standard Service Agreement starts it. Those events are not interchangeable. A case record that stores only “five years” without naming the branch cannot reproduce the expiry.

The early-stop rule is also materially unchanged. Where RIPE NCC has reported the signing party to relevant authorities, and those authorities acquit the party or dismiss charges before the five years end, the restriction ceases when RIPE NCC is informed. This is a state transition, not a general verdict on every data-quality dispute. The text does not say that every restriction requires a criminal referral, and absence of a reported authority outcome cannot be converted into proof of wrongdoing.

State Question the record must answer
Prior data event What material was considered fraudulent or misleading, and when was it supplied?
Former-member event Was the applicable start event an SSA termination under the cited branch?
Attribution What conduct or participation was attributed to which person?
Current relationship Was the application submitted by the person, for the person or through another identified relationship?
Decision Who applied which RIPE document version, and when?
Expiry Which start event plus five years produced the end date?
Early cessation Was a verified acquittal or dismissal received, and on what date?
Correction What changed if the evidence, relationship or calculation was later repaired?

Separating those states prevents a date from carrying more meaning than it has. An SSA termination date does not by itself prove a person’s involvement. A data-submission date does not identify the current applicant. An authority outcome may terminate a restriction without erasing the fact that RIPE NCC previously made a decision under the information then available.

“By or for” is a relationship, not an accusation

The current sentence has two joins. The first connects the person to the prior data: the person supplied it or was involved in supplying it. The second connects the person to the new application: it was submitted by or for that person. Neither join should be inferred from a name appearing somewhere in a corporate file.

Consider the possible roles without inventing a case. The signing party may be a legal person. The person operating the portal may be an employee or external adviser. The represented party may be a successor organisation. A former member may have changed directors, staff or service providers. One name may recur while authority and conduct differ; two names may differ while the same person directs both actions. The policy sentence does not resolve those patterns in the abstract.

A reviewable decision therefore needs a relationship map. It should distinguish applicant, signing party, submitter, represented person, authorised representative and former member. It should say which edge brought the current request within the sentence. This is not a demand to publish a corporate dossier. It is the minimum needed to avoid treating proximity as participation.

The reverse error matters too. A role-only test may miss material conduct by someone who held no official title. RIPE-863’s conduct language can address that weakness. But discretion is not made accountable merely by choosing a broader-sounding word. Involved must become a case-specific attributed fact, not a permanent label detached from the evidence that supported it.

A protected receipt can carry the explanation

RIPE NCC states that it owes confidentiality to persons requesting resources. That boundary is compatible with a strong record. The underlying identity documents, communications and referrals can remain protected. The affected party can still receive a compact explanation, and the public can receive aggregates that contain no names or case files.

Receipt field What it controls
RIPE document and version Binds the decision to RIPE-791 or RIPE-863
Current application and signing party Identifies the request and contractual party
Person-to-application relationship Separates submitter, represented person and applicant
Prior event reference Joins the decision to a protected case without exposing it
Predicate branch Distinguishes signing-party, former-member and by-or-for paths
Attributed conduct States what participation meant in this decision
Evidence classes and dates Shows the basis without copying private evidence into the receipt
Threshold and reason code Explains why the predicate was considered met
Decision authority and time Attributes institutional action
Start-event type and date Selects the fraudulent-submission or SSA-termination clock
Calculated expiry Makes the five-year result reproducible
Bounded consequence States which agreement or service action follows
Notice and contest route Gives the affected party a correction path
Authority-outcome state Records only a verified referral, acquittal or dismissal
Revision history Preserves expiry, early cessation and later correction

The receipt should not attempt to define involved for every future matter. It should state what conduct RIPE NCC attributed in this decision and what evidence classes supported that attribution. Another case may require a different analysis. The common contract is not one universal definition; it is that each exercise of the predicate leaves a bounded, reproducible record.

A privacy-safe public view can be smaller still: counts of restrictions started, expired, ended early, upheld, corrected or withdrawn; the document version used; and distributions of start-event and reason-code classes. Zero is a meaningful count. Aggregate reporting would show whether the rule is used without turning the public registry surface into a list of allegations.

What the source change does not prove

The checked record does not explain why RIPE NCC replaced the old sentence. It does not establish that the intended population is larger or smaller. It does not say that all former contacts and representatives are now outside the rule, or that every associate of a data provider is inside it. It does not define an evidentiary standard, decision-maker, notification form or challenge route for this sentence.

It also identifies no person subject to RIPE-863. No application, refusal, service denial, referral, acquittal, dismissal, appeal or early cessation can be inferred from the policy document. The impact mechanism is conditional: an undocumented attribution could carry a prior data event into a later request, while an over-formal role test could miss relevant conduct. The source proves the design problem, not an observed injury.

Nor did the five-year duration change. The new risk lies in temporal identity: whether the attributed person, predicate branch and chosen start event remain joined closely enough that expiry and correction can be audited. A powerful clock is not made accountable by being precise to the day if the reason it started is left vague.

Sources