Joint SO/AC Working Group (WG) Charter

Similar documents
GNSO WHOIS Survey Drafting Team (WSDT) Charter

DRAFT WORKING GROUP CHARTER

DRAFT WORKING GROUP CHARTER

Standing Selection Mailing list archives: Committee Mailing List:

Working Group Charter

Proposed Next Steps Readiness for post-transition Bylaws 15 May 2018

The Governmental Advisory Committee

GNSO Working Session on the CWG Rec6 Report. Margie Milam 4 December 2010

New gtld Subsequent Procedures PDP WG Face-to- Face Session (Work Track 5) ICANN60 1 November 2017

Issues Report IDN ccpdp 02 April Bart Boswinkel Issue Manager

Submission of Adopted GNSO Council Review of the Johannesburg GAC Communiqué

Amended Charter of the Customer Standing Committee (CSC) Date of Adoption from ccnso and GNSO Councils: 27 June 2018 version 2

Role of Governments in Internet Governance. MEAC-SIG Cairo 2018

August The Board looks forward to the community discussion of this report.

The Who, What, Why, How and When of the Rejection Action Process

21 December GNSO Council Review of the Hyderabad GAC Communiqué. From: James Bladel, GNSO Chair To: Steve Crocker, ICANN Board

Final GNSO Issue Report on the Protection of International Organization Names in New gtlds

ICANN Policy Update - Dakar

At-Large Improvements Work Team D

For GNSO Consideration: Uniform Rapid Suspension System (URS) October 2009

(a) A number of Constituencies, where applicable, organized within the Stakeholder Groups as described in Section 11.5;

GNSO Council Open Mee0ng 7 December 2010

Agenda and resolutions ccnso Council Meeting 18 January 2018

GNSO Report. Dr Bruce Tonkin Chair, GNSO Council ICANN Board Public Forum Marrakech, June 28, 2006

Background to and Status of Work on Protections for Names and Acronyms of the Red Cross movement and International Governmental Organizations (IGOs)

IGO/INGO Identifiers Protection Policy Implementation. Meeting with the IRT ICANN October 2015

Agenda. New gtld Subsequent Procedures PDP WG Avri Doria and Jeff Neuman. Introduction and Timeline Eleeza Agopian

Welcome to Pre-ICANN62 Policy Webinar PRE-ICANN63 POLICY OPEN HOUSE 11 OCTOBER 2018

SUNDAY, NOVEMBER 6, 2016 MINUTES 15:15 16:45 LOCAL IN-PERSON MEETING. MEETING IPC Public Meeting, Part 1 CHAIR FOR MEETING MINUTES TAKEN BY

Final Issue Report on IGO-INGO Access to the UDRP & URS Date: 25 May 2014

From: Rafik Dammak Date: Friday, October 19, 2018 To: Cherine Chalaby Subject: NCSG Comment on UAM

Introduction to the Revised GNSO Policy Development Process. By Marika Konings

ccnso Council Telephone Conference 12 June 2012

Insert title here (75 characters maximum) PRE-ICANN60 POLICY OPEN HOUSE

Internet Service Provider & Connectivity Provider Constituency. Confirmation of Status & Request for Charter Renewal

Report on Implementation of GNSO New GTLD Recommendation #6

ICANN GAC and GAC Capacity building workshops

Attendance list is available at:

Business Constituency Charter (v3.0)

At-Large Advisory Committee Statement.

NEW GENERIC TOP-LEVEL DOMAIN NAMES ( gtld ) DISPUTE RESOLUTION PROCEDURE OBJECTION FORM TO BE COMPLETED BY THE OBJECTOR

2- Sep- 13. Dear ICANN and Economist Intelligence Unit (EIU), Re: Community Priority Evaluation Guidelines

BYLAWS FOR INTERNET CORPORATION FOR ASSIGNED NAMES AND NUMBERS A California Nonprofit Public-Benefit Corporation

INDEPENDENT REVIEW PROCESS INTERNATIONAL CENTRE FOR DISPUTE RESOLUTION

11:00 Los Angeles; 14:00 Washington; 19:00 London; 23:00 Islamabad; (Thursday 28 June) 03:00 Tokyo; 04:00 Hobart

Workshop on the Current State of the UDRP

Name: Byron Holland. Organization: Country Code Names Supporting Organisation Council (ccnso Council) Submission ID: 49

March Getting the best out of the BBC for licence fee payers

NGPC Agenda 28 September 2013

This Guidance applies to complaints where the Complaint Form was received between 01/03/13 and 08/07/15.

26 th Annual Intellectual Property Law Conference

NTSA CUSTOMER COMPLAINT HANDLING PROCEDURE JUNE 2016

Council Telephone Conference 11 th December 2008

ccnso Council Telephone Conference 11 December 2014

ccnso Council Meeting Beijing 10 April 2013

GAC Communiqué Buenos Aires, Argentina

CHAPTER 14 CONSULTATIONS AND DISPUTE SETTLEMENT. Article 1: Definitions

1. Scope of WIPO Rules for New gtld Dispute Resolution in Relation to Procedure

EUROPEAN COMMISSION Directorate-General for Communications Networks, Content and Technology

OpenID Process Document

ISO National Mirror Committee Training

RESOLUTION: OF THE ANTELOPE PROPERTY OWNERS ASSOCIATION, INC. REGARDING POLICIES AND PROCEDURES FOR COVENANT AND RULE ENFORCEMENT

Policy Development Process in RIPE

EHRA NON-FACULTY GRIEVANCE PROCEDURES OF THE UNIVERSITY OF NORTH CAROLINA AT CHAPEL HILL

PARTICIPATION IN NATIONAL MIRROR COMMITTEES AND ISO STANDARDS DEVELOPMENT COMMITTEES

The Development and Revision of FSC Normative Documents FSC-PRO V3-1 EN

Reconsideration Request by Ruby Pike, LLC. Ruby Pike, LLC, as a party adversely affected by an ICANN action...

Fisheries and Aquaculture Standards Revision Process Procedures Contents

ccnso Council Meeting Costa Rica 14 March 2012

ccnso Council Meeting Los Angeles 15 October 2014

2016 Nominating Committee Report Card #1 October 2015 Date: 30 October 2015

RULES OF PROCEDURE. NAESB Operating Practices as approved via Board Resolution September 11, 2015 Page 1

Revised ICANN Procedure For Handling WHOIS Conflicts with Privacy Law

Global Sustainability Standards Board Due Process Protocol October 2018

Texas Reliability Entity Standards Development Process

The Rules of Parliamentary Procedure Model United Nations Turkey Conference Antalya, March 2015

OFFICE OF EQUITY & DIVERSITY

ccnso Council Meeting Marrakech 9 March 2016

INTERNATIONAL CENTRE FOR DISPUTE RESOLUTION (ICDR) Independent Review Panel CASE #

ASIS INTERNATIONAL STANDARDS & GUIDELINES. September 2015

OCC Bulletin : Updated Guidance on Bank Enforcement Actions

MSC Standard Setting Procedure

SUMMARY OF PROCEDURES AT BOARD MEETINGS AND RULES OF ORDER

OPERATING PROCEDURES FOR ASME ADMINISTERED U.S. TECHNICAL ADVISORY GROUPS FOR ISO ACTIVITIES

ccnso Council Call 16 th September 2008

REPORT UNDER THE FREEDOM OF INFORMATION AND PROTECTION OF PRIVACY ACT CASE CITY OF WINNIPEG ACCESS COMPLAINT: REFUSAL OF ACCESS

RESOLUTION OF THE TRES VALLES WEST OWNERS ASSOCIATION REGARDING POLICIES AND PROCEDURES FOR COVENANT AND RULE ENFORCEMENT

GSA Federal Advisory Committee Act Fundamentals

Policy Development Process in RIPE

ICANN s Contractual Compliance Program. Tuesday, 25 October 2011

Summary of Changes to Registry Agreement for New gtlds. (Proposed Final version against v.4)

ccnso Council Meeting San Francisco 16 March 2011

Guideline: ccnso Procedure for the Exercise of the Empowered Community s rights to Reject Specified Actions

Update to Module 2: Geographical Names

Operating Procedures for ATIS Forums and Committees

Reliability Standards Development Procedures

NERC s Implementation of the Process Improvements and Compliance Findings Related to the Independent Evaluation of NERC s Standards Process Manual

Office of the Compliance Officer and Community Liaison (COCL)

TRADEMARK CLEARINGHOUSE

1. Executive Summary. 2 Ibid at page Ibid.

Transcription:

Joint SO/AC Working Group (WG) Charter WG Name: Consumer Choice, Competition and Innovation Working Group (CCI) Section I: Working Group Identification Chartering Organization(s): Charter Approval Date: Name of WG Chair: Name(s) of Appointed Liaison(s): WG Workspace URL: WG Mailing List: GNSO Council, ALAC, CCNSO and GAC (as applicable) [Interim Chair- Rosemary Sinclair] Rosemary Sinclair {Doc1} Important Document {Doc2} Links: {Doc3} {Doc4} Section II: Mission, Purpose, and Deliverables Mission & Scope: The WG aims to develop a report for consideration by SOs/ACs s in developing their response to the request arising from the following Board resolution (2010.12.10.30): Whereas, the area of consumer choice, competition and innovation is one of the strategic areas for ICANN in the 2010 to 2013 strategy plan <http://www.icann.org/en/strategic-plan/strategicplan-2010-2013-19feb10-en.pdf>. Whereas, ICANN has committed to promoting competition, consumer trust and consumer choice in the Affirmation of Commitments <http://www.icann.org/en/documents/affirmation-ofcommitments-30sep09-en.htm>. Whereas, if and when new gtlds (whether in ASCII or other language character sets) have been in operation for one year, ICANN has committed to organize a review that will examine the extent to which the introduction or expansion of gtlds has promoted competition, consumer trust and consumer choice. Resolved (2010.12.10.30), the ICANN Board requests advice from the ALAC, GAC, GNSO and ~ 1 ~

ccnso on establishing the definition, measures, and three year targets for those measures, for competition, consumer trust and consumer choice in the context of the domain name system, such advice to be provided for discussion at the ICANN International Public meeting in San Francisco from 13-18 March 2011. Objectives & Goals: To produce a report to be given to each of the AC/SOs for their consideration. The Working Group Report could be considered by GNSO, ccnso, GAC and ALAC in forwarding advice to the ICANN in response to the Board Resolution (2010.12.10.30). Each AC/SO may act independently on the Working Group Report, and may endorse all, part, or none of the report findings.. Deliverables & Timeframes: The CCI WG is expected to carry out the activities identified in this Charter in order to produce an Update Report to the GNSO Council by the ICANN Dakar Meeting. Section III: Formation, Staffing, and Organization Membership Criteria: The CCI WG will be open to all interested in participating from the GNSO, CCNSO, At-Large, and GAC. Group Formation, Dependencies, & Dissolution: It is desired that this WG be formed as a Joint Working Group, with members of the GNSO, CCNSO, At-Large, and GAC participate, assuming that each such group approves of the terms of this Charter as specified in Section II above. If this Charter is not approved by such SO/ACs, the CCI WG should continue to proceed as a GNSO chartered Working Group to produce the Report. Working Group Roles, Functions, & Duties: The CCI WG shall not communicate directly with the ICANN Board regarding its work product developed under this Charter. The ICANN Staff assigned to the CCI WG will fully support the work of the committee as directed by the Chair including meeting support, document drafting, editing and distribution and other substantive contributions when deemed appropriate. Staff assignments to the CCI WG : GNSO Secretariat 1 ICANN policy staff member- (Margie Milam) ~ 2 ~

The standard WG roles, functions & duties shall be applicable as specified in Section 2.2 of the Working Group Guidelines. The CCI-WG shall follow the GNSO Working Group Guidelines. Statements of Interest (SOI) Guidelines: Each member of the CCI-WG from the GNSO is required to submit an SOI in accordance with Section 5 of the GNSO Operating Procedures. Section IV: Rules of Engagement Decision-Making Methodologies: {Note: The following material was extracted from the Working Group Guidelines, Section 3.6. If a Chartering Organization wishes to deviate from the standard methodology for making decisions or empower the WG to decide its own decision-making methodology, this section should be amended as appropriate}. The Chair will be responsible for designating each position as having one of the following designations: Full consensus - when no one in the group speaks against the recommendation in its last readings. This is also sometimes referred to as Unanimous Consensus. Consensus - a position where only a small minority disagrees, but most agree. [Note: For those that are unfamiliar with ICANN usage, you may associate the definition of Consensus with other definitions and terms of art such as rough consensus or near consensus. It should be noted, however, that in the case of a GNSO PDP originated Working Group, all reports, especially Final Reports, must restrict themselves to the term Consensus as this may have legal implications.] Strong support but significant opposition - a position where, while most of the group supports a recommendation, there are a significant number of those who do not support it. Divergence (also referred to as No Consensus) - a position where there isn't strong support for any particular position, but many different points of view. Sometimes this is due to irreconcilable differences of opinion and sometimes it is due to the fact that no one has a particularly strong or convincing viewpoint, but the members of the group agree that it is worth listing the issue in the report nonetheless. Minority View - refers to a proposal where a small number of people support the recommendation. This can happen in response to a Consensus, Strong support but significant opposition, and No Consensus; or, it can happen in cases where there is neither support nor opposition to a suggestion made by a small number of individuals. In cases of Consensus, Strong support but significant opposition, and No Consensus, an effort should be made to document that variance in viewpoint and to present any Minority View recommendations that may have been made. Documentation of Minority View recommendations normally depends on text offered by the proponent(s). In all cases of Divergence, the WG Chair should encourage the submission of minority viewpoint(s). ~ 3 ~

The recommended method for discovering the consensus level designation on recommendations should work as follows: i. After the group has discussed an issue long enough for all issues to have been raised, understood and discussed, the Chair, or Co-Chairs, make an evaluation of the designation and publish it for the group to review. ii. After the group has discussed the Chair's estimation of designation, the Chair, or Co- Chairs, should reevaluate and publish an updated evaluation. iii. Steps (i) and (ii) should continue until the Chair/Co-Chairs make an evaluation that is accepted by the group. iv. In rare case, a Chair may decide that the use of polls is reasonable. Some of the reasons for this might be: o A decision needs to be made within a time frame that does not allow for the natural process of iteration and settling on a designation to occur. o It becomes obvious after several iterations that it is impossible to arrive at a designation. This will happen most often when trying to discriminate between Consensus and Strong support but Significant Opposition or between Strong support but Significant Opposition and Divergence. Care should be taken in using polls that they do not become votes. A liability with the use of polls is that, in situations where there is Divergence or Strong Opposition, there are often disagreements about the meanings of the poll questions or of the poll results. Based upon the WG's needs, the Chair may direct that WG participants do not have to have their name explicitly associated with any Full Consensus or Consensus view/position. However, in all other cases and in those cases where a group member represents the minority viewpoint, their name must be explicitly linked, especially in those cases where polls where taken. Consensus calls should always involve the entire Working Group and, for this reason, should take place on the designated mailing list to ensure that all Working Group members have the opportunity to fully participate in the consensus process. It is the role of the Chair to designate which level of consensus is reached and announce this designation to the Working Group. Member(s) of the Working Group should be able to challenge the designation of the Chair as part of the Working Group discussion. However, if disagreement persists, members of the WG may use the process set forth below to challenge the designation. If several participants (see Note 1 below) in a WG disagree with the designation given to a position by the Chair or any other consensus call, they may follow these steps sequentially: 1. Send email to the Chair, copying the WG explaining why the decision is believed to be in error. 2. If the Chair still disagrees with the complainants, the Chair will forward the appeal to the CO liaison(s). The Chair must explain his or her reasoning in the response to the complainants and in the submission to the liaison. If the liaison(s) supports the Chair's position, the liaison(s) will provide their response to the complainants. The liaison(s) must explain their reasoning in the response. If the CO liaison disagrees with the Chair, the liaison will forward the appeal to the CO. Should the complainants disagree with ~ 4 ~

the liaison support of the Chair s determination, the complainants may appeal to the Chair of the CO or their designated representative. If the CO agrees with the complainants position, the CO should recommend remedial action to the Chair. 3. In the event of any appeal, the CO will attach a statement of the appeal to the WG and/or Board report. This statement should include all of the documentation from all steps in the appeals process and should include a statement from the CO (see Note 2 below). Note 1: Any Working Group member may raise an issue for reconsideration; however, a formal appeal will require that that a single member demonstrates a sufficient amount of support before a formal appeal process can be invoked. In those cases where a single Working Group member is seeking reconsideration, the member will advise the Chair and/or Liaison of their issue and the Chair and/or Liaison will work with the dissenting member to investigate the issue and to determine if there is sufficient support for the reconsideration to initial a formal appeal process. Note 2: It should be noted that ICANN also has other conflict resolution mechanisms available that could be considered in case any of the parties are dissatisfied with the outcome of this process. Status Reporting: As requested by the GNSO Council Chair/Vice Chairs. Problem/Issue Escalation & Resolution Processes: {Note: the following material was extracted from Sections 3.4, 3.5, and 3.7 of the Working Group Guidelines and may be modified by the Chartering Organization at its discretion} The WG will adhere to ICANN s Expected Standards of Behavior as documented in Section F of the ICANN Accountability and Transparency Frameworks and Principles, January 2008. If a WG member feels that these standards are being abused, the affected party should appeal first to the Chair and Liaison and, if unsatisfactorily resolved, to the Chair of the Chartering Organization or their designated representative. It is important to emphasize that expressed disagreement is not, by itself, grounds for abusive behavior. It should also be taken into account that as a result of cultural differences and language barriers, statements may appear disrespectful or inappropriate to some but are not necessarily intended as such. However, it is expected that WG members make every effort to respect the principles outlined in ICANN s Expected Standards of Behavior as referenced above. The Chair, in consultation with the Chartering Organization liaison(s), is empowered to restrict the participation of someone who seriously disrupts the Working Group. Any such restriction will be reviewed by the Chartering Organization. Generally, the participant should first be warned privately, and then warned publicly before such a restriction is put into place. In extreme circumstances, this requirement may be bypassed. Any WG member that believes that his/her contributions are being systematically ignored or discounted or wants to appeal a decision of the WG or CO should first discuss the circumstances with the WG Chair. In the event that the matter cannot be resolved satisfactorily, the WG member should request an opportunity to discuss the situation with the Chair of the Chartering Organization or their ~ 5 ~

designated representative. In addition, if any member of the WG is of the opinion that someone is not performing their role according to the criteria outlined in this Charter, the same appeals process may be invoked. Closure & Working Group Self-Assessment: Section V: Charter Document History Version Date Description 1.0 13 July 2011 First Draft (Margie Milam) 2.0 Steve Del Bianco Revisions 3.0 5 Sept 2011 Rosemary Sinclair Revisions 4.0 7 Sept 2011 Rosemary Sinclair revisions Staff Contact: Margie Milam Email: margie.milam@icann.org Translations: If translations will be provided please indicate the languages below: n/a ~ 6 ~