April 2024 - IFR2-team - lists.icann.org

IFR2 Team meeting | 14 May at 11:00 UTC
by Brenda Brewer April 30, 2024

April 30, 2024

Dear IFR2 members, Please join IFR2 Team Meeting #12<https://community.icann.org/x/HAByEw> on 14 May at 11:00 UTC. Additional time zone support here<https://www.timeanddate.com/worldclock/fixedtime.html?msg=IFR2+Team+Meeting…>. Invites are sent and .ics is attached for your convenience. Please let me know if you are unable to attend. Thank you! Best, Brenda Join Zoom Meeting: https://icann.zoom.us/j/92773024849?pwd=TkJDZnZQMndWM1RjMks2OElhdUI1QT09 [icann.zoom.us]<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!4G…> Meeting ID (phone only): 927 7302 4849 Passcode: (phone only) 3229647277

1 0

Re: [IFR2-team] [Ext] RE: IFR2 Team meeting | 30 April at 18:00 UTC
by Brenda Brewer April 30, 2024

April 30, 2024

Thank you for letting us know, Edowaye. Best, Brenda From: Edowaye Makanjuola <emakanjuola(a)ncc.gov.ng> Date: Tuesday, April 30, 2024 at 11:06 AM To: Brenda Brewer <brenda.brewer(a)icann.org>, IFR2-team <ifr2-team(a)icann.org> Subject: [Ext] RE: IFR2 Team meeting | 30 April at 18:00 UTC Dear Brenda, I'm sorry, I won't be able to attend the meeting. BR Edowaye Makanjuola(GAC) From: IFR2-team <ifr2-team-bounces(a)icann.org> On Behalf Of Brenda Brewer Sent: Tuesday, 16 April 2024 13:47 To: IFR2-team <ifr2-team(a)icann.org> Subject: [IFR2-team] IFR2 Team meeting | 30 April at 18:00 UTC Dear IFR2 members, Please join IFR2 Team Meeting #11<https://community.icann.org/x/MgCSEg> on 30 April at 18:00 UTC. Additional time zone support here [timeanddate.com]<https://urldefense.com/v3/__https:/www.timeanddate.com/worldclock/fixedtime…>. Invites are sent and .ics is attached for your convenience. Please let me know if you are unable to attend. Thank you! Best, Brenda Join Zoom Meeting: https://icann.zoom.us/j/92773024849?pwd=TkJDZnZQMndWM1RjMks2OElhdUI1QT09 [icann.zoom.us]<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!4G…> Meeting ID (phone only): 927 7302 4849 Passcode: (phone only) 3229647277

1 0

IFR2 Team meeting | 30 April at 18:00 UTC
by Brenda Brewer April 30, 2024

April 30, 2024

Dear IFR2 members, Please join IFR2 Team Meeting #11<https://community.icann.org/x/MgCSEg> on 30 April at 18:00 UTC. Additional time zone support here<https://www.timeanddate.com/worldclock/fixedtime.html?msg=IFR2+Team+Meeting…>. Invites are sent and .ics is attached for your convenience. Please let me know if you are unable to attend. Thank you! Best, Brenda Join Zoom Meeting: https://icann.zoom.us/j/92773024849?pwd=TkJDZnZQMndWM1RjMks2OElhdUI1QT09 [icann.zoom.us]<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!4G…> Meeting ID (phone only): 927 7302 4849 Passcode: (phone only) 3229647277

2 1

REMINDER: IFR2 Team meeting | 30 April at 18:00 UTC
by Brenda Brewer April 30, 2024

April 30, 2024

Please join IFR2 Team Meeting #11<https://community.icann.org/x/MgCSEg> on 30 April 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

2 2

Agenda: IFR2 meeting 30 April 2024 @ 18:00 UTC
by Jennifer Bryce April 24, 2024

April 24, 2024

Dear IFR2 team, Included and attached is the agenda for the next IFR2 team meeting scheduled for 30 April. Second IANA Naming Function Review (IFR2) Meeting 11 30 April 2024 | 18:00 – 19:00 UTC Agenda 1. Welcome, Roll Call, SOI updates 1. 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 10-01 16 April 2024 Leadership to discuss and decide on next steps in terms of group assignments for future meetings. Idea of parallel work will be revisited after today’s exercise. * To be discussed as part of agenda item 4 during the meeting today (30 April). 10-02 16 April 2024 ICANN support team to share with IFR2 review team Google docs so that the review team can finish Statement of Work (SoW) review for homework. The review team to input comments/questions in the shared Google docs. * Links shared with Groups A and B – homework output to be discussed as agenda item 3 during the meeting today (30 April). 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. * On hold for future consideration, once the IFR2 gets to a place in its work where it feels it can phrase the question most meaningfully. 1. Discuss findings from the homework exercise (homework exercise due 30 April - read the Statement of Work - work in breakout groups to review with the following questions in mind): * Are there any deficiencies (anything missing) in the text? * Does anything require clarification? * Is the text/content still necessary? * Is there any additional information or data needed to make an assessment about this text? i. Group A workbook: https://docs.google.com/spreadsheets/d/13-bJJ1vdg4NCujHCnRo40T29KnvVIQbwm0u… ii. Group B workbook: https://docs.google.com/spreadsheets/d/13-bJJ1vdg4NCujHCnRo40T29KnvVIQbwm0u… 1. Next steps: * Temperature check regarding the parallel working approach trialled over the past weeks. * Determine how the group prefers to continue with the next proposed assignment: i. Continue review of the IANA Naming Function, focusing on Article IV Sections 4.2 and 4.3. 1. ICANN80 Kigali – Option to request a room for a meeting in person (75-90min sessions). Team members to indicate if they will be traveling to Kigali. 1. AOB, close

1 0

IFR2 Meeting 10 Notes
by Reda Josifi April 17, 2024

April 17, 2024

Dear IFR2 team members, Please find attached the notes from the IFR2 meeting held on Tuesday, 16 April at 11:00 UTC. The notes are also posted to the meeting record on the wiki and are linked here<https://community.icann.org/pages/viewpage.action?pageId=311558191>. The recording can be directly accessed here.<https://icann.zoom.us/rec/play/AKOB9GWw80ixagd1QyhfclygY2hpqU_hmraH_yo7Pdud…> 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

REMINDER: IFR2 Team meeting | 16 April at 11:00 UTC
by Brenda Brewer April 16, 2024

April 16, 2024

Please join IFR2 Team Meeting #10<https://community.icann.org/x/LwCSEg> on 16 April at 11: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

2 1

IFR2 Team meeting | 14 May at 11:00 UTC
by Brenda Brewer April 16, 2024

April 16, 2024

Please join IFR2 Team Meeting #12<https://community.icann.org/x/HAByEw> on 14 May at 11: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

Update from ICANN on definition section of the IANA Naming Functions Contract
by Marilia Hirano April 16, 2024

April 16, 2024

Hello all, I had the opportunity to meet with Sam Eisner from our Legal team at ICANN and Kim Davies to address some of the questions you had that related to the definitions section of the contract. Ahead of our next call on Tuesday, please review the message Sam drafted that I believe explains a lot of the background and reasoning as to why the terms are defined the way they are. We believe that this information will allow the group to move into the next step of your review. During this phase, myself or someone from PTI/ICANN could provide more operational briefings, as it will be with the full context of each section/deliverable. From Sam Eisner, ICANN’s Deputy General Council: “Dear IFRT, We wanted to provide you some background on the genesis of the definition section within the IANA Naming Function Agreement (the “Agreement”). In many ways, the definition section is the last section drafted within the agreement. A definition section can be at the front or at the back of the agreement, and the function is to make sure that there’s a comprehensive listing of the defined terms – including acronyms and other short form references – that are used within a contract. When drafting the Agreement, the baseline was that many provisions were carried over from the IANA Functions Contract that ICANN previously maintained with the NTIA, as recommended by the Cross-Community Working Group on the IANA Stewardship naming function (CWG-Stewardship). The CWG-Stewardship was provided with external counsel from the law firm of Sidley Austin that ultimately worked with ICANN and ICANN’s outside counsel, Jones Day, to make sure the CWG-Stewardship recommendations were faithfully recorded within the Agreement. The main focus was on drafting of the actual terms of the Agreement to reflect the full intended scope of the IANA Naming Function. As we drafted the Agreement – as is typical – we would define terms along the way and make reference to short forms for frequently used terms such as gTLDs, ccTLDs, NS records, and others. We also referenced foundational documents, such as the 2005 Governmental Advisory Committee Principles and Guidelines for the Delegation and Administration of Country Code Top Level Domains (defined as “GAC 2005 ccTLD Principles”). At the end of the drafting, we then went through and pulled out all of the defined terms used within the Agreement to reflect them within the Definition section. The Definition section therefore includes defined terms that are meant to be read within the context of the Agreement and where they appear within the Agreement. For example, the Agreement includes specific definitions of the terms “Delegation”, “Transfer”, and “Revocation” that are limited to application to ccTLDs. This was intentional, as one of the important principles that emerged was that the Agreement should fully embrace the terms of the Framework of Interpretation, which were fairly new at the time. If you read the defined terms within the context of where they appear in the Agreement, there is very intentional usage of those defined terms only in reference to ccTLD-related obligations. The definitions are NOT trying to define the full scope of how each term is used within the IANA Naming Function. For example, at Annex A, Section 1.d, you’ll see that the defined terms are used to define the scope of PTI’s work for ccTLDs, and then uses the more general term “delegation” later in that same section for gTLDs. The difference is in the use of the defined (i.e., capitalized) term as opposed to the more general (i.e., not capitalized) term. In populating the Definition section, the drafters also made choices to maintain the cohesiveness of the document and reduce potential for inconsistencies. When populating Definitions, if the definition of the term had already been spelled out within the text of the Agreement, we made reference to that section of the Agreement as opposed to duplicating the definition or moving the definition only to the Definition section. Particularly due to the length of the Agreement, we did not want to force readers to have to refer back to the beginning in all instances to understand what a defined term might mean. In addition, where the term is defined outside of the Agreement, we included reference to the source document for that definition, again as a way to make sure that the IANA Naming Function Agreement is always understood within the context of the source documentation, such as the PTI Bylaws, and we are not causing any unintended inconsistency. Please let us know if further discussion or information might be helpful.” Thanks everyone, Marilia Hirano Director, IANA Strategic Programs and PTI Liaison to the IFR2 team Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org> Email: marilia.hirano(a)iana.org<mailto:marilia.hirano@iana.org> Phone: +1 (310) 804-3549

2 1

REMINDER: IFR2 Team meeting | 16 April at 11:00 UTC
by Brenda Brewer April 16, 2024

April 16, 2024

Dear IFR2 members, Please join IFR2 Team Meeting #10<https://community.icann.org/x/LwCSEg> on 16 April at 11:00 UTC. Invites are sent and .ics is attached for your convenience. Please let me know if you are unable to attend. Thank you! Best, Brenda Join Zoom Meeting: https://icann.zoom.us/j/92773024849?pwd=TkJDZnZQMndWM1RjMks2OElhdUI1QT09 [icann.zoom.us]<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!4G…> Meeting ID (phone only): 927 7302 4849 Passcode: (phone only) 3229647277

1 0