Difference between revisions of "ICANN 76"

From ICANNWiki
Jump to navigation Jump to search
Line 1: Line 1:
 +
[[File:Cancun76 banner.png|center|100px x 500px]]
 +
 
{{ICANNMeetings|
 
{{ICANNMeetings|
| logo            = ICANN76 Zoom Backgrounds dark 02 icann-meeting.jpg
+
| logo            = blank.png
 
| dates          = 11-16 March 2023
 
| dates          = 11-16 March 2023
 
Community Forum
 
Community Forum
Line 16: Line 18:
 
From 27 February to 1 March, there will be sessions<ref>[https://www.icann.org/en/announcements/details/icann76-prep-week-schedule-now-available-15-02-2023-en ICANN 76 Prep Week, ICANN Announcements]</ref> on the  
 
From 27 February to 1 March, there will be sessions<ref>[https://www.icann.org/en/announcements/details/icann76-prep-week-schedule-now-available-15-02-2023-en ICANN 76 Prep Week, ICANN Announcements]</ref> on the  
 
* Implementation of [[CCWG-Accountability Work Stream 2|Work Stream 2]] Recommendations, phase 2 of the [[CCWG-Accountability]] process. Work Stream 2 focused on mechanisms following the completion of the [[IANA Functions Stewardship Transition]]
 
* Implementation of [[CCWG-Accountability Work Stream 2|Work Stream 2]] Recommendations, phase 2 of the [[CCWG-Accountability]] process. Work Stream 2 focused on mechanisms following the completion of the [[IANA Functions Stewardship Transition]]
* [[Coalition for Digital Africa]]
+
*[[Coalition for Digital Africa]]
* updates on or from [[Universal Acceptance]], [[Finance|Planning and Finance]], [[GNSO]] policy work<ref>[https://gnso.icann.org/en/group-activities/active Active Group Activities, GNSO]</ref>, [[Contractual Compliance]], [[SUBPRO]], [[Name_Collision#NCAP|NCAP]] study 2, and [[IDN]]s
+
*updates on or from [[Universal Acceptance]], [[Finance|Planning and Finance]], [[GNSO]] policy work<ref>[https://gnso.icann.org/en/group-activities/active Active Group Activities, GNSO]</ref>, [[Contractual Compliance]], [[SUBPRO]], [[Name_Collision#NCAP|NCAP]] study 2, and [[IDN]]s
 
==Topics==  
 
==Topics==  
 
===Sub Pro (aka next round of new TLDs)===  
 
===Sub Pro (aka next round of new TLDs)===  
* the [[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;
 
**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;
* [[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>
===WDS (aka [[SSAD]])===
+
===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>  
 
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>  
 
===UA===
 
===UA===
* [[ICANN Organization]] and the [[UASG]] outlined progress on [[Universal Acceptance|UA]]-readiness and [[IDN]]s
+
*[[ICANN Organization]] and the [[UASG]] outlined progress on [[Universal Acceptance|UA]]-readiness and [[IDN]]s
* [[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>
 
===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>  
* reducing the cost to reduce barriers to entry; introducing formality, such as accreditation; whether registrants are getting what they need – what current channels are available – settlement, courts (costly), through registrar (TDRP);  
+
*reducing the cost to reduce barriers to entry; introducing formality, such as accreditation; whether registrants are getting what they need – what current channels are available – settlement, courts (costly), through registrar (TDRP);
* whether to adjust the TDRP to accommodate registrants, which would require substantial changes or a new separate system.
+
*whether to adjust the TDRP to accommodate registrants, which would require substantial changes or a new separate system.
* gaming or potential gaming of TDRP if available to registrants – could be adjusted for that.
+
*gaming or potential gaming of TDRP if available to registrants – could be adjusted for that.
* This WG focuses on transfers between contracted parties, so disputes among registrants could be out of scope.
+
*This WG focuses on transfers between contracted parties, so disputes among registrants could be out of scope.
* if out of scope the WG could make a recommendation to [[GNSO Council]] that a process for registrants could be considered separately.
+
*if out of scope the WG could make a recommendation to [[GNSO Council]] that a process for registrants could be considered separately.
* Issues raised by [[George Kirikos]] (limitation period of 12 months; with Temp Spec, the Losing Registrar can win 100 percent of the TDRP disputes because the Gaining Registrar doesn’t have access to the Whois info for the FOA because of GDPR; long registration period creating confusion with ownership of the domain name in case of an invalid transfer)<ref>[https://community.icann.org/display/TPRPDP/2023-03-12+ICANN76+Transfer+Policy+Review+PDP+WG+Call Transfer Policy Review WG Session 2, ICANN 76]</ref>
+
*Issues raised by [[George Kirikos]] (limitation period of 12 months; with Temp Spec, the Losing Registrar can win 100 percent of the TDRP disputes because the Gaining Registrar doesn’t have access to the Whois info for the FOA because of GDPR; long registration period creating confusion with ownership of the domain name in case of an invalid transfer)<ref>[https://community.icann.org/display/TPRPDP/2023-03-12+ICANN76+Transfer+Policy+Review+PDP+WG+Call Transfer Policy Review WG Session 2, ICANN 76]</ref>
* Gap Analysis - Reversal of Inter-Registrar Transfers<ref>[https://docs.google.com/document/d/1Mq-Zu-fTdu4xrI1h1YPB1ITGRTxAp2gKzef7cTkgnNg/edit Gap Analysis - Reversal of Inter-Registrar Transfers] Accessed April 6, 2023</ref>
+
*Gap Analysis - Reversal of Inter-Registrar Transfers<ref>[https://docs.google.com/document/d/1Mq-Zu-fTdu4xrI1h1YPB1ITGRTxAp2gKzef7cTkgnNg/edit Gap Analysis - Reversal of Inter-Registrar Transfers] Accessed April 6, 2023</ref>
 
===Geopolitical & Regulatory Developments===
 
===Geopolitical & Regulatory Developments===
 
* The impacts of [[NIS2]]
 
* The impacts of [[NIS2]]
* [[WSIS]]+20<ref>[https://itp.cdn.icann.org/en/files/government-engagement-ge/ge-012-13-03-2023-en.pdf ICANN GE on WSIS+20]</ref>
+
*[[WSIS]]+20<ref>[https://itp.cdn.icann.org/en/files/government-engagement-ge/ge-012-13-03-2023-en.pdf ICANN GE on WSIS+20]</ref>
* 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>
 
===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>
# What criteria should determine when a policy discussion is to be sent to ICANN org vs the ICANN community?
+
#What criteria should determine when a policy discussion is to be sent to ICANN org vs the ICANN community?
# Could changes to the policy development process decrease the burden on the org during an Operational Design Phase?
+
#Could changes to the policy development process decrease the burden on the org during an Operational Design Phase?
 
# 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?
 
===DNS Abuse===
 
===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>
+
*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>
 
===SOIs===
 
===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.
 
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.
 
===[[:Category:Organizational Reviews|Reviews]]===
 
===[[:Category:Organizational Reviews|Reviews]]===
 
====Holistic Review====
 
====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===
Line 64: Line 66:
 
*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>
  
 
==References==
 
==References==
  
 
[[Category:ICANN Meetings]]
 
[[Category:ICANN Meetings]]
 +
 +
<references />

Revision as of 18:14, 11 April 2023

100px x 500px


Blank.png
Dates: 11-16 March 2023

Community Forum

Location: Cancun, Mexico
Venue: Cancun Center
Website: https://76.schedule.icann.org/

ICANN 76 is a Community Forum that will happen in Cancun, Mexico from March 11 through 16 and will have a hybrid format. Registration is available here.

Prep Week[edit | edit source]

From 27 February to 1 March, there will be sessions[1] on the

Topics[edit | edit source]

Sub Pro (aka next round of new TLDs)[edit | edit source]

  • 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;
  • 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).[3]

WDS (aka SSAD)[edit | edit source]

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.[4]

UA[edit | edit source]

Transfer Policy Review[edit | edit source]

The Transfer Policy Review PDP Working Group focused on Phase 2 (aka Group 2) Topics and discussed:[6]

  • reducing the cost to reduce barriers to entry; introducing formality, such as accreditation; whether registrants are getting what they need – what current channels are available – settlement, courts (costly), through registrar (TDRP);
  • whether to adjust the TDRP to accommodate registrants, which would require substantial changes or a new separate system.
  • gaming or potential gaming of TDRP if available to registrants – could be adjusted for that.
  • This WG focuses on transfers between contracted parties, so disputes among registrants could be out of scope.
  • if out of scope the WG could make a recommendation to GNSO Council that a process for registrants could be considered separately.
  • Issues raised by George Kirikos (limitation period of 12 months; with Temp Spec, the Losing Registrar can win 100 percent of the TDRP disputes because the Gaining Registrar doesn’t have access to the Whois info for the FOA because of GDPR; long registration period creating confusion with ownership of the domain name in case of an invalid transfer)[7]
  • Gap Analysis - Reversal of Inter-Registrar Transfers[8]

Geopolitical & Regulatory Developments[edit | edit source]

  • The impacts of NIS2
  • WSIS+20[9]
  • Proposal of the Internet General Law in Peru[10]; the ICANN Board plans to coordinate with other partner Internet governance organizations.
  • The ccNSO discussed getting more involved by developing an Internet Governance Liaison[11]

ODPs[edit | edit source]

ALAC hosted a community-wide discussion of the efficacy of ODPs, asking:[12]

  1. What criteria should determine when a policy discussion is to be sent to ICANN org vs the ICANN community?
  2. Could changes to the policy development process decrease the burden on the org during an Operational Design Phase?
  3. When should outside expertise be brought in (such as system scoping)?
  4. What would have been improved through additional community input without adding to the overall timing?

DNS Abuse[edit | edit source]

SOIs[edit | edit source]

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.[14] * 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.

Reviews[edit | edit source]

Holistic Review[edit | edit source]

  • ccNSO sought a progress update from the ICANN Board on the holistic review and expressed concerns with its vague and undefined scope.[15]

Second NomCom Organizational Review[edit | edit source]

The ICANN Board accepted the Second NomCom Organizational Review

Prioritization[edit | edit source]

  • 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[edit | edit source]

Thanks[edit | edit source]

References[edit | edit source]