- comments-gnso-op-procedures-19jun17@icann.org

[Comments-gnso-op-procedures-19jun17] IPC Comment on Draft GNSO Operating Procedures and Bylaws
by Greg Shatan Aug. 25, 2017

Aug. 25, 2017

The IPC appreciates the opportunity to submit comments on the Draft GNSO Operating Procedures and Bylaws relating to the Empowered Community. The IPC hopes that this submission, although tardy, will still be fully considered. Respectfully Submitted, Gregory S. Shatan IPC President

1 0

[Comments-gnso-op-procedures-19jun17] NCSG Comment on GNSO operating procedures change
by Rafik Dammak Aug. 13, 2017

Aug. 13, 2017

Hi, please find attached the NCSG comment. Best, Rafik

1 0

[Comments-gnso-op-procedures-19jun17] Internet Service and Connectivity Providers (ISPCP) Constituency comment on GNSO Operating Procedures and ICANN Bylaws
by Wolf-Ulrich.Knoben Aug. 10, 2017

Aug. 10, 2017

The ISPCP Constituency respectfully submits the following comment: On the basis of internal deliberations of the constituency as well as an exchange with the Business constituency the ISPCP joins with full support the public comment provided by the BC, in particular with respect to the conclusion of this comment. In addition, regarding Bylaws Art. 11, §3(j)vii ("Approval of a petition to remove a director holding seat 13 or 14) we would like to draw attention to a potential inconsistency with Annex 6 of the GNSO Procedures ("Registries Stakeholder Group and Registrars Stakeholder Group Process to Select ICANN Board Seat #13 Candidates"): the selection of the Board Seat #13 Candidate is done by the Stakeholder Groups of the Contracted Parties House, not including the Nominating Committee Appointee belonging to this house, but the approval of a petition to remove the Board Seat #13 Director requires a vote of the full house, including the Nominating Committee Appointee belonging to this house. Wolf-Ulrich Knoben /Chair of the ISPCP constituency/

1 0

[Comments-gnso-op-procedures-19jun17] RrSG Comment on GNSO Operating Procedures and ICANN Bylaws
by Zoe Bonython Aug. 10, 2017

Aug. 10, 2017

Dear Sir/Madam, On behalf of the RrSG, I would like to submit the comment below on ‘GNSO Operating Procedures and ICANN Bylaws. Kind regards, Zoe Bonython RrSG Secretariat Registrar Stakeholder Group Comment on the GNSO Operating Procedures and ICANN Bylaws This comment is submitted on behalf of the Registrar Stakeholder Group (RrSG). Registrars would like to thank ICANN staff and the Drafting Team (DT) for their work in connection with the revision of the GNSO Operating Procedures and those parts of the ICANN Bylaws pertaining to the GNSO. We believe ICANN staff & the Drafting Team have addressed most of the modifications set forth in the Revised Bylaws. We support the position taken in the proposed GNSO Operating Procedures that the GNSO Council is well equipped to relay the positions of the GNSO Stakeholder Groups and Constituencies. Further, we generally support the voting thresholds proposed for implementation of processes associated with the IANA transition and the parallel process on enhancing ICANN accountability, with one exceptional concern. Our feedback is broken down below. Article 11 Generic Names Supporting Organization We would like to raise a concern regarding Section 11.3 GNSO Council, subsection (j)(ii) and (j)(iii), which state: (ii) GNSO Council Inspection Request as contemplated in Section 22.7: requires an affirmative vote of more than one-fourth (1/4) vote of each House or majority of one House. (iii) GNSO Council Inspection Remedy, as contemplated in Section 22.7 - e, and Stakeholder Group / Constituency Inspection Remedy, as contemplated in Section 22.7 – e(ii) and e(iii), for an inspection requested by the GNSO as a Decisional Participant in the Empowered Community: requires an affirmative vote of more than one-fourth (1/4) vote of each House or majority of one House. We understand that Inspection Requests are defined in the Bylaws as “limited to the accounting books and records of ICANN relevant to the operation of ICANN as a whole, and shall not extend to the underlying sources of such accounting books or records or to documents only relevant to a small or isolated aspect of ICANN's operations or that relate to the minutiae of ICANN's financial records or details of its management and administration (the "Permitted Scope”).” Notwithstanding this definition, it is important to ensure that document inspection is not used to obtain or disclose contractual or sensitive information. The RrSG believes any requests for information related to Registry or Registrar contracts, or information related to their contractual relationships, would qualify as an underlying source and should be excluded. APPENDIX 1: GNSO COUNCIL VOTING RESULTS TABLE Regarding “Approval of a petition to remove a director holding seat 13 or 14” and “Approval of a petition notice to remove a director holding seat 13 or 14” shown on page 43 of the redlined version of the GNSO Operating Procedures, we note the voting thresholds as “>75% of One.” This does not accurately reflect the voting threshold outlined in Art. 11, §3(j)vii and viii. We suggest that table be changed to reflect “>75% of the House that appointed Director” to avoid any confusion.

1 0

[Comments-gnso-op-procedures-19jun17] Business Constituency (BC) comment on changes to Bylaws and GNSO procedures for the Empowered Community
by Steve DelBianco Aug. 10, 2017

Aug. 10, 2017

The ICANN Business Constituency (BC) submits the attached comment on proposed changes to Bylaws and GNSO procedures for the Empowered Community. ( ICANN comment page at https://www.icann.org/public-comments/gnso-op-procedures-2017-06-19-en ) This comment was drafted by Steve DelBianco and approved in accord with the BC charter. — Steve DelBianco Vice chair for policy coordination ICANN Business Constituency

1 0

[Comments-gnso-op-procedures-19jun17] Registries Stakeholder Group (RySG) comments on GNSO Operating Procedures and ICANN Bylaws
by svg＠milathan.ltd Aug. 7, 2017

Aug. 7, 2017

Please find attached, in PDF format, the Registries Stakeholder Group (RySG) comments on GNSO Operating Procedures and ICANN Bylaws. In the interest of time, the RySG did not conduct a formal vote on these comments. They were circulated and debated on our mailing list, with no member expressing opposition to their submission. Please do not hesitate to contact me or any member of the RySG Executive Committee should you have any questions. Best regards, Stéphane Van Gelder RySG Vice Chair (Policy)

1 0