[Working Group] IFR2 Report: FINAL Call for Comments

[Rafik Dammak]

hi everyone,

I am sharing here  the communication related to the final report for IANA
Functions Review 2 (IFR2). This is the last stage before completing work
since the working group reviewed and considered the public comments
submitted regarding the initial report, including comment from NCSG.
NCSG comments supported the recommendations in general from IFR2 (the main
comment is included in the annex for reference). I understand there is no
concern from our side regarding the recommendations and there are no
changes that warrant our attention.

You can find attached the clean and redline versions of the report. Please
review and let me know if you have any  comment or edit that I should raise
by 7th July.

Best regards,

Rafik


---------- Forwarded message ---------

Dear IFR2 Team,



*Final call for comments on the IFR2 Final Report.*



*Due date: 7 July*



Attached for your review is the final IFR2 report which incorporates the
changes discussed on our most recent call. Three versions of the
report are attached
so you can clearly see updates made to the draft report that was published
for public comment.

   - *Redlines Version*- this highlights all the changes we have made since
   the public comment period. It may be difficult to read.
   - *Comments Only Version*- draws the team's attention to changes that
   have not yet been discussed (e.g., removing glossary, adding the
   recommendation table.
   - *Clean Version *- all changes have been accepted; there are no
   comments.

Kindly note that the most significant changes to the report are the
inclusion of the final disposition of the comments table, a recommendation
summary table and the removal of the glossary.



Please review and share any final comments to this email list by 7 July
2025. *After that date, if no significant comments or suggested edits are
received the report will be considered adopted with full consensus of the
review team. *



On behalf of ICANN staff, I’d like to thank you for your contributions to
this review effort and congratulate the team on getting the final report to
this milestone.



*Next steps:*

For your information, the next steps are as follows:



   - *Step 1:* IFR2 final report adopted by the IFR2.



   - *Step 2: *GNSO and ccNSO Councils vote to approve IFR2 recommendations
   1 & 2 by supermajority (as required for any recommendations to amend the
   IANA Naming Functions Contract, per ICANN Bylaws Section 18.6)



   - *Step 3: *Upon completion of Step 2, IFR2 can formally submit the
   Final Report to the ICANN Board. ICANN Board has 45 days from completion of
   Step 2 to act on the recommendations (per Bylaws Section 18.6). *At this
   time, the review team will formally be considered complete, and the review
   team will disband.*



   - *Step 4:* Board action on the IFR2 recommendations.



Please let us know if you have any questions.



Thank you,

Reda
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-discuss/attachments/20250627/709bf0c7/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: DRAFT Second IANA Naming Function Review - Final Report - v1.5 clean.pdf
Type: application/pdf
Size: 1116908 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-discuss/attachments/20250627/709bf0c7/attachment.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: DRAFT Second IANA Naming Function Review - Final Report - v1.5 comments only.pdf
Type: application/pdf
Size: 1145027 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-discuss/attachments/20250627/709bf0c7/attachment-0001.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: DRAFT Second IANA Naming Function Review - Final Report - v1.5 redlines.pdf
Type: application/pdf
Size: 1233917 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-discuss/attachments/20250627/709bf0c7/attachment-0002.pdf>