<html 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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:558395226;
mso-list-type:hybrid;
mso-list-template-ids:1042326778 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1
{mso-list-id:1375619428;
mso-list-type:hybrid;
mso-list-template-ids:232921282 -821103210 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:54.0pt;
text-indent:-18.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:90.0pt;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:126.0pt;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:162.0pt;
text-indent:-18.0pt;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:198.0pt;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:234.0pt;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:270.0pt;
text-indent:-18.0pt;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:306.0pt;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:342.0pt;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><a name="_MailOriginalBody"><span style="color:black">Dear Work Track Members,</span></a><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Please see below the action items and discussion notes captured by staff from the meeting today. <i>These high-level notes are designed to help WT members navigate through the content of the call and are not meant
as a substitute for the transcript or recording</i>. The MP3, transcript, and chat room notes will be provided separately.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">For reference see also the attached slides.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Kind regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Emily<o:p></o:p></span></p>
<div style="mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.0pt;padding:0cm 0cm 1.0pt 0cm">
<p class="MsoNormal" style="border:none;padding:0cm"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><b>ACTION ITEM: Get additional information on the .spa example to include in discussions for the next meeting.<o:p></o:p></b></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoListParagraphCxSpFirst"><o:p> </o:p></p>
<ol style="margin-top:0cm" start="1" type="1">
<li class="MsoListParagraphCxSpMiddle" style="margin-left:0cm;mso-add-space:auto;mso-list:l0 level1 lfo1">
Welcome/Agenda Review/SOI Updates<o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:0cm;mso-add-space:auto;mso-list:l0 level1 lfo1">
Meeting Schedule<o:p></o:p></li></ol>
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
The leadership team held a doodle to get input from WT members on the meeting rotation. The majority of respondents preferred to meet weekly for 60 minutes. The weekly rotation will begin next week on a trial basis.<o:p></o:p></li></ul>
<ol style="margin-top:0cm" start="3" type="1">
<li class="MsoListParagraphCxSpMiddle" style="margin-left:0cm;mso-add-space:auto;mso-list:l0 level1 lfo1">
Discussion of cities<o:p></o:p></li></ol>
<p class="MsoListParagraphCxSpMiddle">Capital city names:<o:p></o:p></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
One WT member expressed that there was some good discussion on this list and encouraged the group to build on the list discussion during the call today.<o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
Key points from contributions on the mailing list are captured in the working document:
<a href="https://docs.google.com/spreadsheets/d/1FuPEq0y-cdSUQ1nvhWKhVnG8PLaC2RYXsCpQu91FDqo/edit#gid=358523414">
https://docs.google.com/spreadsheets/d/1FuPEq0y-cdSUQ1nvhWKhVnG8PLaC2RYXsCpQu91FDqo/edit#gid=358523414</a><o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
On the text on slide 6 summarizing the 2007 policy with respect to capital city names:<o:p></o:p>
<ul style="margin-top:0cm" type="circle">
<li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level2 lfo2">
“Available, but challenge mechanism to governments to initiate an objection. Applicants should be aware of GAC Principles. Applicants must represent that the use of the proposed string is not in violation of the national laws in which the applicant is incorporated.”
<o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level2 lfo2">
A Work Track member expressed that there should be a clear set of objectives used to evaluate all applications that is equitable. Capital city names are at times contested (example: Jerusalem). There are also different linguistic representations of such names.
<o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level2 lfo2">
Some applicants may want to do something with the string that is not in the purview of governments or not agreed to by governments.
<o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level2 lfo2">
A government stakeholder expressed that governments base their positions regarding strings and the attribution of those strings in national law, but national law only helps us to a certain extent.<o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level2 lfo2">
We need to think more carefully about how we come up with objection procedures. <o:p>
</o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level2 lfo2">
“Applicants must represent that the use of the proposed string is not in violation of the national laws in which the applicant is incorporated.” – according to this WT member, this is not a practical provision.
<o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level2 lfo2">
An applicant can be located anywhere in the world, so this does not help us with decisions about the use of a string. We need be more careful about the treatment of this issue.<o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level2 lfo2">
There is a big difference between letters of support and non-objection. Non-objection is not only about non-objection from government authorities. It is superficial to think that the only possible legitimate expression of support or non-objection should come
from national governments. <o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level2 lfo2">
Example from the mailing list – “Perth” was raised again. Different countries may have cities named Perth. There are different representations of a single string. This could be an opportunity for collaboration<o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level2 lfo2">
From this WT member’s perspective, there should be a broader conversation about place names. Focusing specifically on the capital city names for this conversation is too restrictive.
<o:p></o:p></li></ul>
</li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
Question raised: Objection could be explicit or implied. Which are we talking about on this call?<o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
Position expressed by a WT member: Discussing the right of objection is the wrong way to approach this. Basing this on a sovereignty context is ill-advised. In the 2012 round, Tata had to seek a letter of support of non-objection from a small province in Morocco,
even though this province had not expressed any interest in this TLD. We should be careful when we talk about objections that we address the basis of the objection. We should make sure we discuss what right is being violated before we decide if there is an
objection to be had. <o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
Changing the discussion to place names – in the 2012 context, the capital city names had stronger protection than other city names. If we discuss these in a broader context of place names, we need to consider how to approach this issue.
<o:p></o:p></li><li class="MsoListParagraphCxSpLast" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
Position expressed by a WT member: You need to respect the concerns of the people of a country who have attachment to a particular string. This is not just a matter of government, it is about consulting the people of the country. Capital city names should be
treated differently that city names.<o:p></o:p></li></ul>
<p class="MsoNormal" style="margin-left:36.0pt">City names:<o:p></o:p></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraphCxSpFirst" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
Many city names are also brands.<o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
A WT member raised that one possibility is to share a top-level domain among different groups that have an interest in the string.<o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
Position expressed by a WT member: Idealistic but impractical that different geographic locations with the same name and brands could all share a TLD. If we created some sort of hierarchy of rights, we are getting into a huge can of worms.
<o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
Question raised: going back to the comment that citizens of a place have the right to provide input on the use of the that name, where does that right come from?<o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
Position expressed by a WT member: It should not be the case that everything must be written in law. It is not appropriate to use geographic names at the top level without the permission/agreement of the government.
<o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
Position expressed by a WT member: It would be helpful to get suggestions for models where we can manage different perspectives and develop options for a path forward that take into account the different needs.<o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
Position expressed by a WT member: It may not be the place of WT5 to figure out how different geographic interests could “share” a TLD. This was raised more to indicate that there could be benefits to groups coming together to cooperatively manage at TLD.
<o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
Question: What issues are we trying to solve that came up in the previous round?<o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
Idea raised by a WT member: One way to work through this is focusing on context – using the example “Springfield.” If someone wants to use this string for a non-geographic use, for example the Springfield rifle company, and make this clear in their application
(could be generic or a brand) perhaps this is a path forward. <o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
Spa is an example from the last round where there was an applicant who wanted to use the string in a non-geographic context.<o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
Idea raised by a WT member: In the 2012, for city names, if you were using the name in a non-geographic context, you did not need to go through the support/non-objection process. This may be a path forward.
<o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
Position expressed by a WT member: This path cannot be generalized, it should be a conversation between the applicant and the other groups involved.
<o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
Clarification by WT leadership -- In the 2012 round, the applicant specified the purpose of the application in the application process. Objections were also built into the application process. If we need to make the application process clearer, that is something
the WT can explore. <o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
Example raised by a WT member: Spa was used as an example of a string where the applicant wanted to use it in the non-geographic context. In the 2012 round, the applicant applied to use the string in a non-geographic context, but the application was held up
by geographic concerns raised by the Belgian government. Tata was a similar case.
<o:p></o:p></li></ul>
<ol style="margin-top:0cm" start="4" type="1">
<li class="MsoListParagraphCxSpMiddle" style="margin-left:0cm;mso-add-space:auto;mso-list:l0 level1 lfo1">
Continue Discussion of Non-Included Categories<o:p></o:p></li></ol>
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
What is meant by additional categories of geographic names?<o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
This is a discussion of possible types of geographic names not covered in the 2012 AGB. Some examples have been raised on the mailing list, for example rivers, mountains, names associated with cultural and linguistic community.
<o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
In the working document, we have collected suggestions about other areas that members would like to discuss. This is the opportunity to raise these topics. WT members are encouraged include rationale about why these strings would need special treatment if you
think they need it. <o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
Perspective raised by a WT member: Geographical indications should be a distinct category. They are based on local law and should be discussed in this Work Track.<o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
Suggestion by a WT member: Perhaps it is worthwhile to think about geographic names as a brand. What if we looked at “Sydney” as a brand. Part of our problem statement is that in many cases, geographic terms are brands. What is the brand value of a geographic
term – look at cases like camembert cheese or Bordeaux wine or other terms where the geographic association has economic implications.
<o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
Question/issue raised by a WT member: We need to have a clear definition of the term “community” in the context of these discussions. How do we decide what the economic interests are?<o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
Response: In the 2012 round, strings that passed CPE had priority over other applications in a contention set. This specific context of the term community, which it may not be appropriate for this WT to discuss.<o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
Suggestion raised by a WT member: We could look at what rights brands have in the TLD context. Brands cannot insist on letters of support or non-objection for an application. Brands cannot stop other applicants from applying for strings – for example, Apple
the brand is not in a position to stop an association of apple growers from applying for a string related to apples.<o:p></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
There is no rule at this time that a community cannot also be a geographic term, so that is the intersection. But the treatment of community applications will be handled by another Work Track.
<o:p></o:p></li></ul>
<ol style="margin-top:0cm" start="5" type="1">
<li class="MsoListParagraphCxSpMiddle" style="margin-left:0cm;mso-add-space:auto;mso-list:l0 level1 lfo1">
Any Other Business<o:p></o:p></li></ol>
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraphCxSpLast" style="margin-left:18.0pt;mso-add-space:auto;mso-list:l1 level1 lfo2">
None. <o:p></o:p></li></ul>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><b><span style="font-size:11.0pt">Emily Barabas
</span></b><span style="font-size:11.0pt">| Senior Policy Specialist<o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">ICANN</span></b><span style="font-size:11.0pt"> | Internet Corporation for Assigned Names and Numbers<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:11.0pt">Email: emily.barabas@icann.org | Phone: +31 (0)6 84507976<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>