<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:9.0pt;
font-family:"Arial",sans-serif;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;}
span.EmailStyle21
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt'>Hi All,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>At its 27 Jan 2019 meeting, the ICANN Board adopted the GNSO’s consensus recommendations as set by the IGO-INGO Reconvened WG (<a href="https://www.icann.org/resources/board-material/resolutions-2019-01-27-en#2.d">https://www.icann.org/resources/board-material/resolutions-2019-01-27-en#2.d</a>). As noted in the resolution, ICANN Org will shortly form an Implementation Review Team (IRT). You should expect to see a call for volunteers on this mailman list, as well as, other community communication channels if you wish to participate. Your participation will be helpful to help see this portion to its final conclusion. It is expected that the IRT shall execute rather swiftly to get to a Policy Effective Date.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Stephane and Jennifer,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Per your request below, the IRT will be able to make the updates to the “Baphalali Eswatini Red Cross Society” master list before it is converted to DNS labels. The Reconvened WG’s recommendations 4 to 6 from its Final Report were created just for this use case. Also, it will further help to inform the final procedure for such changes in the future. Dennis Chang will be leading the IRT and he is aware of this change as well. I suspect this will be one of the IRT’s early tasks once its formed.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Stay tuned for further notices.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Thank you.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>B<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>GNSO Policy Consultant<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>@berrycobbb<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:11.0pt'>From:</span></b><span style='font-size:11.0pt'> Stephane Hankins <shankins@icrc.org> <br><b>Sent:</b> Friday, January 25, 2019 09:40<br><b>To:</b> Mary Wong <mary.wong@icann.org><br><b>Cc:</b> gnso-igo-ingo@icann.org; Berry Cobb Mail <mail@berrycobb.com>; Jennifer Hauseman <jhauseman@icrc.org><br><b>Subject:</b> Re: [Gnso-igo-ingo] Revisions required to the Table of National Red Cross and Red Crescent names and identifiers<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-family:"Arial",sans-serif'>Dear Mary, dear Berry,</span> <br><span style='font-family:"Arial",sans-serif'> </span> <br><span style='font-family:"Arial",sans-serif'>Thank you for your reply.</span> <br><span style='font-family:"Arial",sans-serif'> </span> <br><span style='font-family:"Arial",sans-serif'>(1) As indicated in my initial communication below, the change in the formal name of the Baphalali eSwatini Red Cross Society is<i> already effective</i> further to a decision adopted by the National Society's General Assembly on 8 September 2018 .</span> <br><span style='font-family:"Arial",sans-serif'> </span> <br><span style='font-family:"Arial",sans-serif'>The table of National Red Cross and Red Crescent Societies names and identifiers would therefore require to be adapted asap.</span> <br><span style='font-family:"Arial",sans-serif'> </span> <br><span style='font-family:"Arial",sans-serif'>Considering that the Board has not yet examined the GNSO's Report and recommendations, could the list not be already revised in order to avoid a lengthy ammendment process?</span> <br><span style='font-family:"Arial",sans-serif'> </span> <br><span style='font-family:"Arial",sans-serif'>(2) Thank your for your update on the Board's consideration of the GNSO's Report and Recommendations on the Red Cross and Red Crescent identifiers. As I will be travelling on Sunday afternoon, I am not sure whether I will be able to listen in on the call, but will try.</span> <br><span style='font-family:"Arial",sans-serif'> </span> <br><span style='font-family:"Arial",sans-serif'>With kind regards,</span> <br><span style='font-family:"Arial",sans-serif'> </span> <br><span style='font-family:"Arial",sans-serif'>Stéphane </span><br><br><br><span style='font-family:"Arial",sans-serif'>Stéphane J. Hankins</span> <br><span style='font-family:"Arial",sans-serif'>Legal adviser</span> <br><span style='font-family:"Arial",sans-serif'>Cooperation and Coordination within the Movement</span> <br><span style='font-family:"Arial",sans-serif'>International Committee of the Red Cross</span> <br><span style='font-family:"Arial",sans-serif'>Tel (Prof.):++41 22 730 24 19<br><br>-----Mary Wong <<a href="mailto:mary.wong@icann.org">mary.wong@icann.org</a>> a écrit : ----- </span><br><span style='font-family:"Arial",sans-serif'>A : Stephane Hankins <<a href="mailto:shankins@icrc.org">shankins@icrc.org</a>>, "<a href="mailto:gnso-igo-ingo@icann.org">gnso-igo-ingo@icann.org</a>" <<a href="mailto:gnso-igo-ingo@icann.org">gnso-igo-ingo@icann.org</a>>, Berry Cobb Mail <<a href="mailto:mail@berrycobb.com">mail@berrycobb.com</a>><br>De : Mary Wong <<a href="mailto:mary.wong@icann.org">mary.wong@icann.org</a>><br>Date : 22/01/2019 22:54<br>Cc: Jennifer Hauseman <<a href="mailto:jhauseman@icrc.org">jhauseman@icrc.org</a>><br>Objet : Re: [Gnso-igo-ingo] Revisions required to the Table of National Red Cross and Red Crescent names and identifiers</span><span style='font-size:11.0pt'><o:p></o:p></span></p><p><span style='font-size:10.0pt'>Dear Stephane and Jennifer,</span> <o:p></o:p></p><p><span style='font-size:10.0pt'>Thank you for this update and for confirming that there is no need to make any changes to the current list as approved by the GNSO Council. Please keep us (especially ICANN Org) updated on developments and the final dates, as there will likely be a need to determine whether and how the amendment process noted amongst the PDP recommendations will be followed, which may in turn depend on where things stand at that point in time in relation to the implementation planning.</span> <o:p></o:p></p><p><span style='font-size:10.0pt'>To your question about Board consideration of the PDP recommendations, you may be interested to know that that the topic is on the Board’s agenda for its public meeting this coming Sunday 27 January at 1800 UTC. As with other Board meetings held in conjunction with a Board Workshop, this meeting will be a public one so you can listen in via the methods listed here: </span><a href="https://www.icann.org/resources/pages/2019-board-meetings"><span style='font-size:10.0pt'>https://www.icann.org/resources/pages/2019-board-meetings</span></a><span style='font-size:10.0pt'>. </span><o:p></o:p></p><p><span style='font-size:10.0pt'>Staff will provide a written update to this mailing list following the meeting for those members who are unable to or otherwise will not be listening in.</span> <o:p></o:p></p><p><span style='font-size:10.0pt'>Thanks and cheers</span> <o:p></o:p></p><p><span style='font-size:10.0pt'>Berry & Mary</span> <o:p></o:p></p><p><span style='font-size:10.0pt'> </span> <o:p></o:p></p><p><span style='font-size:10.0pt'> </span> <o:p></o:p></p><p><b><span style='font-size:12.0pt'>From: </span></b><span style='font-size:12.0pt'>Gnso-igo-ingo <<a href="mailto:gnso-igo-ingo-bounces@icann.org">gnso-igo-ingo-bounces@icann.org</a>> on behalf of Stephane Hankins <<a href="mailto:shankins@icrc.org">shankins@icrc.org</a>><b><br>Date: </b>Tuesday, January 22, 2019 at 12:10<b><br>To: </b>"<a href="mailto:gnso-igo-ingo@icann.org">gnso-igo-ingo@icann.org</a>" <<a href="mailto:gnso-igo-ingo@icann.org">gnso-igo-ingo@icann.org</a>>, Berry Cobb Mail <<a href="mailto:mail@berrycobb.com">mail@berrycobb.com</a>><b><br>Cc: </b>Jennifer Hauseman <<a href="mailto:jhauseman@icrc.org">jhauseman@icrc.org</a>><b><br>Subject: </b>[Gnso-igo-ingo] Revisions required to the Table of National Red Cross and Red Crescent names and identifiers</span> <o:p></o:p></p><p><span style='font-size:10.0pt'> </span> <o:p></o:p></p><p><a name="_MailOriginalBody"></a><span style='font-size:10.0pt'>Dear Berry, dear Members of the Core Group, <br><br>I hope this message finds you well. <br><br>(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”. <br><br>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 <i>Kingdom of eSwatini </i>(it is my understanding that this change is already reflected in the list of States members of ICANN’s <br>Government Advisory Committee)<i>.</i> <br><br>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. <br><br>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”. <br><br>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. <br><br>(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. <br><br>With best wishes to all in 2019 and kind regards, </span><o:p></o:p></p><p><span style='font-size:10.0pt'>Stéphane <br> <br> <br>Stéphane J. Hankins<br>Legal adviser<br>Cooperation and Coordination within the Movement<br>International Committee of the Red Cross<br>Tel (Prof.):++41 22 730 24 19<br><br> </span> <o:p></o:p></p><p><b><span style='font-size:12.0pt'>From:</span></b><span style='font-size:12.0pt'> Gnso-igo-ingo <<a href="mailto:gnso-igo-ingo-bounces@icann.org">gnso-igo-ingo-bounces@icann.org</a>> <b>On Behalf Of </b>Berry Cobb<b><br>Sent:</b> Friday, September 28, 2018 7:11 AM<b><br>To:</b> <a href="mailto:gnso-igo-ingo@icann.org">gnso-igo-ingo@icann.org</a><b><br>Subject:</b> [Gnso-igo-ingo] Reconvened WG Resolution Adopted</span><span style='font-size:10.0pt'> </span><o:p></o:p></p><p><span style='font-size:12.0pt'> </span><span style='font-size:10.0pt'> </span><o:p></o:p></p><p><span style='font-size:12.0pt'>Hi All,</span><span style='font-size:10.0pt'> </span><o:p></o:p></p><p><span style='font-size:12.0pt'>The GNSO Council adopted all of the Reconvened WG recommendations. The motion carried unanimously. </span><span style='font-size:10.0pt'> </span><o:p></o:p></p><p><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_council_resolutions-2320180927-2D3&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DJ69mAe-idEhpAMF1nu2x6c2w3xl7xb5cjS_7sB4h6Y&m=iJ6A2tw3n_zMPpyo-aBIaNv3iS2LaE47pKDOfsKmBdI&s=r0xuSctZZ3_tmPw2q9EaWvWviS0RTPquFvsAaZhL0Rg&e="><span style='font-size:12.0pt'>https://gnso.icann.org/en/council/resolutions#20180927-3</span><span style='font-size:10.0pt'> [gnso.icann.org]</span></a><span style='font-size:12.0pt'> </span><o:p></o:p></p><p><span style='font-size:12.0pt'>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.</span><span style='font-size:10.0pt'> </span><o:p></o:p></p><p><span style='font-size:12.0pt'>Thank you.</span><span style='font-size:10.0pt'> </span><o:p></o:p></p><p><span style='font-size:12.0pt;color:#004080'>Berry Cobb</span><span style='font-size:10.0pt'> </span><o:p></o:p></p><p><span style='font-size:12.0pt;color:#004080'>GNSO Policy Consultant</span><span style='font-size:10.0pt'> </span><o:p></o:p></p><p><span style='font-size:12.0pt;color:#004080'>@berrycobb</span><span style='font-size:10.0pt'> </span><o:p></o:p></p><p><span style='font-size:12.0pt'> </span><span style='font-size:10.0pt'> </span><o:p></o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=3 width="100%" align=center></div><p><span style='font-size:12.0pt'>_______________________________________________<br>Gnso-igo-ingo mailing list<br><a href="mailto:Gnso-igo-ingo@icann.org">Gnso-igo-ingo@icann.org</a></span><u><span style='font-size:10.0pt;color:blue'><br></span></u><a href="https://mm.icann.org/mailman/listinfo/gnso-igo-ingo"><span style='font-size:12.0pt'>https://mm.icann.org/mailman/listinfo/gnso-igo-ingo</span></a><span style='font-size:10.0pt'> </span><o:p></o:p></p><p><span style='font-size:10.0pt'> </span> <o:p></o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=3 width="100%" align=center></div><div align=center><table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 width=503 style='width:377.25pt;border-collapse:collapse'><tr style='height:4.8pt'><td width=71 style='width:53.25pt;padding:0in 0in 0in 0in;height:4.8pt'><p class=MsoNormal><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.avast.com_antivirus&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DJ69mAe-idEhpAMF1nu2x6c2w3xl7xb5cjS_7sB4h6Y&m=iJ6A2tw3n_zMPpyo-aBIaNv3iS2LaE47pKDOfsKmBdI&s=b-zvVOQwTaSuBRrvi8WJDRtIRI4ucjdiG6mT8vlrFes&e="><span style='font-size:12.0pt'>[avast.com]</span></a><span style='font-size:12.0pt'> </span><o:p></o:p></p></td><td width=12 style='width:9.0pt;padding:0in 0in 0in 0in;height:4.8pt'></td><td width=408 style='width:4.25in;padding:0in 0in 0in 0in;height:4.8pt'><p class=MsoNormal><span style='font-size:12.0pt;color:#37605E'>This email has been checked for viruses by Avast antivirus software. </span><u><span style='font-size:12.0pt;color:blue'><br></span></u><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.avast.com_antivirus&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DJ69mAe-idEhpAMF1nu2x6c2w3xl7xb5cjS_7sB4h6Y&m=iJ6A2tw3n_zMPpyo-aBIaNv3iS2LaE47pKDOfsKmBdI&s=b-zvVOQwTaSuBRrvi8WJDRtIRI4ucjdiG6mT8vlrFes&e="><span style='font-size:12.0pt'>www.avast.com [avast.com]</span></a><span style='font-size:12.0pt;color:#37605E'> </span><span style='font-size:11.0pt'><o:p></o:p></span></p></td><td width=12 style='width:9.0pt;padding:0in 0in 0in 0in;height:4.8pt'></td></tr></table></div><p class=MsoNormal align=center style='text-align:center'><span style='font-size:11.0pt'><o:p> </o:p></span></p><p align=center style='text-align:center'><span style='font-size:10.0pt'> </span> <o:p></o:p></p><p align=center style='text-align:center'><u><span style='font-size:10.0pt;color:blue'><br></span></u><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__wm5.ext.icrc.org_mail5_shankins.nsf_iNotes_Mail_-3FOpenDocument-26ui-3Ddwa-5Fframe-26l-3Dfr-26gz-26CR-26MX-26TS-3D20190121T002256-2C69Z-26charset-3DUTF-2D8-26charset-3DUTF-2D8-26KIC-26ua-3Die-26pt-26gn-23DAB4FAD8-2D2DD7-2D40BB-2DA1B8-2D4E2AA1F9FDF2&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DJ69mAe-idEhpAMF1nu2x6c2w3xl7xb5cjS_7sB4h6Y&m=iJ6A2tw3n_zMPpyo-aBIaNv3iS2LaE47pKDOfsKmBdI&s=v4qqY_AfhZSqIWtKXsMODw-g0j2EFU7zA_N1ymM7LYs&e="><span style='font-size:10.0pt'>[wm5.ext.icrc.org]</span></a><span style='font-size:10.0pt'> <br>_______________________________________________</span><span style='font-size:10.0pt;font-family:"Courier New"'><br>Gnso-igo-ingo mailing list<br><a href="mailto:Gnso-igo-ingo@icann.org">Gnso-igo-ingo@icann.org</a></span><u><span style='font-size:10.0pt;color:blue'><br></span></u><a href="https://mm.icann.org/mailman/listinfo/gnso-igo-ingo"><span style='font-size:10.0pt'>https://mm.icann.org/mailman/listinfo/gnso-igo-ingo</span></a><span style='font-size:10.0pt'> =============================================================================== The ICRC - working to protect and assist people affected by armed conflict and other situations of violence. Find out more: </span><a href="www.icrc.org"><span style='font-size:10.0pt'>www.icrc.org</span></a><span style='font-size:10.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. =============================================================================== </span><o:p></o:p></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">www.icrc.org</a><o:p></o:p></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. <o:p></o:p></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></body></html>