Difference between revisions of "ICANN 76"

From ICANNWiki
Jump to navigation Jump to search
Line 24: Line 24:
 
**accepted the [[Second NomCom Organizational Review]]; and  
 
**accepted the [[Second NomCom Organizational Review]]; and  
 
**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>
==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.
  
==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);  
Line 37: Line 37:
 
* 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===
 +
* The impacts of [[NIS2]]
 +
*
 
==References==
 
==References==
  
 
[[Category:ICANN Meetings]]
 
[[Category:ICANN Meetings]]

Revision as of 19:09, 6 April 2023

ICANN76 Zoom Backgrounds dark 02 icann-meeting.jpg
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]

At ICANN 76,

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

  • 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)[5]
  • Gap Analysis - Reversal of Inter-Registrar Transfers[6]

Geopolitical & Regulatory Developments[edit | edit source]

  • The impacts of NIS2

References[edit | edit source]