Jump to content

ICANN 59: Difference between revisions

From ICANNWiki
Jessica (talk | contribs)
No edit summary
Jessica (talk | contribs)
No edit summary
Line 33: Line 33:
* ALAC had a joint session with the GNSO ALAC liaison, [[Cheryl Langdon-Orr]], about the [[GDPR]]
* ALAC had a joint session with the GNSO ALAC liaison, [[Cheryl Langdon-Orr]], about the [[GDPR]]
* ALAC met with senior staff from the [[GSE|Global Stakeholder Engagement]] and [[Public Responsibility]] Support (PRS) teams about growing participation in ICANN policymaking in Africa.
* ALAC met with senior staff from the [[GSE|Global Stakeholder Engagement]] and [[Public Responsibility]] Support (PRS) teams about growing participation in ICANN policymaking in Africa.
===GAC===
GAC focused on
* clarifying the definition of purpose for collection and use of RDS data elements
* Exploring solutions to address data protection requirements
* aligning deliveries of the Next Generation RDS policy development process with the timing of changes to regulations
==References==
==References==
{{reflist}}
{{reflist}}

Revision as of 19:30, 6 October 2021

Dates: 26-29 June 2017
Location: Johannesburg, South Africa
Venue: Sandton Convention Centre
Registration: Registration


ICANN 59 was a ICANN Meeting held in Johannesburg, South Africa, at which Hiro Hotta, .jp, and Patricio Poblete, .cl. received the ICANN Multistakeholder Ethos Award.[1] The first ICANN Empowered Community Forum was held at this meeting.

It was the 3rd return to South Africa after ICANN 21 in Cape Town and ICANN 47 in Durban.[2]

Sessions[edit | edit source]

ASO[edit | edit source]

  • ITEMS International presented the Draft Final Report of the organizational review of the ASO.

ccNSO[edit | edit source]

  • The Cross-Community Working Group on the Use of Country and Territory Names as Top-Level Domains (CWG-UCTN) received support for the recommendation to close the working group and organize a new effort with a broader mandate embedded in a broader context.
  • The ccNSO Guidelines Review Committee (GRC), formed to structure the decision-making of the ccNSO to become a Decisional Participant, found out that the ccNSO decision-making process is incompatible with the timelines of the ICANN Bylaws Approval Action procedure. The GRC proposed 3 solutions, of which the ccNSO Council decided that both the Approval Action process and the Rejection Action petition process should be subject to the request of a members’ ratification vote (under the ccNSO 2004 rules).
  • The ccNSO Council approved Fundamental Bylaw change proposed by ICANN Board.
  • The ccNSO Council initiated the third ccNSO Policy Development Process concerning the Retirement of ccTLDs and review mechanisms for decisions relating to the delegation, transfer, revocation, and retirement of ccTLDs.

GNSO[edit | edit source]

  • The GNSO Council confirmed the leadership team and approved the process and criteria for the GNSO Standing Selection Committee (SSC), which it established to select candidates for ICANN review teams and Empowered Community administration representatives.
  • the GNSO held a joint session with the ccNSO about Empowered Community Administration processes, procedures, and timelines; the review of the Customer Standing Committee charter; and the FY19 Public Technical Identifiers (PTI) budget.
  • The GAC and GNSO's joint session covered Red Cross/Red Crescent and International Governmental Organizations, GAC PDP engagement, and the GNSO review of the GAC Copenhagen Communiqué.
  • GNSO WG leaders met to discuss Key Signing Key Rollover, the PTI budget, and global stakeholder engagement.

ALAC[edit | edit source]

GAC[edit | edit source]

GAC focused on

  • clarifying the definition of purpose for collection and use of RDS data elements
  • Exploring solutions to address data protection requirements
  • aligning deliveries of the Next Generation RDS policy development process with the timing of changes to regulations

References[edit | edit source]