<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: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)"><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:0cm;
margin-bottom:.0001pt;
font-size:11.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:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EstiloCorreo19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 3.0cm 70.85pt 3.0cm;}
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=ES-AR link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'>I also agree with Tijani and following. It was Holly's best to consult the Rails. The history of .amazon and .patagonia give the reasons for this consultation.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'>In the case of .patagonia: when ICANN opens the subject to public comment, it had 1149 comments, the majority opposed to the granting to the private company. For this there were numerous movements in social networks, our own ALSs, and the governments of the countries involved, although these did not have the necessary force. </span><span style='mso-fareast-language:EN-US'>The company withdrew its order.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'>Amazon I do not give details because it is very current. But I was struck by a publication of several organizations where he said that they defend us, they should first consult us. This statement was because they had the main foundations for not assigning the domain to the private company.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'>Regards<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'>Alberto<o:p></o:p></span></p><p class=MsoNormal><a name="_MailEndCompose"><span lang=EN-US style='mso-fareast-language:EN-US'><o:p> </o:p></span></a></p><span style='mso-bookmark:_MailEndCompose'></span><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=ES>De:</span></b><span lang=ES> alac-bounces@atlarge-lists.icann.org [mailto:alac-bounces@atlarge-lists.icann.org] <b>En nombre de </b>h.raiche@internode.on.net<br><b>Enviado el:</b> domingo, 27 de agosto de 2017 12:33 p.m.<br><b>Para:</b> Seun Ojedeji <seun.ojedeji@gmail.com>; Maureen Hilyard <maureen.hilyard@gmail.com><br><b>CC:</b> ALAC <alac@atlarge-lists.icann.org>; Alan Greenberg <alan.greenberg@mcgill.ca><br><b>Asunto:</b> Re: [ALAC] Discussion: WT5 of PDP on New gTLD Subsequent Procedures<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'>I agree with Tijani, Maureen and Seun. But I lilke Seun's idea of coordinating what each RALO rep says - and Alan, would either a webinar or some mechanism be possible so that everyone is aware of all of the arguments? The reps can then both represent regional views, but in the larger context of the different views on the topic<br><br>Holly <o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal><br>----- Original Message -----<o:p></o:p></p><div><div><p class=MsoNormal style='background:#E4E4E4'><b>From:<o:p></o:p></b></p></div><p class=MsoNormal style='background:#E4E4E4'>"Seun Ojedeji" <<a href="mailto:seun.ojedeji@gmail.com">seun.ojedeji@gmail.com</a>><o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><b>To:<o:p></o:p></b></p></div><p class=MsoNormal>"Maureen Hilyard" <<a href="mailto:maureen.hilyard@gmail.com">maureen.hilyard@gmail.com</a>><o:p></o:p></p><div><p class=MsoNormal><b>Cc:<o:p></o:p></b></p></div><p class=MsoNormal>"ALAC" <<a href="mailto:alac@atlarge-lists.icann.org">alac@atlarge-lists.icann.org</a>>, "Alan Greenberg" <<a href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a>><o:p></o:p></p><div><p class=MsoNormal><b>Sent:<o:p></o:p></b></p></div><p class=MsoNormal>Sun, 27 Aug 2017 16:24:13 +0100<o:p></o:p></p><div><p class=MsoNormal><b>Subject:<o:p></o:p></b></p></div><p class=MsoNormal style='margin-bottom:12.0pt'>Re: [ALAC] Discussion: WT5 of PDP on New gTLD Subsequent Procedures<br><br><o:p></o:p></p><div><p class=MsoNormal>Me too, sounds like a feasible route to go. Ofcourse efforts should be made to coordinate amongst the 5 and the entire AtLarge community.<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Regards<o:p></o:p></p><div><p class=MsoNormal>Sent from my mobile<br>Kindly excuse brevity and typos<o:p></o:p></p></div></div></div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Aug 27, 2017 4:15 PM, "Maureen Hilyard" <<a href="mailto:maureen.hilyard@gmail.com">maureen.hilyard@gmail.com</a>> wrote:<o:p></o:p></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><div><p class=MsoNormal>I agree with Tijani, that the ALAC should send regional representatives each with their own opinion.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Sun, Aug 27, 2017 at 12:53 AM, Tijani BEN JEMAA <<a href="mailto:tijani.benjemaa@topnet.tn">tijani.benjemaa@topnet.tn</a>> wrote:<o:p></o:p></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><div><p class=MsoNormal><span style='color:#002E7A'>Bonjour Alan,</span><o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span style='color:#002E7A'>I’m afraid I don’t share your approach.</span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span style='color:#002E7A'>What you are proposing is to send to the WT a neutral (balanced) opinion. You even propose to have opinion balance rather than regional balance.</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='color:#002E7A'>This means that if we have more than a region with the same opinion, we have to take only one and take 2 or more from a region with various opinions. What would be the result????</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='color:#002E7A'>Regions much more represented than others for an issue about geographic names…..</span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span style='color:#002E7A'>I believe we should act exactly as we did for the CCWG: select 5 members from the 5 regions, and each member expresses his opinion in the WT. The final report of the WT will be ratified by the Chartering organizations, and that’s where the opinion of the ALAC as a whole will be shaped. (</span><b>with the understanding that we agree to the terms of reference, and that we are not bound by the outcomes until and unless we ratify them at the conclusion of WT5 work.</b>)<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><div><div><div><div><div><div><p class=MsoNormal><span style='color:#365F91'>-----------------------------------------------------------------------------</span><span style='color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><b><span style='color:#365F91'>Tijani BEN JEMAA</span></b><span style='color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:#365F91'>Executive Director</span><span style='color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:#365F91'>Mediterranean Federation of Internet Associations (<b>FMAI</b>)</span><span style='color:black'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:#365F91'>Phone: +216 98 330 114</span><span style='color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:#365F91'> </span><span style='color:black'> </span><span style='color:#365F91'>+216 52 385 114</span><span style='color:black'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:#365F91'>-----------------------------------------------------------------------------</span><span style='color:black'><o:p></o:p></span></p></div><p class=MsoNormal style='margin-bottom:12.0pt'><span style='color:black'><o:p> </o:p></span></p></div></div></div></div></div></div><div><div><p class=MsoNormal><o:p> </o:p></p><div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>Le 27 août 2017 à 03:29, Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a>> a écrit :<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>The GNSO PDP on New gTLD Subsequent Procedures has decided to initiate a Work Track on the use geographic names at the top level, and the ALAC, along with the GNSO, ccNSO and GAC, has been invited to participate.<br><br>As a first step, co-leaders are being requested and as you know from <a href="http://atlarge-lists.icann.org/pipermail/alac/2017-August/010630.html">http://atlarge-lists.icann.org/pipermail/alac/2017-August/010630.html</a>, the ALAC is seeking someone to take on this role on behalf of the ALAC.<br><br>The co-leaders, once selected, will work with the PDP WG Co-Chairs to establish the further procedures and the full terms of reference will likely be established by the WT itself However, it is envisaged that this new Work Track will operate with procedures comparable to a CCWG. If this is indeed what happens, the Work Track, unlike most GNSO PDP efforts, may include:<br><br>- Members formally appointed by the AC/SOs;<br>- Participants;<br>- A decision process wherein Members only may take part (used only if necessary)<br>- The .<br><br>The ALAC needs to decide how it will participate, and the criteria for selecting Members (presuming this is the path chosen).<br><br>The first part, I think, is relatively simple. I believe the ALAC should agree to be a full participant with the understanding that we agree to the terms of reference, and that we are not bound by the outcomes until and unless we ratify them at the conclusion of WT5 work.<br><br>The selection of Members (if there are any) is more complex. Normally, we are allotted five Members and I would expect that to be the case here. We typically solicit volunteers and the ALAC Appointee Selection Committee makes recommendations to the ALAC, with the expectation is that there be one candidate per region.<br><br>This situation is more challenging in that the ALAC and At-Large may have a variety of positions ranging from:<br><br>- National or local governments should have absolute control over the use of their names (or other geographic identifiers); to<br>- We have many examples of the use of geographic names in existing domains and there is no evidence of harm, so we should allow a very liberal use of geographic names in the new TLDs.<br>- In between, there are views that there should be a mechanism to arbitrate when there are different parties seeking a name, or a process like the Trademark Clearinghouse where parties can register their "interest" in a name.<br><br>It is therefore really important to understand the variety of views and make sure that our delegation to the WT represents all of these.<br><br>In order to do this, I think we need a discussion of what positions are held. This is NOT an opportunity to agree or disagree with positions presented, but to simply understand how views vary within At-Large.<br><br>I would like to open the discussion on this list to start with, and once we have a good idea of ideas, to validate them with the wider At-Large Community.<br><br>With this mail, I am soliciting input on three questions:<br><br>1. Do you agree with my proposal on the conditions for participating or if not, what do you propose instead?<br><br>2. Assuming we will be asked to appoint Members, should we try to balance their views to make sure the majority of our community has a voice on the WT? This *might* mean we end up balancing views and not have all five regions represented.<br><br>3. What are your views on how to address the use of geographic names in Top Level Domains?<br><br>Alan<br><br><br>_______________________________________________<br>ALAC mailing list<br><a href="mailto:ALAC@atlarge-lists.icann.org">ALAC@atlarge-lists.icann.org</a><br><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac">https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br><br>At-Large Online: <a href="http://www.atlarge.icann.org">http://www.atlarge.icann.org</a><br>ALAC Working Wiki: <a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a><o:p></o:p></p></div></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></div></div></div><p class=MsoNormal><br>_______________________________________________<br>ALAC mailing list<br><a href="mailto:ALAC@atlarge-lists.icann.org">ALAC@atlarge-lists.icann.org</a><br><a href="https://atlarge-listsicann.org/mailman/listinfo/alac">https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br><br>At-Large Online: <a href="http://wwwatlarge.icann.org">http://www.atlarge.icann.org</a><br>ALAC Working Wiki: <a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a><o:p></o:p></p></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal><br>_______________________________________________<br>ALAC mailing list<br><a href="mailto:ALAC@atlarge-lists.icann.org">ALAC@atlarge-lists.icann.org</a><br><a href="https://atlarge-listsicann.org/mailman/listinfo/alac">https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br><br>At-Large Online: <a href="http://wwwatlarge.icann.org">http://www.atlarge.icann.org</a><br>ALAC Working Wiki: <a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a><o:p></o:p></p></blockquote></div></div></blockquote></div><div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2">
<br /><br />
<hr style='border:none; color:#909090; background-color:#B0B0B0; height: 1px; width: 99%;' />
<table style='border-collapse:collapse;border:none;'>
<tr>
<td style='border:none;padding:0px 15px 0px 8px'>
<a href="https://www.avast.com/antivirus">
<img border=0 src="http://static.avast.com/emails/avast-mail-stamp.png" alt="Avast logo" />
</a>
</td>
<td>
<p style='color:#3d4d5a; font-family:"Calibri","Verdana","Arial","Helvetica"; font-size:12pt;'>
El software de antivirus Avast ha analizado este correo electrónico en busca de virus.
<br><a href="https://www.avast.com/antivirus">www.avast.com</a>
</p>
</td>
</tr>
</table>
<br />
<a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"> </a></div></body></html>