ICANN 67

Event
Process	ICANN
Date	Mar. 7, 2020 – Mar. 12, 2020
Venue	Online
Websites	67.schedule.icann.org
← ICANN 66 ICANN 68 →

ICANN 67 was held as a virtual community forum in March 2020. It was the first meeting to be fully virtual as a result of the COVID-19 pandemic. The original host was Cancun, and the time zone for meeting scheduling was Eastern Standard Time. ICANN 67 had 1,752 attendees, 130 countries/territories represented, and 65 sessions.

The meeting week concentrated a reduced set of sessions necessary to advance active policy and advisory work, with particular emphasis across the community on New gTLD Subsequent Procedures, continued work on gTLD registration data policy (EPDP Phase 2), and a high-profile community dialogue on the proposed change of control of Public Interest Registry (PIR).

New gTLD Program: Subsequent Procedures

New gTLD Subsequent Procedures (SubPro) was the dominant cross-community policy focus at ICANN67, including multiple working sessions and extensive participation by the GAC in SubPro-related discussions. The GAC structured its ICANN 67 agenda to prioritize SubPro work, enabling participation in multiple hours of PDP working group discussions across the week.

The Post-ICANN67 Policy Report notes SubPro as a primary theme across community interactions, including discussions with the ICANN Board and bilateral engagement with At-Large leadership where subsequent rounds of new gTLDs featured prominently alongside registration data topics. The GAC Communiqué also addressed subsequent rounds of new gTLDs as a core area of government attention at ICANN67.

Registration Data: EPDP Phase 2

Work on the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data (Phase 2) continued during ICANN67 through dedicated team sessions focused on the standardized system for access to non-public registration data and related implementation constraints.

Meeting outcomes included the EPDP Phase 2 Team finalizing draft recommendations on a set of "Priority 2" topics (including treatment of affiliated vs. accredited privacy/proxy services, data retention, city field redaction, and feasibility of a uniform anonymized email mechanism for unique contacts), with those recommendations intended to be incorporated into an addendum for publication for Public Comment after the meeting. These EPDP discussions also featured as cross-community issues in GAC engagement with other groups, including in its exchanges with At-Large leadership and its meeting with the ICANN Board.

Rights Protection Mechanisms

Rights protection mechanisms (RPMs) remained active at ICANN 67 through working sessions of the Review of All Rights Protection Mechanisms in All gTLDs PDP Working Group. The GNSO Policy Briefing materials prepared for ICANN 67 anticipated multiple RPM PDP working sessions during the meeting week oriented around reviewing public comment input to the Phase 1 Initial Report and assessing whether current RPMs collectively meet their intended purposes or require additional policy recommendations. The Post-ICANN67 Policy Report recorded continuing community attention to RPM work as part of the reduced but policy-centered ICANN67 program.

DNS Abuse, Security, and Stability

ICANN 67 included security and stability sessions spanning DNSSEC operational issues, broader protocol developments affecting the DNS, and community discussion of DNS abuse. The SSAC held its DNSSEC and Security Workshop and covered topics including Key Signing Key (KSK) rollovers, DNS over HTTPS (DoH) and DNS over TLS (DoT), third-party DNS providers, and other routing-security issues. SSAC updates also referenced ongoing work streams relevant to DNS Abuse and the Name Collision Analysis Project (NCAP).

At-Large regional coordination at ICANN67 included an AFRALO–AfrICANN joint meeting that issued a statement calling for intensified efforts by ICANN org and the community to curb DNS abuse, situating abuse mitigation as a cross-community operational priority in the virtual meeting context.

Supporting Organizations and Advisory Committees

GNSO

The GNSO held 19 sessions including GNSO policy development process (PDP) working group meetings, Stakeholder Group and Constituency work meetings, and a GNSO Council meeting.

The Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data Phase 2 Team finalized its draft recommendations on the following Priority 2 topics:

• display of information of affiliated vs. accredited privacy/proxy providers;
• data retention;
• city field redaction; and
• feasibility of unique contacts to have a uniform anonymized email address.

• The New gTLD Subsequent Procedures PDP Working Group held three sessions on

• whether to allow closed generic top-level domains;
• Global Public Interest topics such as Mandatory Public Interest Commitments (PICs), Voluntary Public Interest Commitments, tentatively called Registry Voluntary Commitments (RVCs), DNS Abuse, and Verified TLDs; and
• Draft recommendations on GAC Advice and GAC Early Warning.

The Review of All Rights Protection Mechanisms in All gTLDs PDP working group reviewed the draft Phase 1 Initial Report, with 26 preliminary recommendations, 17 specific community questions, and 24 proposals. The working group deliberated RPM-related recommendations of the Temporary Specification team and the Competition, Consumer Trust, and Consumer Choice Review Team.

ALAC and RALOs

At-Large activity during ICANN 67 combined policy workshops, cross-community framing sessions, and leadership engagement tied to organizational priorities and external-facing narratives about multistakeholder legitimacy under geopolitical pressure. Prior to ICANN 67, the ALAC submitted eight policy statements and provided Board-facing advice on DNS Abuse and on the proposed sale/transfer issues associated with PIR; these inputs were treated as baseline positions for At-Large's meeting-week engagement.

At-Large's ICANN67 policy workshops and roundtables focused on three clusters:

• DNS Abuse and compliance leverage: two policy workshops framed end-user harm, At-Large engagement strategy, and the practical enforceability of DNS Abuse expectations via Contractual Compliance tooling, including audit/threshold approaches and multi-scenario case studies tested with compliance staff feedback.

• Cybersecurity/geopolitics and "One World. One Internet." narrative: a cross-community roundtable led by At-Large leadership posed structured questions about "Internet fragmentation," state sovereignty pressures, and how ICANN's policy justifications interact with cybercrime/cybersecurity legal frameworks and UN cybersecurity processes.

• Encrypted DNS (DoH/DoT): a policy workshop examined DoT/DoH background, operational implications, and the trade space for end users and DNS operations. At-Large positioned this as an ongoing monitoring and policy-development topic within its technical/policy working groups, including the At-Large Consolidated Policy Working Group (CPWG).

At-Large also held policy discussions connected to the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data, the SubPro PDP, and the evolution of its internal "At-Large Interactive Policy Platform," a topic taxonomy intended to structure At-Large engagement and align post-ATLAS III and At-Large Review implementation efforts around a defined set of end-user-impacting themes.

RSSAC

During ICANN 67, the RSSAC held work sessions and its monthly meeting, approving a new advisory on DNS root server metrics (RSSAC047), updates to RSSAC002 and RSSAC026, and an RSSAC statement providing input on the SSR2 Review Team Draft Report. RSSAC work planning discussed follow-on caucus activity, including potential new statements of work related to tools for local perspectives on the root server system and mitigations for a rogue root server operator scenario.

SSAC

The SSAC held a DNSSEC and Security workshop, that discussed:

• Key Signing Key (KSK) Rolls;
• DNS over HTTPS and DNS over TLS;
• DNSSEC via third-party DNS Providers.

The SSAC also summarized for the public its publications since ICANN 66:

• SAC109: The Implications of DNS over HTTPS and DNS over TLS;
• SAC108: SSAC Comments on the IANA Proposal for Future Root Zone KSK Rollovers;
• SAC107: SSAC Comment to NIST on Quantum Cryptography Algorithms;
• SSAC2020-06: SSAC Public Comment on the Initial Report of the New gTLD Auction Proceeds Cross-Community Working Group;
• SSAC2020-05: SSAC Public Comment on Third Accountability and Transparency Review Team (ATRT3) Draft Report.

Finally, the SSAC gave updates on:

• the Name Collision Analysis Project (NCAP);
• DNS Abuse;
• a Scan of Threats to Internet Naming and Addressing;
• the Temporary Specification for gTLD Registration Data; and
• the Second Security, Stability, and Resiliency (SSR2) Review Team Draft Report.

GAC

The GAC adapted its ICANN 67 agenda to accommodate the virtual meeting format by canceling many internal working group sessions and bilateral meetings, while prioritizing participation in cross-community policy work, particularly the SubPro, and preserving its traditional meeting with the ICANN Board. GAC members discussed with the Board a set of topics that included the proposed PIR acquisition, subsequent rounds of new gTLDs, implementation of Cross-Community Working Group on Enhancing ICANN Accountability Work Stream 2 recommendations, access to non-public gTLD registration data, and Registration Directory Services/WHOIS2 Review recommendations.

The GAC Communiqué issued for ICANN 67 reflected government positions and concerns across these agenda areas, including subsequent rounds of new gTLDs and registration data matters, and formed the basis for follow-up interactions with the ICANN Board through the standard communiqué/scorecard process.

ccNSO

The ccNSO substantially re-scoped its ICANN 67 program as the meeting moved online: the ccNSO Council deferred its workshop to ICANN 68; Tech Day and the ccNSO Members Meeting were canceled; and several planned joint sessions (including with ALAC, GAC, the GNSO Council, and the Board) were also canceled. The ccNSO Council nonetheless conducted its monthly meeting on March 12, 2020, electing a leadership team (including re-election of the chair and vice chair) and addressing the procedural and participation implications of meeting cancellation/virtualization for future ICANN Public Meetings. A concrete cross-community operational decision point discussed at the Council meeting was whether to approve proposed changes to Public Technical Identifiers (PTI) performance Service Level Agreements (SLAs) for ccTLD Creation/Transfer validation and reviews, after the Customer Standing Committee requested the ccNSO and GNSO Councils to approve those SLA changes.

ccNSO policy development activity continued outside the ICANN67 session framework, with notable workstreams highlighted in the post-meeting reporting:

• The ccPDP Working Group on Retirement of Delegated Top-Level Domains continued discussion, including stress-testing considerations for retirement scenarios tied to ISO 3166-1 country/territory changes.

• The ccPDP Working Group on Review Mechanisms advanced the development of review mechanisms for ccTLD delegation/transfer/revocation/retirement decisions, with a structured invitation to other SO/AC participants and ICANN org experts and supporting webinars to broaden informed participation.

• Preparatory steps continued toward a potential ccPDP on Selection of IDN ccTLD Strings, pending an ICANN General Counsel opinion and subsequent ccNSO Council consideration of an Issue Report; the proposed approach anticipated subgroups focused on confusing similarity evaluation review and the management of variant IDN ccTLDs, with an explicit intent to enable coordination with the GNSO where relevant.Template:ICANN Meeting

ICANN67 was ICANN's first fully virtual Public Meeting, held from March 7–12, 2020, after the ICANN Board transitioned the meeting format in response to the COVID-19 outbreak while keeping the original dates unchanged. The meeting week concentrated a reduced set of sessions necessary to advance active policy and advisory work, with particular emphasis across the community on New gTLD Subsequent Procedures, continued work on gTLD registration data policy (EPDP Phase 2), and a high-profile community dialogue on the proposed change of control of Public Interest Registry (PIR).

Meeting Information

ICANN67 was the first ICANN Public Meeting conducted fully online. The meeting had originally been planned as an in-person Community Forum in Cancún, Mexico, but the ICANN Board transitioned it to a virtual format in late February 2020 due to COVID-19. The ICANN Meetings calendar later listed ICANN67 as “Online Only (*Cancún)”.

The transition decision was formalized through ICANN Board action, which directed ICANN org to proceed with a virtual ICANN67 meeting and to adjust planning accordingly. In operational terms, the week’s programming was narrowed to sessions considered necessary to move policy and advisory work forward, with other topics expected to be handled intersessionally through webinars and regular calls.

New gTLD Program: Subsequent Procedures

New gTLD Subsequent Procedures (SubPro) was the dominant cross-community policy focus at ICANN67, including multiple working sessions and extensive participation by the Governmental Advisory Committee (GAC) in SubPro-related discussions. The GAC structured its ICANN67 agenda to prioritize SubPro work, enabling participation in multiple hours of PDP working group discussions across the week.

The Post-ICANN67 Policy Report notes SubPro as a primary theme across community interactions, including discussions with the ICANN Board and bilateral engagement with At-Large leadership where subsequent rounds of new gTLDs featured prominently alongside registration data topics. The GAC Communiqué also addressed subsequent rounds of new gTLDs as a core area of government attention at ICANN67.

Registration Data: EPDP Phase 2

Work on the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data (Phase 2) continued during ICANN67 through dedicated team sessions focused on the standardized system for access to non-public registration data and related implementation constraints.

Meeting outcomes included the EPDP Phase 2 Team finalizing draft recommendations on a set of “Priority 2” topics (including treatment of affiliated vs. accredited privacy/proxy services, data retention, city field redaction, and feasibility of a uniform anonymized email mechanism for unique contacts), with those recommendations intended to be incorporated into an addendum for publication for Public Comment after the meeting. These EPDP discussions also featured as cross-community issues in GAC engagement with other groups, including in its exchanges with At-Large leadership and its meeting with the ICANN Board.

Rights Protection Mechanisms

Rights protection mechanisms (RPMs) remained active at ICANN67 through working sessions of the Review of All Rights Protection Mechanisms in All gTLDs PDP Working Group. The GNSO Policy Briefing materials prepared for ICANN67 anticipated multiple RPM PDP working sessions during the meeting week oriented around reviewing public comment input to the Phase 1 Initial Report and assessing whether current RPMs collectively meet their intended purposes or require additional policy recommendations. The Post-ICANN67 Policy Report recorded continuing community attention to RPM work as part of the reduced but policy-centered ICANN67 program.

DNS Abuse, Security, and Stability

ICANN67 included security and stability sessions spanning DNSSEC operational issues, broader protocol developments affecting the DNS, and community discussion of DNS abuse. The Security and Stability Advisory Committee (SSAC) held its DNSSEC and Security Workshop and covered topics including Key Signing Key (KSK) rollovers, DNS over HTTPS (DoH) and DNS over TLS (DoT), third-party DNS providers, and other routing-security issues; SSAC updates also referenced ongoing work streams relevant to DNS abuse and the Name Collision Analysis Project (NCAP).

At-Large regional coordination at ICANN67 included an AFRALO–AfrICANN joint meeting that issued a statement calling for intensified efforts by ICANN org and the community to curb DNS abuse, situating abuse mitigation as a cross-community operational priority in the virtual meeting context.

Supporting Organizations and Advisory Committees

ccNSO

The Post-ICANN67 Policy Report recorded ccNSO Council discussion of lessons learned from the virtual meeting format and potential actions if future ICANN Public Meetings were also held virtually. Substantively, the ccNSO Council was positioned to decide whether to approve proposed changes to Public Technical Identifiers (PTI) performance service level agreements (SLAs) for ccTLD Creation/Transfer validation and reviews, following a request from the Customer Standing Committee (CSC) to both the ccNSO and GNSO Councils to approve the proposed updates.

ccNSO workspace materials for ICANN67 also reflected that the meeting-week cadence for ccNSO working group/committee meetings and Tech Day was canceled in light of the transition to a virtual format, with intended deferral of Tech Day presentations and a return of other work to regular intersessional rotations.

GNSO

Within the reduced ICANN67 schedule, the GNSO concentrated on active PDP work streams and Council coordination, including (i) SubPro sessions, (ii) EPDP Phase 2 work on access to non-public registration data and deferred issues, and (iii) RPM PDP sessions reviewing public comment on the Phase 1 Initial Report. GNSO policy briefing materials circulated for ICANN67 also documented which policy efforts would and would not meet during the week, reflecting the meeting’s prioritization and scheduling constraints under the virtual format (for example, the Transfer Policy Review Scoping Team was not scheduled to meet at ICANN67).

ALAC and RALOs

The Post-ICANN67 Policy Report described At-Large leadership engagement on key organizational issues and policy topics during ICANN67, including interactions relevant to subsequent rounds of new gTLDs and registration data policy work alongside broader community sessions. At-Large regional engagement also included the AFRALO–AfrICANN DNS abuse statement referenced above.

GAC

The GAC adapted its ICANN67 agenda to accommodate the virtual meeting format by canceling many internal working group sessions and bilateral meetings, while prioritizing participation in cross-community policy work—particularly SubPro—and preserving its traditional meeting with the ICANN Board. GAC members discussed with the Board a set of topics that included the proposed PIR acquisition, subsequent rounds of new gTLDs, implementation of Cross-Community Working Group on Enhancing ICANN Accountability Work Stream 2 recommendations, access to non-public gTLD registration data, and Registration Directory Services/WHOIS2 Review recommendations.

The GAC Communiqué issued for ICANN67 reflected government positions and concerns across these agenda areas, including subsequent rounds of new gTLDs and registration data matters, and formed the basis for follow-up interactions with the ICANN Board through the standard communiqué/scorecard process.

RSSAC

During ICANN67, the Root Server System Advisory Committee (RSSAC) held work sessions and its monthly meeting, approving a new advisory on DNS root server metrics (RSSAC047), updates to RSSAC002 and RSSAC026, and an RSSAC statement providing input on the SSR2 Review Team Draft Report. RSSAC work planning discussed follow-on caucus activity, including potential new statements of work related to tools for local perspectives on the root server system and mitigations for a rogue root server operator scenario.

SSAC

At ICANN67, the SSAC’s DNSSEC and Security Workshop covered operational and security topics with direct implications for DNS infrastructure and resolver behavior, including DoH/DoT impacts and potential abuses, RPKI deployment impacts, and routing-security issues. The SSAC public meeting also summarized recently published advisories and comments (including SAC109 on DoH/DoT and SAC108 on future root zone KSK rollovers) and provided updates on ongoing work streams including DNS abuse and NCAP.

Board and Leadership Actions

ICANN67 included a public meeting of the ICANN Board and a targeted community dialogue session that ICANN org allocated within the Public Forum program for discussion of the proposed transfer of ownership of Public Interest Registry (PIR). The Post-ICANN67 Policy Report recorded that PIR’s proposed acquisition, subsequent rounds of new gTLDs, Work Stream 2 implementation, access to non-public registration data, and RDS/WHOIS2 Review recommendations were among the issues raised in GAC–Board discussions during the meeting week.Template:ICANN Meeting

ICANN67 was ICANN's first fully virtual Public Meeting, held from March 7–12, 2020, after the ICANN Board transitioned the meeting format in response to the COVID-19 outbreak while keeping the original dates unchanged. The meeting week concentrated a reduced set of sessions necessary to advance active policy and advisory work, with particular emphasis across the community on New gTLD Subsequent Procedures, continued work on gTLD registration data policy (EPDP Phase 2), and a high-profile community dialogue on the proposed change of control of Public Interest Registry (PIR).

Meeting Information

ICANN67 was the first ICANN Public Meeting conducted fully online. The meeting had originally been planned as an in-person Community Forum in Cancún, Mexico, but the ICANN Board transitioned it to a virtual format in late February 2020 due to COVID-19. The ICANN Meetings calendar later listed ICANN67 as “Online Only (*Cancún)”.

The transition decision was formalized through ICANN Board action, which directed ICANN org to proceed with a virtual ICANN67 meeting and to adjust planning accordingly. In operational terms, the week’s programming was narrowed to sessions considered necessary to move policy and advisory work forward, with other topics expected to be handled intersessionally through webinars and regular calls.

New gTLD Program: Subsequent Procedures

New gTLD Subsequent Procedures (SubPro) was the dominant cross-community policy focus at ICANN67, including multiple working sessions and extensive participation by the Governmental Advisory Committee (GAC) in SubPro-related discussions. The GAC structured its ICANN67 agenda to prioritize SubPro work, enabling participation in multiple hours of PDP working group discussions across the week.

The Post-ICANN67 Policy Report notes SubPro as a primary theme across community interactions, including discussions with the ICANN Board and bilateral engagement with At-Large leadership where subsequent rounds of new gTLDs featured prominently alongside registration data topics. The GAC Communiqué also addressed subsequent rounds of new gTLDs as a core area of government attention at ICANN67.

Registration Data: EPDP Phase 2

Work on the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data (Phase 2) continued during ICANN67 through dedicated team sessions focused on the standardized system for access to non-public registration data and related implementation constraints.

Meeting outcomes included the EPDP Phase 2 Team finalizing draft recommendations on a set of “Priority 2” topics (including treatment of affiliated vs. accredited privacy/proxy services, data retention, city field redaction, and feasibility of a uniform anonymized email mechanism for unique contacts), with those recommendations intended to be incorporated into an addendum for publication for Public Comment after the meeting. These EPDP discussions also featured as cross-community issues in GAC engagement with other groups, including in its exchanges with At-Large leadership and its meeting with the ICANN Board.

Rights Protection Mechanisms

Rights protection mechanisms (RPMs) remained active at ICANN67 through working sessions of the Review of All Rights Protection Mechanisms in All gTLDs PDP Working Group. The GNSO Policy Briefing materials prepared for ICANN67 anticipated multiple RPM PDP working sessions during the meeting week oriented around reviewing public comment input to the Phase 1 Initial Report and assessing whether current RPMs collectively meet their intended purposes or require additional policy recommendations. The Post-ICANN67 Policy Report recorded continuing community attention to RPM work as part of the reduced but policy-centered ICANN67 program.

DNS Abuse, Security, and Stability

ICANN67 included security and stability sessions spanning DNSSEC operational issues, broader protocol developments affecting the DNS, and community discussion of DNS abuse. The Security and Stability Advisory Committee (SSAC) held its DNSSEC and Security Workshop and covered topics including Key Signing Key (KSK) rollovers, DNS over HTTPS (DoH) and DNS over TLS (DoT), third-party DNS providers, and other routing-security issues; SSAC updates also referenced ongoing work streams relevant to DNS abuse and the Name Collision Analysis Project (NCAP).

At-Large regional coordination at ICANN67 included an AFRALO–AfrICANN joint meeting that issued a statement calling for intensified efforts by ICANN org and the community to curb DNS abuse, situating abuse mitigation as a cross-community operational priority in the virtual meeting context.

Supporting Organizations and Advisory Committees

ccNSO

The Post-ICANN67 Policy Report recorded ccNSO Council discussion of lessons learned from the virtual meeting format and potential actions if future ICANN Public Meetings were also held virtually. Substantively, the ccNSO Council was positioned to decide whether to approve proposed changes to Public Technical Identifiers (PTI) performance service level agreements (SLAs) for ccTLD Creation/Transfer validation and reviews, following a request from the Customer Standing Committee (CSC) to both the ccNSO and GNSO Councils to approve the proposed updates.

ccNSO workspace materials for ICANN67 also reflected that the meeting-week cadence for ccNSO working group/committee meetings and Tech Day was canceled in light of the transition to a virtual format, with intended deferral of Tech Day presentations and a return of other work to regular intersessional rotations.

GNSO

Within the reduced ICANN 67 schedule, the GNSO concentrated on active PDP work streams and Council coordination, including (i) SubPro sessions, (ii) EPDP Phase 2 work on access to non-public registration data and deferred issues, and (iii) RPM PDP sessions reviewing public comment on the Phase 1 Initial Report. GNSO policy briefing materials circulated for ICANN67 also documented which policy efforts would and would not meet during the week, reflecting the meeting’s prioritization and scheduling constraints under the virtual format (for example, the Transfer Policy Review Scoping Team was not scheduled to meet at ICANN67).

ALAC and RALOs

The Post-ICANN67 Policy Report described At-Large leadership engagement on key organizational issues and policy topics during ICANN 67, including interactions relevant to subsequent rounds of new gTLDs and registration data policy work alongside broader community sessions. At-Large regional engagement also included the AFRALO–AfrICANN DNS abuse statement referenced above.

GAC

The GAC adapted its ICANN 67 agenda to accommodate the virtual meeting format by canceling many internal working group sessions and bilateral meetings, while prioritizing participation in cross-community policy work—particularly SubPro—and preserving its traditional meeting with the ICANN Board. GAC members discussed with the Board a set of topics that included the proposed PIR acquisition, subsequent rounds of new gTLDs, implementation of Cross-Community Working Group on Enhancing ICANN Accountability Work Stream 2 recommendations, access to non-public gTLD registration data, and Registration Directory Services/WHOIS2 Review recommendations.

The GAC Communiqué issued for ICANN 67 reflected government positions and concerns across these agenda areas, including subsequent rounds of new gTLDs and registration data matters, and formed the basis for follow-up interactions with the ICANN Board through the standard communiqué/scorecard process.

RSSAC

During ICANN67, the Root Server System Advisory Committee (RSSAC) held work sessions and its monthly meeting, approving a new advisory on DNS root server metrics (RSSAC047), updates to RSSAC002 and RSSAC026, and an RSSAC statement providing input on the SSR2 Review Team Draft Report. RSSAC work planning discussed follow-on caucus activity, including potential new statements of work related to tools for local perspectives on the root server system and mitigations for a rogue root server operator scenario.

SSAC

At ICANN67, the SSAC’s DNSSEC and Security Workshop covered operational and security topics with direct implications for DNS infrastructure and resolver behavior, including DoH/DoT impacts and potential abuses, RPKI deployment impacts, and routing-security issues. The SSAC public meeting also summarized recently published advisories and comments (including SAC109 on DoH/DoT and SAC108 on future root zone KSK rollovers) and provided updates on ongoing work streams including DNS abuse and NCAP.

Board and Leadership Actions

ICANN67 included a public meeting of the ICANN Board and a targeted community dialogue session that ICANN org allocated within the Public Forum program for discussion of the proposed transfer of ownership of Public Interest Registry (PIR). The Post-ICANN67 Policy Report recorded that PIR’s proposed acquisition, subsequent rounds of new gTLDs, Work Stream 2 implementation, access to non-public registration data, and RDS/WHOIS2 Review recommendations were among the issues raised in GAC–Board discussions during the meeting week.

Generic Top-level Domain

Expedited Policy Development Process

Governmental Advisory Committee. Considers and provides advice on the activities of ICANN as they relate to concerns of governments, particularly matters where there may be an interaction between ICANN's policies and various laws and international agreements or where they may affect public policy issues (ICANN Bylaws).

Policy Development Process

Generic Top-level Domain

Generic Names Supporting Organization. Develops and recommends to the Board substantive policies relating to generic top-level domains and other responsibilities set forth in the Bylaws (ICANN Bylaws).

Domain Name System Security Extensions

Security and Stability Advisory Committee. Advises the ICANN community and Board on matters relating to the security and integrity of the Internet's naming and address allocation systems (ICANN Bylaws).

HTTP over Transport Layer Security (TLS), distinguishing secured traffic from insecure traffic by the use of a different server port (RFC 2818).

DNS over HTTPS

Allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery (RFC 8446).

The African Regional At-Large Organization

Top-Level Domain

At-Large Advisory Committee. Considers and provides advice on the activities of ICANN related to the interests of individual Internet users (ICANN Bylaws). Not to be confused with the Non-Commercial Stakeholder Group.

Root Server System Advisory Committee. Advises the ICANN community and Board on matters relating to the operation, administration, security, and integrity of the Internet's Root Server System (ICANN Bylaws).

Internet Assigned Numbers Authority

Country Code Names Supporting Organization. Develops and recommends to the Board global policies relating to country-code top-level domains (ICANN Bylaws).

Public Technical Identifiers

Country code top-level domain. Determined by "ISO 3166-1: Codes for the representation of names of countries and their subdivisions — Part 1: Country codes".

International Organization for Standardization

Internationalized Domain Name

Country code top-level domain. Determined by "ISO 3166-1: Codes for the representation of names of countries and their subdivisions — Part 1: Country codes".