May 2017 - council - lists.icann.org

Reminder: Document and Motion deadline Monday, 8 May 2017 at 23:59 UTC for the GNSO Council Meeting 18 May 2017 at 12:00 UTC
by Nathalie Peregrine 04 May '17

04 May '17

Dear Councilors, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. MONDAY, 8 May 2017 at 23:59 UTC) of the GNSO Council Meeting on 18 May 2017 at 12:00 UTC. Motions should be sent to the Council mailing list and will then be posted on the Wiki at: https://community.icann.org/x/eQLfAw[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> Thank you very much. Kind regards, Nathalie -- Nathalie Peregrine Specialist, SOAC Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

Re: [council] Board Seat #14 Election
by Marika Konings 04 May '17

04 May '17

Paul, we are trying to confirm what is at a minimum required under the new ICANN Bylaws. In the past both a communication as well as the adoption of a motion have been used to confirm the nomination. Now the GNSO Chair also needs to notify the EC Administration in addition to the ICANN Board Secretary. In case a motion is required, it will obviously need to wait until the next Council meeting which has been scheduled for 18 May. If a letter from the GNSO Chair is sufficient, following the notification that has been received from the NCPH, staff can work with James to get this done as soon as possible. Best regards, Marika On 5/3/17, 19:04, "council-bounces(a)gnso.icann.org on behalf of icannlists" <council-bounces(a)gnso.icann.org on behalf of icannlists(a)winston.com> wrote: Do we need a GNSO Motion to make this formal, or does it just happen? If so, is today the deadline? Best, Paul -----Original Message----- From: council-bounces(a)gnso.icann.org [mailto:council-bounces@gnso.icann.org] On Behalf Of James M. Bladel Sent: Wednesday, May 03, 2017 2:30 PM To: GNSO Council List <council(a)gnso.icann.org> Subject: [council] FW: Board Seat #14 Election Councilors – Please see below for an announcement from Tapani. Thank you, J. On 5/3/17, 7:47 , "Tapani Tarvainen" <ncsg(a)tapani.tarvainen.info> wrote: Dear James, On behalf of NCPH I'd like to inform you that NCPH has elected Matthew Shears <matthew(a)intpolicy.com> to the Board, replacing Markus Kummer on seat #14. The election was conducted by vote among NCPH councillors, with the following result: Total Ballots Cast (including duplicates): 13 Ballots Counted (excluding duplicates): 12 Voters Who Haven't Voted: 1 Board Seat 14 1: 11 votes [] Matthew Shears 2: 1 vote [] Markus Kummer 3: 0 votes [] Abstain Sincerely, Tapani Tarvainen Non-Commercial Stakeholder Group Chair _______________________________________________ council mailing list council(a)gnso.icann.org https://mm.icann.org/mailman/listinfo/council ________________________________ The contents of this message may be privileged and confidential. If this message has been received in error, please delete it without reading it. Your receipt of this message is not intended to waive any applicable privilege. Please do not disseminate this message without the permission of the author. Any tax advice contained in this email was not intended to be used, and cannot be used, by you (or any other taxpayer) to avoid penalties under applicable tax laws and regulations. _______________________________________________ council mailing list council(a)gnso.icann.org https://mm.icann.org/mailman/listinfo/council

2 1

Path forward for CCWG-IG
by James M. Bladel 04 May '17

04 May '17

Colleagues – At our meeting at ICANN57 (Hyderabad) the GNSO Council extended its support as a Chartering Organization for this CCWG, but tasked the leadership of this group to review its charter, and come to ICANN58 (Copenhagen) with a report of its findings and, potentially, a revised charter. (https://gnso.icann.org/en/council/resolutions#20161107-3) As a result, the CCWG presented an updated charter shortly before our meeting in Copenhagen, but the Council did not have sufficient time to consider it during our Public Meeting at ICANN58 (http://mm.icann.org/pipermail/council/2017-March/019816.html) Finally, we briefly discussed this topic during our last meeting on 20 APR, but no action was taken. (https://gnso.icann.org/en/meetings/agenda-council-20apr17-en.htm, Item #8). I propose that we target our next meeting (18 MAY) for a decision on this revised charter, and the GNSO’s continued participation as a Chartering Organization in the CCWG. With this in mind, I ask all Councilors to discuss the revised charter with their respective SG/C (and here on the Council list) with the goal of submitting a relevant motion supporting or withdrawing from this CCWG by our Motion & Document deadline (currently 8 MAY). Thank you, J.

4 5

MOTION FOR ELECTRONIC (EMAIL) VOTE - Initiate Amendment Process on Specific Red Cross Names
by James M. Bladel 04 May '17

04 May '17

Councilors – Attached and copied below, please find an amended version of the Motion to Initiate Policy Amendment Process on Specific Red Cross Names that was discussed during our last meeting. Recall that, during our last GNSO Council call on 20 April, the Council agreed to defer this Motion to an electronic vote, in order to allow for certain updates to be made to the text of the motion. Also note that the Council agreed to proceed with an electronic vote outside a regularly scheduled Council meeting. The updated language of the motion has been reviewed and approved by me as its proposer, and Michele and Rubens as its seconders. It includes some minor clarifications received as feedback from the ICRC representatives, but does not include any items that materially changed the scope of the affected strings, or any other items that were not discussed previously in Copenhagen. This email will also serve as notice that, as Council Chair, I am hereby formally providing all Councilors with the requisite minimum 7 days’ advance notice of the electronic vote, in accordance with Section 4.10.2.d. of the GNSO Operating Procedures (https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf). The 4-day voting period will begin at 23:59 UTC on Tuesday 2 May 2017 and close at 23:59 UTC on Saturday 6 May 2017. (Please be reminded that the GNSO Operating Procedures require that electronic voting be an open vote, and its outcome be published and recorded, with accompanying voter statements, if any, as minutes for purposes of formal record keeping.) Thank you, J. ------------------ James Bladel GNSO Chair _______________________ Initiation of Policy Amendment Process on Specific Red Cross and Red Crescent Names - Deferred to electronic vote Submitted by: James Bladel Seconded: Rubens Kuhl, Michele Neylon WHEREAS, in November 2013, the GNSO completed a Policy Development Process (PDP) which resulted in a number of consensus recommendations for protecting the identifiers of International Governmental Organizations and International Non-Governmental Organizations, including the International Red Cross and Red Crescent Movement (Movement), at the top and second level in all generic top-level domains (gTLDs) (PDP Working Group Final Report: https://gnso.icann.org/en/issues/igo-ingo-final-10nov13-en.pdf, with Minority Statements: https://gnso.icann.org/en/issues/igo-ingo-final-minority-positions-10nov13-…<https://gnso.icann.org/en/issues/igo-ingo-final-minority-positions-10nov13-…)>); WHEREAS, the GNSO Council approved all the PDP consensus recommendations on 20 November 2013 (http://gnso.icann.org/en/council/resolutions#20131120-2<http://gnso.icann.org/en/council/resolutions#20131120-2)>) and, following a mandatory public comment period on the final PDP recommendations, sent its Recommendations Report to the ICANN Board on 23 January 2014 (https://gnso.icann.org/en/issues/council-board-igo-ingo-23jan14-en.pdf<https://gnso.icann.org/en/issues/council-board-igo-ingo-23jan14-en.pdf)>); WHEREAS, on 30 April 2014 the Board adopted those of the GNSO’s PDP recommendations that were consistent with GAC advice on the topic, which in relation to the Movement were for the terms “Red Cross”, “Red Crescent”, “Red Crystal”, and “Red Lion & Sun” (referred to as “Scope 1 Identifiers” by the PDP Working Group) to be reserved at the top and second levels, with an Exception Procedure to be designed for the affected organization (http://www.icann.org/en/groups/board/documents/resolutions-30apr14-en.htm#2…<http://www.icann.org/en/groups/board/documents/resolutions-30apr14-en.htm#2…)>); WHEREAS, between June 2014 and January 2015 the Board and the GNSO Council engaged in discussions of the remaining inconsistencies between GAC advice and GNSO policy, which in relation to the Movement concerned the names of 189 National Red Cross and Red Crescent Societies, and the names and acronyms of the International Committee of the Red Cross and International Federation of the Red Cross and Red Crescent Societies (referred to as “Scope 2 Identifiers” by the PDP Working Group); WHEREAS, at ICANN57 in November 2016 the Board proposed that the GAC and the GNSO engage in a facilitated, good faith discussion to attempt to resolve the remaining inconsistencies between GAC public policy advice and GNSO consensus policy recommendations regarding the “Scope 2 Identifiers” of the Movement; WHEREAS, representatives from the GAC and the GNSO engaged in such a facilitated, good faith discussion at ICANN58 in March 2017 during which the following matters were noted: (1) The public policy considerations associated with protecting the Movement’s identifiers in the domain name system (DNS); (2) The GAC’s rationale for seeking permanent protection for the terms most closely associated with the Movement and its respective components is grounded in the protections of the designations “Red Cross”, “Red Crescent”, “Red Lion and Sun”, and “Red Crystal” under international treaty law and under multiple national laws; (3) The list of names of the Red Cross and Red Crescent National Societies is a finite, limited list of specific names of the National Societies recognized within the Movement (http://www.ifrc.org/Docs/ExcelExport/NS_Directory.pdf ); (4) There are no other legitimate uses for these terms; and (5) The GAC had provided clarification following the completion of the GNSO PDP, via its March 2014 Singapore Communique, on the finite scope of the specific list of Movement names for which permanent protections were being requested (https://gacweb.icann.org/download/attachments/28278854/Final%20Communique%2…<https://gacweb.icann.org/download/attachments/28278854/Final%20Communique%2…)>); WHEREAS, following the GAC-GNSO discussion, the Board passed a resolution on 16 March 2017 requesting that the GNSO initiate its process for Amendments or Modifications of Approved Policies, as described in Section 16 of the GNSO PDP Manual (https://gnso.icann.org/en/council/annex-2-pdp-manual-01sep16-en.pdf<https://gnso.icann.org/en/council/annex-2-pdp-manual-01sep16-en.pdf)>), to consider amending the GNSO’s approved policy concerning the specific names of the Red Cross and Red Crescent National Societies and the specific names International Committee of the Red Cross and International Federation of Red Cross and Red Crescent Societies (collectively, Recommendation 5 in Section 3.1 of the PDP Working Group Final Report): and WHEREAS, the GNSO Council agrees that the aforementioned set of exceptional circumstances provides a justifiable basis for the Council to take this extraordinary step to reconsider the policy recommendation and that this is not to be viewed as the Council’s consent to reopen PDP recommendations in all cases where GNSO-developed policy is in discord with GAC advice: RESOLVED, 1.The GNSO Council hereby initiates the process described in Section 16 of the GNSO PDP Manual; accordingly, the GNSO Council requests that the PDP Working Group be reconvened for the purpose of consultation by the GNSO Council on the following proposed amendment to Recommendation 5 in Section 3.1 of the PDP Working Group Final Report: (a) The full names of the 190 Red Cross National Societies and the full names of the International Committee of the Red Cross and International Federation of Red Cross and Red Crescent Societies are to be placed into Specification 5 of the Base gTLD Registry Agreement, with an exception procedure to be created for cases where the relevant Red Cross Red Crescent Movement organization wishes to apply for their protected string at the second level; (b) In placing the specified identifiers into Specification 5 of the Registry Agreement, this should apply to an exact match of the full name of the relevant National Society recognized within the International Red Cross and Red Crescent Movement (in English and the official languages of its state of origin), the full names of the International Committee of the Red Cross and of the International Federation of Red Cross and Red Crescent Societies (in the six official United Nations languages) and a defined limited set of variations of these names; and (c) In considering the proposed amendment, account is to be duly taken of the matters noted during the GAC-GNSO facilitated discussion at ICANN58 as well as of the GAC’s public policy advice to reserve the finite list of names of the Red Cross and Red Crescent National Societies, as recognized within the International Red Cross and Red Crescent Movement, in all gTLDs. 2. In accordance with Section 16 of the PDP Manual, the GNSO Council directs ICANN staff to post the proposed amendment to Recommendation 5 for public comment, for a period of 30 days commencing from the date of the first meeting of the reconvened PDP Working Group. 3. In accordance with Section 16 of the PDP Manual, the GNSO Council intends to put the proposed amendment to a vote following consultation with the PDP Working Group and the conclusion of the requisite public comment period. The GNSO Council notes that approval of the proposed amendment requires a Supermajority Vote of both Houses in favour of the amendment. 4. The Council thanks all of those who participated in the talks at ICANN58 in Copenhagen, and in particular Bruce Tonkin for moderating the discussion.

7 11

FW: Board Seat #14 Election
by James M. Bladel 04 May '17

04 May '17

Councilors – Please see below for an announcement from Tapani. Thank you, J. On 5/3/17, 7:47 , "Tapani Tarvainen" <ncsg(a)tapani.tarvainen.info> wrote: Dear James, On behalf of NCPH I'd like to inform you that NCPH has elected Matthew Shears <matthew(a)intpolicy.com> to the Board, replacing Markus Kummer on seat #14. The election was conducted by vote among NCPH councillors, with the following result: Total Ballots Cast (including duplicates): 13 Ballots Counted (excluding duplicates): 12 Voters Who Haven't Voted: 1 Board Seat 14 1: 11 votes [] Matthew Shears 2: 1 vote [] Markus Kummer 3: 0 votes [] Abstain Sincerely, Tapani Tarvainen Non-Commercial Stakeholder Group Chair

2 1

FW: [soac-chairs] Jordan Carter - ccNSO appointed co-chair of the CCWG-Accountability
by James M. Bladel 03 May '17

03 May '17

Councilors – See below for an announcement from Katrina: The ccNSO has appointed Jordan Carter (.NZ) to replace Mathieu. Thank you, J. From: <soac-chairs-bounces(a)icann.org> on behalf of Katrina Sataki <katrina(a)nic.lv> Date: Wednesday, May 3, 2017 at 8:17 Subject: [soac-chairs] Jordan Carter - ccNSO appointed co-chair of the CCWG-Accountability Dear Thomas and Leon, As you know, the ccNSO Council received a letter of resignation from Mathieu Weill effective 28 April. In his letter Mathieu announced that he was stepping down from the position of the ccNSO appointed co-chair of the CCWG Accountability. I am pleased to inform you that the ccNSO Council has asked Jordan Carter (.nz) to replace Mathieu as the ccNSO appointed co-chair of the CCWG Accountability effective immediately, and Jordan kindly accepted the challenge. As to the replacement of Mathieu as a member of the CCWG, we will inform you at a later stage after we have concluded our call for volunteer process. On behalf of the ccNSO Council, ]{atrina Sataki Chair

1 0

Update: Notification of Electronic vote: Motion to Initiation of Policy Amendment Process on Specific Red Cross and Red Crescent Names: 3 May 2017 - 7 May 2017
by Nathalie Peregrine 03 May '17

03 May '17

Dear Councilors, The GNSO Council email ballot on the motion to initiate a policy amendment process of specific Red Cross Names will be launched shortly. Considering the friendly amendment made to Resolved Clause 2, (please see updated motion here: (https://community.icann.org/x/fwLfAw) which has been accepted by the Motion seconders, the electronic vote will now start a day later. The vote opens at 23:59 UTC on Wednesday 3 May 2017 and closes at 23:59 UTC on Sunday 7 May 2017. Please make sure that you receive your ballot, from tally(a)icann.org<mailto:tally@icann.org>, and if you do not please let me know immediately: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Please remember that if you are off email, you can cast your vote by voice, but please provide me with a telephone number before 1 May. Please be sure to mark only one response: · In favour, · Not in favour, · Abstain Please also note the following applicable procedures: o The Operating Procedures do not permit absentee voting for either motion. Under Section 4.5 of the GNSO Operating Procedures, an abstention counts as a vote “not in favour”. The ballot includes a text box for you to state your reason(s) if you wish, should you decide to abstain from voting on either motion. o The voting threshold required for the motion to pass successfully is a simple majority of the Council. o In accordance with the rules for a vote outside a Council meeting, this ballot will be an open vote (i.e. not secret) and we will record and publish the outcomes as required by the GNSO Operating Procedures. Please let me know if you have any questions. Thank you. Kind regards, Nathalie Nathalie Peregrine Specialist, SOAC Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

Timing of Vote (Re: MOTION FOR ELECTRONIC (EMAIL) VOTE - Initiate Amendment Process on Specific Red Cross Names)
by Mary Wong 03 May '17

03 May '17

Dear all, Following consultation with James as the GNSO Chair, staff will hold off from sending out ballots for the electronic vote on this motion for at least the next 24 hours. This step is being taken to allow Michele and Rubens, as seconders of the motion, to indicate whether or not they accept the proposed amendment (below) as friendly, and Paul and others to provide follow up comments. Michele and/or Rubens – please note, and thank you. Thanks and cheers Mary From: "James M. Bladel" <jbladel(a)godaddy.com> Date: Tuesday, May 2, 2017 at 18:56 To: icannlists <icannlists(a)winston.com>, Mary Wong <mary.wong(a)icann.org>, Rafik Dammak <rafik.dammak(a)gmail.com> Cc: GNSO Council List <council(a)gnso.icann.org> Subject: Re: [council] [Ext] Re: MOTION FOR ELECTRONIC (EMAIL) VOTE - Initiate Amendment Process on Specific Red Cross Names Paul – The process outlined in Section 16 ultimately leaves the decision to the Council on whether/how to amend a previous PDP, taking in to account input from Public Comment and in consultation with the previous PDP working group. But as I noted below, it isn’t our intention to “fix” the PDP’s recommendations with the language in the motion, but instead to give some guidance to the re-convened PDP working group, and for the Public Comment and Council to consider their recommended amendments (if any). I can see your concern is that, if we hold a comment period on the proposed amendment in the motion, while at the same time asking the PDP WG to reconvene and consider this same language, it gives the perception that the PDP WG is simply being asked to rubber stamp the predetermined outcome. And this was not the intention behind including the amendment in the motion. To make this explicitly clear, I’m proposing that we delay the Public Comment period on the proposed motion until –after- the reconvened PDP WG has delivered their recommendations. This would change Resolved #2 to read: 2. In accordance with Section 16 of the PDP Manual, the GNSO Council directs ICANN staff to post the recommendations of the reconvened PDP Working Group, and its proposed amendment(s) to Recommendation 5, if any, for public comment for a period of 30 days following the conclusion of the PDP WG. Please indicate whether this address your/IPC concerns, and I’ll ask that the Seconders consider this amendment as Friendly. Thank you, J. From: icannlists <icannlists(a)winston.com> Date: Tuesday, May 2, 2017 at 16:43 To: Mary Wong <mary.wong(a)icann.org>, "James M. Bladel" <jbladel(a)godaddy.com>, Rafik Dammak <rafik.dammak(a)gmail.com> Cc: GNSO Council List <council(a)gnso.icann.org> Subject: RE: [council] [Ext] Re: MOTION FOR ELECTRONIC (EMAIL) VOTE - Initiate Amendment Process on Specific Red Cross Names Thanks Mary. James, the concerns we are hearing from our folks deal with whether or not the work of the revived WG will be taken seriously. The motion seems to indicate that the public comment period for the work of the Small Group will run simultaneously with the work of the revived WG. What is the WG comes to conclusions which are not consistent with the Small Group’s conclusions? Will the WG’s conclusions be given full weight? Is there any mechanism for the work of the revived WG to be published for comment? If not, why would revived WG members cooperate if they are just going to be expected to be a rubber stamp? Best, Paul From: council-bounces(a)gnso.icann.org [mailto:council-bounces@gnso.icann.org] On Behalf Of Mary Wong Sent: Wednesday, April 26, 2017 5:52 PM To: James M. Bladel <jbladel(a)godaddy.com>; Rafik Dammak <rafik.dammak(a)gmail.com> Cc: GNSO Council List <council(a)gnso.icann.org> Subject: Re: [council] [Ext] Re: MOTION FOR ELECTRONIC (EMAIL) VOTE - Initiate Amendment Process on Specific Red Cross Names Hello everyone – staff confirms James’ understanding of when and how the limited set of variations of the 190 Red Cross National Society names. The desire to have a single, limited list of specific variants of those 190 names is hopefully reflected in the language of the Board request as well as the current GNSO Council motion. Regarding the number of Red Cross National Societies: The number 189 was used in the Whereas clauses of the motion because there were 189 such societies at the time. The 190th Red Cross National Society (Tuvalu) only became part of the International Red Cross Red Crescent Movement in December 2015. In this regard, Councilors may find it helpful to know that stringent criteria apply to the formation and recognition of a Red Cross National Society. For example, it can only be formed in a State that is party to the Geneva Conventions (currently, 196), and it must be formally recognized by the International Committee of the Red Cross in order to become a component of the Movement. Perhaps one way to avoid confusion is to use the phrase “then-189” in the Whereas clauses and “now-190” in the Resolved portion? On the motion: As James noted, this motion covers the kick-off of the potential amendment process. At the end of the consultations with the reconvened PDP Working Group and following review of the public comments received, the Council will still have to vote on whether to adopt the proposed amendment – and that motion can carry only by Supermajority vote. I hope this is helpful. Cheers Mary From: <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of "James M. Bladel" <jbladel(a)godaddy.com<mailto:jbladel@godaddy.com>> Date: Wednesday, April 26, 2017 at 11:30 To: Rafik Dammak <rafik.dammak(a)gmail.com<mailto:rafik.dammak@gmail.com>> Cc: GNSO Council List <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: [Ext] Re: [council] MOTION FOR ELECTRONIC (EMAIL) VOTE - Initiate Amendment Process on Specific Red Cross Names Hello Rafik. I’ll try to address your questions below, but hoping Staff (Mary) will correct me if I get something wrong. A tighter definition for “limited set of variations” will be part of the work of the amendment (if any) resulting from the reconstituted PDP WG. But speaking generally, we noted that some groups had a formal name that was significant different than the name that it used commonly online For example, a national organization might be formally recognized as “The Red Cross of Canada” but was more commonly known as “Canadian Red Cross.” (example only, I have no idea if this organization fits the problem statement). The idea is that definitive articles and prepositions like “The” or “of” may or may not be included in the formal name, or dropped from the common name. Note that this is different than language variations / translations, and is significantly less than what the GAC/ICRC was requesting (which was a much larger list of variants and all permutations). As for the shift in numbers: The original PDP was focused on 189 organizations, but we were informed in Copenhagen that a new org was recently recognized, bringing the current number to 190. I agree that we should standardize all language on this latter figure. Good catch. And finally, a note for all Councilors: As you discuss this motion amongst your SG/C, please remind them that all we are considering is a motion that initiates a process, and that this process includes additional deliberations of the PDP WG, a Public Comment period, and a final Council vote on any resulting recommendations, assuming they differ from the original PDP conclusions. It is therefore not necessary (and perhaps not appropriate) to try and “fix” these concerns in the motion itself. But instead, the motion should launch the process, and the process can address the more substantive questions & concerns. In short, let’s have some confidence that the Working Group will conduct a thorough and comprehensive review of the issues, and take every opportunity to course-correct them if they do not. I hope this is helpful. Thank you, J. ------------------ James Bladel GNSO Chair From: Rafik Dammak <rafik.dammak(a)gmail.com<mailto:rafik.dammak@gmail.com>> Date: Tuesday, April 25, 2017 at 19:51 To: "James M. Bladel" <jbladel(a)godaddy.com<mailto:jbladel@godaddy.com>> Cc: GNSO Council List <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: Re: [council] MOTION FOR ELECTRONIC (EMAIL) VOTE - Initiate Amendment Process on Specific Red Cross Names Hi James, quick question with regard to Resolved.1.b which mentions "a defined limited set of variations of these names" how and who will decide for those variations? btw I just noticed that in the whereas we have "189 National Red Cross and Red Crescent Societies," and in resolved "190 Red Cross National Societies", shouldn't be the same number (the latter is missing "Red Crescent" mention, a matter of consistency within the motion)? Best, Rafik 2017-04-26 7:04 GMT+09:00 James M. Bladel <jbladel(a)godaddy.com<mailto:jbladel@godaddy.com>>: Councilors – Attached and copied below, please find an amended version of the Motion to Initiate Policy Amendment Process on Specific Red Cross Names that was discussed during our last meeting. Recall that, during our last GNSO Council call on 20 April, the Council agreed to defer this Motion to an electronic vote, in order to allow for certain updates to be made to the text of the motion. Also note that the Council agreed to proceed with an electronic vote outside a regularly scheduled Council meeting. The updated language of the motion has been reviewed and approved by me as its proposer, and Michele and Rubens as its seconders. It includes some minor clarifications received as feedback from the ICRC representatives, but does not include any items that materially changed the scope of the affected strings, or any other items that were not discussed previously in Copenhagen. This email will also serve as notice that, as Council Chair, I am hereby formally providing all Councilors with the requisite minimum 7 days’ advance notice of the electronic vote, in accordance with Section 4.10.2.d. of the GNSO Operating Procedures (https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf)[gnso.icann.…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…>. The 4-day voting period will begin at 23:59 UTC on Tuesday 2 May 2017 and close at 23:59 UTC on Saturday 6 May 2017. (Please be reminded that the GNSO Operating Procedures require that electronic voting be an open vote, and its outcome be published and recorded, with accompanying voter statements, if any, as minutes for purposes of formal record keeping.) Thank you, J. ------------------ James Bladel GNSO Chair _______________________ Initiation of Policy Amendment Process on Specific Red Cross and Red Crescent Names - Deferred to electronic vote Submitted by: James Bladel Seconded: Rubens Kuhl, Michele Neylon WHEREAS, in November 2013, the GNSO completed a Policy Development Process (PDP) which resulted in a number of consensus recommendations for protecting the identifiers of International Governmental Organizations and International Non-Governmental Organizations, including the International Red Cross and Red Crescent Movement (Movement), at the top and second level in all generic top-level domains (gTLDs) (PDP Working Group Final Report: https://gnso.icann.org/en/issues/igo-ingo-final-10nov13-en.pdf[gnso.icann.o…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_issu…>, with Minority Statements: https://gnso.icann.org/en/issues/igo-ingo-final-minority-positions-10nov13-…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_issu…>); WHEREAS, the GNSO Council approved all the PDP consensus recommendations on 20 November 2013 (http://gnso.icann.org/en/council/resolutions#20131120-2[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_counc…>) and, following a mandatory public comment period on the final PDP recommendations, sent its Recommendations Report to the ICANN Board on 23 January 2014 (https://gnso.icann.org/en/issues/council-board-igo-ingo-23jan14-en.pdf[gnso…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_issu…>); WHEREAS, on 30 April 2014 the Board adopted those of the GNSO’s PDP recommendations that were consistent with GAC advice on the topic, which in relation to the Movement were for the terms “Red Cross”, “Red Crescent”, “Red Crystal”, and “Red Lion & Sun” (referred to as “Scope 1 Identifiers” by the PDP Working Group) to be reserved at the top and second levels, with an Exception Procedure to be designed for the affected organization (http://www.icann.org/en/groups/board/documents/resolutions-30apr14-en.htm#2…<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_en_groups…>); WHEREAS, between June 2014 and January 2015 the Board and the GNSO Council engaged in discussions of the remaining inconsistencies between GAC advice and GNSO policy, which in relation to the Movement concerned the names of 189 National Red Cross and Red Crescent Societies, and the names and acronyms of the International Committee of the Red Cross and International Federation of the Red Cross and Red Crescent Societies (referred to as “Scope 2 Identifiers” by the PDP Working Group); WHEREAS, at ICANN57 in November 2016 the Board proposed that the GAC and the GNSO engage in a facilitated, good faith discussion to attempt to resolve the remaining inconsistencies between GAC public policy advice and GNSO consensus policy recommendations regarding the “Scope 2 Identifiers” of the Movement; WHEREAS, representatives from the GAC and the GNSO engaged in such a facilitated, good faith discussion at ICANN58 in March 2017 during which the following matters were noted: (1) The public policy considerations associated with protecting the Movement’s identifiers in the domain name system (DNS); (2) The GAC’s rationale for seeking permanent protection for the terms most closely associated with the Movement and its respective components is grounded in the protections of the designations “Red Cross”, “Red Crescent”, “Red Lion and Sun”, and “Red Crystal” under international treaty law and under multiple national laws; (3) The list of names of the Red Cross and Red Crescent National Societies is a finite, limited list of specific names of the National Societies recognized within the Movement (http://www.ifrc.org/Docs/ExcelExport/NS_Directory.pdf[ifrc.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ifrc.org_Docs_Excel…> ); (4) There are no other legitimate uses for these terms; and (5) The GAC had provided clarification following the completion of the GNSO PDP, via its March 2014 Singapore Communique, on the finite scope of the specific list of Movement names for which permanent protections were being requested (https://gacweb.icann.org/download/attachments/28278854/Final%20Communique%2…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gacweb.icann.org_downl…>); WHEREAS, following the GAC-GNSO discussion, the Board passed a resolution on 16 March 2017 requesting that the GNSO initiate its process for Amendments or Modifications of Approved Policies, as described in Section 16 of the GNSO PDP Manual (https://gnso.icann.org/en/council/annex-2-pdp-manual-01sep16-en.pdf[gnso.ic…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…>), to consider amending the GNSO’s approved policy concerning the specific names of the Red Cross and Red Crescent National Societies and the specific names International Committee of the Red Cross and International Federation of Red Cross and Red Crescent Societies (collectively, Recommendation 5 in Section 3.1 of the PDP Working Group Final Report): and WHEREAS, the GNSO Council agrees that the aforementioned set of exceptional circumstances provides a justifiable basis for the Council to take this extraordinary step to reconsider the policy recommendation and that this is not to be viewed as the Council’s consent to reopen PDP recommendations in all cases where GNSO-developed policy is in discord with GAC advice: RESOLVED, 1.The GNSO Council hereby initiates the process described in Section 16 of the GNSO PDP Manual; accordingly, the GNSO Council requests that the PDP Working Group be reconvened for the purpose of consultation by the GNSO Council on the following proposed amendment to Recommendation 5 in Section 3.1 of the PDP Working Group Final Report: (a) The full names of the 190 Red Cross National Societies and the full names of the International Committee of the Red Cross and International Federation of Red Cross and Red Crescent Societies are to be placed into Specification 5 of the Base gTLD Registry Agreement, with an exception procedure to be created for cases where the relevant Red Cross Red Crescent Movement organization wishes to apply for their protected string at the second level; (b) In placing the specified identifiers into Specification 5 of the Registry Agreement, this should apply to an exact match of the full name of the relevant National Society recognized within the International Red Cross and Red Crescent Movement (in English and the official languages of its state of origin), the full names of the International Committee of the Red Cross and of the International Federation of Red Cross and Red Crescent Societies (in the six official United Nations languages) and a defined limited set of variations of these names; and (c) In considering the proposed amendment, account is to be duly taken of the matters noted during the GAC-GNSO facilitated discussion at ICANN58 as well as of the GAC’s public policy advice to reserve the finite list of names of the Red Cross and Red Crescent National Societies, as recognized within the International Red Cross and Red Crescent Movement, in all gTLDs. 2. In accordance with Section 16 of the PDP Manual, the GNSO Council directs ICANN staff to post the proposed amendment to Recommendation 5 for public comment, for a period of 30 days commencing from the date of the first meeting of the reconvened PDP Working Group. 3. In accordance with Section 16 of the PDP Manual, the GNSO Council intends to put the proposed amendment to a vote following consultation with the PDP Working Group and the conclusion of the requisite public comment period. The GNSO Council notes that approval of the proposed amendment requires a Supermajority Vote of both Houses in favour of the amendment. 4. The Council thanks all of those who participated in the talks at ICANN58 in Copenhagen, and in particular Bruce Tonkin for moderating the discussion. _______________________________________________ council mailing list council(a)gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council ________________________________ The contents of this message may be privileged and confidential. If this message has been received in error, please delete it without reading it. Your receipt of this message is not intended to waive any applicable privilege. Please do not disseminate this message without the permission of the author. Any tax advice contained in this email was not intended to be used, and cannot be used, by you (or any other taxpayer) to avoid penalties under applicable tax laws and regulations.

3 3

Action Items: GNSO Council meeting 20 April 2017
by Nathalie Peregrine 02 May '17

02 May '17

Dear Councilors, Apologies for the delay in sending this, it was stuck in my Drafts folder and I only noticed today. Please find the action items, below and as attachment, arising from the GNSO Council meeting on 20 April 2017. Please take note of the action items coming out of the Council meeting and the proposed timing for delivering on these actions. The next GNSO Council meeting is on the 18 May 2017. ACTION ITEMS FROM GNSO COUNCIL MEETING 20 APRIL 2017 Item 2: Opening Remarks / Review of Projects & Action List Open Action Item from ICANN58: * Councilors Erika Mann and Keith Drazek to circulate updated draft on proposed Council action following the letter from the Thick Whois IRT on privacy issues Item 4. COUNCIL VOTE – Approval of GNSO Council Review of the GAC Communique from Copenhagen Action items: * GNSO Councilors to provide final input on draft GNSO Council Review of the GAC Communique (DONE) * Council Chairs and staff to prepare letter to the ICANN Board summarizing GNSO Council input; letter to be sent in time for the Board-GAC meeting on 27 April 2017 (DONE) Item 5. COUNCIL VOTE – Initiation of GNSO Process for Amending Approved GNSO Policy Recommendations Relating to Certain Red Cross Movement Names Immediate Action Items: * GNSO Council Chairs and staff to circulate updated motion to the Council list for review (DONE) * GNSO Council Chair to formally announce dates and times of electronic balloting period pursuant to GNSO Operating Procedures for Voting Outside a Meeting (DONE) * ICANN staff to conduct electronic vote and announce voting results (IN PROCESS) Action Items (if Vote is Successful): * ICANN staff to reconvene original PDP Working Group * ICANN staff to post proposed policy amendment for public comment for 30 days commencing from the date of the first meeting of the reconvened PDP Working Group * GNSO Council to vote on final proposal following close of public comment period and receipt of input from the reconvened PDP Working Group Item 6: COUNCIL VOTE – GNSO Council Comments on the Proposed ICANN Budget for Financial Year (FY) 2018 Action Items: * ICANN staff to submit approved comments to the public comment forum (DONE) Item 7: COUNCIL VOTE – Approval of GNSO Nominees for the Registration Directory Services Review Team Action Items: * ICANN staff to communicate the names of the GNSO-endorsed candidates to staff supporting the RDS Review Team (RDS-RT) (DONE) * ICANN staff to inform the endorsed candidates that the GNSO Council expects that, if selected for the RDS-RT, the nominee will represent the views of the entire GNSO community in their work on the RDS-RT, and will provide regular feedback as a group on the discussions taking place as well as the positions being taken by GNSO representatives on the RDS-RT (IN PROCESS) * ICANN staff to request that staff colleagues supporting the RDS-RT to notify the unsuccessful applicants who did not receive endorsement (if any) for this RDS-RT, thanking them for their interest (DONE) Item 8: COUNCIL DISCUSSION – Updated Charter for the Cross Community Working Group on Internet Governance Action Items: * Councilors to work with staff to compile a list of questions to be sent to the CCWG-IG * Topic to be added to the May Council meeting agenda either as a further discussion item or a motion on the GNSO’s next steps on this topic Item 9: COUNCIL DISCUSSION – PLANNING FOR ICANN59 IN JOHANNESBURG, JUNE 2017 Action Items: * Council chairs to work with staff to update GNSO block schedule based on overall meeting schedule updates As a reminder, all Action items in progress can be found posted on the wiki page here: https://community.icann.org/x/RgZlAg[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> Please let me know if I missed anything or if you have questions. Thank you. Kind regards, Nathalie -- Nathalie Peregrine Specialist, SOAC Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0