Summary

  • On 5 October, the Reviews CCG co-chairs asked to deliver the Final Report at ICANN88 and to keep the group empanelled while it is considered.
  • ICANN’s Board Chair previewed discussion of the group’s remaining timeline, but neither the preview nor the request records an approval.

A report deadline and the life of the group that wrote the report are different clocks. The Reviews CCG co-chairs put both on the table in a 5 October work-plan update to the ICANN Supporting Organization and Advisory Committee nominating groups. They asked to move delivery of the Final Report to ICANN88. Separately, they asked that the group remain empanelled during consideration of that report so members could answer questions or clarify points.

The request follows a materially changed draft process. ICANN’s first Review of Reviews public-comment proceeding closed on 4 August. Its outcome page records 23 submissions: 21 in the proceeding and two late submissions from the Noncommercial Stakeholder Group and Public Internet Registry. The co-chairs say the comments produced substantive changes. They also describe parallel work on stress-testing the proposed framework, refining definitions, and developing procedures and safeguards.

The co-chairs planned to use ICANN87 in Bali to explain and test the revised approach before finalizing a Second Draft Report. They anticipated publishing that draft for another public-comment period shortly after the meeting. The October update does not set the second comment period’s length or a precise date for the Final Report. The public-comment page still lists 25 August as the first report’s due date; the co-chairs’ later message describes the updated schedule.

The second request matters because finishing a report does not end the process of considering it. If the group is available while the report is considered, it can clarify what a recommendation means and how the revised text responds to public input. That is a continuing advisory role. The co-chairs did not ask the group to decide whether its recommendations should be adopted, and their letter does not say which body must approve the revised timetable or continued empanelment.

On 13 October, ICANN Board Chair Tripti Sinha previewed a Board workshop discussion of the CCG’s key changes, the timeline for its remaining work, and implementation considerations. The preview establishes that these topics were on the agenda. It is not a minute, resolution, or confirmation that the 5 October request was granted. The public materials reviewed for this article contain no approval of the extension.

That timetable should also be kept separate from the Bylaws pause on Specific Reviews. Article 27.6 has its own rule: the pause runs for 12 months from its effective date unless the Board accepts and directs implementation of a later community recommendation, or four of seven Supporting Organizations and Advisory Committees support a further pause. The total pause cannot exceed 24 months, and an extension requires a rationale. A request to keep the Reviews CCG working through ICANN88 does not, by itself, satisfy either condition.

The distinction is practical. One decision changes when the report is delivered; another preserves access to the group while the report is under consideration; a third would change the Bylaws timetable. Until the public record identifies the status and scope of each, a later reader cannot tell whether the group is still answering questions, whether its work plan changed, or whether a separate legal trigger was met.

Primary records: the 5 October co-chair update, the public-comment outcome, the Board Chair’s 13 October preview, the Board’s charter approval, and the approved Article 27.6 text; the Board activity register reviewed on 17 October.