Jump to content

ICANN 59: Difference between revisions

From ICANNWiki
← Older edit
VisualWikitext
Jessica (talk | contribs)
Bureaucrats, Check users, lookupuser, Administrators, translator
14,952 edits
Christiane (talk | contribs)
Bureaucrats, steward, Administrators, translator
3,206 edits
m Christiane moved page ICANN 59 - Johannesburg to ICANN 59 over redirect: Standardize
 
(8 intermediate revisions by one other user not shown)
Line 11: Line 11:
| historicalimport =
| historicalimport =
}}
}}
 
'''ICANN 59''' was a [[ICANN Meetings|ICANN Meeting]] held in Johannesburg, South Africa, at which [[Hiro Hotta]], [[.jp]], and [[Patricio Poblete]], [[.cl]]. received the [[ICANN Multistakeholder Ethos Award]].<ref>[https://meetings.icann.org/en/johannesburg59/post-icann59-policy-report-13jul17-en Post-ICANN 59 Policy Report]</ref> The first [[ICANN Empowered Community]] Forum was held at this meeting.
'''ICANN 59''' was a [[ICANN Meetings|ICANN Meeting]] held in Johannesburg, South Africa, at which [[Hiro Hotta]] and [[Patricio Poblete]] received the [[Multistakeholder Ethos Award]].<ref>[https://meetings.icann.org/en/johannesburg59/post-icann59-policy-report-13jul17-en Post-ICANN 59 Policy Report]</ref>


It was the 3rd return to South Africa after [[ICANN 21]] in Cape Town and [[ICANN 47]] in Durban.<ref>[https://meetings.icann.org/en/calendar ICANN Meeting Calendar]</ref>
It was the 3rd return to South Africa after [[ICANN 21]] in Cape Town and [[ICANN 47]] in Durban.<ref>[https://meetings.icann.org/en/calendar ICANN Meeting Calendar]</ref>
Line 20: Line 19:
===ccNSO===
===ccNSO===
* 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 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 [[Empowered Community|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 Guidelines Review Committee (GRC), formed to structure the decision-making of the ccNSO to become a [[ICANN Empowered Community|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 [https://www.icann.org/en/announcements/details/proposed-fundamentals-bylaws-changes-to-move-the-board-governance-committees-reconsideration-process-responsibilities-to-another-board-committee-31-3-2017-en Fundamental Bylaw change proposed by ICANN Board].
* The ccNSO Council approved [https://www.icann.org/en/announcements/details/proposed-fundamentals-bylaws-changes-to-move-the-board-governance-committees-reconsideration-process-responsibilities-to-another-board-committee-31-3-2017-en Fundamental Bylaw change proposed by ICANN Board].
 
* The ccNSO Council initiated the [[CcNSO Policy Development Process - Retirement|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===
* 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 [[GSE|global stakeholder engagement]].
===ALAC===
* The ALAC discussed [[Global Public Interest]] issues like nTLD consumer safeguards with [[Bryan Schilling]], the [[DAAR|Domain Abuse Activity Reporting Project]], and the [[First Competition, Consumer Trust, and Consumer Choice Review]].
* the ALAC discussed the method and timeline for developing the At-Large Review Recommendations Feasibility Assessment and Implementation Plan
* 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.
===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
===RSSAC===
The RSSAC gave presentations on RSSAC026: RSSAC Lexicon and RSSAC027: May 2017 Workshop Report
==References==
==References==
{{reflist}}
{{reflist}}

Latest revision as of 21:42, 11 April 2024

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

RSSAC[edit | edit source]

The RSSAC gave presentations on RSSAC026: RSSAC Lexicon and RSSAC027: May 2017 Workshop Report

References[edit | edit source]

Address Supporting Organization. Advises the Board with respect to policy issues relating to the operation, assignment, and management of Internet addresses (ICANN Bylaws).

Country Code Names Supporting Organization. Develops and recommends to the Board global policies relating to country-code top-level domains (ICANN Bylaws).

Generic Names Supporting Organization. Develops and recommends to the Board substantive policies relating to generic top-level domains and other responsibilities set forth in the Bylaws (ICANN Bylaws).

Governmental Advisory Committee. Considers and provides advice on the activities of ICANN as they relate to concerns of governments, particularly matters where there may be an interaction between ICANN's policies and various laws and international agreements or where they may affect public policy issues (ICANN Bylaws).

At-Large Advisory Committee. Considers and provides advice on the activities of ICANN related to the interests of individual Internet users (ICANN Bylaws). Not to be confused with the Non-Commercial Stakeholder Group.

Root Server System Advisory Committee. Advises the ICANN community and Board on matters relating to the operation, administration, security, and integrity of the Internet's Root Server System (ICANN Bylaws).

Retrieved from "https://icannwiki.org/index.php?title=ICANN_59&oldid=1349391"