Summary

  • ICANN org told the Reviews CCG on 18 September 2026 that its records showed formal adoption of the 2016 Uniform Framework by the GNSO and ccNSO, but no adoption or endorsement by any other SO/AC.
  • The Board was not asked to adopt the framework, so the document does not by itself prove agreement to the Board role described in it or an ICANN-wide standing mechanism.
  • The current Reviews CCG remains separately authorized by its 2025 charter, SO/AC nominations and Board approval; the unresolved question concerns a future Structural Review group.

A document reached two councils, not the whole institution

The most useful line in ICANN's 18 September status note is also the most restrictive. ICANN org said the Country Code Names Supporting Organization and the Generic Names Supporting Organization formally approved the Uniform Framework of Principles for Future CCWGs in late 2016. It then said a review of organizational records did not show adoption or endorsement by any other Supporting Organization or Advisory Committee.

That distinction changes what the document can prove. The GNSO Council approved the final framework on 13 October 2016. Its resolution directed staff, once the ccNSO had also acted, to inform every SO/AC of the two councils' adoption and recommend that the principles be consulted when future CCWGs were considered. The ccNSO Council followed on 7 November with Resolution 123-07. It adopted the final report and framework, invited ICANN's Advisory Committees and the Address Supporting Organization to adopt it, and asked that it be posted as a guideline.

Notification, invitation and consultation are visible in the record. Further adoption is not. ICANN org consequently described the framework as, at best, a reference point rather than a proven and available mechanism for convening cross-community groups. That is a record-bound conclusion, not a claim that no one ever cited or informally followed the document.

The Board boundary is equally explicit. The GNSO project page lists public comment before Board consideration as not applicable and the Board resolution as not applicable. Ten years later, ICANN org said the Board had never been asked to consider and adopt the framework. It followed that there had been no Board agreement to the role assigned to it in the document.

What Version 1 actually supplies

The 27-page final framework calls itself a general framework and a collection of community-agreed guidelines, not rigid rules for every case. Its operative model begins with a separate charter. At least two SO/ACs must adopt the same identical charter through their own normal processes before a CCWG is formed. Those adopters become the chartering organizations.

The charter is meant to carry the missing authorization detail. It identifies the chartering organizations and their approval dates. It defines members, participants and observers; specifies whether Board or staff liaisons participate and in what capacity; establishes the decision method and any thresholds; preserves minority positions and escalation; and states whether the Board is expected to act on final recommendations.

Appointments also have a defined source. Chartering organizations appoint members under their own rules. Other volunteers may participate, but the framework's default says a formal consensus call is limited to appointed members. Openness can widen evidence and expertise without silently changing who is authorized to make a decision.

Outputs return to the chartering organizations. Unless the charter provides another rule, all of them must at least not object before a final deliverable becomes the formal CCWG consensus output. Implementation or onward submission occurs only after the organizational and, where appropriate, Board treatment named in the charter. The framework is therefore a recipe for producing authority records, not a substitute for them.

The current Reviews CCG has its own receipt

The present Review of Reviews Cross Community Group should not be placed inside the 2016 adoption gap. Its authorization can be traced independently.

The 2025 Reviews CCG charter names the SO/ACs, the Board and ICANN org as nominating groups. It states that nominating a member is deemed support for the charter. It also says members act in their individual capacity rather than representing their nominating groups, while the final decision on the proposal remains with the SOs and ACs. Internally the group seeks consensus. Externally every SO and AC is asked to decide under its own procedures whether to support the recommendations, and the process closes if two or more do not support them.

On 5 September 2025, the Board approved that charter and appointed James Galvin and León Sánchez as Board participants. A letter from the Board Chair subsequently confirmed both acts. Those records do not make the 2016 framework universally adopted. They do show that the current CCG possesses a distinct charter, appointment route, external support process and Board relationship.

Structural Review still needs a formation record

The June 2026 Review of Reviews draft proposed that phases of a future Structural Review be conducted by a cross-community working group using existing practices. At the 1 September meeting, members discussed keeping the room open to broad participation because the work could reach ICANN's structure, Board composition and relationships among silos. The same meeting produced an action to obtain more information on the status of the CCWG method.

ICANN org's later answer did not say a future group was impossible. It said the 2016 document could not be treated as an already proven ICANN-wide mechanism. The suggested path was to specify the necessary attributes: which or how many SO/ACs approve the charter, how participation is balanced, what endorsement threshold applies before recommendations reach the Board, and what dialogue occurs if the Board declines a recommendation.

That approach separates the name from the mandate. A body may be called a CCWG, a cross-community group or something else. Its authority still depends on recorded acts by the institutions whose participation is claimed.

A charter-adoption receipt

Before the future Structural Review group begins, one public record should bind the design to the acts that authorize it. It should identify the exact charter version and hash. For each SO/AC it should record whether the body considered, adopted, endorsed, objected to or took no action on that version, with the date and resolution. It should state whether that act makes the body a chartering organization, nominating group, observer or neither.

The same receipt should disclose appointment authority, the member-participant distinction, internal thresholds, minority and escalation rules, and the treatment each institution must give the final deliverable. The Board row should specify liaison status, consideration, any rejection dialogue, approval and implementation role. Amendments and withdrawals should create new versions rather than silently altering the source of authority.

Broad participation can improve the evidence before a Structural Review. It cannot fill an empty adoption cell. The durable safeguard is modest: let the framework guide the questions, and let a versioned charter receipt show the answers.

Sources