Bureaucrats, steward, Administrators, translator
875
edits
Changes
mLine 13:
Line 13: − *The [[ICANN Board]] adopted the [[Sub Pro]] Final Report Scorecard in full; Section A identifies the adopted outputs. Section B identifies the pending outputs. Section C identifies dependencies; + − ** explained that before a launch date is set for the next round of new gTLDs, ICANN must+ − *# process the 38 pending SubPro recommendations.+ − *# determine an expedited approach for the [[Implementation Review Team]] (IRT) process + − *# complete and apply the outcomes of the [[Closed Generics]] Facilitated Dialogue+ − *# ensure charter questions of the [[EPDP on Internationalized Domain Names]] impact the next Applicant Guidebook.+ − + + Line 26:
Line 27: − + + − + Line 35:
Line 37: + Line 59:
Line 62: − + + − + + − + + + + − + Line 76:
Line 84: − − + − − ====SOIs==== − The SOI Task Force team within the GNSO agreed on proposed changes to enhance representative transparency. However, some members are concerned they cannot disclose their clients’ identities.<ref>[https://opensrs.com/blog/icann76-recap/ ICANN76 Recap, OPENSRS]</ref> The Council Committee for Overseeing and Implementing Continuous Improvement (CCOICI) Working Group Self-Assessment (WGSA) into a single Recommendations Report about SOIs. The CCOICI integrated public comments and submitted its Recommendations Report to the Council on 5 January 2023.<ref>[https://community.icann.org/display/CCFOICI/Council+Committee+for+Overseeing+and+Implementing+Continuous+Improvement+Home CCOICI, Community, ICANN]</ref> − Line 101:
Line 104: + + + + + − +
Christiane moved page ICANN 76 - Cancún to ICANN 76 over redirect: Standardize
===Sub Pro (aka next round of new TLDs)===
===Sub Pro (aka next round of new TLDs)===
====ICANN Board====
====ICANN Board====
The [[ICANN Board]] adopted the [[Sub Pro]] Final Report Scorecard in full; Section A identifies the adopted outputs. Section B identifies the pending outputs. Section C identifies dependencies. The board also explained that before a launch date is set for the next round of new gTLDs, ICANN must
# process the 38 pending SubPro recommendations.
# determine an expedited approach for the [[Implementation Review Team]] (IRT) process
# complete and apply the outcomes of the [[Closed Generics]] Facilitated Dialogue
# ensure charter questions of the [[EPDP on Internationalized Domain Names]] impact the next Applicant Guidebook.
*[[NCUC]] focused on developing Applicant Support, which in the past led to the [[Applicant Guidebook]], and ensuring new applicants have more than 18 months to apply in the next round and significantly slashing the application fee (estimated USD$$240,000) for people from developing countries. The board is afraid that if they pay someone's attorney fee, it may create a conflict of interest as in "who does the attorney represent?" [[Kathy Kleiman]] recommended creating boards or groups willing to work at low cost or pro bono (she explained the [[EFF]] does this).<ref>[https://static.sched.com/hosted_files/icann76/c0/TRANSC_I76CUN_Sat11Mar2023_GNSO-%20NCUC%20Membership%20Meet-en.pdf NCUC Membership Meeting Transcript, ICANN 76]</ref>
====GNSO====
*The [[NCUC]] focused on developing Applicant Support, which in the past led to the [[Applicant Guidebook]], and ensuring new applicants have more than 18 months to apply in the next round and significantly slashing the application fee (estimated USD$$240,000) for people from developing countries. The board is afraid that if they pay someone's attorney fee, it may create a conflict of interest as in "who does the attorney represent?" [[Kathy Kleiman]] recommended creating boards or groups willing to work at low cost or pro bono (she explained the [[EFF]] does this).<ref>[https://static.sched.com/hosted_files/icann76/c0/TRANSC_I76CUN_Sat11Mar2023_GNSO-%20NCUC%20Membership%20Meet-en.pdf NCUC Membership Meeting Transcript, ICANN 76]</ref>
====RSSAC====
====RSSAC====
The [[RSSAC]] responded that three hypothetical growth rates for the root zone (100, 1,000, or 10,000 new top-level domains) in the next round of new gTLDs would not be worrisome but RSOs would need advanced notice of expected changes to the root zone to adapt and a projection of the change rate would be helpful since it is largely an administrative function.<ref>[https://www.icann.org/en/system/files/files/rssac-031-02feb18-en.pdf RSSAC031]</ref>
The [[RSSAC]] responded that three hypothetical growth rates for the root zone (100, 1,000, or 10,000 new top-level domains) in the next round of new gTLDs would not be worrisome but RSOs would need advanced notice of expected changes to the root zone to adapt and a projection of the change rate would be helpful since it is largely an administrative function.<ref>[https://www.icann.org/en/system/files/files/rssac-031-02feb18-en.pdf RSSAC031]</ref>
At-Large also introduced an initial framework to its members that will be used to identify New gTLDs SubPro recommendations to consider as prerequisites ahead of opening the next round of gTLDs.
At-Large also introduced an initial framework to its members that will be used to identify New gTLDs SubPro recommendations to consider as prerequisites ahead of opening the next round of gTLDs.
====The GAC====
====The GAC====
The [[GAC]] had concerns over [[Registry]] [[Public Interest Commitments|voluntary commitments]], Applicant Support, GAC Consensus Advice and GAC Early Warnings, community applications, and auctions.
The [[GAC]] had concerns over [[Registry]] [[Public Interest Commitments|voluntary commitments]], Applicant Support, GAC Consensus Advice and GAC Early Warnings, [[Community TLD|community applications]], [[Auctions of Last Resort|auctions of last resort]], and [[Closed Generics]].<ref>[https://gac.icann.org/contentMigrated/icann76-cancun-communique?language_id=1 ICANN76 Cancun Communique, GAC, ICANN.org]</ref>
===RDDS aks WDS aka [[SSAD]] ===
===RDDS aks WDS aka [[SSAD]] ===
* The Board adopted the [[ODA]] on the [[Whois Disclosure System]] and the ICANN Org renamed it “Registration Data Request Service.” This service should be operative by the end of 2023 and run as a pilot for two years to gather disclosure request volumes to determine whether to build the full Standardized System for Access and Disclosure of non-public domain registration data.<ref>[https://opensrs.com/blog/icann76-recap/ ICANN76 Recap, OPENSRS]</ref> Law enforcement will not be forced to use RDRS, but there is nothing precluding them from using it. The RDRS will not solve the problem of access to data caused by the [[GDPR]].
* The Board adopted the [[ODA]] on the [[Whois Disclosure System]] and the ICANN Org renamed it “Registration Data Request Service.” This service should be operative by the end of 2023 and run as a pilot for two years to gather disclosure request volumes to determine whether to build the full Standardized System for Access and Disclosure of non-public domain registration data.<ref>[https://opensrs.com/blog/icann76-recap/ ICANN76 Recap, OPENSRS]</ref> Law enforcement will not be forced to use RDRS, but there is nothing precluding them from using it. The RDRS will not solve the problem of access to data caused by the [[GDPR]].
*The [[GAC]] PSWG noted a lack of functionality to maintain the confidentiality of requests for Law Enforcement Agencies, which will likely lead to reduced engagement from them
* The [[GAC]] PSWG noted a lack of functionality to maintain the confidentiality of requests for Law Enforcement Agencies, which will likely lead to reduced engagement from them.<ref>[https://gac.icann.org/contentMigrated/icann76-cancun-communique?language_id=1 ICANN76 Cancun Communique, GAC, ICANN.org]</ref> The GAC also noted the importance of maximizing voluntary participation in the system through potential incentive structures.
===UA===
===UA===
*[[EPDP on Internationalized Domain Names]] Team held two working sessions toward publishing the Phase 1 Initial Report focusing on top-level IDN gTLD definition and variant management.
*[[EPDP on Internationalized Domain Names]] Team held two working sessions toward publishing the Phase 1 Initial Report focusing on top-level IDN gTLD definition and variant management.
*ISPCP recommended making a UA roadmap for public resolvers<ref>[https://static.sched.com/hosted_files/icann76/82/TRANSC_I76CUN_Sat11Mar2023_GNSO-%20ISPCP%20Membership%20Meet%20%281%20of%202%29-en.pdf ISPCP Transcript, ICANN 76]</ref>
*ISPCP recommended making a UA roadmap for public resolvers<ref>[https://static.sched.com/hosted_files/icann76/82/TRANSC_I76CUN_Sat11Mar2023_GNSO-%20ISPCP%20Membership%20Meet%20%281%20of%202%29-en.pdf ISPCP Transcript, ICANN 76]</ref>
*The new Chair of the Universal Acceptance and Internationalized Domain Names Working Group briefed the GAC; reminded them of the upcoming UA Day 2023, which took place in 53 locations around the world on March 28, 2023; and said the EPDP on IDNs was expected to deliver an Initial Report in April 2023 and a Final Report by the end of the year.
===Transfer Policy Review===
===Transfer Policy Review===
The Transfer Policy Review PDP Working Group focused on Phase 2 (aka Group 2) Topics and discussed:<ref>[https://community.icann.org/display/TPRPDP/2023-03-11+ICANN76+Transfer+Policy+Review+PDP+WG+Call Transfer Policy Review WG Session 1, ICANN 76]</ref>
The Transfer Policy Review PDP Working Group focused on Phase 2 (aka Group 2) Topics and discussed:<ref>[https://community.icann.org/display/TPRPDP/2023-03-11+ICANN76+Transfer+Policy+Review+PDP+WG+Call Transfer Policy Review WG Session 1, ICANN 76]</ref>
*The GAC Public Safety Working Group ([[PSWG]]) advocated for improved measures to combat DNS Abuse, explained the importance of [[WHOIS]] data and mitigating DNS Abuse, shared U.K. and U.S. [[cybercrime]] statistics, and updated the GAC on [[DNS Abuse Responses|initiatives]] from the community.<ref>[https://gac.icann.org/contentMigrated/icann76-cancun-communique?language_id=1 ICANN76 Cancun Communique, GAC, ICANN.org]</ref>
*The GAC Public Safety Working Group ([[PSWG]]) advocated for improved measures to combat DNS Abuse, explained the importance of [[WHOIS]] data and mitigating DNS Abuse, shared U.K. and U.S. [[cybercrime]] statistics, and updated the GAC on [[DNS Abuse Responses|initiatives]] from the community.<ref>[https://gac.icann.org/contentMigrated/icann76-cancun-communique?language_id=1 ICANN76 Cancun Communique, GAC, ICANN.org]</ref>
*The GAC expressed concerns over the negotiations in relation to Recommendations 14 (ICANN should include provisions in the agreements to provide incentives, including financial incentives for registries, especially open registries, to adopt proactive anti-abuse measures<ref>[https://www.icann.org/en/system/files/files/cct-final-08sep18-en.pdf CCT Review 1 Final Report, pg98]</ref>) and 15 (ICANN should establish thresholds of abuse at which [[Contractual Compliance]] inquiries are automatically triggered, with a higher threshold at which registrars and registries are presumed to be in default of their agreements. For example, if the community determines that ICANN org itself is ill-suited or unable to enforce such provisions, then a DNS Abuse Dispute Resolution Policy (DADRP) should be considered as an additional means to enforce policies and deter DNS Security Abuse<ref>[https://www.icann.org/en/system/files/files/cct-final-08sep18-en.pdf CCT Review 1 Final Report, pg99]</ref>) from the [[First Competition, Consumer Trust, and Consumer Choice Review|Competition, Consumer Trust, and Consumer Choice Review]].
*The GAC expressed concerns over the negotiations in relation to Recommendations 14 (ICANN should include provisions in the agreements to provide incentives, including financial incentives for registries, especially open registries, to adopt proactive anti-abuse measures<ref>[https://www.icann.org/en/system/files/files/cct-final-08sep18-en.pdf CCT Review 1 Final Report, pg98]</ref>) and 15 (ICANN should establish thresholds of abuse at which [[Contractual Compliance]] inquiries are automatically triggered, with a higher threshold at which registrars and registries are presumed to be in default of their agreements. For example, if the community determines that ICANN org itself is ill-suited or unable to enforce such provisions, then a DNS Abuse Dispute Resolution Policy (DADRP) should be considered as an additional means to enforce policies and deter DNS Security Abuse<ref>[https://www.icann.org/en/system/files/files/cct-final-08sep18-en.pdf CCT Review 1 Final Report, pg99]</ref>) from the [[First Competition, Consumer Trust, and Consumer Choice Review|Competition, Consumer Trust, and Consumer Choice Review]].
*The Internet and Jurisdiction Policy Network explained to the GAC in detail its framework for [[DNS Abuse Responses]]
*The [[Internet and Jurisdiction Policy Network]] explained to the GAC in detail its framework for [[DNS Abuse Responses]]
The GAC reaffirmed the importance of increasing the number and geographical distribution of applications from underrepresented regions through the Applicant Support Program and its support for proposals to reduce or eliminate ongoing ICANN registry fees to expand financial support.
===DNSSEC===
===DNSSEC===
[[SSAC]] asked ICANN Board and Org to promote [[DNSSEC]] similarly to how it has approached UA. Specifically, [[Russ Mundy]] asked for an analysis of the gaps and requirements to accomplish widespread use of DNSSEC.<ref>[https://meetings.icann.org/sites/default/files/icann76-policy-outcome-report-10apr23-en.pdf ICANN76 Policy Outcomes Report, pg 19]</ref>
[[SSAC]] asked ICANN Board and Org to promote [[DNSSEC]] similarly to how it has approached UA. Specifically, [[Russ Mundy]] asked for an analysis of the gaps and requirements to accomplish widespread use of DNSSEC.<ref>[https://meetings.icann.org/sites/default/files/icann76-policy-outcome-report-10apr23-en.pdf ICANN76 Policy Outcomes Report, pg 19]</ref> The SSAC also held a workshop on DNSSEC about novel usages; proposals to solve bottlenecks; DNSSEC provision automation by registries, registrars, and handling multiple signing parties; and the challenges of blockchain-based naming systems for malware defenders.<ref>[https://meetings.icann.org/sites/default/files/icann76-policy-outcome-report-10apr23-en.pdf ICANN76 Policy Outcomes Report, pg36]</ref>
===Curative Rights===
===Curative Rights===
The GAC Consensus Advice on the [[EPDP for Specific Curative Rights Protections for IGOs]] aka "curative rights" called for a permanent pre-registration notification system. The ICANN Board does not support that approach and proposed an alternative post-registration notification system. The ICANN organization was remiss in delivering that alternative system and the board will consult with the GAC to determine if its curative rights are still consistent.<ref>ICANN76 policy outcome report, published 10 Apr 2023, pgs7-8</ref>
The ICANN Board said: The GAC Consensus Advice on the [[EPDP for Specific Curative Rights Protections for IGOs]] aka "curative rights" called for a permanent pre-registration notification system. The ICANN Board does not support that approach and proposed an alternative post-registration notification system. The ICANN organization was remiss in delivering that alternative system and the board will consult with the GAC to determine if its curative rights are still consistent.<ref>ICANN76 policy outcome report, published 10 Apr 2023, pgs7-8</ref>
The GAC advised the Board to approve the recommendations of the EPDP on Specific Curative Rights Protections for implementation and to maintain the current moratorium on the registration of IGO acronyms as domain names in New gTLDs presently in place until the full implementation of the recommendations of the EPDP on Specific Curative Rights Protections.
===ICANN-Wide Process Improvements===
===ICANN-Wide Process Improvements===
====Work Stream 2====
====Work Stream 2====
The [[GAC Working Group on Human Rights & International Law|HRILWG]] updated the [[GAC]] on the implementation of [[Work Stream 2]] (WS2) Recommendation 1 on diversity, including the work of the WS2 Community Coordination Group (CCG) on developing tools and reminded the GAC to make the Fiscal Year 2024 Additional Budget Request for sign language at [[ICANN Meetings]].
The [[GAC Working Group on Human Rights & International Law|HRILWG]] updated the [[GAC]] on the implementation of [[Work Stream 2]] (WS2) Recommendation 1 on diversity, including the work of the WS2 Community Coordination Group (CCG) on developing tools and reminded the GAC to make the Fiscal Year 2024 Additional Budget Request for sign language at [[ICANN Meetings]].<ref>[https://gac.icann.org/contentMigrated/icann76-cancun-communique?language_id=1 ICANN76 Cancun Communique, GAC, ICANN.org]</ref>
====Volunteer Appreciation====
====Volunteer Appreciation====
**to receive honest feedback from the multistakeholder community and the ICANN Board when its advice is not adopted.
**to receive honest feedback from the multistakeholder community and the ICANN Board when its advice is not adopted.
Matthew Shears proposed an interactive session to raise awareness of security from the SSAC perspective.
Matthew Shears proposed an interactive session to raise awareness of security from the SSAC perspective.
====[[PDP]]====
====[[PDP]]====
The ICANN Board asked the CSG about how to balance agility in policy development with accountability and transparency, to which they responded that they should allow the GNSO Guidance Process to work through applicant support first and then evaluate it as a mechanism, form expert working groups for specific problems, create Rapid Response Teams, and rely on limited scopes and small teams.
The ICANN Board asked the [[CSG]] about how to balance agility in policy development with accountability and transparency, to which they responded that they should allow the [[GNSO Guidance Process]] to work through applicant support first and then evaluate it as a mechanism, form expert working groups for specific problems, create Rapid Response Teams, and rely on limited scopes and small teams.
====ODPs====
====ODPs====
ALAC hosted a community-wide discussion of the efficacy of [[ODP]]s, asking:<ref>[https://community.icann.org/display/atlarge/At-Large+Meetings+-+Thursday%2C+16+March+2023 ALAC Community Discussion Agenda, ICANN 76]</ref>
ALAC hosted a community-wide discussion of the efficacy of [[ODP]]s, asking:<ref>[https://community.icann.org/display/atlarge/At-Large+Meetings+-+Thursday%2C+16+March+2023 ALAC Community Discussion Agenda, ICANN 76]</ref>
*The [[CEO Search Committee]] held a plenary listening session to set goals
*The [[CEO Search Committee]] held a plenary listening session to set goals
*ccNSO member [[Byron Holland]] raised concerns about not having a permanent [[ICANN President]] and CEO for up to a year.<ref>ICANN76 policy outcome report, published 10 Apr 2023, pg6</ref>
*ccNSO member [[Byron Holland]] raised concerns about not having a permanent [[ICANN President]] and CEO for up to a year.<ref>ICANN76 policy outcome report, published 10 Apr 2023, pg6</ref>
===SO/AC Process Improvements===
===SO/AC Process Improvements===
====GNSO====
The SOI Task Force team within the GNSO agreed on proposed changes to enhance representative transparency. However, some members are concerned they cannot disclose their clients’ identities.<ref>[https://opensrs.com/blog/icann76-recap/ ICANN76 Recap, OPENSRS]</ref> The Council Committee for Overseeing and Implementing Continuous Improvement (CCOICI) Working Group Self-Assessment (WGSA) into a single Recommendations Report about SOIs. The CCOICI integrated public comments and submitted its Recommendations Report to the Council on 5 January 2023.<ref>[https://community.icann.org/display/CCFOICI/Council+Committee+for+Overseeing+and+Implementing+Continuous+Improvement+Home CCOICI, Community, ICANN]</ref>
GAC Members were concerned about a proposed exception in the SOI that could permit GNSO participants to refrain from disclosing the identity of the entities they represent in GNSO working groups.
====GAC====
====GAC====
The GAC Operating Principles Evolution Working Group (GOPE WG) finalized its review of the Preliminary Analysis of GAC Operating Principles, which will be the basis for prioritizing the review of the GAC Operating Principles.
The GAC Operating Principles Evolution Working Group (GOPE WG) finalized its review of the Preliminary Analysis of GAC Operating Principles, which will be the basis for prioritizing the review of the GAC Operating Principles.<ref>[https://gac.icann.org/contentMigrated/icann76-cancun-communique?language_id=1 ICANN76 Cancun Communique, GAC, ICANN.org]</ref>
====ASO====
====ASO====