Summary

  • ICANN Reconsideration is broader on paper than a simple checklist review. A materially harmed requester may allege that Board or staff conduct contradicted the Mission, Commitments, Core Values or established policy, ignored material information, or relied on false or inaccurate relevant information.
  • The mechanism remains self-review. BAMC consists of three to seven voting Board members, determines whether a request is sufficiently stated, may dismiss it, investigates surviving claims and recommends an outcome. The same Board is not bound by the recommendation and issues the final decision.
  • Access burdens are decisive: a 30-day filing window, a mandatory form, proof of material harm and adverse impact, a 25-page argument limit, identification of a specific Board or staff act, complete evidence at the outset and a restricted rebuttal. Recent annual reports show summary dismissal and denial far more often than an express merits correction.
  • The Bylaws categorically exclude disputes relating to Internet numbering resources from Reconsideration and also from the Independent Review Process. Number communities must normally use RIR procedures, ASO/NRO routes, the global policy safeguards, the IANA Numbering Services agreement or an appropriate court or contractual remedy.

A remedy whose name promises a second look

"Reconsideration" sounds broader than appeal. It suggests an institution willing to pause, reopen its reasoning and correct itself before a dispute becomes expensive or irreversible. ICANN presents the mechanism as one of the ways a person materially affected by Board or staff conduct can ask the Board to review that conduct. It is public, generally financed by ICANN and designed to move faster than independent adjudication.

The name can also mislead. Reconsideration is not a new hearing before a body standing outside ICANN. It does not transfer decision-making power to the complainant, the Ombuds or a panel of judges. The Board Accountability Mechanisms Committee, known as BAMC, performs the gatekeeping and merits analysis. BAMC is a Board committee. It sends a recommendation to the full Board. The Board may accept or reject that recommendation and supplies the final answer.

The mechanism therefore sits between administration and adjudication. It has legal standards, deadlines, a public evidentiary record, reasoned recommendations and a right of rebuttal. It can examine more than whether the correct form was used. Yet it remains an exercise of corporate self-correction. Its authority comes from the Bylaws, and its remedy is a new Board decision rather than an independent order imposed on the corporation.

This distinction is especially significant when the complaint alleges mandate overreach. If the Board is said to have exceeded ICANN's Mission, asking a Board committee and then the Board to decide the allegation tests the institution's willingness to police itself. It does not provide structural independence. The review can still be careful, transparent and corrective. But its legitimacy depends on the quality of reasons, conflict handling, evidence and the availability of a different forum when self-review fails.

For Internet number resources, the difficulty is more fundamental. The current Bylaws expressly remove disputes relating to those resources from Reconsideration. A number-community claimant may have a compelling account of overreach and still be at the wrong door.

The legal test reaches mission overreach in express terms

The current ICANN Bylaws do not confine Reconsideration to clerical mistakes. Section 4.2 permits a request by a person or entity materially affected by an action or inaction of the Board or staff. The requester must show adverse effect and fit the complaint within one of three grounds.

The first ground is conduct contradicting ICANN's Mission, Commitments, Core Values or established policies. This is the clearest answer to the question whether mandate overreach can be raised. If the Board acts outside the mission described in Article 1, the text allows a Reconsideration challenge unless an exclusion applies.

The second ground is a Board or staff action or refusal to act taken without considering material information. It has a qualification: a requester cannot complain about omitted information that the requester could have submitted but did not submit at the relevant time. The third ground concerns reliance on false or inaccurate relevant information.

These grounds are substantive in the sense that they can require examination of mission limits, materiality and the factual basis for a decision. A Board resolution adopted after every prescribed meeting can still contradict the Mission. A staff determination reached through the usual steps can still rest on a material falsehood. Reconsideration is not textually limited to asking whether notice was sent and a vote occurred.

At the same time, each ground directs attention to the legality and integrity of decision-making rather than inviting BAMC to choose the policy it prefers. The question is not simply whether the outcome was bad for the requester. The requester must connect the outcome to a governing contradiction, omitted material fact or inaccurate fact. Disagreement with judgment, priority or commercial effect is limited public evidence unless translated into one of those standards.

That translation explains why the mechanism often feels procedural even when the Bylaws permit a Mission claim. Mandate is tested through governing text. Fact error is tested through the record. Failure to consider is tested by what was available and who could have supplied it. The Board is asked to reconsider the lawfulness and basis of its choice, not to surrender the choice.

BAMC is the Board examining the Board

The BAMC Charter approved in October 2023 states the institutional fact plainly. The committee consists of at least three and no more than seven voting Board members appointed annually by the Board. Voting directors are the voting members, and members serve at the Board's discretion.

BAMC has substantial authority. It evaluates each request, decides whether it is sufficiently stated, can dismiss an limited public evidence or frivolous request, considers urgency, conducts factual investigation, asks for further submissions and makes a merits recommendation when a request survives. It may seek consultants with Board-approved resources. It can ask staff for views, invite third-party information and decide whether to hear the requester.

Those powers can support serious review. Directors may know the institution's governing documents and can obtain the records needed to reconstruct a decision. A committee can move more quickly than a newly appointed tribunal. Board ownership can also make implementation easier: the people who recommend correction sit within the body capable of ordering it.

The same features create an independence problem. BAMC members are directors of the corporation whose conduct is challenged. Even if a particular member did not participate in the original decision, the committee shares fiduciary responsibility, colleagues, counsel and institutional reputation with the decision-maker. Staff lawyers and officers who advise the Board may appear in the review record. The final decision returns to the Board.

Conflict rules and recusals mitigate personal conflicts. Published minutes show members recusing themselves in particular matters, sometimes in numbers large enough to affect quorum. Recusal is necessary, but it cannot transform a Board committee into an outside adjudicator. The structural relationship survives after individual conflicts are removed.

The honest description is therefore not that BAMC is biased by definition, nor that it is independent. It is a self-review committee operating under public rules. Its work should be judged accordingly: Did it define the challenged action accurately? Did it separate threshold questions from merits? Did it disclose staff submissions? Did it address each argument? Did conflicted directors withdraw? Did the final Board give reasons rather than adopt the committee's conclusion by formula?

The first hearing is about whether there will be a hearing

Every request begins with a sufficiency review. BAMC asks whether the requester is eligible, timely, materially harmed and challenging conduct within Section 4.2. It also asks whether one of the three grounds is stated with enough specificity. A failure at this stage produces summary dismissal without a merits recommendation to the Board.

This gate is not an administrative triviality. It is where a large share of recent requests end. The 2023 BAMC annual report says Request 23-1 was dismissed because the requester did not adequately allege material and adverse harm. The report emphasizes that the result was a procedural review and did not decide the substance of the claims about the .NET registry agreement.

The 2024 report gives a fuller example. Request 23-2 challenged several decisions and acts connected with the grant program. BAMC found deficiencies including failure to identify adverse effect, untimeliness for older conduct and failure to identify a specific Board or staff action for part of the complaint. It summarily dismissed the request while recognizing the significance of the wider concerns.

That distinction is legally coherent but publicly difficult. A claimant may believe the institution crossed a constitutional line. The published answer may say only that this claimant did not plead injury, filed too late or described the target too broadly. The decision protects the mechanism from becoming a general advisory jurisdiction. It also means the overreach allegation remains unanswered.

Threshold decisions deserve the same quality of explanation as merits decisions because they define access. "Insufficiently stated" should identify which fact, causal link, authority or date is missing. A dismissal should never imply that the challenged conduct was validated. BAMC's own reports sometimes make that boundary express; every decision should.

Material harm converts a public complaint into a personal case

ICANN's Mission is framed around the global Internet community, yet ordinary Reconsideration standing is not a public-interest licence. Every requester must demonstrate material harm and adverse impact caused by the challenged Board or staff conduct. Concern about governance, expenditure or precedent is not enough on its own.

This requirement serves a legitimate function. Without it, any person could demand a full Board review of any decision, imposing cost and delay on a globally visible institution. A material-harm rule focuses resources on people with a real stake and reduces strategic filings made only to preserve future objections.

But the rule is difficult for diffuse harms. Mandate overreach can affect institutional legitimacy before it causes a measurable injury to one entity. A policy may shift authority across communities, weaken a limit or establish a precedent whose later effects are uncertain. Those concerns can be serious even when no individual can quantify loss within thirty days.

The standing requirement can also favor commercial claimants. An applicant, contracting party or directly affected service user can often identify a delayed application, lost opportunity, expense or adverse determination. A volunteer, technical community or public-interest entity may have stronger constitutional concerns but a less individualized injury.

The Empowered Community offers a partial answer. It may bring a Community Reconsideration Request concerning the exercise of its powers if the Decisional Entities authorize the action under Annex D. The community route does not require an ordinary individual to prove the same personal harm. It does, however, require institutional coalition and applies only within the defined community powers.

The result is a two-track legitimacy model. Individual access depends on injury. Constitutional access depends on organized community authorization. A concern that fits neither can be debated, submitted in public comment, raised with the Ombuds or pursued politically, but it does not automatically receive a Reconsideration judgment.

Thirty days rewards vigilance and punishes ambiguity

For Board action, the ordinary filing period is thirty days from publication of the resolution or, if the rationale is posted later, from publication of the rationale. For staff action, the clock runs from when the requester knew or reasonably should have known. For inaction, it runs from when the requester reasonably concluded that timely action would not occur.

Thirty days can be sufficient for a party already following a matter with counsel and a complete record. It is demanding for a dispersed community that must learn what happened, obtain documents, decide who is injured, identify a governing contradiction and authorize a filing. The rule is especially difficult where the harm becomes clear only after implementation.

The inaction rule adds judgment. A requester must decide when delay became a refusal. Filing too early can invite the answer that no final inaction exists. Filing too late can invite the answer that the requester should have concluded earlier. The public record can reduce uncertainty if ICANN states decision dates and whether a matter remains under active consideration.

Urgent review is even tighter. A requester seeking urgency must apply within two business days after the challenged Board resolution is posted, explain urgency and show a likelihood of success. BAMC decides the urgency request within two business days and, if accepted, seeks a completed filing on another short timetable.

These limits protect continuity. An institution cannot leave every decision indefinitely vulnerable to a low-cost reopening. Yet strict time limits make publication quality part of substantive accountability. A resolution should identify the act, rationale, material information, authority and effective date clearly enough for an affected person to evaluate the claim before the clock expires.

Where essential facts are withheld or a rationale changes materially, a rigid application of time can reward opacity. BAMC should state how disclosure affected the filing date in every contested case. Timeliness is fair only when the event starting the clock is intelligible.

The requester must arrive with the theory largely complete

The Bylaws require use of the prescribed form and limit the main argument to twenty-five double-spaced pages, excluding exhibits. Documentary evidence has no comparable page cap. The requester must identify the specific action or inaction, explain harm, choose the applicable ground, state the requested relief and provide the evidence supporting the case.

This design favors disciplined claims. It prevents a complainant from submitting a broad grievance and asking BAMC to discover a legal theory. It gives the committee and affected staff notice of the case to be answered. A page limit can improve clarity when the underlying record is large.

The burden is still asymmetrical. ICANN begins with access to its own decision papers, staff, counsel and institutional history. The requester may have only the published rationale. Documentary disclosure can help, but obtaining it may take longer than the Reconsideration deadline, and some material may be withheld for privilege, confidentiality, security or other recognized reasons.

The rebuttal does not cure a weak opening. After BAMC issues its recommendation, the requester has fifteen days and ten pages to rebut it. The rebuttal must address issues in the recommendation and generally cannot add evidence supporting an original argument if that evidence could have been supplied at filing. A claimant who learns how ICANN characterizes the dispute only after the recommendation may have little room to reconstruct the case.

BAMC may ask for clarification, hear the requester or seek third-party information, but the requester cannot demand discovery in the manner available in litigation. The committee's decision whether to grant an opportunity to be heard is final. The review rests on a public written record.

This makes front-loaded accuracy decisive. A strong filing needs a chronology, exact citations to the Mission or policy, an explanation of causation and harm, the omitted or inaccurate information, evidence that it was material, and a remedy within the Board's power. Moral force is not a substitute for this architecture.

The Ombuds adds a view, not a new centre of authority

When a request survives summary dismissal, the Bylaws generally send it to the ICANN Ombuds for substantive evaluation. The Ombuds may seek outside expert assistance within the assigned budget and is expected to report to BAMC promptly. BAMC then performs its own review.

This step can add distance from the original Board decision. The Ombuds can examine fairness, context and community effect without being a voting director. A reasoned Ombuds assessment may identify assumptions the corporate decision-makers missed.

The independence gain is limited. The Ombuds evaluation is advisory to BAMC. It does not replace the committee's recommendation or bind the Board. The Ombuds must recuse from matters on which the office previously took a position or where the office's conduct is involved. In those cases BAMC proceeds without that contribution.

The 2023 annual report illustrates the sequence. Request 22-5 passed the sufficiency check and received an Ombuds evaluation. BAMC issued a recommendation, the requester filed no rebuttal and the Board adopted the recommendation denying relief. Passing the first gate therefore means a claim will be examined; it does not shift the ultimate authority.

The Ombuds role should be visible in final decisions. If BAMC agrees, it should explain why. If it disagrees, it should identify the point of departure. A short reference to having considered the evaluation does little to show that the added perspective changed the analysis.

Community expectations should also remain precise. The Ombuds can improve fairness and facilitate resolution. The office is not an appellate tribunal with power to reverse a Board action. Treating it as one sets claimants up for disappointment and allows the Board to receive credit for independence it has not granted.

A merits review asks whether judgment stayed within law

When BAMC reaches the merits, it may have to examine both procedure and outcome. The distinction is easiest to see in disputes over expert determinations. ICANN's decisions have said that Reconsideration is not a general opportunity for the Board committee to substitute its view for that of an expert panel. Review instead asks whether the provider followed the governing standards and whether ICANN acted consistently in accepting the result.

That can require looking at outcome evidence. If a panel ignored a mandatory criterion, relied on a fact that was demonstrably false or applied a rule to one applicant but not another, procedural compliance cannot be assessed without understanding the decision's effect. The Board's 2018 decisions on community-priority disputes describe this overlap while rejecting the particular claims presented.

Mission overreach works similarly. BAMC need not decide whether it would have adopted the policy. It must determine whether the action fits the mission language and commitments. That inquiry can be substantial. It may require interpreting the scope clause, identifying the affected policy community and deciding whether the stated public-interest rationale supplies authority or merely explains motive.

The danger lies in collapsing deference into validation. If every contested judgment is described as a reasonable exercise of Board discretion, the Mission ground becomes symbolic. A meaningful review should state the limiting rule and test the action against it. It should identify conduct that would have crossed the line, even when the actual conduct did not.

At the other extreme, Reconsideration should not become a universal second policy debate. Board members have fiduciary duties and often must balance core values. The fact that another reasonable outcome existed does not establish a contradiction, omitted fact or false premise.

The mechanism is strongest in the middle: exact authority, exact facts, a visible standard and a remedy directed at the defect rather than the preferred policy.

The remedy is a recommendation followed by another Board decision

BAMC must produce a documented recommendation addressing each argument. The requester may rebut. The Board then decides. The Bylaws expressly state that the Board is not bound by BAMC's recommendation. The Board's decision and rationale must be public, and the requester may ask for the recording and transcript of the substantive Board discussion as well as the briefing materials, subject to stated redaction grounds.

This structure gives the Board flexibility. It can deny a request, reconsider or modify an earlier act, direct staff to take another step, seek more information or recognize that events have already supplied the requested relief. A narrowly tailored correction may preserve continuity better than full reversal.

Flexibility also makes remedy quality difficult to measure. A request can be formally denied after the institution changes course for another stated reason. It can become moot because the challenged activity stops. A Board can agree that more explanation is needed without conceding the original decision was unlawful. Counting only express grants misses those effects.

The reverse problem is equally serious. A detailed recommendation can create the appearance of independent adjudication even though the Board is affirming its own committee. If the final rationale simply incorporates BAMC's analysis and states agreement, readers cannot tell what the full Board added.

A credible final decision should identify four things: the challenged act, the standard, the corrective consequence and the implementation owner. If relief is partial, it should say which defect was corrected and which claim was denied. If the matter is moot, it should explain whether the change was caused by the request, an unrelated event or a decision already underway.

Reconsideration does not create precedent in the same way as a binding court judgment. Still, consistency matters. Later decisions should explain departures from earlier interpretations of standing, materiality, timeliness and scope. Otherwise the Board controls not only the answer but the memory of the mechanism.

Recent outcomes show gatekeeping more clearly than correction

The annual BAMC reports provide useful but bounded evidence. They use reporting periods tied to annual meetings, and a request can appear across more than one report as it moves from filing to decision. They should not be converted casually into a lifetime success rate.

The 2021 report records three requests received and three summary dismissals. One challenged conduct by a third-party registrar rather than Board or staff conduct. The others failed the stated threshold requirements, including material harm.

The 2022 report records six requests received during its period. BAMC acted on four and summarily dismissed all four. One additional request was withdrawn after passing the sufficiency review, and another remained pending. The dismissals turned on standing, failure to identify a governing violation, a challenge to third-party conduct and related threshold defects.

The 2023 report records the later merits denial of Request 22-5 and the summary dismissal of Request 23-1. The 2024 report records three requests received, one withdrawal, one summary dismissal and one request pending BAMC consideration at the report date. Across these recent periods, the dominant visible outcomes are threshold dismissal, withdrawal and denial, not a final Board statement granting a Mission challenge.

This pattern supports a modest conclusion. Reconsideration is primarily a gatekeeping and self-review mechanism in present practice. It filters complaints that do not identify a reviewable ICANN act, concrete harm, timeliness and a recognized ground. Claims that survive are not commonly shown in the annual summaries as producing express merits reversal.

The pattern does not prove that the mechanism has no corrective effect. The denominator is small, cases differ, and some disputes are resolved or changed before final disposition. Nor does a high dismissal share prove bad faith; a public, no-filing-fee route attracts claims beyond its jurisdiction. But the record places a burden on ICANN to demonstrate where Reconsideration changed conduct, not merely where it produced reasons for leaving conduct unchanged.

Mootness can be success, evasion or coincidence

Older decisions show why outcome coding needs care. Request 14-42 challenged a geographic-names evaluation involving "Tata." Later events caused further review, the applicant failed to provide required support and the application was listed as not proceeding. BAMC treated the requested relief as achieved and the Reconsideration matter as moot.

Request 17-5 sought a hold on the .KID/.KIDS contention set while accountability matters were resolved. ICANN placed the set on hold, and the Board concluded that the requester had received the relief sought. Again, the formal result was not a merits finding that ICANN had violated its Bylaws.

These outcomes can represent effective self-correction. If a filing causes ICANN to pause a harmful act, insisting on a ceremonial finding may add little. Early relief is often better than a late victory.

Mootness can also conceal causation. The challenged action may have changed because of market events, another review, a court case or ordinary administration. If the public record merely says that relief has occurred, the mechanism receives neither deserved credit nor deserved criticism.

Every moot decision should therefore state the chronology. When did ICANN first decide to change course? What role did the request play? Was the original reasoning withdrawn, preserved or superseded? Can the same issue recur? If recurrence is possible, a legal question may remain significant even after the immediate remedy is supplied.

The same care applies to withdrawal. A requester may settle, obtain relief, lose interest, run out of resources or conclude that the forum cannot help. A withdrawal count alone says nothing about legitimacy. Published closure notes should distinguish resolution from abandonment where confidentiality permits.

Independent review has sometimes exposed the limits of self-review

The relationship between Reconsideration and independent review supplies a revealing comparison. In the .SPORT dispute, earlier Reconsideration requests were denied. An Independent Review panel later declared the claimant the prevailing party and recommended that the Board reconsider the requests together using the relevant conflict standard. The Board accepted that recommendation and sent the matters back for evaluation, after which the Board again denied them.

The episode does not show that the independent panel dictated the final substantive answer. It shows that outside review could require the Board to take another look and apply a clearer frame. Reconsideration alone had not produced that correction.

The current Independent Review Process has stronger stated purposes, including ensuring that ICANN stays within its Mission and providing independent third-party review. It can generate binding declarations within its Bylaw design and is structurally different from BAMC self-review. It is also more demanding, slower and potentially costly.

For many ordinary claimants, Reconsideration remains the accessible first route because ICANN absorbs normal administrative costs and the filing is public. That makes its quality significant even where later review exists. A weak first review increases cost for everyone and may allow harm to become irreversible before an outside body acts.

Yet the comparison must not create false reassurance for the number community. The same Bylaws that exclude number-resource disputes from Reconsideration also exclude claims relating to Internet numbering resources from Independent Review. A number claimant cannot assume that an outside ICANN panel will correct a BAMC refusal.

Number-resource disputes are outside the door by design

Section 4.2(d) lists four exclusions from Reconsideration: disputes relating to country-code delegation and re-delegation, Internet numbering resources, protocol parameters, and decisions approving or rejecting grant-program applications. The number exclusion is categorical in wording. It does not say that BAMC may hear a number dispute if the requester alleges Mission overreach.

The independent-review exclusion uses materially parallel language. Section 4.3(c) removes claims relating to Internet numbering resources. The architecture therefore does more than send number disputes from a quick Board review to an independent ICANN tribunal. It sends them elsewhere.

The reason lies in the post-transition settlement. Names, numbers and protocol parameters have different operational communities and accountability arrangements. The number community created the NRO, ASO structures, regional procedures and a direct IANA Numbering Services agreement. A universal ICANN appeal could allow the names-centred corporation to become the appellate authority over a federated number-policy system.

The exclusion protects that autonomy. It also creates an accountability gap if readers assume that ICANN's general Mission remedies cover every Mission-related act. A Board action can involve numbers and still fall outside the two best-known ICANN review mechanisms. The affected party must identify the right forum before the short deadlines elsewhere expire.

Mixed disputes will be difficult. A complaint might concern a general corporate resolution, Board composition, expenditure or disclosure while also affecting number resources. The phrase "relating to" is broad. The public materials selected for this analysis do not establish a comprehensive boundary for every mixed case. A prudent claimant should not rely on relabelling a number dispute as governance; it should seek the governing route and preserve any legal rights promptly.

The exclusion should be visible on every filing guide. A person should not spend the thirty-day period preparing a Reconsideration case only to learn at dismissal that the matter belongs with an RIR, the NRO, the ASO, a contract route or a court.

A number grievance must be classified before it can be remedied

"Number-related grievance" is too broad to identify one forum. At least five distinct disputes can arise.

A regional allocation-policy complaint concerns rules adopted in one RIR region. The relevant regional policy-development procedure, appeal route, membership mechanism or local law will usually govern. ICANN's Board does not become the appellate body merely because the resource ultimately appears in a global registry.

A complaint that an RIR, the NRO or an NRO body failed to follow the global policy-development procedure belongs within the number community's accountability arrangements. The NRO Memorandum of Understanding provides for an Advisory Appeals Panel concerning alleged failure to follow the documented global policy route. The exact standing, scope and effect must be checked against the current governing text.

A disagreement over an ICANN Board response to a global policy should follow the ASO global policy safeguards. The Board must explain a rejection, the ASO and RIRs can reconsider or reaffirm, a resubmitted proposal faces a supermajority rejection threshold, and a second rejection leads to mediation.

An operational complaint about IANA numbering service belongs under the IANA Numbering Services agreement, its performance measures, escalation and dispute provisions. The IANA Numbering Services Review Committee provides recurring community oversight of service levels.

A corporate, fiduciary, contractual or public-law claim may belong in court or another dispute forum with jurisdiction. That route depends on the parties, agreement, place of incorporation, harm and relief sought. The existence of an ICANN Bylaw exclusion does not decide every external legal right.

Classification is therefore the first act of advocacy. The claimant should identify the decision-maker, governing document, duty, review holder, deadline and remedy. Choosing the wrong institution can turn a strong grievance into an easy dismissal.

Mandate overreach is hardest when mandate is distributed

In generic names, ICANN often contracts directly with the affected registry or registrar and implements policy through a comparatively centralized corporate structure. In numbers, authority is distributed. Regional communities make regional policy. All five must agree for a global policy requiring IANA action. The ASO checks the route. The ICANN Board performs a defined review. PTI carries out registry services. The RIRs oversee performance under their agreement.

Overreach can occur at any link. An RIR board might displace a regional community. The ASO might misstate whether global consensus exists. ICANN's Board might treat its review power as an originating power. PTI might implement something not authorized by policy. A court might issue an order affecting registry continuity. Calling all of these "ICANN overreach" obscures the responsible institution.

Reconsideration is a poor universal remedy for precisely that reason. BAMC has authority over Board and staff conduct, not the acts of every RIR or community body. Extending it to all number disputes would put a Board committee above institutions that do not derive their regional mandate from the Board.

But exclusion should not become impunity. Where ICANN itself acts, the number system still needs a credible way to test whether it stayed within the Bylaws and agreements. The global policy route and service contract cover significant classes of conduct, but the public should be able to locate the applicable remedy without reconstructing two decades of institutional history.

ICANN and the NRO should publish a joint remedies map for number matters. It should distinguish policy, recognition, service, disclosure, representation, budget, Board-seat and legal-continuity disputes. For each, it should identify who may complain, to whom, by when, under which standard and with what possible result.

Self-review can be improved without pretending it is a court

The first reform is decisional separation. BAMC membership should exclude directors who participated materially in the challenged action wherever enough unconflicted directors remain. The minutes should identify recusals and the reason at a useful level without disclosing protected information. If quorum fails, the full Board should explain the alternative handling rather than quietly collapsing the distinction.

Second, sufficiency decisions should use a stable public test. Timeliness, material harm, challenged actor, reviewable conduct, ground and exclusion should appear as separate findings. A failure on one should not be phrased as a judgment on the others.

Third, claimants should receive an early notice of curable defects when time permits. BAMC should not coach the merits, but a missing date, unclear challenged act or incomplete harm statement could be identified before final dismissal. A short cure period would improve access without opening endless amendment.

Fourth, the requester should have a presumptive right to a short hearing in a surviving Mission case. BAMC could deny only with reasons. A hearing does not make the committee independent, but it reduces the risk that a constitutional claim is flattened into competing papers.

Fifth, staff views and third-party submissions should be posted promptly enough for response. The Bylaws require a public written record. Fairness requires more than publication after BAMC has already formed its view.

Sixth, the Board's final decision should contain its own analysis. Incorporation by reference may avoid repetition, but at least one section should explain why the full Board agrees or disagrees and what it learned from the rebuttal.

Seventh, annual reports should add outcome fields for relief supplied, conduct changed, request moot, partial correction, implementation complete and recurrence risk. Counting filings and dismissals is not enough to test remedial value.

Number accountability needs its own visible guarantees

The number exclusion should be paired with affirmative safeguards, not left as a footnote. The NRO and ASO already maintain policy and operational accountability arrangements. Their visibility and interoperability can improve.

Each RIR should publish a current remedies page covering policy procedure, membership decisions, registry service, executive conduct and continuity. The five pages should use common headings even if regional law and remedies differ. A network operator facing a deadline should not need to infer whether a community appeal, arbitration, ombuds function or court claim applies.

The ASO should maintain a single record for every global policy proposal: five regional outcomes, Address Council verification, Board action, any request for changes, reconsideration by the regions, resubmission and mediation. The record should distinguish policy merits from compliance with the agreed route.

The IANA Numbering Services Review Committee should continue publishing performance evidence and should link any service exception to the escalation path and resolution. Aggregate percentages are useful; case closure shows whether accountability worked.

ICANN Board papers affecting the ASO, RIR recognition or number services should state why the number-resource exclusion does or does not affect review rights. This is not an invitation for BAMC to enlarge its jurisdiction. It is notice to affected parties about where to go.

Continuity planning also matters. A severe RIR governance or court crisis can threaten records and service beyond one region. Emergency measures should identify their authority, duration, review holder and exit condition in advance. Urgency must not become a permanent transfer of policy power.

Finally, the communities should examine genuine gaps. If a class of ICANN Board action relating to numbers is excluded from both Reconsideration and Independent Review yet not covered by the global policy route, service agreement, Empowered Community or an accessible legal remedy, the gap should be documented and addressed through the proper constitutional route.

A useful review must distinguish error, disagreement and exclusion

The Reconsideration mechanism performs three different acts that public debate often combines.

It can correct error. A Board or staff act may contradict the Mission, omit a material fact or rely on an inaccurate one. A well-founded request can produce another decision, additional explanation, a pause or a modified action.

It can reject disagreement. A requester may suffer harm and dislike the outcome while failing to show a governing contradiction or factual defect. BAMC and the Board are entitled to say that discretion was exercised lawfully. The legitimacy of that answer depends on reasons, not requester satisfaction.

It can enforce exclusion. A complaint may be serious but concern a third party, a country-code delegation, protocol parameters, a grant decision or Internet numbering resources. The Board mechanism is then not the assigned forum. Dismissal says where authority is absent; it does not establish that the underlying conduct was sound.

Clear decisions should label which act they are performing. Too much institutional language treats every denial as vindication. That confuses jurisdiction with merit and discourages claimants from pursuing the correct route.

The distinction is most urgent for number disputes. A BAMC refusal based on Section 4.2(d) should say that no conclusion has been reached on the number grievance and identify the known alternative routes. The Board should not cite the absence of a successful Reconsideration request as evidence that its number-related conduct was accepted.

Conclusion

ICANN Reconsideration can reach mandate overreach in theory. The Bylaws expressly allow a materially harmed person to allege that Board or staff conduct contradicted the Mission, Commitments, Core Values or established policy. The mechanism can investigate facts, obtain an Ombuds view, receive a rebuttal and produce a public Board decision.

Its institutional design nevertheless favors review of the decision-making basis over transfer of decision-making power. BAMC is made of directors. It controls the sufficiency gate and recommends the result. The Board is not bound and gives the final answer. The claimant must file quickly, plead material harm, identify exact conduct, supply the theory and evidence early, and fit the dispute within a narrow set of grounds.

The recent public record shows what that design does most often: it filters. Summary dismissals for standing, timeliness, actor and stated-ground defects are common. Merits denials appear more readily than express grants. Some filings may still cause a pause, obtain relief or become moot, which is why raw win-loss counting is inadequate.

For Internet numbering resources, the answer is sharper. Reconsideration does not merely provide a weak remedy; the Bylaws exclude the dispute class. Independent Review carries the same exclusion. A number claimant must use the regional, ASO, NRO, service-contract, Empowered Community or legal route suited to the challenged act.

Self-review has value when it is fast, candid and capable of correction. It becomes constitutional theatre when reasons only explain why the institution was right. The test is not how many pages BAMC publishes. It is whether a valid defect changes the act, whether a threshold dismissal preserves the distinction between access and merits, and whether excluded communities have a visible remedy elsewhere.

Reconsideration can review power only through the limits power has already written for itself. It cannot supply authority where the Bylaws deliberately placed the dispute beyond the Board's second look.

Sources