- Gnso-igo-ingo - lists.icann.org

Call for IRT - Policy Implementation: Red Cross list update
by mail＠berrycobb.com Feb. 28, 2019

Feb. 28, 2019

Hi Reconvened WG Members, A call for volunteers for the IRT implementing the Board adopted recommendations is below. If you are not already a part of the IRT that implemented the first round of consensus policies for IGOs & INGOs and are interested to see this portion through, please send a note to Dennis. We expect the first meeting towards the end of March 2019. Thank you. B GNSO Policy Consultant @berrycobbb --------------------------------------------------------------------------------------------------------------------------- Call for Volunteers: IGO and INGO Identifiers Protection Policy Implementation On 27 January 2019, the Board <https://www.icann.org/resources/board-material/resolutions-2019-01-27-en#2.d> adopted policy recommendations on Protections for Certain Red Cross and Red Crescent Names in All Generic Top-Level Domains and directed their implementation. This new consensus policy will supplement the previously-adopted <https://www.icann.org/resources/pages/igo-ingo-protection-policy-2018-01-16…> Protection of IGO and INGO Identifiers in All gTLDs Policy by which the specific terms Red Cross, Red Crescent, Red Lion & Sun and Red Crystal were withheld from registration. The Implementation Review Team (IRT) supporting the implementation of the <https://www.icann.org/resources/pages/igo-ingo-protection-policy-2018-01-16…> Protection of IGO and INGO Identifiers in All gTLDs Policy will add these new recommendations to its scope. The key responsibilities of the IRT are as follows: * Work with ICANN org to ensure that the implementation fulfills the original intentions of the approved policy recommendations * Review the proposed implementation plan as drafted by ICANN org for the recommendations as approved by the Board * Assist in case of questions or need for clarification related to the adopted recommendations * Advise on technical and operational details related to the implementation of recommendations by contracted parties For this IRT, volunteers involved in the Red Cross organization, members from the Reconvened Working Group, and Registry professionals capable of implementing the reservation of labels (that will range in the thousands) in the domain registration process are particularly sought. Familiarity with the <https://gnso.icann.org/sites/default/files/file/field-file-attach/red-cross…> policy recommendations as well as the deliberations that informed those recommendations is a minimum requirement for IRT members. All volunteers responding to this call are expected to understand the role and remit of the IRT for the implementation project. The implementation of these recommendations is estimated to take approximately one year. The IRT is anticipated to meet monthly starting in late March 2019 for one hour. These meeting will be held remotely but there may be opportunities to meet in person during ICANN meetings. Between the meetings, the IRT will be working using collaborative tools. The expected time commitment for supporting the implementation is about one to two hours per week. How to apply To participate, please send an email to <mailto:dennis.chang@icann.org> dennis.chang(a)icann.org before Monday, 18 March 2019, 11:59 UTC. Please see <https://community.icann.org/display/IIPIRT/IGO+and+INGO+Identifiers+Protect…> IGO and INGO Policy IRT wiki page for the list of current IRT members. Background In November 2012, the GNSO Council launched the PDP on the Protection of IGO-INGO Identifiers in All gTLDs. The aim was to consider what the appropriate form and scope of protection for IGO and INGO identifiers would be at both the top level and second level of the Domain Name System (DNS), for the Red Cross, the International Olympic Committee (IOC), and other IGOs and INGOs. All these organizations perform important public interest or humanitarian work. Cybersquatting and related abuse of domain names identical or confusingly similar to their names and acronyms could significantly impact their missions and resources. In April 2014, the Board adopted part of the PDP outcomes, which included consensus recommendations that a limited list of Red Cross, IOC, IGO, and INGO identifiers be reserved. For the Red Cross, these are “Red Cross,” “Red Crescent,” “Red Crystal,” and “Red Lion and Sun” at the top level and second level. For IGOs, only their full organizational names are reserved at the second level. The appropriate protections for many of the other identifiers associated with the Red Cross and IGOs – i.e., Red Cross National Society names, the names and acronyms of the International Red Cross Movement, and IGO acronyms – had not been finalized. The Board facilitated a set of dialogues with the GAC and the GNSO to reconcile the inconsistencies between GAC advice and the GNSO PDP recommendations for the Red Cross names while the discussion continues over the acronyms. In May 2017, the GNSO Council initiated the policy amendment process only for specific names associated with the Red Cross names and reconvened the PDP WG. The recommendations that emerged from the Reconvened PDP WG are as follows: 1. a finite list of the full names of the 191 Red Cross National Societies, the International Committee of the Red Cross (ICRC) and the International Federation of Red Cross and Red Crescent Societies (IFRC) to be placed into Specification 5 of the Base gTLD Registry Agreement [for reservation.] 2. an exception procedure is to be put in place for cases where the relevant RCRC Organization wishes to apply for its protected string(s) at the second level. 3. future error corrections, additions to and deletions [for the list] of reserved names [shall be done] in accordance with the criteria listed in Recommendations #4-6 below. 4. changes to the finite list [to be done] in accordance with the variant criteria as defined by this WG. any and all future changes to the finite list be made only upon notification to ICANN Organization and the confirmation, by designated representatives of the International Red Cross and Red Crescent Movement (Movement), to the effect that: (a) the proposed changes have been communicated to the GAC as well as the GNSO Council; (b) any new National Societies’ names to be added to the list have been recognized in accordance with all the applicable rules and procedures of the Movement; and (c) any proposed deletions from the list would be based on the cessation of operations of that National Society or its removal from the Movement in accordance with all applicable rules and procedures of the Red Cross Movement. a proposed correction of any errors (e.g. in translation or spelling) in the finite list of reserved names be made only through the submission of a formal request to ICANN Organization by official and designated representatives of the International Red Cross and Red Crescent and/or Registry Operators describing in detail the nature of the error and the specific correction to be made in the form of a direct replacement to the erroneous entry. The ICANN Organization shall have the right to refer the request to the GAC or otherwise conduct an investigation into the accuracy of the correction sought. Kind Regards, Dennis S. Chang GDD Services & Engagement Program Director Telephone: +1 213 293 7889 Skype: dennisSchang www.icann.org <http://www.icann.org>

1 0

Revisions required to the Table of National Red Cross and Red Crescent names and identifiers
by Stephane Hankins Feb. 5, 2019

Feb. 5, 2019

Dear Berry, dear Members of the Core Group, I hope this message finds you well. (1) We wish to inform you herewith of several revisions to be brought to the table of National Red Cross and Red Crescent Society identifiers we have submitted, and thus, in order to reflect the recent change in the name of the “Baphalali Swaziland Red Cross Society” to “Baphalali Eswatini Red Cross Society”. This change in the official name of the Swaziland Red Cross follows the decision by the King and Head of State of Swaziland adopted in April 2018 to change the official name of the country to Kingdom of eSwatini (it is my understanding that this change is already reflected in the list of States members of ICANN’s Government Advisory Committee). The change of the official name of the “Baphalali Swaziland Red Cross Society” was confirmed by decision of the National Society’s General Assembly of 8 September 2018. Given that the change of name of the National Society in legal documents (including in the Baphalali eSwatini Red Cross Society’s legislation of recognition) will not be immediately effective, we recommend to keep the list of names in the table unchanged and to add thereto an additional set of identifiers including the new name “eSwatini”. Please find attached herewith consequently a revised list of names for the Baphalali Eswatini Red Cross Society. We could also submit a revised version of the global table if this is easier. (2) We also wish to take this opportunity to ask you when the Board report and the GNSO's recommendations on the red cross and red crescent identifiers are due for consideration by ICANN’s Board. With best wishes to all in 2019 and kind regards, Stéphane Stéphane J. Hankins Legal adviser Cooperation and Coordination within the Movement International Committee of the Red Cross Tel (Prof.):++41 22 730 24 19 From: Gnso-igo-ingo <gnso-igo-ingo-bounces(a)icann.org> On Behalf Of Berry Cobb Sent: Friday, September 28, 2018 7:11 AM To: gnso-igo-ingo(a)icann.org Subject: [Gnso-igo-ingo] Reconvened WG Resolution Adopted Hi All, The GNSO Council adopted all of the Reconvened WG recommendations. The motion carried unanimously. https://gnso.icann.org/en/council/resolutions#20180927-3 Staff will prepare a Board report and an additional public comment will be opened before the Board considers the GNSO recommendations. I suspect there will be brief updates by the GNSO and GAC about this milestone, but it is likely the Board will not consider this until at least December 2018 or early 2019. After which, the IRT will begin the implementation phase. Thank you. Berry Cobb GNSO Policy Consultant @berrycobb _______________________________________________ Gnso-igo-ingo mailing list Gnso-igo-ingo(a)icann.org https://mm.icann.org/mailman/listinfo/gnso-igo-ingo This email has been checked for viruses by Avast antivirus software. www.avast.com _______________________________________________ Gnso-igo-ingo mailing list Gnso-igo-ingo(a)icann.org https://mm.icann.org/mailman/listinfo/gnso-igo-ingo =============================================================================== The ICRC - working to protect and assist people affected by armed conflict and other situations of violence. Find out more: www.icrc.org This e-mail is intended for the named recipient(s) only. Its contents are confidential and may only be retained by the named recipient (s) and may only be copied or disclosed with the consent of the International Committee of the Red Cross (ICRC). If you are not an intended recipient please delete this e-mail and notify the sender. ===============================================================================

4 4

FOR YOUR INFORMATION: Public comment proceeding open for Red Cross PDP recommendations
by Mary Wong Nov. 28, 2018

Nov. 28, 2018

Dear Thomas and Working Group members, As noted in the message below to the GNSO Council, the consensus recommendations from this PDP Working Group are proceeding toward Board consideration, based on the GNSO Council’s approval in September 2018 and after the close of this current public comment proceeding. The current timeline should allow the topic to be placed on the Board’s agenda sometime in early 2019. Thank you all again for all the hard work and collaboration on this reconvened PDP. Staff will continue to keep you informed of progress on the matter. Thanks and cheers Berry and Mary From: council <council-bounces(a)gnso.icann.org> on behalf of Mary Wong <mary.wong(a)icann.org> Date: Wednesday, November 21, 2018 at 14:45 To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] FOR YOUR INFORMATION: Public comment proceeding open for Red Cross PDP recommendations Dear Councilors, This note is to inform you that, in accordance with the transparency requirements of the ICANN Bylaws (Article 3, Section 3.6), a public comment period has just been opened for the final recommendations from the reconvened PDP on Red Cross names: https://www.icann.org/news/announcement-2018-11-21-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…>. You will recall that the GNSO Council approved all the final PDP recommendations at its meeting in September 2018. This public comment proceeding is intended to provide a reasonable opportunity for public input on the proposed policy prior to Board action on the matter. In addition, the Bylaws permit the GAC to provide timely advice at this stage should there be any public policy concerns. Staff currently anticipates that the Board consideration of the PDP recommendations can therefore take place in early 2019, following the close of the public comment period. At that time, staff will forward the PDP Final Report, the GNSO Council’s Recommendations Report (approved by the GNSO Council in October 2018) and any relevant public input to the Board. Under the ICANN Bylaws, the Board is also obliged to take into account any timely GAC advice that may be published. Staff will continue to keep you informed of the status of this matter. Thank you. Cheers Mary Mary Wong Vice President, Strategic Community Operations, Planning & Engagement Internet Corporation for Assigned Names and Numbers (ICANN) Email: mary.wong(a)icann.org<mailto:mary.wong@icann.org> Telephone: +1-603-5744892

2 3

ICANN63: GNSO Sessions How to Get Organized and Remote Participation Details
by Julie Bisland Oct. 8, 2018

Oct. 8, 2018

Dear all, The one-stop wiki page for all your Remote Participation queries is now available. This wiki page covers remote participation details for all GNSO open and public meetings. In addition to this, ICANN meetings' team has put together an updated ICANN meeting website which allows you to download all GNSO-related meetings to your inbox calendar in one go. 2 LINKS TO BOOKMARK NOW: ICANN63 Meeting Schedule<https://63.schedule.icann.org/> GNSO Remote Participation Wiki Page<https://community.icann.org/x/nxVpBQ> Step 1 - Create a profile and your personalized ICANN63 schedule Go to the Meeting Schedule webpage and create a profile and login. Every session on the schedule can be selected and added to your individual schedule by clicking the Add box to the bottom right of each meeting, this adds it to your individual schedule which you can then email to yourself or add to your calendar. See next step. Step 2 - There are two ways to import your schedule into Outlook: once you've added all your chosen meetings to "My Schedule" go to Export. 1. Importing creates a one-time snapshot of your schedule and copies it into Outlook. If you subsequently make changes to your Pathable calendar, they will not be reflected in Outlook. 2. Subscribing creates a live feed of your schedule in Outlook. Outlook checks for changes every few hours and updates your calendar appropriately. * For Outlook calendars: http://support.pathable.com/knowledgebase/articles/81449-moving-your-schedu…<https://urldefense.proofpoint.com/v2/url?u=http-3A__support.pathable.com_kn…> * For Google calendars: http://support.pathable.com/knowledgebase/articles/1313-moving-your-schedul…<https://urldefense.proofpoint.com/v2/url?u=http-3A__support.pathable.com_kn…> Step 3 All Adobe Connect rooms (which can be found on the session information on the ICANN63 Meeting Schedule<https://63.schedule.icann.org/> and on the <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> GNSO Remote Participation Wiki Page<https://community.icann.org/x/nxVpBQ>) will provide audio streaming only, Adobe Connect room microphones will not be enabled. If you cannot join an Adobe Connect room for a session, and will need to dial in with your phone, please refer to the <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> GNSO Remote Participation Wiki Page<https://community.icann.org/x/nxVpBQ> for the audio pass codes and dial in numbers. Please also follow the previous steps if you wish to take part in the session over the phone. Step 4 Please download the mobile app by searching for "ICANN63" in your app stores. Nathalie Peregrine and Terri Agnew will be onsite in Barcelona to assist you directly. For all GNSO meeting related queries (RP or others), please email us at: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> and we will be more than happy to assist! Kind regards, GNSO SO/AC Support team Julie Bisland Secretariat Operations Coordinator for the GNSO Internet Corporation for Assigned Names and Numbers (ICANN) Email: julie.bisland(a)icann.org<mailto:julie.bisland@icann.org> Skype ID: 79613b691cb8a6c1 Find out more about the GNSO by visiting the GNSO Newcomer pages<https://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy…>

1 0

Reconvened WG Resolution Adopted
by Berry Cobb Sept. 29, 2018

Sept. 29, 2018

Hi All, The GNSO Council adopted all of the Reconvened WG recommendations. The motion carried unanimously. https://gnso.icann.org/en/council/resolutions#20180927-3 Staff will prepare a Board report and an additional public comment will be opened before the Board considers the GNSO recommendations. I suspect there will be brief updates by the GNSO and GAC about this milestone, but it is likely the Board will not consider this until at least December 2018 or early 2019. After which, the IRT will begin the implementation phase. Thank you. B Berry Cobb GNSO Policy Consultant @berrycobb

4 3

Additional Information (Re: Recordings, attendance & AC Chat | Reconvened IGO-INGO Protections in all gTLDs PDP Working Group on Red Cross Names Call to Discuss Recommendations| Wednesday, 12 September 2018)
by Mary Wong Sept. 18, 2018

Sept. 18, 2018

Dear Chuck and everyone, To follow up on Chuck’s request, the legal requirements for the formation and recognition of a National Society by the International Committee of the Red Cross are listed in Article 4 of the Statutes of the International Red Cross & Red Crescent Movement: https://www.icrc.org/eng/resources/documents/misc/6erk5h.htm (these were also summarized by the Red Cross representatives and discussed at the facilitated discussion held in Copenhagen, March 2017, during ICANN57: https://gnso.icann.org/sites/default/files/file/field-file-attach/transcrip…) Additional Information: The International Federation of Red Cross & Red Crescent Societies is the official representative of its member national societies, and it has specific rules of procedure governing the admittance of National Societies: https://media.ifrc.org/ifrc/wp-content/uploads/sites/5/2018/02/02_IFRC-Rule… (see, in particular, Rule 2). Collectively, the International Committee of the Red Cross, the International Federation of Red Cross & Red Crescent Societies and the National Societies comprise the International Red Cross & Red Crescent Movement, which is governed by the International Conference of the Red Cross and Red Crescent, the Council of Delegates and the Standing Commission (https://www.icrc.org/eng/resources/documents/misc/components-movement.htm) Overview of Working Group Deliberation Process: At an early stage in its deliberations, the Reconvened PDP Working Group discussed the legal basis and public policy rationale for protecting the designations of the Red Cross National Societies and international movement; you can find the meeting records at https://community.icann.org/display/GWGTCT/2017+Meetings. The discussions included a review of the relevant parts of the prior PDP work and documents submitted for the March 2017 Copenhagen facilitated discussions and subsequently by the Red Cross. These discussions covered the scope of the Geneva Conventions and public policy rationale documented in GAC advice (for instance, at the 17 August 2017 meeting: https://community.icann.org/display/GWGTCT/2017-08-17+IGO+INGO+PDP+Working+…) and also included email follow ups; for instance, Stephane Hankin of the Red Cross specifically responded with additional comments on the legal and public policy basis for protection: https://mm.icann.org/pipermail/gnso-igo-ingo/2017-September/000087.html. The Reconvened PDP Working Group spent a significant portion of its 2018 meetings discussing a process for additions to the list of names (i.e. when a new National Society is formed and recognized) as well as corrections; and it also discussed criteria for determination of the common and usual names (variants) of the list of recognized National Societies submitted by the Red Cross; these meeting records can be reviewed at https://community.icann.org/display/GWGTCT/2018+Meetings. As Chuck noted, these discussions took into account the practical difficulty of having to convene a PDP to approve changes and corrections. We hope this additional and more specific information is helpful. Cheers Mary & Berry From: Gnso-igo-ingo <gnso-igo-ingo-bounces(a)icann.org> on behalf of Chuck <consult(a)cgomes.com> Date: Thursday, September 13, 2018 at 10:51 To: Andrea Glandon <andrea.glandon(a)icann.org>, "gnso-igo-ingo(a)icann.org" <gnso-igo-ingo(a)icann.org>, 'Arsène Tungali' <arsenebaguma(a)gmail.com>, 'Stephanie Perrin' <stephanie.perrin(a)mail.utoronto.ca>, 'Tatiana Tropina' <tatiana.tropina(a)gmail.com>, 'Ayden Férdeline' <icann(a)ferdeline.com>, "mpsilvavalent(a)gmail.com" <mpsilvavalent(a)gmail.com>, "rafik.dammak(a)gmail.com" <rafik.dammak(a)gmail.com>, 'farzaneh badii' <farzaneh.badii(a)gmail.com>, 'Heather Forrest' <haforrestesq(a)gmail.com>, Dennis Chang <dennis.chang(a)icann.org>, Maryam Bakoshi <maryam.bakoshi(a)icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: Re: [Gnso-igo-ingo] Recordings, attendance & AC Chat | Reconvened IGO-INGO Protections in all gTLDs PDP Working Group on Red Cross Names Call to Discuss Recommendations| Wednesday, 12 September 2018 I just listened to the recording. Without minimizing any of the other concerns discussed, I thought that Farzaneh’s concern regarding the process for adding names without a PDP was an important one. I think Mary and Barry answered it at a high level, noting that there would have to be a lengthy international process before that could happen, but I wonder if it might be helpful to outline in brief bullet form what steps the international community and the GNSO would have to go through before a name could be added to the finite list. I understand that it is all in the report, but it might be easier for everyone to grasp it if those steps were listed in a concise manner. On the same topic, I would like to call attention to the WG recommended procedures for updating the finite list; in creating those procedures, the WG was fully cognizant of the time and effort required for a PDP to consider changes. The NCSG has made it abundantly clear that they have limited resources that make it difficult to participate in all PDPs, so I would think that it would be beneficial to avoid PDPs when possible without compromising the bottom-up policy development process and I believe the recommendations sufficiently constrain the update process to accomplish that. Finally, I confess to be the one who suggested maybe the GNSO should consider not allowing SGs to defer motions related to PDPs in which they did not actively participate. First note that I did NOT suggest that such SGs should not be able to participate in the public comment process. Second, let me say that part of the basis of that idea was to create an incentive for WG participation. A WG setting is much better suited for a constructive discussion on policy concerns than the public comment process. Chuck From: Gnso-igo-ingo <gnso-igo-ingo-bounces(a)icann.org> On Behalf Of Andrea Glandon Sent: Wednesday, September 12, 2018 3:11 PM To: gnso-igo-ingo(a)icann.org; Arsène Tungali <arsenebaguma(a)gmail.com>; Stephanie Perrin <stephanie.perrin(a)mail.utoronto.ca>; Tatiana Tropina <tatiana.tropina(a)gmail.com>; Ayden Férdeline <icann(a)ferdeline.com>; mpsilvavalent(a)gmail.com; rafik.dammak(a)gmail.com; farzaneh badii <farzaneh.badii(a)gmail.com>; Heather Forrest <haforrestesq(a)gmail.com>; Dennis Chang <dennis.chang(a)icann.org>; Maryam Bakoshi <maryam.bakoshi(a)icann.org> Cc: gnso-secs(a)icann.org Subject: [Gnso-igo-ingo] Recordings, attendance & AC Chat | Reconvened IGO-INGO Protections in all gTLDs PDP Working Group on Red Cross Names Call to Discuss Recommendations| Wednesday, 12 September 2018 Dear all, Please find attached the attendance and AC chat and below the mp3 and Adobe Connect recording for the reconvened IGO-INGO Protections in all gTLDs PDP Working Group on Red Cross Names call to discuss recommendations held on Wednesday, 12 September 2018 at 13:00 UTC. Mp3: https://audio.icann.org/gnso/gnso-red-cross-recs-12sep18-en.mp3 <https://urldefense.proofpoint.com/v2/url?u=https-3A__audio.icann.org_gnso_g…> AC recording: https://participate.icann.org/p6y990qikgd/<https://participate.icann.org/p6y990qikgd/?OWASP_CSRFTOKEN=81a39a1ebb180a13…> The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: http://gnso.icann.org/en/group-activities/calendar[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_group…> Mailing list archive: http://mm.icann.org/pipermail/gnso-igo-ingo/ Agenda Wiki page: https://community.icann.org/x/aQCrBQ ** Please let me know if your name has been left off the list ** Kind Regards, Andrea Glandon

2 2

Recordings, attendance & AC Chat | Reconvened IGO-INGO Protections in all gTLDs PDP Working Group on Red Cross Names Call to Discuss Recommendations| Wednesday, 12 September 2018
by Andrea Glandon Sept. 13, 2018

Sept. 13, 2018

Dear all, Please find attached the attendance and AC chat and below the mp3 and Adobe Connect recording for the reconvened IGO-INGO Protections in all gTLDs PDP Working Group on Red Cross Names call to discuss recommendations held on Wednesday, 12 September 2018 at 13:00 UTC. Mp3: https://audio.icann.org/gnso/gnso-red-cross-recs-12sep18-en.mp3 <https://urldefense.proofpoint.com/v2/url?u=https-3A__audio.icann.org_gnso_g…> AC recording: https://participate.icann.org/p6y990qikgd/<https://participate.icann.org/p6y990qikgd/?OWASP_CSRFTOKEN=81a39a1ebb180a13…> The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: http://gnso.icann.org/en/group-activities/calendar[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_group…> Mailing list archive: http://mm.icann.org/pipermail/gnso-igo-ingo/ Agenda Wiki page: https://community.icann.org/x/aQCrBQ ** Please let me know if your name has been left off the list ** Kind Regards, Andrea Glandon

3 4

Motion of the reconvened Working Group - Red Cross and Red Crescent protections - next steps
by Stephane Hankins Sept. 10, 2018

Sept. 10, 2018

Dear Berry, dear Thomas, dear all, Further to the recent GNSO Council decision to defer the motion on the Reconvened Working Group's report and final recommendations on the protections of the Red Cross and Red Crescent designations and names, could you kindly update us on the consultations intended between GNSO Counsellors, the Chair of the reconvened Working Group and ICANN Staff. Please do not hesitate to let us know if a participation or contribution from our side is required in these discussions - and thus, in advance of the GNSO's reexamination of the motion which we understand to be planned on 27 September. With kind regards, Stéphane Hankins Stéphane J. Hankins Legal adviser Movement Cooperation and Coordination International Committee of the Red Cross Tel: +0041 22 730 2419 <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <STYLE type="text/css">  </STYLE> </head> <body> <hr style="color: #000000;background-color: #000000;height: 1px;"/> <p>The ICRC - working to protect and assist people affected by armed conflict and other situations of violence. Find out more: <a href="http://www.icrc.org">www.icrc.org</a><p> <p>This e-mail is intended for the named recipient(s) only.<br> Its contents are confidential and may only be retained by the named recipient(s) and may only be copied or disclosed with the consent of the International Committee of the Red Cross (ICRC). If you are not an intended recipient please delete this e-mail and notify the sender. </p> <hr style="color: #000000;background-color: #000000;height: 1px;"/> </body> </html>

2 1

Test Message - Please disregard
by mail＠berrycobb.com Aug. 30, 2018

Aug. 30, 2018

This is a test message only. Please disregard. Thank you. B Berry A. Cobb GNSO Policy Consultant @berrycobb

1 0

FW: FW: [gnso-chairs] Please review: GNSOCouncil motions 16 August 2018
by Jeff Neuman Aug. 22, 2018

Aug. 22, 2018

Resending as I don’t believe this went through. From: Jeff Neuman Sent: Friday, August 17, 2018 1:54 PM To: mail(a)berrycobb.com; christopher.lamb17(a)gmail.com; 'Greg Shatan' <gregshatanipc(a)gmail.com> Cc: gnso-igo-ingo(a)icann.org Subject: RE: [Gnso-igo-ingo] FW: [gnso-chairs] Please review: GNSOCouncil motions 16 August 2018 All, The NCSG Call where this was discussed can be found here: https://listserv.syr.edu/scripts/wa.exe?A2=ind1808&L=NCSG-DISCUSS&O=D&P=120…. The conversation starts somewhere around 6:30 in. They acknowledge no one from the NCSG participated (in the chat transcript), but ultimately will abstain or vote no. It seemed apparent from listening to the call that they did not really review the final report and the changes. Here is my summary of the oral conversation: 1. Farzanah stated that she has not really had a chance to review, but thinks that this is overreach by the Red Cross. In fact, she refers to objecting to acronyms (My note: She did not read final report because there are no acronyms); She recommends a no or an abstention. 2. Amr: My understanding is that there is no real legal basis to protect these names. Amr wants to know where acronyms stand and where the discussions are taking place. [My note: It is clear that the NCSG did not understand scope of the referral back] 3. [Other person – Did not get name] – Where is the report and is there a summary of the report?; Link given to her. 4. Rafik: We can ask questions and list them and hopefully Council will answer them. He brings up the possibility of deferring the motion. He says we can say there was not enough time to review. So we need more time to understand. The WG said they reviewed our comment carefully. Apparently Thomas Rickert was supposed to reach out to Rafik, but Rafik said he has not heard anything.F 5. Farzanah – We should have participated in the WG, but we can still vote no. Our NCSG “Values” are against this. 6. Rafik: Lets work on our rationale for saying no during the deferral. Yes, we did not have people working on the Group. But this WG took up so much time that a lot people stopped participating after the many years. This is from the chat transcript: Tatiana Tropina:I am not comfortable with voting on this motion, I agree with Farz that we need to raise the questions, esp with regard to what GNSO said in 2017 (there is a reference to this in our comment) Amr Elsadr:Report here: https://mm.icann.org/pipermail/council/attachments/20180807/ab4b45f9/red-cr… Amr Elsadr:Summary of recommendations at the beginning of the report. Tatiana Tropina:I wonder if we have to vote tomorrow. Tatiana Tropina:I wonder if we defer what's gotta change! Amr Elsadr:Wouldn't mind a deferral. Tatiana Tropina:I won't mind a deferral but at the end the report won't change and we will vote no or abstain. Tatiana Tropina:so we can just vote no or abstain with the statements. Claire Craig:If we defer is there a timeframe? Farzaneh Badii:I will read it. I wonder how carefully they read it :) Amr Elsadr:We need to get real. Nobody from NCSG participated in this WG, and the WG is submitted to the Council with Full Consensus of its members. The motion will pass on Council, irrespective of our views/votes. Tatiana Tropina:okay let's asl for a deferral tomorrow Tatiana Tropina:Amr, that's what am saying, the deferral would be only to strategise our abstentions/nos Tatiana Tropina:and supermajority, yes Elsa Saade:i tend to agree with Tatiana on this one Amr Elsadr::-) Tatiana Tropina:I am somewhere in the middile ground, I won't mind just to vote no tomorrow Tatiana Tropina:It's just stand on our ground. So instead of deferral we can just say a big no right on the spot. But deferral is better, some fuss :-) Farzaneh Badii:I can help with the reason Stephanie Perrin:Can we come up with a clear paragraph as to what we are objecting to? Tatiana Tropina:No requires no explanation, but abstention won't count. Hmmmm. Hard choice, let's defer Amr Elsadr:If our councilors would like this motion to be defered, should be for a good reason. One reason might be to investigate whether or not the WG has made its recommendations based on a legal basis, or not. If there is a legal basis for these names to be reserved, then the WG should demonstrate this. If there isn't..., Tatiana Tropina:Farzaneh, the comment you drafted is really outlining all the reasons very good, but if there is anything else you could add - am sure we all will appreciate.... Farzaneh Badii:sure. I just have to check if they changed anything based on our comments. I doubt it :) Tatiana Tropina:Amr, do you think the reason that the WG chair promised to get in contact with us and explain how our comments were addressed etc etc is not a good reason? The fact that we need investigate... ? Tatiana Tropina:I saw they still had the magic number 191... Jeffrey J. Neuman Senior Vice President |Valideus USA | Com Laude USA 1751 Pinnacle Drive, Suite 600 Mclean, VA 22102, United States E: jeff.neuman(a)valideus.com<mailto:jeff.neuman@valideus.com> or jeff.neuman(a)comlaude.com<mailto:jeff.neuman@comlaude.com> T: +1.703.635.7514 M: +1.202.549.5079 @Jintlaw From: Gnso-igo-ingo <gnso-igo-ingo-bounces(a)icann.org<mailto:gnso-igo-ingo-bounces@icann.org>> On Behalf Of mail(a)berrycobb.com<mailto:mail@berrycobb.com> Sent: Friday, August 17, 2018 8:21 AM To: christopher.lamb17(a)gmail.com<mailto:christopher.lamb17@gmail.com>; 'Greg Shatan' <gregshatanipc(a)gmail.com<mailto:gregshatanipc@gmail.com>> Cc: gnso-igo-ingo(a)icann.org<mailto:gnso-igo-ingo@icann.org> Subject: Re: [Gnso-igo-ingo] FW: [gnso-chairs] Please review: GNSOCouncil motions 16 August 2018 Hi All, You can view the bicameral structure of the GNSO Council here: https://gnso.icann.org/en/about/council The structure of the GNSO, descriptions of each Stakeholder Group and Constituency as well as ExCom composition can be found on their respective pages nested under the Council description page linked above. Thank you. B Berry A. Cobb GNSO Policy Consultant @berrycobb From: christopher.lamb17(a)gmail.com<mailto:christopher.lamb17@gmail.com> [mailto:christopher.lamb17@gmail.com] Sent: Friday, August 17, 2018 00:04 To: Greg Shatan Cc: Chuck Gomes Consulting; Berry Cobb; gnso-igo-ingo(a)icann.org<mailto:gnso-igo-ingo@icann.org> Subject: Re: [Gnso-igo-ingo] FW: [gnso-chairs] Please review: GNSOCouncil motions 16 August 2018 Dear Greg, Thanks. I was attempting to locate the source of the concerns to see if that added to my understanding of the way forward, and I had misread the constituencies website . These concerns will no doubt emerge from the consultations and explanations ahead, but the whole result is really quite frustrating. Cheers Chris From: Greg Shatan Sent: Friday, August 17, 2018 13:33 To: Christopher Lamb Cc: Chuck Gomes Consulting ; Berry Cobb ; gnso-igo-ingo(a)icann.org<mailto:gnso-igo-ingo@icann.org> Subject: Re: [Gnso-igo-ingo] FW: [gnso-chairs] Please review: GNSOCouncil motions 16 August 2018 Christopher, The RrSG is not affiliated with the NCSG -- they are on opposite sides of the aisle in the GNSO. The NCSG is the Non-Commercial Stakeholders Group, one of the two Stakeholder Groups in the Non-Contracted Parties House of the GNSO. (The other is the Commercial Stakeholders Group, which in turn comprises the Business Constituency, the Intellectual Property Constituency and the ISP and Connectivity Providers Constituency.) (The NCSG in turn comprises the Non-Commercial Users Constituency (NCUC) and the Non-Profit Organization Operational Concerns Constituency (NPOC).) The RrSG is the Registrar Stakeholder Group, one of the two Stakeholder Groups in the Contracted Parties House of the GNSO. (The other is the Registry Stakeholder Group (RySG).) Best regards, Greg On Thu, Aug 16, 2018 at 11:18 PM <christopher.lamb17(a)gmail.com<mailto:christopher.lamb17@gmail.com>> wrote: Dear all, Agreed, and it will be good to keep track of developments through the updates which Berry has generously offered to provide. Am I right to understand that it is the RrSG within NCSG which has instigated this deferral? Chris From: Chuck Sent: Friday, August 17, 2018 10:39 To: mail(a)berrycobb.com<mailto:mail@berrycobb.com> ; gnso-igo-ingo(a)icann.org<mailto:gnso-igo-ingo@icann.org> Subject: Re: [Gnso-igo-ingo] FW: [gnso-chairs] Please review: GNSOCouncil motions 16 August 2018 It is very disappointing that the NCSG failed to participate in the process and then requests a deferral. Chuck From: Gnso-igo-ingo <gnso-igo-ingo-bounces(a)icann.org<mailto:gnso-igo-ingo-bounces@icann.org>> On Behalf Of mail(a)berrycobb.com<mailto:mail@berrycobb.com> Sent: Thursday, August 16, 2018 5:15 PM To: gnso-igo-ingo(a)icann.org<mailto:gnso-igo-ingo@icann.org> Subject: [Gnso-igo-ingo] FW: [gnso-chairs] Please review: GNSO Council motions 16 August 2018 Hi All, As an FYI, the motion to approve the Reconvened WG’s report was deferred by the NCSG. It will be considered by the GNSO Council at its 27 September meeting. Concerns about the legal basis were for protections were raised. Thomas had agreed to consult with them to help them better understand the WG’s findings and full support for its consensus recommendations. I will update the group as things progress. Below are links to the recordings and motions adopted by the Council at its meeting today. Thank you. B Please find below the MP3, Adobe Connect recording and chat of the GNSO Council meeting held on Thursday, 16 August 2018 at 21:00 UTC. MP3: https://audio.icann.org/gnso/gnso-council-16aug18-en.mp3 Adobe Connect Recording URL: https://participate.icann.org/p377bzpfiry/ Adobe Connect chat at: https://gnso.icann.org/sites/default/files/file/field-file-attach/transcrip… All on page: https://gnso.icann.org/en/group-activities/calendar Berry A. Cobb GNSO Policy Consultant @berrycobb From: Gnso-chairs [mailto:gnso-chairs-bounces@icann.org] On Behalf Of Terri Agnew Sent: Thursday, August 16, 2018 19:22 To: gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org> Cc: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Subject: [gnso-chairs] Please review: GNSO Council motions 16 August 2018 Dear all, Please find below the resolutions from the GNSO Council at its meeting on Thursday, 16 August 2018. If no objections we will send to the council list. Approved - Consent Agenda: Adoption of the GNSO Council Review of GAC Communiqué for submission to the ICANN Board Made by Martin Silva Valent Seconded by Michele Neylon Whereas, 1. The Governmental Advisory Committee advises the ICANN Board on issues of public policy, and especially where there may be an interaction between ICANN's activities or policies and national laws or international agreements. It usually does so as part of a Communiqué, which is published towards the end of every ICANN meeting. 2. The GNSO is responsible for developing and recommending to the ICANN Board substantive policies relating to generic top-level domains. 3. The GNSO has expressed a desire to provide feedback to the ICANN Board on issues in the GAC Communiqué as these relate to generic top-level domains to inform the ICANN Board as well as the broader community of past, present or future gTLD policy activities that may directly or indirectly relate to advice provided by the GAC. 4. The GNSO Council hopes that the input provided through its review of the GAC Communiqué will further enhance the co-ordination and promote the sharing of information on gTLD related policy activities between the GAC, Board and the GNSO. Resolved, 1. The GNSO Council adopts the GNSO Council Review of the Panama GAC Communiqué (see https://gnso.icann.org/sites/default/files/file/field-file-attach/review-ga…) and requests that the GNSO Council Chair communicate the GNSO Review of the Panama GAC Communiqué to the ICANN Board. 2. The GNSO Council requests that the GNSO Chair also informs the GAC Chair of the communication between the GNSO Council and the ICANN Board. Vote results<https://gnso.icann.org/en/meetings/gnso-council-motion-recorder-16aug18-en.…> DEFFERED - MOTION TO APPROVE THE FINAL RECOMMENDATIONS FROM THE RECONVENED WORKING GROUP ON RED CROSS NAMES Proposed by: Heather Forrest Seconded by: Whereas: 1. In November 2013, the Working Group for the Protection of International Governmental Organizations (IGO) and International Non-Governmental Organizations (INGO) in All gTLDs completed a Policy Development Process (PDP) and submitted its Final Report to the GNSO Council (https://gnso.icann.org/en/issues/igo-ingo-final-10nov13-en.pdf, including Minority Statements: https://gnso.icann.org/en/issues/igo-ingo-final-minority-positions-10nov13- en.pdf<https://gnso.icann.org/en/issues/igo-ingo-final-minority-positions-10nov13-…>); 2. On 20 November 2013, the GNSO Council approved all the consensus recommendations in the PDP Final Report (http://gnso.icann.org/en/council/resolutions#20131120-2) 3. On 30 April 2014, the ICANN Board approved those of the GNSO’s consensus recommendations that were consistent with advice received from the Governmental Advisory Committee (GAC) on the topic of IGO and INGO protections (which approval, in relation to the Red Cross, was limited to withholding from registration at both the top and second levels the specific terms designated as so-called “Scope 1” identifiers by the PDP Working Group (i.e., “Red Cross”, “Red Crescent”, “Red Crystal” and “Red Lion & Sun” in all six official languages of the United Nations)) and requested additional time to consider those remaining consensus PDP recommendations that were not consistent with GAC advice (http://www.icann.org/en/groups/board/documents/resolutions-30apr14-en.htm#2…) 4. In March 2017, representatives of the GAC and GNSO held a discussion at the ICANN58 Public Meeting in Copenhagen, facilitated by former ICANN Board member Dr. Bruce Tonkin, to discuss a possible path forward for reconciling GAC advice and GNSO policy on the topic of protection at the second level of the domain name system for IGO acronyms and the remaining names and acronyms associated with the Red Cross (being those designated by the IGO-INGO PDP Working Group as “Scope 2” identifiers); 5. Following the March 2017 facilitated discussion, the ICANN Board passed a resolution requesting that the GNSO Council consider initiating the Policy Amendment Process documented in the GNSO PDP Manual in respect of certain of the so-called “Scope 2” identifiers for the Red Cross, i.e., the full names of the National Societies recognized within the International Red Cross and Red Crescent movement, and the full names of the International Red Cross and Red Crescent Movement, the International Committee of the Red Cross, and the International Federation of Red Cross and Red Crescent Societies (in the six official languages of the United Nations) (https://www.icann.org/resources/board-material/resolutions-2017-03-16- en#2.e.i); 6. In May 2017, the GNSO Council passed a resolution noting that the March 2017 facilitated discussions had highlighted a set of exceptional circumstances (in the availability of a finite list of names and documented evidence of the legal basis for their protection) constituting a justifiable basis for the Council’s taking the extraordinary step of reconvening the original IGO-INGO PDP Working Group pursuant to Section 16 of the GNSO PDP Manual for the specific purpose of considering possible modifications to its previous consensus policy recommendations concerning and limited to the so-called “Scope 2” Red Cross full names noted by the Board, and including a defined, finite list of variants of those names, and with acronyms and any other names not falling within the scope of this reconvened effort (https://gnso.icann.org/en/council/resolutions#20170503-071) 7. The Reconvened PDP Working Group held its first meeting on 14 June 2017, and has since worked diligently to develop a set of recommendations that were published for public comment on 21 June 2018 (https://www.icann.org/public-comments/red-cross-protection-initial-2018-06-…) and 8. Following the close of the public comment period on 31 July 2018, the Reconvened PDP Working Group reviewed the comments that were received and completed its Final Report and finite List of names, which it submitted to the GNSO Council for its consideration on 6 August 2018 (https://gnso.icann.org/en/issues/igo-ingo/red-cross-protection-policy-amend… https://gnso.icann.org/en/issues/igo-ingo/red-cross-identifiers-proposed-re…) Resolved: 1. The GNSO Council has reviewed the Final Report and approves all of the consensus recommendations made by the Reconvened PDP Working Group; 2. The GNSO Council thanks the Reconvened PDP Working Group for its diligence and its successful work in attaining consensus on all recommendations; 3. The GNSO Council thanks the International Red Cross and Red Crescent Movement for its efforts in providing the documentation and information needed to justify and underpin the consensus recommendations; and 4. The GNSO Council directs ICANN staff to prepare a Recommendations Report for delivery to the ICANN Board in accordance with the process outlined in the ICANN Bylaws. Vote results<https://gnso.icann.org/en/meetings/gnso-council-motion-recorder-16aug18-en.…> Approved - MOTION IN RELATION TO THE ADOPTION OF THE GNSO REVIEW WORKING GROUP IMPLEMENTATION FINAL REPORT Made by: Rafik Dammak Seconded by: Donna Austin Whereas: 1. The second independent review of the GNSO commenced in 2014. 2. The Final Report of the independent examiner was published on 15 September 2015 (see https://www.icann.org/en/system/files/files/gnso-review-final-15sep15-en.pdf) and contained 36 recommendations in the areas of: participation & representation, continuous development, transparency and alignment with ICANN's future. 3. The GNSO Council adopted the GNSO Review Recommendations Feasibility and Prioritization analysis (see:http://gnso.icann.org/en/drafts/review-feasibility-prioritization-25feb…) on 14 April 2016 with the modification of Recommendation 21, that the council recommends staff working with the GNSO to institute methods of information sharing of highly relevant research related to gTLDs to help the GNSO community members increase their knowledge base (low priority). 4. On 25 June 2016, the ICANN Board accepted the Final Report from the independent examiner, taking into account the GNSO Working Party's Feasibility and Prioritization Analysis of the GNSO Review Recommendations, adopted with modifications by the GNSO Council, the Board adopts thirty-four (34) recommendations of the Final Report (i.e. all recommendations excluding recommendations 23 and 32). 5. Furthermore, the Board requested that the GNSO Council convene a group that oversees the implementation of Board-accepted recommendations. An implementation plan, containing a realistic timeline for the implementation, definition of desired outcomes and a way to measure current state as well as progress toward the desired outcome, shall be submitted to the Board as soon as possible, but no later than six (6) months after the adoption of this resolution. 6. The GNSO Council requested that ICANN policy staff prepare a discussion paper that outlines the possible options for dealing with the implementation of the GNSO Review recommendations following adoption by the ICANN Board taking into account the past implementation of the GNSO Review as well as existing mechanisms such as the SCI, the GNSO Review Working Party and other applicable best practices and lessons learned from past reviews. This discussion paper was submitted to the GNSO Council on 20 June 2016 (see http://gnso.icann.org/en/drafts/review-implementation-recommendations-discu…) 7. The GNSO Council reviewed and discussed next steps during the ICANN meeting in Helsinki where it was proposed to repurpose the SCI as a Working Group to develop the requested implementation plan as outlined in the staff discussion paper. 8. The GNSO Council adopted the Charter<https://gnso.icann.org/en/drafts/gnso-review-charter-21jul16-en.pdf> of the GNSO Review Working Group during its meeting on 21 July 2016. 9. This Working Group was tasked to develop an implementation plan for the GNSO Review recommendations<http://gnso.icann.org/en/drafts/review-feasibility-prioritization-25feb16-e…> which were adopted<https://www.icann.org/resources/board-material/resolutions-2016-06-25-en#2.e> by the ICANN Board on 25 June 2016. 10. The implementation plan<https://community.icann.org/download/attachments/61610342/GNSO%20Review%20I…> was adopted<https://community.icann.org/display/gnsocouncilmeetings/Motions+1+December+…> by the GNSO Council on 15 December 2016. 11. On 03 February 2017 the ICANN Organizational Effectiveness Committee (OEC) of the Board of Directors adopted<https://www.icann.org/resources/board-material/resolutions-2017-02-03-en#1.e> the plan. 12. Following approval of the implementation plan by the ICANN Board of Directors, the GNSO Review Working Group executed the implementation of the recommendations as specified in the implementation plan, and provided the GNSO Council with regular status updates (at a minimum prior to every ICANN meeting) on the status of implementation, including an overview for which recommendations implementation was considered complete. 13. On 26 July 2018 the GNSO Review Working Group submitted to the GNSO Council for consideration the GNSO2 Review Implementation Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/gnso2-rev…> indicating that the Working Group had agreed by full consensus that all GNSO Review recommendations have been implemented as of 21 June 2018. Resolved: 1. The GNSO Council adopts the GNSO2 Review Implementation Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/gnso2-rev…>. 2. The GNSO Council directs staff to submit the GNSO2 Review Implementation Final Report to the OEC of the ICANN Board of Directors for its consideration. 3. The GNSO Council thanks the GNSO Review Working Group members for their diligence and dedication in the successful execution of the implementation of the GNSO review recommendations. 4. The GNSO Council shall decide to disband the GNSO Review Working Group after the Implementation Final Report has been approved by the ICANN Board of Directors. Vote results<https://gnso.icann.org/en/meetings/gnso-council-motion-recorder-16aug18-en.…> ________________________________ _______________________________________________ Gnso-igo-ingo mailing list Gnso-igo-ingo(a)icann.org<mailto:Gnso-igo-ingo@icann.org> https://mm.icann.org/mailman/listinfo/gnso-igo-ingo ________________________________ [Avast logo]<https://www.avast.com/antivirus> This email has been checked for viruses by Avast antivirus software. www.avast.com<https://www.avast.com/antivirus> _______________________________________________ Gnso-igo-ingo mailing list Gnso-igo-ingo(a)icann.org<mailto:Gnso-igo-ingo@icann.org> https://mm.icann.org/mailman/listinfo/gnso-igo-ingo

4 3