Difference between revisions of "ICANN 76"

From ICANNWiki
Jump to navigation Jump to search
Line 30: Line 30:
 
* [[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>
 
===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>  
Line 52: Line 53:
 
===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===
+
===GNSO Council===
The SOI Task Force team within the GNSO agreed on proposed changes to enhance representative transparency. However, some members are concerned that they cannot disclose their clients’ identities.<ref>[https://opensrs.com/blog/icann76-recap/ ICANN76 Recap, OPENSRS]</ref>
+
====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.
 
==AOB==
 
==AOB==
 
The ICANN Board
 
The ICANN Board

Revision as of 17:15, 7 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

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

Topics

At ICANN 76,

Sub Pro

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

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

Transfer Policy Review

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

  • The impacts of NIS2
  • WSIS+20[9]
  • Proposal of the Internet General Law in Peru[10]
  • The ccNSO discussed getting more involved by developing an Internet Governance Liaison[11]

ODPs

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

GNSO Council

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

AOB

The ICANN Board

References