Jump to content

ICANN 76: Difference between revisions

From ICANNWiki
Jessica (talk | contribs)
Jessica (talk | contribs)
No edit summary
Line 25: Line 25:
**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>
===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.<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
Line 47: Line 49:
# 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===
* 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===
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>


==References==
==References==


[[Category:ICANN Meetings]]
[[Category:ICANN Meetings]]

Revision as of 16:24, 7 April 2023

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,

Sub Pro[edit | edit source]

WDS[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:[5]

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

Geopolitical & Regulatory Developments[edit | edit source]

  • The impacts of NIS2
  • WSIS+20[8]
  • Proposal of the Internet General Law in Peru[9]

ODPs[edit | edit source]

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

  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 that they cannot disclose their clients’ identities.[12]

References[edit | edit source]