ICANN 76: Difference between revisions
No edit summary |
|||
| Line 20: | Line 20: | ||
*# ensure charter questions of the [[EPDP on Internationalized Domain Names]] impact the next Applicant Guidebook. | *# 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> | *[[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> | ||
===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]]. | ||
| Line 43: | Line 40: | ||
*Proposal of the Internet General Law in Peru<ref>[https://wb2server.congreso.gob.pe/spley-portal/#/expediente/2021/878 IGL in Peru] Accessed April 6, 2023</ref>; the ICANN Board plans to coordinate with other partner Internet governance organizations. | *Proposal of the Internet General Law in Peru<ref>[https://wb2server.congreso.gob.pe/spley-portal/#/expediente/2021/878 IGL in Peru] Accessed April 6, 2023</ref>; the ICANN Board plans to coordinate with other partner Internet governance organizations. | ||
*The [[ccNSO]] discussed getting more involved by developing an Internet Governance Liaison<ref>[https://static.sched.com/hosted_files/icann76/9c/TRANSC_I76CUN_Sat11Mar2023_ccNSO-%20Internet%20Governance%20Liaison%20Committee-en.pdf IGLC Session, ICANN 76]</ref> | *The [[ccNSO]] discussed getting more involved by developing an Internet Governance Liaison<ref>[https://static.sched.com/hosted_files/icann76/9c/TRANSC_I76CUN_Sat11Mar2023_ccNSO-%20Internet%20Governance%20Liaison%20Committee-en.pdf IGLC Session, ICANN 76]</ref> | ||
===DNS Abuse=== | |||
*A team of [[Registrar]] and [[Registry]] representatives are negotiating changes to the [[RAA]] and [[Registry Agreement]] (RA) with [[:Category:ICANN Staff|ICANN Staff]]. The revised contractual language will be published for comment by June 2023 (ICANN 77)<ref>[https://opensrs.com/blog/icann76-recap/ ICANN76 Recap, OPENSRS]</ref> | |||
*the ALAC, BC, and IPC sent a joint letter seeking consultation on the DNS abuse negotiations with the Contracted Parties (precedent from 2009 and | |||
2013). ICANN Board said Contracted Parties entered DNS abuse negotiations with a specific scope with ICANN Contractual Compliance for more enforcement tools. ICANN Board will consider conducting a listening session with the ICANN community. | |||
===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> | |||
===Process Improvements=== | |||
====[[PDP]]=== | |||
The ICANN Board asked the CSG about how to balance agility in policy development with accountability and transparency, to which they responded: | |||
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. | |||
===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 [gnso.icann.org] to the Council on 5 January 2023. | |||
===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> | ||
| Line 49: | Line 58: | ||
# When should outside expertise be brought in (such as system scoping)? | # When should outside expertise be brought in (such as system scoping)? | ||
# What would have been improved through additional community input without adding to the overall timing? | # What would have been improved through additional community input without adding to the overall timing? | ||
=== | ====IRT Process Improvements==== | ||
The ICANN Board asked the [[CPH]] about concrete steps for improving the [[Implementation Review Team]] process. Complexity is often a result of [[PDP]] scoping. The [[RySG]] responded that they plan to: more narrowly tailor their PDPs with a more clearly defined charter, have the early involvement of the ICANN Board and ICANN organization liaisons, include observations from the [[ODA]] during the PDP, and break up the IRT. The [[RrSG]] responded that it would be helpful to have a more regular cadence and detailed agendas for IRT work sessions, include default language for IRT work from the PDP, and escalate issues to the GNSO Council or ICANN Board.<ref>ICANN76 policy outcome report, published 10 Apr 2023, pgs9</ref> | |||
====[[:Category:Organizational Reviews|Reviews]]==== | |||
=====Holistic Review===== | |||
= | |||
===[[:Category:Organizational Reviews|Reviews]]=== | |||
====Holistic Review==== | |||
*[[ccNSO]] sought a progress update from the ICANN Board on the holistic review and expressed concerns with its vague and undefined scope.<ref>ICANN76 policy outcome report, published 10 Apr 2023, pg5</ref> | *[[ccNSO]] sought a progress update from the ICANN Board on the holistic review and expressed concerns with its vague and undefined scope.<ref>ICANN76 policy outcome report, published 10 Apr 2023, pg5</ref> | ||
====Second NomCom Organizational Review==== | =====Second NomCom Organizational Review===== | ||
The ICANN Board accepted the [[Second NomCom Organizational Review]] | The ICANN Board accepted the [[Second NomCom Organizational Review]] | ||
===Prioritization=== | ====Prioritization==== | ||
* ICANN Chief Financial Officer [[Xavier Calvez]] said the [[prioritization]] pilot had been a success and ICANN Org planned to integrate prioritization across ICANN.ref>ICANN76 policy outcome report, published 10 Apr 2023, pg5</ref> | * ICANN Chief Financial Officer [[Xavier Calvez]] said the [[prioritization]] pilot had been a success and ICANN Org planned to integrate prioritization across ICANN.ref>ICANN76 policy outcome report, published 10 Apr 2023, pg5</ref> | ||
===CEO Search=== | ====CEO Search==== | ||
*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> | ||
===Thanks=== | ===Thanks=== | ||
* thanked [[Manal Ismail]] for her service to the ICANN Board and [[Jonathan Spring]] for his service to the [[SSAC]].<ref>[https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-regular-meeting-of-the-icann-board-16-03-2023-en#section1 ICANN Board Resolutions, March 16, 2023]</ref> | * thanked [[Manal Ismail]] for her service to the ICANN Board and [[Jonathan Spring]] for his service to the [[SSAC]].<ref>[https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-regular-meeting-of-the-icann-board-16-03-2023-en#section1 ICANN Board Resolutions, March 16, 2023]</ref> | ||