Changes

**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;  

**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

** explained that before a launch date is set for the next round of new gTLDs, ICANN must

#  process the 38 pending SubPro recommendations.

*#  process the 38 pending SubPro recommendations.

#  determine an expedited approach for the [[Implementation Review Team]] (IRT) process  

*#  determine an expedited approach for the [[Implementation Review Team]] (IRT) process  

# complete and apply the outcomes of the [[Closed Generics]] Facilitated Dialogue

*# 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.

*# 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>

====IRT Process Improvements====

====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>  

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>

 

===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]].