February 2025 - IFR2-team - lists.icann.org

FW: REMINDER! Meeting Invitation: IFR2 Team Meeting | 25 February @ 18:00 UTC
by Brenda Brewer Feb. 25, 2025

Feb. 25, 2025

Dear IFR2 Members, Please join IFR2 Team Meeting #31<https://community.icann.org/x/D4BZGw> on 25 February at 18:00 UTC. Additional time zone support here<https://www.timeanddate.com/worldclock/fixedtime.html?msg=IFR2+Team+Meeting…>. The join details are noted below as well as attached .ics. Join Zoom Meeting: https://icann.zoom.us/j/92773024849?pwd=TkJDZnZQMndWM1RjMks2OElhdUI1QT09<https://urldefense.com/v3/__https:/icann.zoom.us/j/92773024849?pwd=TkJDZnZQ…> Meeting ID: 927 7302 4849 Passcode: 1rDw.e0TiY --- One tap mobile +19294362866,,92773024849#,,,,*3229647277# US (New York) +13017158592,,92773024849#,,,,*3229647277# US (Washington DC) --- Phone Connection Details Find your local number: https://icann.zoom.us/u/aeJngYAfC [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/aeJngYAfC__;!!PtGJab4!9a…> Meeting ID (phone only): 927 7302 4849 Passcode: (phone only) 3229647277 Please send apologies to brenda.brewer(a)icann.org<mailto:brenda.brewer@icann.org>. Thank you. Kind regards, Brenda -- Brenda Brewer Policy Operations Coordinator Internet Corporation for Assigned Names and Numbers (ICANN) From: Brenda Brewer <brenda.brewer(a)icann.org> Date: Tuesday, February 11, 2025 at 6:29 AM To: IFR2-team <ifr2-team(a)icann.org> Cc: Brenda Brewer <brenda.brewer(a)icann.org> Subject: Meeting Invitation: IFR2 Team Meeting | 25 February @ 18:00 UTC Dear IFR2 Members, Please join IFR2 Team Meeting #31<https://community.icann.org/x/D4BZGw> on 25 February at 18:00 UTC. Additional time zone support here<https://www.timeanddate.com/worldclock/fixedtime.html?msg=IFR2+Team+Meeting…>. The join details are noted below as well as attached .ics. Join Zoom Meeting: https://icann.zoom.us/j/92773024849?pwd=TkJDZnZQMndWM1RjMks2OElhdUI1QT09<https://urldefense.com/v3/__https:/icann.zoom.us/j/92773024849?pwd=TkJDZnZQ…> Meeting ID: 927 7302 4849 Passcode: 1rDw.e0TiY --- One tap mobile +19294362866,,92773024849#,,,,*3229647277# US (New York) +13017158592,,92773024849#,,,,*3229647277# US (Washington DC) --- Phone Connection Details Find your local number: https://icann.zoom.us/u/aeJngYAfC [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/aeJngYAfC__;!!PtGJab4!9a…> Meeting ID (phone only): 927 7302 4849 Passcode: (phone only) 3229647277 Please send apologies to brenda.brewer(a)icann.org<mailto:brenda.brewer@icann.org>. Thank you. Kind regards, Brenda -- Brenda Brewer Policy Operations Coordinator Internet Corporation for Assigned Names and Numbers (ICANN)

3 2

Agenda: IFR2 meeting 25 February @ 18:00 UTC
by Reda Josifi Feb. 25, 2025

Feb. 25, 2025

Dear IFR2 team, Included and attached is the agenda for the next IFR2 team meeting scheduled for 25 February @ 18:00 UTC. Second IANA Naming Function Review (IFR2) Meeting 31 25 February 2025 | 18:00 UTC Agenda Homework Due 25 February * Read Recommendations from IFR1<Recommendations%20from%20IFR1%20%20•%09Leadership%20has%20reviewed%20and%20does%20not%20see%20any%20issues%20with%20recommendations%20from%20IFR1.%20Frequency%20of%20reviews%20is%20captured%20in%20our%20recommendations%20but%20otherwise%20everything%20has%20been%20completed%20and%20does%20not%20have%20an%20impact%20on%20the%20SLAs.> * Please note that Leadership has reviewed the IFR1 recommendations and has not found any issues. * The frequency of reviews is captured in our draft IFR2 report recommendations but otherwise everything has been completed and does not have an impact on the SLAs. * Read DRAFT IFR2 Report<https://docs.google.com/document/d/1OhYAxMXOrHRJq4vQ0aOROjt5skUpYqcF/edit> * Please note that Article VIII, Section 8.1 incidental finding on the Ombudsman has been added as Incidental Finding #4 on page 6. * Goal is to have draft report up for public comment prior to ICANN82 (7 March 2025) * Think about report edits/final tasks that you would like to see happen prior to publishing the report for public review. * Review and be prepared to discuss the priority levels and suggested timelines for Recommendations 1-4 on pages 3-5. 1) Welcome, Roll Call, SOI updates 2) Action Items (all action items tracked in the Google sheet linked here<https://docs.google.com/spreadsheets/d/1DFJ30deCZoV7ictJ-sNw3LXzBhp8TMkp/ed…>) Reference Date Action item Status 26-01 26 November 2024 Sam Eisner to provide IFR2 group more information on the amendment paths/recommendations and the level of detail needed for recommendations. Sam will follow up with more information in the coming weeks. 26-03 26 November 2024 Peter to draft a description of what the perceived problem the IFR2 review team is facing re: Article 8 and share it with the IFR2 team. Peter shared his thoughts via email on 19 February. 07-01 4 March 2024 As follow up from the 6 March CSC briefing: Co-chairs to consider formally asking the CSC liaison if there is anything they would like to bring to the attention of the IFR2. Open task in case the CSC brings anything else to the attention of the IFR2 group. 3) Recommendations from IFR1<https://community.icann.org/display/ifr/Background+Resources%3A+Quick+Links…> * Discuss any questions or concerns that came up during the team’s review of the IFR1 Recommendations. Leadership has reviewed and does not see any issues with recommendations from IFR1. 4) Draft IFR2 Report<https://docs.google.com/document/d/1OhYAxMXOrHRJq4vQ0aOROjt5skUpYqcF/edit>: * Reference: IFR1 Report<https://community.icann.org/pages/viewpage.action?pageId=120819021&preview=…> * Goal is to have draft report up for public comment prior to ICANN82 (7 March 2025). Discuss and agree upon final report edits or tasks that you would like to see happen prior to publishing the report for public review. * Discuss the priority levels and suggested timelines for Recommendations 1-4 on pages 3-5. 5)Next Meeting: * Monday, 10 March at 22:00 UTC 6) AOB, close

4 3

Follow Up: Action Item #26-01
by Reda Josifi Feb. 25, 2025

Feb. 25, 2025

Dear IFR2 Team, As a follow up to Action Item #26-01<https://docs.google.com/spreadsheets/d/1DFJ30deCZoV7ictJ-sNw3LXzBhp8TMkp/ed…> (26 November 2024 meeting), please see below for Sam Eisner’s guidance on Peter’s question regarding more information on amendment paths and recommendations. The meeting recording is linked here<https://icann.zoom.us/rec/play/pDCTeTfY5A5qP7rqWwcDp_Ylcjb7gsVzh3j4zeSyQc1M…> and if you need to reference the recording, the discussion took place at around 21 minutes and 13 seconds. There are two ways to achieve amendment to the IANA Naming Function Agreement. 1. The IFR’s ability to require a unilateral amendment if all procedural requirements of the IFR are met in reaching such a recommendation (and the similar rights of special IFRs or separation cross community working groups); or 2. The ability for ICANN and PTI to mutually agree to an amendment to the agreement, which also requires ICANN’s adherence to the procedures set out at Section 16.3 of the Bylaws in the event that any term as defined as a “Material Term” is impacted. Modification to any of those “Material Terms” require ICANN to present the proposals to both the ccNSO and GNSO Councils for an opportunity to reject such changes. In the event the IFRT has amendments to the IANA Naming Function Contract that they do not believe rise to the level of requiring full procedural power of the IFRT to mandate, but are instead recommendations of amendments that they urge ICANN and PTI to jointly explore, the IFR could issue a recommendation - noting that it is not invoking the process of Section 18.6 of the ICANN Bylaws or intending to cause an amendment under Section 7.3(c) of the IANA Naming Function Contract - but instead is solely recommending the exploration of such an amendment if mutual agreement on terms can be met. The IFRT could further note that it intends these as general recommendations Under Section 18.5 of the ICANN Bylaws for improvement of the IANA Naming Function Contract. Please let me know if you have further questions. Thank you, Reda

1 0

FW: REMINDER! IFR2 Team Meeting | 25 February @ 18:00 UTC
by Brenda Brewer Feb. 24, 2025

Feb. 24, 2025

Please join IFR2 Team Meeting #31<https://community.icann.org/x/D4BZGw> on 25 February at 18:00 UTC. Additional time zone support here<https://www.timeanddate.com/worldclock/fixedtime.html?msg=IFR2+Team+Meeting…>. Join Zoom Meeting: https://icann.zoom.us/j/92773024849?pwd=TkJDZnZQMndWM1RjMks2OElhdUI1QT09 Meeting ID: 927 7302 4849 Passcode: 1rDw.e0TiY --- One tap mobile +19294362866,,92773024849#,,,,*3229647277# US (New York) +13017158592,,92773024849#,,,,*3229647277# US (Washington DC) --- Phone Connection Details Find your local number: https://icann.zoom.us/u/aeJngYAfC Meeting ID (phone only): 927 7302 4849 Passcode: (phone only) 3229647277

1 0

FWD [IFR2/CSC research on Naming Function Contract Article VIII]
by Peter Koch Feb. 19, 2025

Feb. 19, 2025

Dear IFR2 team, for the sole purpose of documentation here is the the initial problem statement for Rick and Jonathan who had volunteered to research the origins of the special role of the (then) Ombudsman in the IANA Functions Contract as developed during the IANA Stewardship Transition. Meanwhile we have discussed the in depth results as reflected in the Draft Report. It just occured that this piece had not been shared with the whole team. Best regards Peter ----- Forwarded message from Peter Koch <pk(a)denic.de> ----- From: Peter Koch To: Ashley Heineman, Rick Wilhelm, Jonathan Robinson Cc: Brenda Brewer, Reda Josifi, Elizabeth Garber Subject: IFR2/CSC research on Naming Function Contract Article VIII Date: Thu, 2 Jan 2025 11:22:33 +0100 Dear all, this is my attempt to a summary for the 'research' on the role of the Ombudsman in the Naming Functions Contract. During the review of the IANA Naming Functions Contract as well as in communication with the Customer Standing Committee (CSC), there were questions raised about section VIII (escalation mechanisms) of the contract, in particular: ARTICLE VIII: ESCALATION MECHANISMS Section 8.1 Complaint Resolution Process. (a) If Contractor receives a customer service complaint from a customer (a "Complaint"), Contractor will review the Complaint and attempt to resolve it to the reasonable satisfaction of the person or entity who brought the Complaint (the "Complainant") as soon as reasonably practicable. If the Complaint is not so resolved, the Complainant may escalate the matter in writing to Contractor's management team, in which case Contractor shall notify the CSC. If the Complaint is still not resolved, the Complainant or the President of Contractor may escalate the matter in writing to ICANN's Ombudsman. (b) If (i) a Complainant is a customer and (ii) after completing the escalation process provided for in Section 8.1(a), the Complaint is still not resolved, then (A) the CSC may conduct a review to determine whether the Complaint is subject of a persistent performance issue of Contractor or an indication of a systemic problem with Contractor's performance of the IANA Naming Function pursuant to the terms of this Contract (a "Performance Issue") and (B) the Complainant may (x) request mediation, which shall be conducted in a manner consistent with the terms and process set forth below in Section 8.1(c) and (y) if the issue is not resolved following such mediation and the Complaint meets the requirements of the Independent Review Process, initiate an Independent Review Process (as defined in the ICANN's Bylaws). If the CSC determines that a Performance Issue exists, the CSC may seek remediation of the Performance Issue through the IANA Problem Resolution Process described in Section 8.2. (c) Customer Mediation Process. (i) If a Complainant is a customer of Contractor, after completing the escalation process provided for in Section 8.1(a), the customer may initiate mediation by delivering a written notice to the President of Contractor and the Secretary of ICANN. (ii) There shall be a single mediator who shall be selected by the agreement of the customer and ICANN. ICANN shall propose a slate of at least five potential mediators, and the customer shall select a mediator from the slate or request a new slate until a mutually agreed mediator is selected. The customer may recommend potential mediators for inclusion on the slates selected by ICANN. ICANN shall not unreasonably decline to include mediators recommended by the customer on proposed slates and the customer shall not unreasonably withhold consent to the selection of a mediator on slates proposed by ICANN. (iii) The mediator shall be a licensed attorney with general knowledge of contract law and general knowledge of the DNS and ICANN. The mediator may not have any ongoing business relationship with ICANN, Contractor or the customer. The mediator must confirm in writing that he or she is not, directly or indirectly, and will not become during the term of the mediation, an employee, partner, executive officer, director, consultant or advisor of ICANN, Contractor or the customer. (iv) The mediator shall conduct the mediation in accordance with this Section 8.1(c), the laws of California and the rules and procedures of a well-respected international dispute resolution provider. (v) The mediation will be conducted in the English language and will occur in Los Angeles County, California, unless another location is mutually agreed between ICANN, Contractor and the customer. (vi) ICANN, Contractor and the customer shall discuss the dispute in good faith and attempt, with the mediator's assistance, to reach an amicable resolution of the dispute. (vii) ICANN shall bear all costs of the mediator. (viii) If ICANN, Contractor and the customer have engaged in good faith participation in the mediation but have not resolved the dispute for any reason, ICANN, Contractor and the customer may terminate the mediation at any time by declaring an impasse. 13 (ix) If a resolution to the dispute is reached by ICANN, Contractor and the customer, ICANN, Contractor and the customer shall document such resolution. Section 8.2 IANA Problem Resolution Process. Following the Effective Date, Contractor shall work cooperatively with the CSC to develop "Remedial Action Procedures" for the purpose of addressing Performance Issues. If the CSC determines that a Performance Issue exists, the CSC may seek resolution of the Performance Issue with Contractor, in which case Contractor shall comply with such Remedial Action Procedures if and to the extent the CSC also complies with such procedures. Section 8.3 Notice and Mitigation Plan. (a) Contractor shall promptly inform ICANN of any issue or dispute arising from its performance of the requirements and services contemplated by this Contract prior to the Complaint being escalated pursuant to Section 8.1(a), and shall agree with ICANN on a plan to resolve the Complaint. (b) If, for any reason, Contractor fails to meet any of the requirements of this Contract, Contractor shall (i) conduct an analysis of its operations to determine the root cause of such failure, (ii) develop a mitigation plan to avoid the root cause of such failure from occurring in the future, and (iii) deliver the report to ICANN upon its completion. Contractor shall modify and update any mitigation plan as directed by ICANN. The questions discussed with the CSC: 1) Is the process described in 8.1(a) optional? While we discussed the semantics of the 'may' in 8.1(a), it occurs to me that the steps are of course optional (as in: no obligation to esacalate), but going through it is a precondition for the next steps described in 8.1(b). 2) The role of the Ombudsman We observed that the role of the Ombudsman beyond Section 4.2 and Article 5 had never occured (at least had not occured with particular reference to section 8.1(a)). We also observed that an escalation to the Ombudsman could be started by both the Complainant and the Contractor. We understood that this was a result of the Stewardship Transition discussion but we have been unable to research the exact details of that reasoning. This is what should be found out by the volunteer small team. The reason for addressing this within the IFR is that this is the only way (for the CSC, and maybe others) to initiate a change, if so desired. Best regards Peter ----- End forwarded message ----- -- DENIC eG, Theodor-Stern-Kai 1, 60596 Frankfurt am Main, GERMANY E-Mail: pk(a)denic.de, Fon: +49 69 27235-165, https://www.denic.de Angaben nach § 25a Absatz 1 GenG: DENIC eG (Sitz: Frankfurt am Main) Vorstand: Thomas Keller, Martin Küchenthal, Andreas Musielak, Sebastian Röthler Vorsitzender des Aufsichtsrats: Daniel Rink Eingetragen unter Nr. 770 im Genossenschaftsregister, Amtsgericht Frankfurt am Main Allgemeiner Hinweis zur Erfüllung unserer Informationspflichten gemäß Art. 13, Art. 14 DS-GVO: Informationen zur Verarbeitung personenbezogener Daten durch DENIC finden Sie unter https://www.denic.de/datenverarbeitung-allgemein/

1 0

IFR2 Meeting 30 Notes
by Reda Josifi Feb. 18, 2025

Feb. 18, 2025

Dear IFR2 team members, Please find attached the notes from the IFR2 meeting held on Tuesday, 11 February at 18:00 UTC. The notes are also posted to the meeting record on the wiki, linked here<https://community.icann.org/pages/viewpage.action?pageId=458850317>. The recording can be directly accessed here<https://icann.zoom.us/rec/play/G_btRS6CDoxH5vkGZlsvbiBqs9S_VhQHtzKhQMJfaMDz…>. Thank you, Reda -- Reda Josifi Project Manager, Office of the Chief Technology Officer (OCTO) Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: 202-709-2427 www.icann.org<http://www.icann.org>

1 0

Meeting Invitation: IFR2 Team Meeting | 25 February @ 18:00 UTC
by Brenda Brewer Feb. 11, 2025

Feb. 11, 2025

Dear IFR2 Members, Please join IFR2 Team Meeting #31<https://community.icann.org/x/D4BZGw> on 25 February at 18:00 UTC. Additional time zone support here<https://www.timeanddate.com/worldclock/fixedtime.html?msg=IFR2+Team+Meeting…>. The join details are noted below as well as attached .ics. Join Zoom Meeting: https://icann.zoom.us/j/92773024849?pwd=TkJDZnZQMndWM1RjMks2OElhdUI1QT09<https://urldefense.com/v3/__https:/icann.zoom.us/j/92773024849?pwd=TkJDZnZQ…> Meeting ID: 927 7302 4849 Passcode: 1rDw.e0TiY --- One tap mobile +19294362866,,92773024849#,,,,*3229647277# US (New York) +13017158592,,92773024849#,,,,*3229647277# US (Washington DC) --- Phone Connection Details Find your local number: https://icann.zoom.us/u/aeJngYAfC [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/aeJngYAfC__;!!PtGJab4!9a…> Meeting ID (phone only): 927 7302 4849 Passcode: (phone only) 3229647277 Please send apologies to brenda.brewer(a)icann.org<mailto:brenda.brewer@icann.org>. Thank you. Kind regards, Brenda -- Brenda Brewer Policy Operations Coordinator Internet Corporation for Assigned Names and Numbers (ICANN)

1 0

SAVE the DATE PLACEHOLDER: IFR2 Team Work Session at ICANN82
by Brenda Brewer Feb. 11, 2025

Feb. 11, 2025

Second IANA Naming Function Review (IFR2) Team Work Session Monday, March 10, 2025 3:00 PM - 4:00 PM (PT) Details to follow when ICANN82 schedule is published here<https://icann82.sched.com/>.

1 0

IFR2 Team Meeting | 25 February @ 18:00 UTC
by Brenda Brewer Feb. 11, 2025

Feb. 11, 2025

Please join IFR2 Team Meeting #31<https://community.icann.org/x/D4BZGw> on 25 February at 18:00 UTC. Additional time zone support here<https://www.timeanddate.com/worldclock/fixedtime.html?msg=IFR2+Team+Meeting…>. Join Zoom Meeting: https://icann.zoom.us/j/92773024849?pwd=TkJDZnZQMndWM1RjMks2OElhdUI1QT09 Meeting ID: 927 7302 4849 Passcode: 1rDw.e0TiY --- One tap mobile +19294362866,,92773024849#,,,,*3229647277# US (New York) +13017158592,,92773024849#,,,,*3229647277# US (Washington DC) --- Phone Connection Details Find your local number: https://icann.zoom.us/u/aeJngYAfC Meeting ID (phone only): 927 7302 4849 Passcode: (phone only) 3229647277

1 0

Re: REMINDER! Meeting Invite: IFR2 Team Meeting | 11 February @ 11:00 UTC
by Brenda Brewer Feb. 11, 2025

Feb. 11, 2025

Dear IFR2 Members, Please join IFR2 Team Meeting #30<https://community.icann.org/x/DYBZGw> on 11 February at 11:00 UTC. Additional time zone support here [timeanddate.com]<https://urldefense.com/v3/__https:/www.timeanddate.com/worldclock/fixedtime…>. The join details are noted below as well as attached .ics. Join Zoom Meeting: https://icann.zoom.us/j/92773024849?pwd=TkJDZnZQMndWM1RjMks2OElhdUI1QT09<https://urldefense.com/v3/__https:/icann.zoom.us/j/92773024849?pwd=TkJDZnZQ…> Meeting ID: 927 7302 4849 Passcode: 1rDw.e0TiY --- One tap mobile +19294362866,,92773024849#,,,,*3229647277# US (New York) +13017158592,,92773024849#,,,,*3229647277# US (Washington DC) --- Phone Connection Details Find your local number: https://icann.zoom.us/u/aeJngYAfC [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/aeJngYAfC__;!!PtGJab4!9a…> Meeting ID (phone only): 927 7302 4849 Passcode: (phone only) 3229647277 Please send apologies to brenda.brewer(a)icann.org<mailto:brenda.brewer@icann.org>. Thank you. Kind regards, Brenda -- Brenda Brewer Policy Operations Coordinator Internet Corporation for Assigned Names and Numbers (ICANN) From: IFR2-team <ifr2-team(a)icann.org> Reply-To: Brenda Brewer <brenda.brewer(a)icann.org> Date: Friday, January 24, 2025 at 11:03 AM To: IFR2-team <ifr2-team(a)icann.org> Subject: [IFR2-team] Meeting Invite: IFR2 Team Meeting | 11 February @ 11:00 UTC Dear IFR2 Members, Please join IFR2 Team Meeting #30<https://community.icann.org/x/DYBZGw> on 11 February at 11:00 UTC. Additional time zone support here [timeanddate.com]<https://urldefense.com/v3/__https:/www.timeanddate.com/worldclock/fixedtime…>. The join details are noted below as well as attached .ics. Join Zoom Meeting: https://icann.zoom.us/j/92773024849?pwd=TkJDZnZQMndWM1RjMks2OElhdUI1QT09<https://urldefense.com/v3/__https:/icann.zoom.us/j/92773024849?pwd=TkJDZnZQ…> Meeting ID: 927 7302 4849 Passcode: 1rDw.e0TiY --- One tap mobile +19294362866,,92773024849#,,,,*3229647277# US (New York) +13017158592,,92773024849#,,,,*3229647277# US (Washington DC) --- Phone Connection Details Find your local number: https://icann.zoom.us/u/aeJngYAfC [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/aeJngYAfC__;!!PtGJab4!9a…> Meeting ID (phone only): 927 7302 4849 Passcode: (phone only) 3229647277 Please send apologies to brenda.brewer(a)icann.org<mailto:brenda.brewer@icann.org>. Thank you. Kind regards, Brenda -- Brenda Brewer Policy Operations Coordinator Internet Corporation for Assigned Names and Numbers (ICANN)

3 2