October 2013 - council - lists.icann.org

Argentinian Govt. denies visas on the basis that they are for ICANN meeting. Tourist visas not a problem. Fwd: ICANN-48 Visas Denied
by Zahid Jamil Oct. 23, 2013

Oct. 23, 2013

Best regards, Zahid Jamil Barrister-at-law Chair Domain Name Dispute Resolution Center www.dndrc.com Jamil & Jamil Barristers-at-law Suites 219-221 Central Hotel Annexe, Merewether Road, Karachi. Suite No 12, First Floor, Rehman Arcade, Aabpara Market, Islamabad. Cell: +923008238230 Tel: +92 213 5680760 / 5685276 / 5655025 Fax: +92 213 5655026 www.jamilandjamil.com Notice / Disclaimer This message contains confidential information and its contents are being communicated only for the intended recipients . If you are not the intended recipient you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this message by mistake and delete it from your system. The contents above may contain/are the intellectual property of DNDRC/Jamil & Jamil, Barristers-at-Law, and constitute privileged information protected by attorney client privilege. The reproduction, publication, use, amendment, modification of any kind whatsoever of any part or parts (including photocopying or storing it in any medium by electronic means whether or not transiently or incidentally or some other use of this communication) without prior written permission and consent of DNDRC/Jamil & Jamil is prohibited. Sent from my iPad Begin forwarded message: > From: Consular Section <consular_epaki(a)mrecic.gov.ar> > Date: October 23, 2013 at 15:45:11 GMT+8 > To: consular_epaki <consular_epaki(a)mrecic.gov.ar> > Subject: ICANN-48 Visas Denied > > Dear Prospective Participants: > > This is Carlos López Sanabria, Head of Consular Section of the Argentine Embassy in Islamabad. I am writing you to inform that unfortunately all visa requested for ICANN-48 to be held in Buenos Aires have been denied. The Consular Section is processing the reconsideration of your visas and will convey you any news regarding your visas. > > For any further information please contact directly the Consular Section which is the official link between the applicants and the Argentine authorities. > > Regards, > Carlos López Sanabria > > ----- > Carlos López Sanabria > First Secretary > Head of the Consular Section > Embassy of the Argentine Republic > House 60, Street 1, F-6/3, Islamabad > > Tel: 051 287 4485/843 8126 > Fax: 051 282 5564 > E-mail: consular_epaki(a)mrecic.gov.ar > Webpage: www.epaki.mrecic.gov.ar >

5 5

Agenda for ICANN Board meeting - 23 Oct 2013
by Bruce Tonkin Oct. 23, 2013

Oct. 23, 2013

From: http://www.icann.org/en/groups/board/documents/agenda-23oct13-en.htm Agenda for ICANN Special Board Meeting 23 October 2013 Consent Agenda 1. Approval of Minutes of 28 September 2013 Board Meeting 2. Appointment of Xiaodong Lee and Carlos Martinez to the Security & Stability Advisory Committee 3. Thank You from Security and Stability Advisory Committee to Vanda Scartezini 4. Receipt of ccNSO Report to the Board, IDN ccPDP Main Agenda 1. AOB

1 0

RAA PDP motion
by Winterfeldt, Brian J. Oct. 23, 2013

Oct. 23, 2013

Dear all: Please confirm timely receipt of my email correspondence and draft motion from yesterday, prior to our 23:59 UTC motions and materials deadline. I am not sure why exactly, but it did not appear on our public listserv at http://gnso.icann.org/mailing-lists/archives/council/. Thank you, Brian Brian J. Winterfeldt Head of Internet Practice Katten Muchin Rosenman LLP 2900 K Street NW, North Tower - Suite 200 / Washington, DC 20007-5118 p / (202) 625-3562 f / (202) 339-8244 brian.winterfeldt(a)kattenlaw.com<mailto:brian.winterfeldt@kattenlaw.com> / www.kattenlaw.com<http://www.kattenlaw.com/> From: Winterfeldt, Brian J. Sent: Monday, October 21, 2013 7:48 PM To: council(a)gnso.icann.org<mailto:council@gnso.icann.org> Subject: RAA PDP motion Dear all: In view of our prior discussions in relation to advancing the Privacy and Proxy Services Accreditation PDP, attached please find a draft motion that, if passed, would adopt the latest version of the charter. The effect of the motion, if passed by the Council, would then be to set up the PDP Working Group as soon as possible. Thank you, Brian Brian J. Winterfeldt Head of Internet Practice Katten Muchin Rosenman LLP 2900 K Street NW, North Tower - Suite 200 / Washington, DC 20007-5118 p / (202) 625-3562 f / (202) 339-8244 brian.winterfeldt(a)kattenlaw.com<mailto:brian.winterfeldt@kattenlaw.com> / www.kattenlaw.com<http://www.kattenlaw.com/> =========================================================== CIRCULAR 230 DISCLOSURE: Pursuant to Regulations Governing Practice Before the Internal Revenue Service, any tax advice contained herein is not intended or written to be used and cannot be used by a taxpayer for the purpose of avoiding tax penalties that may be imposed on the taxpayer. =========================================================== CONFIDENTIALITY NOTICE: This electronic mail message and any attached files contain information intended for the exclusive use of the individual or entity to whom it is addressed and may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any viewing, copying, disclosure or distribution of this information may be subject to legal restriction or sanction. Please notify the sender, by electronic mail or telephone, of any unintended recipients and delete the original message without making any copies. =========================================================== NOTIFICATION: Katten Muchin Rosenman LLP is an Illinois limited liability partnership that has elected to be governed by the Illinois Uniform Partnership Act (1997). ===========================================================

3 2

Proposed Agenda for the GNSO Council Meeting 31 October 2013 at 11:00 UTC.
by Glen de Saint Géry Oct. 22, 2013

Oct. 22, 2013

Dear Councillors, Please find the proposed Agenda for the GNSO Council Meeting 31 October 2013 at 11:00 UTC. http://gnso.icann.org/en/meetings/agenda-council-31oct13-en.htm The agenda is also posted on the Wiki at: https://community.icann.org/display/gnsocouncilmeetings/Agenda+31+October+2… And the motions are posted at: https://community.icann.org/display/gnsocouncilmeetings/Motions+31+October+… This agenda was established according to the GNSO Council Operating Procedures approved 13 September 2012 for the GNSO Council and updated. <http://gnso.icann.org/en/council/op-procedures-13jun13-en.pdf > For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. Meeting Times 11:00 UTC<http://www.timeanddate.com/worldclock/fixedtime.html?msg=council+meeting&is…> http://tinyurl.com/py4mo84 Coordinated Universal Time 11:00 UTC 04:00 Los Angeles; 07:00 Washington; 11:00 London; 12:00 Paris; 00:00 Wellington next day Dial-in numbers will be sent individually to Council members. Councillors should notify the GNSO Secretariat in advance if a dial out call is needed. GNSO Council meeting audio cast http://stream.icann.org:8000/gnso.m3u Item 1: Administrative matters (10 mins) 1.1 Roll Call 1.2 Statement of interest updates 1.3 Review/amend agenda 1.4. Note the status of minutes for the previous Council meeting per the GNSO Operating Procedures: Minutes of the GNSO Council meeting 10 October 2013<http://gnso.icann.org/mailing-lists/archives/council/msg15059.html> will be posted as approved on 23 October 2013 Item 2: Opening Remarks / Review of Projects & Action List (10 mins) Review focus areas and provide updates on specific key themes / topics Include review of Projects List<http://gnso.icann.org/meetings/projects-list.pdf> and Action List<https://community.icann.org/display/gnsocouncilmeetings/Action+Items>. Comments or questions arising. Item 3: Consent agenda (5 mins) Item 4: MOTION - To approve a charter for the Translation and Transliteration of Contact Information PDP Working Group (10 mins) On 13 June 2013 the GNSO Council initiated a Policy Development Process (PDP) on the Translation and Transliteration of Contact Information and decided to create a PDP Working Group for the purposes of fulfilling the requirements of the PDP. Following a call for volunteers, a Drafting Team was formed and its members have developed a charter for consideration by the GNSO Council. The drafting team has submitted the charter and so the GNSO Council, having reviewed the charter, will vote on whether to approve it as submitted by the Drafting Team. 4.1 - Review motion 1<https://community.icann.org/display/gnsocouncilmeetings/Motions+31+October+…> 4.2 - Discussion 4.3 - Next steps Item 5: MOTION - Adoption of the Thick Whois Policy Development Process Final Report<http://gnso.icann.org/en/issues/whois/thick-final-21oct13-en.pdf> and Recommendations (10 mins) The Final Report on Thick Whois<http://gnso.icann.org/en/issues/whois/thick-final-21oct13-en.pdf> has been prepared as required by the GNSO PDP in the ICANN Bylaws. The Final Report is based on the Initial Report of 21 June 2013 and has been updated to reflect the review and analysis of the Public Comments received by the Thick Whois Working Group, in addition to further deliberations. The report is submitted to the GNSO Council for its consideration. The conclusions and recommendations for next steps on the issues included in this PDP are outlined in Section 7 of the report. 5.1 - Review motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+31+October+…> 2 5.2 - Discussion 5.3 - Next steps Item 6: MOTION - To approve a charter for the Standing Committee on GNSO Improvements Implementation (SCI) (10 mins) The GNSO Council approved the original charter for the Standing Committee on GNSO Improvements Implementation (SCI) in 2011. Recently, the SCI determined that the Charter no longer reflected its current role as a standing committee, and furthermore did not contain procedures for selecting its Chair and Vice-Chair. The SCI requested guidance from the GNSO Council as to how to proceed with revisions to the Charter and at its meeting on 05 September 2013 the GNSO Council endorsed the SCI as a standing committee and further requested that the SCI proceed to revise the Charter as it may deem necessary, with the exception of the section on Decision Making. The SCI has since revised the Charter to reflect its role as a standing committee and to include procedures to select the Chair and Vice Chair. 6.1 - Review motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+31+October+…> 3 6.2 - Discussion 6.3 - Next steps Item 7: MOTION - A charter for the Privacy & Proxy Services Accreditation PDP WG (10 mins) ICANN staff prepared a paper<http://gnso.icann.org/en/issues/raa/negotiations-conclusion-16sep13-en.pdf> to summarise the outcomes of the 2013 Registrar Accreditation Agreement (RAA) negotiations in order to set the scene for subsequent associated policy development work to be managed by the Council. This is an ICANN Board initiated PDP. The staff paper contained a draft charter for the PDP WG and the Council has discussed this. Refinements to the charter have been proposed as has a title for the PDP WG. Here the Council needs to decide to move ahead with the revised draft charter prepared by staff or to institute a drafting team to revise and / or develop the PDP WG charter. 7.1 Motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+31+October+…> 4 7.2 Discussion 7.2 Next steps Item 8: INPUT & DISCUSSION - Prospective improvements to the Policy Development Process (10 mins) The Council is committed to on-going enhancements to the methods of working of the Council and the work initiated and managed by the Council. The PDP process is a cornerstone of policy making within the GNSO and, as such, the work of the Council. The PDP outcomes and associated processes are the subject of focus and attention both within the GNSO and the broader ICANN Community. The Council has previously discussed a paper prepared by ICANN staff<http://gnso.icann.org/en/drafts/pdp-improvements-22aug13-en.pdf> on potential improvements to the PDP process. The discussion is now encapsulated in a table form and further work needs to be done on reviewing the table and agreeing concrete next steps. 8.1 - Review of table of prospective PDP Improvements<http://gnso.icann.org/en/drafts/pdp-improvements-table-23sep13-en.pdf> (Marika Konings) 8.2 - Discussion 8.3 - Next steps Item 9: DISCUSSION - Policy issues surrounding string confusion (10 mins) The Council previously discussed issues associated with the string confusion decisions that have been taken e.g. relating to plural and singular versions of the same term and the apparently contradictory decisions on identical strings. The Council agreed to write to the ICANN board and new gTLD programme committee<http://gnso.icann.org/en/correspondence/robinson-to-crocker-chalaby-18sep13…> and to consider appropriate additional action. Further, the Council subsequently (10 October 2013) agreed that additional action will be contingent on receiving advice from ICANN legal counsel as to whether or not any additional GNSO work on the topic will have the potential to be used in a timely and effective manner within the new gTLD programme. Here the Council needs to hear if any such advice, requested via ICANN policy staff, has been forthcoming and, if so, what further action to take. 9.1 - Update on advice received 9.2 - Discussion 9.2 - Next steps Item 10: UPDATE & DISCUSSION - Protection of IGO-INGO Identifiers in all gTLDs Policy Development Process (10 mins) The WG Chair will provide an update on status of WG deliberations and the public comment<http://www.icann.org/en/news/public-comment/igo-ingo-final-20sep13-en.htm> solicitation process for the draft Final Report<http://gnso.icann.org/en/issues/igo-ingo-final-20sep13-en.pdf>. This PDP WG was formed to develop a set of policy recommendations to address the issue of whether and if so, what types of protections should be provided for the identifiers of certain IGOs and INGOs including the RCRC and IOC at the top and second levels in all gTLDs. For further information please see: http://gnso.icann.org/en/group-activities/active/igo-ingo. 10.1 - Review of proposed WG recommendations (Thomas Rickert) 10.2 - Discussion 10.3 - Next steps Item 11: UPDATE & DISCUSSION - Planning for Buenos Aires (10 mins) Making the most out of the face-to-face meeting time available at the ICANN Meeting in Buenos Aires will take planning. GNSO Council Vice Chair, Wolf-Ulrich Knoben has again volunteered to lead this and will be working with the Council and staff on this effort. Here the Council has the opportunity to feed into plans and provide input based on past experience. Included in this item will be the opportunity to shape the approach to and substance of the Council's proposed meetings with other groups in such as the CCNSO, the GAC and the ICANN board. 11.1 - Update (Wolf-Ulrich Knoben) 11.2 - Discussion 11.3 - Next steps Item 12: Any Other Business (5 mins) Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article X, Section 3) 9. Except as otherwise specified in these Bylaws, Annex A hereto, or the GNSO Operating Procedures, the default threshold to pass a GNSO Council motion or other voting action requires a simple majority vote of each House. The voting thresholds described below shall apply to the following GNSO actions: a. Create an Issues Report: requires an affirmative vote of more than one-fourth (1/4) vote of each House or majority of one House. b. Initiate a Policy Development Process ("PDP") Within Scope (as described in Annex A<http://www.icann.org/en/about/governance/bylaws#AnnexA>): requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. c. Initiate a PDP Not Within Scope: requires an affirmative vote of GNSO Supermajority. d. Approve a PDP Team Charter for a PDP Within Scope: requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. e. Approve a PDP Team Charter for a PDP Not Within Scope: requires an affirmative vote of a GNSO Supermajority. f. Changes to an Approved PDP Team Charter: For any PDP Team Charter approved under d. or e. above, the GNSO Council may approve an amendment to the Charter through a simple majority vote of each House. g. Terminate a PDP: Once initiated, and prior to the publication of a Final Report, the GNSO Council may terminate a PDP only for significant cause, upon a motion that passes with a GNSO Supermajority Vote in favor of termination. h. Approve a PDP Recommendation Without a GNSO Supermajority: requires an affirmative vote of a majority of each House and further requires that one GNSO Council member representative of at least 3 of the 4 Stakeholder Groups supports the Recommendation. i. Approve a PDP Recommendation With a GNSO Supermajority: requires an affirmative vote of a GNSO Supermajority, j. Approve a PDP Recommendation Imposing New Obligations on Certain Contracting Parties: where an ICANN contract provision specifies that "a two-thirds vote of the council" demonstrates the presence of a consensus, the GNSO Supermajority vote threshold will have to be met or exceeded. k. Modification of Approved PDP Recommendation: Prior to Final Approval by the ICANN Board, an Approved PDP Recommendation may be modified or amended by the GNSO Council with a GNSO Supermajority vote. l. A "GNSO Supermajority" shall mean: (a) two-thirds (2/3) of the Council members of each House, or (b) three-fourths (3/4) of one House and a majority of the other House." Appendix 2: Absentee Voting Procedures (GNSO Operating Procedures 4.4<http://gnso.icann.org/council/gnso-operating-procedures-22sep11-en.pdf>) 4.4.1 Applicability Absentee voting is permitted for the following limited number of Council motions or measures. a. Initiate a Policy Development Process (PDP); b. Approve a PDP recommendation; c. Recommend amendments to the GNSO Operating Procedures (GOP) or ICANN Bylaws; d. Fill a Council position open for election. 4.4.2 Absentee ballots, when permitted, must be submitted within the announced time limit, which shall be 72 hours from the meeting's adjournment. In exceptional circumstances, announced at the time of the vote, the Chair may reduce this time to 24 hours or extend the time to 7 calendar days, provided such amendment is verbally confirmed by all Vice-Chairs present. 4.4.3 The GNSO Secretariat will administer, record, and tabulate absentee votes according to these procedures and will provide reasonable means for transmitting and authenticating absentee ballots, which could include voting by telephone, e- mail, web-based interface, or other technologies as may become available. 4.4.4 Absentee balloting does not affect quorum requirements. (There must be a quorum for the meeting in which the vote is initiated.) ---------------------------------------------------------------------------- Local time between October and March, Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- Reference (Coordinated Universal Time) UTC 11:00 ---------------------------------------------------------------------------- California, USA (PDT<http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) UTC-7+1DST 04:00 New York/Washington DC, USA (EST) UTC-4+1DST 07:00 Rio de Janiero, Brazil (BRST) UTC-3+1DST 09:00 Montevideo, Uruguay (UYST<http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>) UTC-3+1DST 09:00 London, United Kingdom (BST) UTC+0DST 11:00 Abuja, Nigeria (WAT<http://www.timeanddate.com/library/abbreviations/timezones/africa/wat.html>) UTC+1+0DST 12:00 Bonn, Germany (CEST) UTC+1+0DST 12:00 Stockholm, Sweden (CET) UTC+1+0DST 12:00 Istanbul, Turkey (EEST) UTC+2+0DST 13:00 Ramat Hasharon, Israel(IST<http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.…>) UTC+2+0DST 13:00 Karachi, Pakistan (PKT<http://www.timeanddate.com/library/abbreviations/timezones/asia/pkt.html> ) UTC+5+0DST 16:00 Beijing/Hong Kong, China (HKT ) UTC+8+0DST 19:00 Perth, Australia (WST<http://timeanddate.com/library/abbreviations/timezones/au/wst.html>) UTC+8+0DST 19:00 Wellington, New Zealand (NZDT<http://www.timeanddate.com/library/abbreviations/timezones/pacific/nzdt.html> ) UTC+12+1DST 00:00 (next day) ---------------------------------------------------------------------------- DST starts/ends on last Sunday of March 2014, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com - http://tinyurl Please let me know if you have any questions. Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

Draft PDP charter - Privacy & Proxy Accreditation Services PDP WG
by Jonathan Robinson Oct. 21, 2013

Oct. 21, 2013

All, Following up on our discussion regarding the charter for the "RAA Remaining Issues PDP" on our call on Thursday last week, I hope that we can start a discussion right away regarding possible revisions to the draft charter prepared by staff which I forwarded to you all just prior to our meeting. I believe our aim should be to form a view as to whether or not the draft charter, as amended according to our anticipated discussions, is a document that can be voted on for adoption at our next Council meeting. As a reminder, our options are essentially either: 1. Discuss and revise this draft charter for formal adoption by the Council, which will then proceed to form a Working Group (WG) to begin work; or 2. Create a Drafting Team (DT) to finalize a charter - based either upon this draft or starting from a blank slate - to be proposed for adoption at a later Council meeting. On our Thursday call last week, several Councillors supported option 1 above as a pragmatic way forward i.e. to see if we can find agreement as to the terms of the charter that will govern the WG's work. I am therefore circulating the draft Charter again (re-titled and slightly revised to more accurately reflect the scope of the PDP) for discussion. My sense is that the scope will be largely governed by the specific issues that are laid out in Section III of the draft Charter. So, perhaps we can start by discussing possible revisions to these questions, not in terms of substantive discussion over the merits or content of the answers, but in relation to whether they sufficiently describe and frame the scope of work for the WG. If we are able to reach agreement within the next week, we can then propose the revised charter for adoption on 21 October i.e. within the document deadline for our upcoming 31 October meeting. I look forward to an engaging and constructive discussion on the list on this topic. Thanks, Jonathan

4 6

Thick Whois Policy Development Process: Submission of Final Report and Motion for next meeting
by Volker Greimann Oct. 21, 2013

Oct. 21, 2013

Dear fellow councillors, I would like to present the Final Report on the Thick Whois Policy Development Process (as attached) for consideration of and deliberation by the Council at the forthcoming GNSO Council meeting. The Working Group has come to full consensus on the contents of the report and proposed the following motion: *Motion on the Adoption of the Thick Whois Policy Development Process Final Report and Recommendations* WHEREAS 1. On 14 March 2012, the GNSO Council launched a Policy Development Process (PDP) on Thick Whois to make recommendations to the GNSO Council regarding the use of thick Whois by all gTLD registries, both existing and future. 2. This PDP has followed the prescribed PDP steps as stated in the Bylaws, resulting in a Final Report delivered on 21 October 2013; 3. The Thick Whois PDP WG has reached full consensus on the recommendations contained in the report in relation to Thick Whois; 4. The GNSO Council has reviewed and discussed these recommendations. Now therefore be it resolved, 1. The GNSO Council recommends to the ICANN Board of Directors the adoption of Thick Whois recommendations as detailed in section 7.1 of the Final Report [include link] 2. The GNSO Council shall convene a Thick Whois Implementation Review Team to assist ICANN Staff in developing the implementation details for the new policy should it be approved by the ICANN Board. The Implementation Review Team will be tasked with evaluating the proposed implementation of the policy recommendations as approved by the Board and is expected to work with ICANN Staff to ensure that the resultant implementation fulfills the intentions of the approved policy recommendations. If the Implementation Review Team identifies any potential modifications to the policy recommendations or need for new policy recommendations, the Implementation Review Team shall refer these to the GNSO Council for its consideration and follow-up, as appropriate. Following adoption by the ICANN Board of the recommendations, the GNSO Secretariat is authorized to issue a call for volunteers for a Thick Whois Implementation Review Team to the members of the Thick Whois Working Group. -- Should you have any further questions, please do not hesitate to contact us. Best regards, Volker A. Greimann - legal department - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann(a)key-systems.net Web: www.key-systems.net / www.RRPproxy.net www.domaindiscount24.com / www.BrandShelter.com Follow us on Twitter or join our fan community on Facebook and stay updated: www.facebook.com/KeySystems www.twitter.com/key_systems CEO: Alexander Siffrin Registration No.: HR B 18835 - Saarbruecken V.A.T. ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone.

3 3

FW: SCI Charter Revisions
by Jonathan Robinson Oct. 21, 2013

Oct. 21, 2013

All, Please see below a note and associated attachment from Ron Andruff regarding the SCI. I thought it had gone the Council but it did not. I expect we'll aim to move this forward at the Council meeting on 31 October 2013. Jonathan From: Ron Andruff [mailto:randruff@rnapartners.com] Sent: 15 October 2013 14:32 To: jrobinson(a)afilias.info Cc: council(a)gnso.icann.org; gnso-improvem-impl-sc(a)icann.org Subject: RE: SCI Charter Revisions Dear Jonathan, As I noted below the SCI took up discussion of the charter revisions based on the guidance provided by you and the Council in your message below. Accordingly, the SCI has revised the charter per the guidance as follows: 1. It confirms that the SCI is a standing committee and; 2. It includes other changes the SCI deemed necessary including updating it to reflect the current role of the SCI and to include procedures for Chair and Vice Chair elections and; 3. It includes the original text concerning the decision-making methodology and a note that the methodology is under consideration by the GNSO Council. The SCI awaits Council's final determination in this regard. Please let me know if you or the Councilors have questions concerning the modified charter or need additional information. Kind regards, RA Ron Andruff RNA Partners www.rnapartners.com From: Ron Andruff [mailto:randruff@rnapartners.com] Sent: Tuesday, September 10, 2013 09:07 To: 'jrobinson(a)afilias.info' Cc: 'council(a)gnso.icann.org'; 'gnso-improvem-impl-sc(a)icann.org' Subject: RE: SCI Charter Revisions Dear Jonathan, Thank you and the GNSO Council for providing the SCI with this way forward. We will pick this up on our regularly scheduled call today. Kind regards, RA Ron Andruff RNA Partners www.rnapartners.com From: Jonathan Robinson [mailto:jrobinson@afilias.info] Sent: Monday, September 9, 2013 18:30 To: 'Ron Andruff' Cc: council(a)gnso.icann.org Subject: RE: SCI Charter Revisions Dear Ron, Thank-you again for this letter. As you will no doubt by now be aware, the Council did discuss the SCI and the important questions you have raised in your communication below. Essentially the Council agreed the following: 1. That the Charter of the SCI should be modified to confirm that the SCI is a standing committee and; 2. That the Council would like the SCI to undertake the work to propose the above and any other changes it deems necessary and then to submit these to the Council and; 3. That the SCI should not propose to modify the decision making methodology (away from full consensus) as the GNSO Council will consider this particular issue further. Noting: That should the decision be made to move from full consensus in future, that should be a decision for the GNSO Council. I trust that you will find this response and the associated guidance helpful. In addition, please could you convey my thanks on behalf of the Council to the SCI for their work to date and on-going contribution. Best wishes, Jonathan Jonathan Robinson Chair ICANN GNSO Council <mailto:jonathan.robinson@ipracon.com> jonathan.robinson(a)ipracon.com Tel: +44 (0)20 7993 6103 skype: jonathan.m.r From: Ron Andruff [mailto:randruff@rnapartners.com] Sent: 02 September 2013 03:44 To: jrobinson(a)afilias.info; gnso-improvem-impl-sc(a)icann.org Subject: SCI Charter Revisions Importance: High Dear Jonathan, I understand that the GNSO Council will be discussing the SCI Charter revisions on its next call scheduled for September 5th, 2013. At its meeting on August 6th, 2013, the SCI members discussed the outcomes from the GNSO Sessions in Durban on this matter and decided that it would be helpful to more formally seek guidance from the Council with respect to the next steps for the SCI Charter. One aspect, in particular, based on the discussion in Durban, seems clear, i.e. that the GNSO Council would like the SCI to continue as a 'standing committee'. We would like the Charter to reflect that, should that indeed be the case. (I refer you to the email on this topic that I sent you on 08 July 2013, just prior to Durban.) At the Wrap-Up Session the GNSO Council also discussed the SCI process for decision-making ('full consensus' versus Standard Methodology for Making Decisions). The SCI understands that the Council agreed to consider this issue further on its mailing list and Council members were encouraged to share their views in support of one or the other option. We now understand that Jeff Neuman will provide background information as to why the SCI was initially required to operate under full consensus. At the SCI's August 6th meeting and since then on our mailing list, members expressed an interest in helping guide the discussion for the Council as to why SCI members feel there should or should not be full consensus. The impetus behind the recommendation to reconsider using "full or unanimous consensus" or "rough or near consensus" came from my request, as in-coming SCI Chair, to review and update the SCI Charter, as well as the SCI Wiki since the Committee now had over two years of experience behind it and the language in both the document and on the Wiki was outdated. I also noted at the time, and do so here again for Council's edification, the SCI Charter is further governed by the GNSO Working Group Guidelines. The response within the SCI came in two forms: Those that feel that being forced to come to unanimous consensus "improves our product" because it ensures that the Committee dedicates the time to explore all points of view and works to find stronger outcomes; the arguments against full consensus included concerns about potentially using the SCI in a way that would drive substantive outcomes in the GNSO, whether intentionally or not, by pushing through decisions on procedure/process to meet an immediate need, or that any member choosing to remain steadfast in opposition could capture the SCI process. All SCI members however respect that balanced discussions result in consensus - in some form - leading to better appreciation of each member's contributions, more confidence in the Committee itself and in the process. The SCI has the luxury of not having to work under any time constraints on procedural and process issues (rather than substantive issues). Within the Standard Methodology for Making Decisions and the five forms of consent defined in the Guidelines, 'rough or near consent' (defined as "a position where only a small minority disagrees, but most agree") immediately follows 'full or unanimous consent'. We are all aware of the ramifications of full consensus, having worked under this standard since ICANN's inception. 'Near consensus', provides the basis for Committee members to argue for their respective stakeholder group's position, while it also provides for written rationale entered into the public record for any and all dissenting opinion(s), thus providing more context to the GNSO Council to assist it in coming to its own determinations. Notably, the SCI does not make any determinations other than to propose recommendations to the GNSO Council, which it, in turn, discusses, accepts, modifies or rejects, as Council deems appropriate. On behalf of the SCI, we hope that this background information will inform your discussions, however the SCI would be happy to further brief the Council on the Charter and consensus issues, if so requested. We would also be grateful to know as soon as possible if the Council, as the Chartering organization, would prefer to take on the task of revising the SCI Charter or pass that responsibility to the SCI once it has made its determination on the consensus issue. The SCI stands ready to assist in this task in whichever way the Council deems appropriate. We await your guidance. Kind regards, Ron Andruff SCI Chair Ron Andruff RNA Partners www.rnapartners.com

1 0

REMINDER: Document and Motion deadline Monday 21 OCTOBER 2013 at 23:59 UTC for Council meeting on 31 OCTOBER 2013 at 11:00 UTC
by Glen de Saint Géry Oct. 20, 2013

Oct. 20, 2013

Dear Councillors, Reminder! Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e MONDAY, 21 OCTOBER 2013 at 23:59 UTC) of the GNSO Council meeting on 31 October 2013 at 11:00 UTC. Motions should be sent to the Council mailing list and will then be posted on the Wiki at: https://community.icann.org/display/gnsocouncilmeetings/Motions+31+October+… Thank you very much. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org

1 0

FW: GNSO Council Update
by Jonathan Robinson Oct. 18, 2013

Oct. 18, 2013

All, Please see below for an update sent out today to SG & Constituency chairs. Thanks, Jonathan From: Jonathan Robinson [mailto:jonathan.robinson@ipracon.com] Sent: 18 October 2013 06:38 To: 'kdrazek(a)Verisign.com'; Michele Neylon :: Blacknight (michele(a)blacknight.com) (michele(a)blacknight.com) 'Elisa Cooper'; 'Kristina Rosette'; 'tony holmes'; 'Robin Gross'; 'William Drake'; 'Marie-Laure Lemineur' Cc: 'Glen de Saint Géry'; 'gnso-secs(a)icann.org'; MASON COLE (mcole(a)5x5com.com) 'WUKnoben' Subject: GNSO Council Update Importance: High Dear Colleagues, We are now inevitably starting to turn our attention towards the countdown to the ICANN annual meeting in Buenos Aires, so it seems timely to provide you with an update containing a few points relating to the work and running of the GNSO Council. The GNSO weekend working sessions are well established by now. We have a full agenda emerging, including covering much of the policy work being undertaken within the GNSO, as well as interaction with senior staff, the ICANN Board and the GAC. Whilst the weekend sessions provide an excellent opportunity for the Council to become well-briefed and work together, they are clearly much more than GNSO Council sessions. They are an opportunity for interaction within the whole GNSO and so, other commitments and logistics permitting, I would like to take this opportunity to remind you of the opportunity to participate and to invite and encourage you and colleagues within your groups to do so. For the first time I believe, we have a GNSO Council development meeting, which will be held on Friday 22nd November between 10h00 & 18h00, followed by a meal in the evening. The motivation for the meeting is to run an induction and development workshop for the new GNSO Council i.e. the Council to be seated and in place from the Buenos Aires meeting onwards. We plan to kick off on Friday 22nd at 10h00 with a first session to include additional participation from the leadership of the groups represented on the Council. So, we would very much like to have attendance from the Chair (or Vice Chair or alternative if not available) of your SG or Constituency as appropriate, in order to give additional perspective to that of your Councillors for the first 60-90 minutes of the meeting. Accordingly, please can you let Glen De Saint Gery (glen(a)icann.org) which individual from your leadership group (if not the chair) will be able to attend? Regarding the leadership of the Council, you will be aware of the requirement to elect a Council Chair for the forthcoming year as well as select two Vice Chairs of the Council. My understanding is that both Vice Chairs will be changing and we can look forward to confirmation of the new Vice Chairs in due course. The Council confirmed a timetable for the election of the Chair at its 10th October meeting. From my perspective, I have enjoyed the not inconsiderable challenge of working as GNSO Council Chair over the past year and am pleased to confirm to you that I am available, if elected, to continue in the role for the year ahead. Its challenging and stimulating and there is plenty more work ahead! If you have any questions or input relating to this note, or indeed any aspect of the leadership and running of the Council, please do get in touch with me. I am personally committed to a well-managed and effective GNSO Council and am open to any feedback in how best to achieve that. Best wishes, Jonathan Jonathan Robinson Chair ICANN GNSO Council jonathan.robinson(a)ipracon.com Tel: +44 (0)20 7993 6103 skype: jonathan.m.r

1 0

REMINDER: Document and Motion deadline Monday 21 OCTOBER 2013 at 23:59 UTC for Council meeting on 31 OCTOBER 2013 at 11:00 UTC
by Glen de Saint Géry Oct. 17, 2013

Oct. 17, 2013

Dear Councillors, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e MONDAY, 21 OCTOBER 2013 at 23:59 UTC) of the GNSO Council meeting on 31 October 2013 at 11:00 UTC. Motions should be sent to the Council mailing list and will then be posted on the Wiki at: https://community.icann.org/display/gnsocouncilmeetings/Motions+31+October+… Thank you very much. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org

1 0