<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">James,</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">I'm curious to know how you came to the conclusion that acronyms are in scope? Looking at the background for this reconvened WG, I came to the opposite conclusion (as stated in my prior email).</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Thanks!</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Greg</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Aug 8, 2017 at 11:34 AM, <a href="mailto:jbladel@godaddy.com">jbladel@godaddy.com</a> <span dir="ltr"><<a href="mailto:jbladel@godaddy.com" target="_blank">jbladel@godaddy.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="m_-6757547543672459552WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Thanks, Chuck.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Well, acronyms are in scope, insomuch as we acknowledge that they are more suited for inclusion in the work on IGO/INGO Curative Rights (as Stephane points out).<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Thanks—<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">J.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><u></u> <u></u></span></p>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Chuck Gomes Consulting <<a href="mailto:consult@cgomes.com" target="_blank">consult@cgomes.com</a>> on behalf of Chuck Gomes Consulting <<a href="mailto:consult@cgomes.com" target="_blank">consult@cgomes.com</a>><br>
<b>Date: </b>Tuesday, August 8, 2017 at 10:19 <br>
<b>To: </b>"James M. Bladel" <<a href="mailto:jbladel@godaddy.com" target="_blank">jbladel@godaddy.com</a>>, 'Stephane Hankins' <<a href="mailto:shankins@icrc.org" target="_blank">shankins@icrc.org</a>><span class=""><br>
<b>Cc: </b>"'<a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a>'" <<a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a>>, "<a href="mailto:gnso-igo-ingo@icann.org" target="_blank">gnso-igo-ingo@icann.org</a>" <<a href="mailto:gnso-igo-ingo@icann.org" target="_blank">gnso-igo-ingo@icann.org</a>><br>
</span><b>Subject: </b>RE: [Gnso-igo-ingo] Follow-up to the second WG call of 20 July 2017 - Reconvened IGO-INGO Working Group on Red Cross and Red Crescent Names and Identifiers<u></u><u></u></span></p>
</div><div><div class="h5">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"><u></u> <u></u></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt">James,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt">In my opinion you summarized the issues of our work in a concise, clear and useful manner, understanding that acronyms are apparently out of scope for this WG. Thanks.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Chuck</span><u></u><u></u></p>
<p class="MsoNormal"><a name="m_-6757547543672459552__MailEndCompose"><span style="font-size:11.0pt"> </span></a><u></u><u></u></p>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> <a href="mailto:jbladel@godaddy.com" target="_blank">jbladel@godaddy.com</a> [mailto:<a href="mailto:jbladel@godaddy.com" target="_blank">jbladel@godaddy.com</a>]
<br>
<b>Sent:</b> Tuesday, August 8, 2017 6:31 AM<br>
<b>To:</b> Chuck Gomes Consulting <<a href="mailto:consult@cgomes.com" target="_blank">consult@cgomes.com</a>>; 'Stephane Hankins' <<a href="mailto:shankins@icrc.org" target="_blank">shankins@icrc.org</a>><br>
<b>Cc:</b> <a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a>; <a href="mailto:gnso-igo-ingo@icann.org" target="_blank">gnso-igo-ingo@icann.org</a><br>
<b>Subject:</b> Re: [Gnso-igo-ingo] Follow-up to the second WG call of 20 July 2017 - Reconvened IGO-INGO Working Group on Red Cross and Red Crescent Names and Identifiers</span><u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Thanks to Chuck, Stephane and especially Charlotte for their valuable contributions in this thread.
</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><u></u><u></u></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:11.0pt">If we go back to the Facilitated Discussions in Copenhagen, we landed on three factors for reconsidering protections for RC/RC strings in the DNS (note, these are also reflected
in the GNSO Council resolution that re-activated this PDP). Roughly paraphrased, they were:</span><u></u><u></u></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="margin-left:0in"><span style="font-size:11.0pt">That the protections were based upon / reflected in national and international law, and</span><u></u><u></u></li><li class="MsoNormal" style="margin-left:0in"><span style="font-size:11.0pt">That the list of covered strings was finite, and was amended only via consistent & visible processes, and</span><u></u><u></u></li><li class="MsoNormal" style="margin-left:0in"><span style="font-size:11.0pt">There were no other legitimate uses for the string.</span><u></u><u></u></li></ul>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Circling back to Charlotte’s message, her points (1) and (2) and (3) are meant to establish that the first two tests are being met. Similarly, points (3) and (5) help to define the list of covered strings
as finite, and only occasionally modified via well-established processes (Marshall Islands). However, I believe that point (4) (ICRC and IFRC) fail the third test: requiring that there are no other legitimate uses for the strings.
</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt">This is always a problem with acronyms, as they often collide with unrelated terms, organizations, or industries. For example, a quick search of “ICRC” notes that while this string is commonly associated
with the International Committee of the Red Cross, it is also used by the Indiana Civil Rights Commission, the International Certification and Reciprocity Consortium, the Intercollege Relations Commission, and the International Conference of Reformed Churches.
Policies should not prohibit or reserve the use of these strings in gTLDs, but rather ensure access to curative rights for the RC (or any of the other organizations) that are harmed when these strings are abused.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><br>
Thanks—</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><br>
J.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><u></u><u></u></p>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black"><<a href="mailto:gnso-igo-ingo-bounces@icann.org" target="_blank">gnso-igo-ingo-bounces@icann.<wbr>org</a>> on behalf of Chuck Gomes Consulting <<a href="mailto:consult@cgomes.com" target="_blank">consult@cgomes.com</a>><br>
<b>Date: </b>Monday, August 7, 2017 at 10:51 <br>
<b>To: </b>'Stephane Hankins' <<a href="mailto:shankins@icrc.org" target="_blank">shankins@icrc.org</a>><br>
<b>Cc: </b>"'<a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a>'" <<a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a>>, "<a href="mailto:gnso-igo-ingo@icann.org" target="_blank">gnso-igo-ingo@icann.org</a>" <<a href="mailto:gnso-igo-ingo@icann.org" target="_blank">gnso-igo-ingo@icann.org</a>><br>
<b>Subject: </b>Re: [Gnso-igo-ingo] Follow-up to the second WG call of 20 July 2017 - Reconvened IGO-INGO Working Group on Red Cross and Red Crescent Names and Identifiers</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><u></u><u></u></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt">Stephane,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt">You in essence did what I was suggesting Charlotte do. It wasn’t that I didn’t understand but rather that it was a fairly complicated and long message that I thought would benefit from a simpler explanation.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Chuck</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> Stephane Hankins [<a href="mailto:shankins@icrc.org" target="_blank">mailto:shankins@icrc.org</a>]
<br>
<b>Sent:</b> Monday, August 7, 2017 12:50 AM<br>
<b>To:</b> Chuck Gomes Consulting <<a href="mailto:consult@cgomes.com" target="_blank">consult@cgomes.com</a>><br>
<b>Cc:</b> 'Charlotte Lindsey Curtet' <<a href="mailto:clindsey@icrc.org" target="_blank">clindsey@icrc.org</a>>;
<a href="mailto:gnso-igo-ingo@icann.org" target="_blank">gnso-igo-ingo@icann.org</a>; <a href="mailto:gnso-secs@icann.org" target="_blank">
gnso-secs@icann.org</a><br>
<b>Subject:</b> Re: [Gnso-igo-ingo] Follow-up to the second WG call of 20 July 2017 - Reconvened IGO-INGO Working Group on Red Cross and Red Crescent Names and Identifiers</span><u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif">Dear Chuck,</span>
<br>
<br>
<span style="font-family:"Arial",sans-serif">Could you kindly clarify for us what is unclear. Charlotte's message below is to us written in a reasonably plain language.</span>
<br>
<br>
<span style="font-family:"Arial",sans-serif">Point (2) aims to explicate what, in our understanding, an ammendment to the GNSO's 2013 Recommendations would imply in order to achieve a reconciliation with past GAC advice.</span>
<br>
<br>
<span style="font-family:"Arial",sans-serif">Point (3) suggests that in the interest of achieving a reconciliation of the 2013 GNSO recommendation and GAC advice, consideration would also require to be given to the full names of the ICRC and of the International
Federation (the two international bodies within the International red Cross and Red Crescent Movement), in addition to the identifiers of National Red Cross and Red Crescent Societies.</span>
<br>
<br>
<span style="font-family:"Arial",sans-serif">Point (4) confirms our ask regarding the ICRC and IFRC acronyms and suggests that the reconvened WG also consider to issue a recommendation in regard to the latter (in line with the GAC advice).</span>
<br>
<br>
<span style="font-family:"Arial",sans-serif">Point (5) recalls our availability to provide a revised list of name in the interest of consistency, as discussed and requested in Copenhagen.</span>
<br>
<br>
<span style="font-family:"Arial",sans-serif">If the concern is regarding the attachments, please advise what you think could be helpful. The suggestion was made, if I am not mistaken during the last WG session, that further clarity be provided regarding the
legal grounds for the protections for the Red Cross and Red Crescent identifiers - this is what the attached Report (and its annexes) seek to provide.</span>
<br>
<br>
<span style="font-family:"Arial",sans-serif">Many thanks and kind regards,</span>
<br>
<br>
<span style="font-family:"Arial",sans-serif">Stéphane (and Charlotte - presently on leave)</span>
<br>
<br>
<br>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5f5f5f">From: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">"Chuck Gomes Consulting" <<a href="mailto:consult@cgomes.com" target="_blank">consult@cgomes.com</a>></span>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5f5f5f">To: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">"'Charlotte Lindsey Curtet'" <<a href="mailto:clindsey@icrc.org" target="_blank">clindsey@icrc.org</a>>, <<a href="mailto:gnso-igo-ingo@icann.org" target="_blank">gnso-igo-ingo@icann.org</a>></span>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5f5f5f">Cc: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif"><a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a></span>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5f5f5f">Date: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">06.08.2017 19:11</span>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5f5f5f">Subject: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">Re: [Gnso-igo-ingo] Follow-up to the second WG call of 20 July 2017 - Reconvened IGO-INGO Working
Group on Red Cross and Red Crescent Names and Identifiers</span> <br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5f5f5f">Sent by: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif"><a href="mailto:gnso-igo-ingo-bounces@icann.org" target="_blank">gnso-igo-ingo-bounces@icann.<wbr>org</a></span>
<u></u><u></u></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" noshade style="color:#a0a0a0" align="center">
</div>
<p class="MsoNormal"><br>
<br>
<br>
Thanks for this Charlotte. I appreciate the need for being precise when writing legal language but found that I had to read this several times to grasp what is said. It would be helpful for me if your message was briefly summarized with a list of the key
points made. <br>
<br>
Chuck <br>
<br>
<b>From:</b> <a href="mailto:gnso-igo-ingo-bounces@icann.org" target="_blank">gnso-igo-ingo-bounces@icann.<wbr>org</a> [<a href="mailto:gnso-igo-ingo-bounces@icann.org" target="_blank">mailto:gnso-igo-ingo-bounces@<wbr>icann.org</a>]
<b>On Behalf Of </b>Charlotte Lindsey Curtet<b><br>
Sent:</b> Friday, August 4, 2017 4:46 AM<b><br>
To:</b> <a href="mailto:gnso-igo-ingo@icann.org" target="_blank">gnso-igo-ingo@icann.org</a><b><br>
Cc:</b> <a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a><b><br>
Subject:</b> [Gnso-igo-ingo] Follow-up to the second WG call of 20 July 2017 - Reconvened IGO-INGO Working Group on Red Cross and Red Crescent Names and Identifiers
<br>
<br>
<span style="font-family:"Arial",sans-serif">Dear Thomas, dear James, <br>
Dear Members of the reconvened Working Group, </span><br>
<span style="font-family:"Arial",sans-serif"><br>
(1) Further to the discussions held during the second meeting of the reconvened Working group IGO/INGO Protections PDP Working Group held on 20 July, please find attached a copy of the Non-paper we had submitted to ICANN’s Board and to the process in 2013.
<br>
The attached includes a descriptive of the legal protections of the Red Cross, Red Crescent and Red Crystal designations and of the names/identifiers of the respective Red Cross and Red Crescent organizations under international law and under the domestic laws
in force in multiple national jurisdictions. </span><br>
<span style="font-family:"Arial",sans-serif"><br>
It includes as an annex an outline of relevant extracts from the first Geneva Convention of 1949 and of the third Additional Protocol adopted in 2005, and a list of national laws in force in different national jurisdictions on the use and protection of the
emblems and their designations (the list would require now to be updated to include more recent national laws/Governmental decrees, as adopted
<i>inter alia</i> in South Sudan, Sweden and Venezuela). </span><br>
<span style="font-family:"Arial",sans-serif"><br>
(2) We take note, as underlined during the recent reconvened Working group discussions, of the WG’s defined objectives to determine whether the current protections accorded to the Red Cross and Red Crescent designations and identifiers (as included under Specification
5 of the Model Registry Agreement) should be confirmed as permanent.</span> <br>
<span style="font-family:"Arial",sans-serif"><br>
In line with the recommendations of the NGPC/the Board's Resolutions that the GNSO’s 2013 Recommendations be reconciled with the GAC’s consistent advice, this would imply that the GNSO’s 2013 recommendations be revised on two counts:
<br>
</span> <span style="font-family:"Arial",sans-serif"><br>
- firstly, to extend the protections accorded to the Red Cross, Red Crescent and Red Crystal designations (Scope 1 identifiers) to the full exact match names of the respective Red Cross and Red Crescent organizations (Scope 2 identifiers); and
<br>
- second, to confirm the protections of the Red Cross and Red Crescent designations and identifiers (Scope 1 and Scope 2)
<i>as permanent</i>.</span> <span style="font-family:"Arial",sans-serif"><br>
</span> <span style="font-family:"Arial",sans-serif"><br>
(3) As recalled during the last reconvened Working Group session and in line with the GNSO’s decision to initiate its process for Amendments or Modifications of Approved Policies
<i>with regard to Recommendation 5 Section 3.1 of the 2013 Final Report</i>, the extension of the protections should importantly be made to cover not only the names of the respective
<i>National Red Cross and Red Crescent Societies</i> (190 in total to date), but also the full exact match names of the two international components of the International Red Cross and Red Crescent Movement in the six UN languages. This is congruent with the
definition of Scope 2 identifiers as included in the Final Report of the 2013 PDP – page 10.
<br>
This is also confirmed under the Board’s Resolution (2017.03.16.13) and the latter's Operative paragraph (1).
</span><u></u><u></u></p>
<p><span style="font-size:10.0pt">Reference is also made in this regard to the GAC’s consistent advice [as expressly stipulated in the GAC Communiqués adopted in Singapore (27 March 2014), Los Angeles (15 October 2014), Singapore (11 February 2015), and confirmed
in subsequent advice] that the Red Cross and Red Crescent identifiers be afforded permanent protections. We wish to underline in this regard that the names of the International Committee of the Red Cross, of the International Federation of Red Cross and Red
Crescent Societies, and of the International Red Cross and Red Crescent Movement are included under Specification 5 to the Model Registry Agreement and already enjoy temporary protections.
<br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
(4) With respect to the ICRC and IFRC acronyms (also included under the definition of Scope 2 names adopted by the GNSO in 2013), the extension of the
<i>permanent</i> protections is not requested here, and thus in line with the GAC’s past advice, as adopted in Durban (18 July 2013), that
<i>“[t]he same complementary cost neutral mechanisms to be worked out […] for the protections of IGO’s be used to also protect the acronyms of the International Committee of the Red Cross (ICRC/IFRC) and the International Federation of Red Cross and Red Crescent
Societies (IFRC/FICR)”</i>. Given however the importance of also protecting the acronyms of the ICRC and of the IFRC (particularly the ICRC acronym under which the ICRC is very commonly known and identified and which forms a part of the ICRC’s institutional
logo), we would propose that the reconvened WG consider to issue also a recommendation in regard to the ICRC and IFRC acronyms in line with the GAC’s above-mentioned Durban Communiqué.
<br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
(5) Lastly and further to recent exchanges with ICANN Staff, we wish to inform the members of the reconvened Working Group that, in line with the agreement during the Facilitated discussion held in Copenhagen, we are amenable to work further on a revised list
of Red Cross and Red Crescent identifiers to replace the current list included under Specification 5 – this would notably aim to amend the current titles of the two categories of Red Cross and Red Crescent designations and identifiers (as these do not offer
clarity) and to further harmonize the list of National Red Cross and Red Crescent Societies identifiers (and their
<i>limited</i> and well defined variations). <br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
We also wish members of the WG to note, as indicated during the Copenhagen discussion, that a new National Society is in the process of formation and recognition, namely the “Marshall Islands Red Cross Society” and that its name will also soon require to be
added to the list. <br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
Please do not hesitate to contact us should you require any further clarification.
<br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
With kind regards,</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
Charlotte <br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
Charlotte Lindsey Curtet<br>
Director<br>
Communication and Information Management Department<br>
International Committee of the Red Cross (ICRC)<br>
Tel: <a href="tel:+41%2022%20730%2027%2073" value="+41227302773" target="_blank">+ 41 22 730 2773</a><br>
email: </span><a href="mailto:clindsey@icrc.org" target="_blank"><span style="font-size:10.0pt;color:#0082bf">clindsey@icrc.org</span></a><span style="font-size:12.0pt">
</span><span style="font-size:10.0pt"><br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
Annexes: <br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
- ICRC and IFRC Position paper to ICANN's Board, July/August 2013:</span><span style="font-size:12.0pt">
<br>
<br>
<br>
</span><span style="font-size:10.0pt"><br>
- Extracts from the Government Advisory Committee's Communiqués relevant to the protection of the Red Cross and Red Crescent designations and identifiers:</span><span style="font-size:12.0pt">
<br>
<br>
==============================<wbr>==============================<wbr>=================== The ICRC - working to protect and assist people affected by armed conflict and other situations of violence. Find out more:
</span><a href="http://www.icrc.org/" target="_blank"><span style="font-size:12.0pt;color:#0082bf">www.icrc.org</span></a><span style="font-size:12.0pt"> 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. ==============================<wbr>==============================<wbr>===================
</span><tt><span style="font-size:10.0pt">______________________________<wbr>_________________</span></tt><span style="font-size:10.0pt;font-family:"Courier New",serif"><br>
<tt>Gnso-igo-ingo mailing list</tt><br>
<tt><a href="mailto:Gnso-igo-ingo@icann.org" target="_blank">Gnso-igo-ingo@icann.org</a></tt><br>
</span><a href="https://mm.icann.org/mailman/listinfo/gnso-igo-ingo" target="_blank"><tt><span style="font-size:10.0pt">https://mm.icann.org/mailman/<wbr>listinfo/gnso-igo-ingo</span></tt></a>
<u></u><u></u></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:11.0pt">
<hr size="1" width="100%" noshade style="color:black" align="center">
</span></div>
<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" target="_blank">www.icrc.org</a><u></u><u></u></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. <u></u><u></u></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:11.0pt">
<hr size="1" width="100%" noshade style="color:black" align="center">
</span></div>
</div></div></div>
</div>
<br>______________________________<wbr>_________________<br>
Gnso-igo-ingo mailing list<br>
<a href="mailto:Gnso-igo-ingo@icann.org">Gnso-igo-ingo@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-igo-ingo" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-igo-ingo</a><br></blockquote></div><br></div>