1 of 9

At-Large ICANN80 Talking Points

At-Large Welcome Session at ICANN80

10-13 June 2024

2 of 9

Agenda

Policy Talking Points

EPDP on IDNs
IANA Naming Function Review (IFR2)
New gTLD Next Round
Registration Data Request Service
SPIRT Charter Drafting Team
Transfer Policy Review

Resources

BACKGROUND

Overview

On 26 January 2020, the ICANN Board passed a resolution to defer contractual compliance enforcement of the gaining registrar's requirement to obtain express authorization of an inter-registrar transfer from the Transfer Contact via a Standardized Form of Authorization (FOA). ICANN Contractual Compliance will defer enforcement of Section I(A)(2.1) of the Transfer Policy until the matter is settled in the GNSO Council's Transfer Policy Review.

On 18 February 2021, the GNSO Council initiated the two-phase Transfer Policy Review PDP. The purpose of the PDP is to determine if changes to the policy are needed to improve the ease, security, and efficacy of Inter-Registrar and Inter-Registrant Transfers. As recommended in the Final Issue Report, the PDP will address the following topics in sequence:

The Gaining and Losing Forms of Authorization, AuthInfo Codes [also known as the Transfer Authorization Code (TAC)], and NACKing transfers (Phase 1A).
The change of registrant (Phase 1B).
The transfer emergency action contact and reversing inter-registrar transfers, Transfer Dispute Resolution Policy, and ICANN-approved transfers (Phase 2).

The GNSO Council adopted the PDP working group charter on 24 March 2021. According to PDP 3.0, the working group adopted a representative model with set criteria and expectations for their members and chairs. The working group met for the first time on 14 May 2021.

Why is Transfer Policy important to At-Large and End Users?

Emphasis on the Registrant perspective. The processes and requirements for transferring a domain name between one registrar to another affect registrants and End Users.
Registrars have obligations to registrants. Processes and requirements provided by Registrars to Registrants (End Users) to access the Transfer Authorization Code (TAC) must be simple, consistent, and secure.

Registrants should easily be able to transfer their domain to a new registrar or a different registrant.
Processes should be secure and protect against unauthorized activity related to the registrant’s account.

3 of 9

EPDP on Internationalized Domain Names

Leads: Satish Babu, Hadia Elminiawi, and Abdulkarim Oloyede

Talking Points:

At-Large supports the application of the "Same Entity" principle at the second-level
This mitigates user confusability, improves user experiences, simplifies domain name lifecycle events, and reduces cost for registrants
Contracted parties and ICANN Org need to coordinate to ensure a good user experience and avoid potential security risks
At-Large supports using a machine-readable, standards-based approach to format IDN Tables
Existing protocols must enable end-users to determine the entire variant domain name set

ICANN80 Sessions:

GNSO: IDN EPDP Working Session on Monday, 10 June at 11:45 - 13:00 (UTC)

BACKGROUND

Overview

On 26 January 2020, the ICANN Board passed a resolution to defer contractual compliance enforcement of the gaining registrar's requirement to obtain express authorization of an inter-registrar transfer from the Transfer Contact via a Standardized Form of Authorization (FOA). ICANN Contractual Compliance will defer enforcement of Section I(A)(2.1) of the Transfer Policy until the matter is settled in the GNSO Council's Transfer Policy Review.

On 18 February 2021, the GNSO Council initiated the two-phase Transfer Policy Review PDP. The purpose of the PDP is to determine if changes to the policy are needed to improve the ease, security, and efficacy of Inter-Registrar and Inter-Registrant Transfers. As recommended in the Final Issue Report, the PDP will address the following topics in sequence:

The Gaining and Losing Forms of Authorization, AuthInfo Codes [also known as the Transfer Authorization Code (TAC)], and NACKing transfers (Phase 1A).
The change of registrant (Phase 1B).
The transfer emergency action contact and reversing inter-registrar transfers, Transfer Dispute Resolution Policy, and ICANN-approved transfers (Phase 2).

The GNSO Council adopted the PDP working group charter on 24 March 2021. According to PDP 3.0, the working group adopted a representative model with set criteria and expectations for their members and chairs. The working group met for the first time on 14 May 2021.

Why is Transfer Policy important to At-Large and End Users?

Emphasis on the Registrant perspective. The processes and requirements for transferring a domain name between one registrar to another affect registrants and End Users.
Registrars have obligations to registrants. Processes and requirements provided by Registrars to Registrants (End Users) to access the Transfer Authorization Code (TAC) must be simple, consistent, and secure.

Registrants should easily be able to transfer their domain to a new registrar or a different registrant.
Processes should be secure and protect against unauthorized activity related to the registrant’s account.

4 of 9

IANA Naming Function Review (IFR2)

Leads: Carlton Samuels

Talking Points:

At-Large supports the continued review of the IANA Naming Function Review.
IFR2 is an accountability mechanism created as part of the IANA stewardship transition.
IFR2 has met to discuss work plans, terms of reference, and the IANA Naming Function Contract.

ICANN80 Sessions:

Second IANA Naming Function Review (IFR2) Team Work Session on Tuesday, June 11 at 07:00 - 08:15 (UTC)

BACKGROUND

Overview

On 26 January 2020, the ICANN Board passed a resolution to defer contractual compliance enforcement of the gaining registrar's requirement to obtain express authorization of an inter-registrar transfer from the Transfer Contact via a Standardized Form of Authorization (FOA). ICANN Contractual Compliance will defer enforcement of Section I(A)(2.1) of the Transfer Policy until the matter is settled in the GNSO Council's Transfer Policy Review.

On 18 February 2021, the GNSO Council initiated the two-phase Transfer Policy Review PDP. The purpose of the PDP is to determine if changes to the policy are needed to improve the ease, security, and efficacy of Inter-Registrar and Inter-Registrant Transfers. As recommended in the Final Issue Report, the PDP will address the following topics in sequence:

The Gaining and Losing Forms of Authorization, AuthInfo Codes [also known as the Transfer Authorization Code (TAC)], and NACKing transfers (Phase 1A).
The change of registrant (Phase 1B).
The transfer emergency action contact and reversing inter-registrar transfers, Transfer Dispute Resolution Policy, and ICANN-approved transfers (Phase 2).

The GNSO Council adopted the PDP working group charter on 24 March 2021. According to PDP 3.0, the working group adopted a representative model with set criteria and expectations for their members and chairs. The working group met for the first time on 14 May 2021.

Why is Transfer Policy important to At-Large and End Users?

Emphasis on the Registrant perspective. The processes and requirements for transferring a domain name between one registrar to another affect registrants and End Users.
Registrars have obligations to registrants. Processes and requirements provided by Registrars to Registrants (End Users) to access the Transfer Authorization Code (TAC) must be simple, consistent, and secure.

Registrants should easily be able to transfer their domain to a new registrar or a different registrant.
Processes should be secure and protect against unauthorized activity related to the registrant’s account.

5 of 9

Next Round

Leads: Justine Chew and Cheryl Langdon-Orr

Talking Points:

The Next Round must focus on communities and underserved regions.
Success requires expansion of the Registry Pool, which requires requisite support for effective inclusion of underserved / undeveloped / indigenous communities, small businesses, non-profit orgs as potential applicants.
Namespace expansion must remain conservative, in order to minimize potential of end user confusion and associated risks/harm.

ICANN80 Sessions:

New gTLD Program: Next Round - Implementation Status Update on Tuesday, 28 May at 18:00 - 19:30 (UTC)
GDS: SubPro IRT Work Session on Monday, 10 June at 07:00 - 08:15 (UTC)
GAC Discussion: New gTLD Program Next Round on Monday, 10 June at 08:45 - 10:15 (UTC)
GDS: SubPro IRT Work Session (2 of 3) on Wednesday, June 12 at 07:00 - 08:15 (UTC)
GDS: SubPro IRT Work Session (3 of 3) on Thursday, June 13 at 07:00 - 08:15 (UTC)

BACKGROUND

Overview

On 26 January 2020, the ICANN Board passed a resolution to defer contractual compliance enforcement of the gaining registrar's requirement to obtain express authorization of an inter-registrar transfer from the Transfer Contact via a Standardized Form of Authorization (FOA). ICANN Contractual Compliance will defer enforcement of Section I(A)(2.1) of the Transfer Policy until the matter is settled in the GNSO Council's Transfer Policy Review.

On 18 February 2021, the GNSO Council initiated the two-phase Transfer Policy Review PDP. The purpose of the PDP is to determine if changes to the policy are needed to improve the ease, security, and efficacy of Inter-Registrar and Inter-Registrant Transfers. As recommended in the Final Issue Report, the PDP will address the following topics in sequence:

The Gaining and Losing Forms of Authorization, AuthInfo Codes [also known as the Transfer Authorization Code (TAC)], and NACKing transfers (Phase 1A).
The change of registrant (Phase 1B).
The transfer emergency action contact and reversing inter-registrar transfers, Transfer Dispute Resolution Policy, and ICANN-approved transfers (Phase 2).

The GNSO Council adopted the PDP working group charter on 24 March 2021. According to PDP 3.0, the working group adopted a representative model with set criteria and expectations for their members and chairs. The working group met for the first time on 14 May 2021.

Why is Transfer Policy important to At-Large and End Users?

Emphasis on the Registrant perspective. The processes and requirements for transferring a domain name between one registrar to another affect registrants and End Users.
Registrars have obligations to registrants. Processes and requirements provided by Registrars to Registrants (End Users) to access the Transfer Authorization Code (TAC) must be simple, consistent, and secure.

Registrants should easily be able to transfer their domain to a new registrar or a different registrant.
Processes should be secure and protect against unauthorized activity related to the registrant’s account.

6 of 9

Registration Data Request Service (RDRS)

Leads: Alan Greenberg

Talking Points:

Centralized Data Requests and Reporting are Essential.
At-Large supports ICANN org’s continued efforts to progress the RDRS system.
Promotion and usage of RDRS is encouraged.�

ICANN80 Sessions:

Registration Data Request Service (RDRS) Update - From Pilot Program Launch to May 2024 on Wednesday, May 29 at 16:30 - 17:30 (UTC)
GNSO: RDRS Standing Committee Work Session on Monday, June 10 at 08:45 - 10:15 (UTC)

BACKGROUND

Overview

On 26 January 2020, the ICANN Board passed a resolution to defer contractual compliance enforcement of the gaining registrar's requirement to obtain express authorization of an inter-registrar transfer from the Transfer Contact via a Standardized Form of Authorization (FOA). ICANN Contractual Compliance will defer enforcement of Section I(A)(2.1) of the Transfer Policy until the matter is settled in the GNSO Council's Transfer Policy Review.

On 18 February 2021, the GNSO Council initiated the two-phase Transfer Policy Review PDP. The purpose of the PDP is to determine if changes to the policy are needed to improve the ease, security, and efficacy of Inter-Registrar and Inter-Registrant Transfers. As recommended in the Final Issue Report, the PDP will address the following topics in sequence:

The Gaining and Losing Forms of Authorization, AuthInfo Codes [also known as the Transfer Authorization Code (TAC)], and NACKing transfers (Phase 1A).
The change of registrant (Phase 1B).
The transfer emergency action contact and reversing inter-registrar transfers, Transfer Dispute Resolution Policy, and ICANN-approved transfers (Phase 2).

The GNSO Council adopted the PDP working group charter on 24 March 2021. According to PDP 3.0, the working group adopted a representative model with set criteria and expectations for their members and chairs. The working group met for the first time on 14 May 2021.

Why is Transfer Policy important to At-Large and End Users?

Emphasis on the Registrant perspective. The processes and requirements for transferring a domain name between one registrar to another affect registrants and End Users.
Registrars have obligations to registrants. Processes and requirements provided by Registrars to Registrants (End Users) to access the Transfer Authorization Code (TAC) must be simple, consistent, and secure.

Registrants should easily be able to transfer their domain to a new registrar or a different registrant.
Processes should be secure and protect against unauthorized activity related to the registrant’s account.

7 of 9

SPIRT Charter Drafting Team

Leads: Alan Greenberg

Talking Points:

Implementation of SubPro Final Report recommendations on Predictability is important to the development of the Next Round.
The Drafting Team’s only task is to develop the draft Charter for the SPIRT, with the Charter being subject to GNSO Council approval.
The SPIRT will be the body empowered to provide input to the GNSO Council, the ICANN Board, ICANN org, and the ICANN community on unforeseen issues arising for the Next Round of the New gTLD Program

ICANN80 Sessions:

GNSO Council Meeting on Wednesday, June 12 at 11:45 - 13:45 (UTC)

BACKGROUND

Overview

On 26 January 2020, the ICANN Board passed a resolution to defer contractual compliance enforcement of the gaining registrar's requirement to obtain express authorization of an inter-registrar transfer from the Transfer Contact via a Standardized Form of Authorization (FOA). ICANN Contractual Compliance will defer enforcement of Section I(A)(2.1) of the Transfer Policy until the matter is settled in the GNSO Council's Transfer Policy Review.

On 18 February 2021, the GNSO Council initiated the two-phase Transfer Policy Review PDP. The purpose of the PDP is to determine if changes to the policy are needed to improve the ease, security, and efficacy of Inter-Registrar and Inter-Registrant Transfers. As recommended in the Final Issue Report, the PDP will address the following topics in sequence:

The Gaining and Losing Forms of Authorization, AuthInfo Codes [also known as the Transfer Authorization Code (TAC)], and NACKing transfers (Phase 1A).
The change of registrant (Phase 1B).
The transfer emergency action contact and reversing inter-registrar transfers, Transfer Dispute Resolution Policy, and ICANN-approved transfers (Phase 2).

The GNSO Council adopted the PDP working group charter on 24 March 2021. According to PDP 3.0, the working group adopted a representative model with set criteria and expectations for their members and chairs. The working group met for the first time on 14 May 2021.

Why is Transfer Policy important to At-Large and End Users?

Emphasis on the Registrant perspective. The processes and requirements for transferring a domain name between one registrar to another affect registrants and End Users.
Registrars have obligations to registrants. Processes and requirements provided by Registrars to Registrants (End Users) to access the Transfer Authorization Code (TAC) must be simple, consistent, and secure.

Registrants should easily be able to transfer their domain to a new registrar or a different registrant.
Processes should be secure and protect against unauthorized activity related to the registrant’s account.

8 of 9

Transfer Policy Review

Leads: Steinar Grøtterød

Talking Points:

No “transfer lock” due to a Change of Registrant Data (CORD).
Prior and new registrants should receive a notification when a CORD is executed. Registrants MUST have an option to “opt-out” from the notification requirement.
At-Large supports a 30-days restriction to transfer a domain name after the initial registration.
Registrants must be able to initiate a Transfer Dispute Process.
Registrar must restrict the Registered Name Holder from transferring a domain name to a new Registrar within 30 days / 720 hours of the completion of an inter-Registrar transfer. The Registrant should have an option to opt-out from the post-transfer lock.

ICANN80 Sessions:

GNSO: Transfer Policy Review PDP Working Group on Tuesday, June 11 at 13:30 - 15:00 (UTC)

BACKGROUND

Overview

On 26 January 2020, the ICANN Board passed a resolution to defer contractual compliance enforcement of the gaining registrar's requirement to obtain express authorization of an inter-registrar transfer from the Transfer Contact via a Standardized Form of Authorization (FOA). ICANN Contractual Compliance will defer enforcement of Section I(A)(2.1) of the Transfer Policy until the matter is settled in the GNSO Council's Transfer Policy Review.

On 18 February 2021, the GNSO Council initiated the two-phase Transfer Policy Review PDP. The purpose of the PDP is to determine if changes to the policy are needed to improve the ease, security, and efficacy of Inter-Registrar and Inter-Registrant Transfers. As recommended in the Final Issue Report, the PDP will address the following topics in sequence:

The Gaining and Losing Forms of Authorization, AuthInfo Codes [also known as the Transfer Authorization Code (TAC)], and NACKing transfers (Phase 1A).
The change of registrant (Phase 1B).
The transfer emergency action contact and reversing inter-registrar transfers, Transfer Dispute Resolution Policy, and ICANN-approved transfers (Phase 2).

The GNSO Council adopted the PDP working group charter on 24 March 2021. According to PDP 3.0, the working group adopted a representative model with set criteria and expectations for their members and chairs. The working group met for the first time on 14 May 2021.

Why is Transfer Policy important to At-Large and End Users?

Emphasis on the Registrant perspective. The processes and requirements for transferring a domain name between one registrar to another affect registrants and End Users.
Registrars have obligations to registrants. Processes and requirements provided by Registrars to Registrants (End Users) to access the Transfer Authorization Code (TAC) must be simple, consistent, and secure.

Registrants should easily be able to transfer their domain to a new registrar or a different registrant.
Processes should be secure and protect against unauthorized activity related to the registrant’s account.

9 of 9

At-Large Resources

Web Pages

Workspaces

Social Media

BACKGROUND

Overview

On 26 January 2020, the ICANN Board passed a resolution to defer contractual compliance enforcement of the gaining registrar's requirement to obtain express authorization of an inter-registrar transfer from the Transfer Contact via a Standardized Form of Authorization (FOA). ICANN Contractual Compliance will defer enforcement of Section I(A)(2.1) of the Transfer Policy until the matter is settled in the GNSO Council's Transfer Policy Review.

On 18 February 2021, the GNSO Council initiated the two-phase Transfer Policy Review PDP. The purpose of the PDP is to determine if changes to the policy are needed to improve the ease, security, and efficacy of Inter-Registrar and Inter-Registrant Transfers. As recommended in the Final Issue Report, the PDP will address the following topics in sequence:

The Gaining and Losing Forms of Authorization, AuthInfo Codes [also known as the Transfer Authorization Code (TAC)], and NACKing transfers (Phase 1A).
The change of registrant (Phase 1B).
The transfer emergency action contact and reversing inter-registrar transfers, Transfer Dispute Resolution Policy, and ICANN-approved transfers (Phase 2).

The GNSO Council adopted the PDP working group charter on 24 March 2021. According to PDP 3.0, the working group adopted a representative model with set criteria and expectations for their members and chairs. The working group met for the first time on 14 May 2021.

Why is Transfer Policy important to At-Large and End Users?

Emphasis on the Registrant perspective. The processes and requirements for transferring a domain name between one registrar to another affect registrants and End Users.
Registrars have obligations to registrants. Processes and requirements provided by Registrars to Registrants (End Users) to access the Transfer Authorization Code (TAC) must be simple, consistent, and secure.

Registrants should easily be able to transfer their domain to a new registrar or a different registrant.
Processes should be secure and protect against unauthorized activity related to the registrant’s account.