<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:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@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;}
@font-face
{font-family:"\@MS Gothic";
panose-1:2 11 6 9 7 2 5 8 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.apple-style-span
{mso-style-name:apple-style-span;}
span.apple-tab-span
{mso-style-name:apple-tab-span;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.E-MailFormatvorlage22
{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 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:512570132;
mso-list-template-ids:2023524422;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1
{mso-list-id:1742412812;
mso-list-template-ids:1342056760;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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="DE" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">+1<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">BG,<br>
Katrin<br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">DOTZON GmbH - digital identities for tomorrow<br>
Akazienstrasse 28<br>
10823 Berlin<br>
Deutschland - Germany<br>
Tel: +49 30 49802722<br>
Fax: +49 30 49802727<br>
Mobile: +49 173 2019240<br>
<a href="mailto:ohlmer@dotzon.consulting">ohlmer@dotzon.consulting</a><br>
<a href="http://www.dotzon.consulting">www.dotzon.consulting</a><br>
</span><span style="font-size:7.5pt;font-family:"Arial",sans-serif"><br>
DOTZON GmbH<br>
Registergericht: Amtsgericht Berlin-Charlottenburg, HRB 118598<br>
Geschäftsführer: Katrin Ohlmer<br>
Sitz der Gesellschaft: Akazienstrasse 28, 10823 Berlin</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b>Von:</b> Gnso-newgtld-wg [mailto:gnso-newgtld-wg-bounces@icann.org]
<b>Im Auftrag von </b>Maxim Alzoba<br>
<b>Gesendet:</b> Donnerstag, 28. <span lang="EN-US">Dezember 2017 08:05<br>
<b>An:</b> lists@christopherwilkinson.eu<br>
<b>Cc:</b> <br>
<b>Betreff:</b> Re: [Gnso-newgtld-wg] Notes and Action Items - New gTLD Subsequent Procedures PDP Working Group - 11 December 2017<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal">Dear Cristopher, <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I do not think we need to prescribe the form of the entities for GEOs.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Legal form of GEO applicant does not have to be non-for profit (it does not work in cases. where municipal entity decides to run tender, where the highest bidder is allowed<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">to have a letter of support from the city). Also costs are also the same (except for taxation) for commercial entities.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">And since municipal entities represent large populations of people (and usually heads of cities are elected),<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> they represent public interest in GEOs, and non non-for profits applying for the job.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">In the cases where the municipal entity acts on it's own as an applicant - they can not be non-for profit and also can not follow<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">all the text in the RA (after all cities follow national law, which usually is quite prescriptive in the areas of what cities can and can not do).<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">As for Registration Restrictions - not necessary GEOs will use it (they are already limited by the local persons interest (most probably citizens of other areas do not need it)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">, and there is no need to make it worse).<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">If an entity can not bear the costs, it does not matter, which legal form was used before it<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">loses ability to run Registry business, so I am not sure why we need to have two different approaches to the evaluation.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"> Short list of costs: COI instrument, contracts with ISPs with DDoS protection, rack space for hardware in at least two datacenters, salary for engineers/office, Secondary DNS Anycast cloud services, office rent costs, legal advice cost
- talking to ICANN Compliance might need it e.t.c ... or the procurement of all/some of those services from the backend providers (RSPs).<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">My thinking is that financial model evaluation was more an abstract test then real model used later by Registries, so it is not known if it was useful, and audits of newly created legal entities can not show the future of the entity (though
it might be helpful for old ones).<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">In the current round thorough research did not help with predictions of ICANN's actions / lack of actions and I do not think <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">that it will help in the next one.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica",sans-serif;color:black">Sincerely Yours,<br>
<br>
Maxim Alzoba<br>
Special projects manager,<br>
International Relations Department,<br>
FAITID<br>
<br>
m. +7 916 6761580(+whatsapp)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica",sans-serif;color:black">skype oldfrogger<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica",sans-serif;color:black">Current UTC offset: +3.00 (.Moscow)<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">On Dec 27, 2017, at 22:10, <a href="mailto:lists@christopherwilkinson.eu">
lists@christopherwilkinson.eu</a> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal">Dear Emily:<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">1.<span class="apple-tab-span"> </span>Re: Potential TLD types/categories<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">It is not clear what is meant by ‘carve-out’. Regarding Geo-Names, I consider that they should be generally Not for Profit, in the public interests in the areas that they serve. They would normally have Registration Restrictions, for instance,
location based.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Regarding evaluation criteria, I consider that much more stringent economic considerations should be applied generally to ‘for profit’ proposals. This is not a ‘carve-out’ but a general requirement.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">2.<span class="apple-tab-span"> </span>Framework of Predictability:<span class="apple-tab-span">
</span>I recall that during the previous round, a source of ‘unpredictability’ was the lack of understanding by applicants of the policy context with which they were engaging at local, national and international level. For applicants to reduce unpredictability,
I would recommend much more thorough research before applying.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">In this context, the use of the word ‘generic’ is increasingly misleading. We should avoid any suggestion that the default is ‘generic’ and that anything else is a ‘carve-out’.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">On the contrary, nearly all categories show specific characteristics of their own. These are not ‘carve outs’ but rather distinct categories.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Regards<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Christopher Wilkinson<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">On 21 Dec 2017, at 20:18, Emily Barabas <<a href="mailto:emily.barabas@icann.org">emily.barabas@icann.org</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal" style="background:white">Dear Working Group members,<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"> <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">On the 11 December Working Group call, the co-chairs invited Working Group members to provide input on two items over the mailing list. This note serves as a reminder of the issues for which they are seeking comments. <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"> <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">On the call, the WG reviewed the status of conversations regarding potential TLD types/categories for subsequent procedures (<a href="https://docs.google.com/spreadsheets/d/1mA_hTUhLhJSsfcmoQwREtUqxykZ5KfJffzJAAhEvNlA/edit#gid=0"><span style="color:#954F72">https://docs.google.com/spreadsheets/d/1mA_hTUhLhJSsfcmoQwREtUqxykZ5KfJffzJAAhEvNlA/edit#gid=0</span></a>).
Your input is encouraged on the following questions:<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"> <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<ul style="margin-top:0cm" type="disc">
<li class="MsoNormal" style="margin-left:0cm;mso-list:l0 level1 lfo1;background:white">
Is it critical to carve out exceptions for some of the identified types? If so, what are the <b>pros/cons </b>for carving out specific mechanisms to accommodate any of the proposed types?<span style="font-size:12.0pt"><o:p></o:p></span></li><li class="MsoNormal" style="margin-left:0cm;mso-list:l0 level1 lfo1;background:white">
If there are <b>critical exceptions</b> needed for any of the proposed types, please help identify what they might be (e.g., applicant eligibility criteria, evaluation criteria/process, contractual requirements, etc.).<span style="font-size:12.0pt"><o:p></o:p></span></li></ul>
<div>
<p class="MsoNormal" style="background:white"> <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">The WG touched briefly on the Framework for Predictability (<a href="https://docs.google.com/document/d/1lzXxBLMtFr03BKnHsa-Ss7kR7EAJt7pCI1EP3H81tfQ/edit#heading=h.8pcr95hvmmz"><span style="color:#954F72">https://docs.google.com/document/d/1lzXxBLMtFr03BKnHsa-Ss7kR7EAJt7pCI1EP3H81tfQ/edit#heading=h.8pcr95hvmmz</span></a>),
which is intended to balance ICANN Org’s ability to operate in an effective manner while ensuring the community is properly consulted when issues arise. Your input is requested on the following: <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"MS Gothic"">
</span><span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<ul style="margin-top:0cm" type="disc">
<li class="MsoNormal" style="margin-left:0cm;mso-list:l1 level1 lfo2;background:white">
What are some use cases we can apply against the framework to test how it would work in practice?<span style="font-size:12.0pt"><o:p></o:p></span></li></ul>
<div>
<p class="MsoNormal" style="background:white"> <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">For background, please see the attached slides for the call. In order to help the Working Group progress deliberations on this topic, please share your thoughts on the mailing list prior to the next full Working
Group call on 8 January 2018.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"> <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">Kind regards,<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">Emily<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"> <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"> <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"> <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<div>
<p class="MsoNormal" style="background:white"><b><span style="font-size:12.0pt">From:<span class="apple-converted-space"> </span></span></b><span style="font-size:12.0pt">Gnso-newgtld-wg <<a href="mailto:gnso-newgtld-wg-bounces@icann.org"><span style="color:#954F72">gnso-newgtld-wg-bounces@icann.org</span></a>>
on behalf of Emily Barabas <<a href="mailto:emily.barabas@icann.org"><span style="color:#954F72">emily.barabas@icann.org</span></a>><br>
<b>Date:<span class="apple-converted-space"> </span></b>Monday 11 December 2017 at 12:11<br>
<b>To:<span class="apple-converted-space"> </span></b>"<a href="mailto:gnso-newgtld-wg@icann.org"><span style="color:#954F72">gnso-newgtld-wg@icann.org</span></a>" <<a href="mailto:gnso-newgtld-wg@icann.org"><span style="color:#954F72">gnso-newgtld-wg@icann.org</span></a>><br>
<b>Subject:<span class="apple-converted-space"> </span></b>[Gnso-newgtld-wg] Notes and Action Items - New gTLD Subsequent Procedures PDP Working Group - 11 December 2017<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"> <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal" style="background:white">Dear Working Group members,<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"> <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">Please find below notes and action items from the call today. These high-level notes are designed to help Working Group members navigate through the content of the call and are not a substitute for the chat transcript
or the recording. The call recording, call transcript, and chat transcript will soon be available here:<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_SQxyB&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mBQzlSaM6eYCHFBU-v48zs-QSrjHB0aWmHuE4X4drzI&m=JEW8DnUXx2bEgewpLq4ebIZVMtuhZshCB5JwVdtHj4Y&s=pE0ABBF34dzGWetkfjMphb2NWNS_azPVgS-tWeASZUY&e="><span style="color:#954F72">https://community.icann.org/x/SQxyB[community.icann.org]</span></a>.<span class="apple-converted-space"> </span><span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"> <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">Some excerpts from the chat room are included in the notes. Please see the chat transcript for a full record of chat comments.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"> <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">Slides are attached for reference.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"> <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">Kind regards,<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">Emily<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div style="border:none;border-bottom:solid windowtext 1.0pt;padding:0cm 0cm 1.0pt 0cm">
<div>
<p class="MsoNormal" style="background:white"> <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal" style="background:white"> <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>ACTION ITEM: Co-Chairs will contact Ombudsman regarding concerns raised on this call.</b><span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"> <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">1. SOI Updates<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- no updates<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">2. Work Track Updates<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- Work Track 1 - next call on 19 Dec will cover systems, communications, and application queuing<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- Work Track 2 - There was a WT2 call last week which covered Contractual Compliance and TLD Rollout and CC2 comments on these topics. The next call is 21 December - the call will focus on reviewing strawman recommendations prepared by the co-leads.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- Work Track 3 - Next meeting is on 12 December at 15:00 UTC. WT3 will discuss Community Applications and Objections.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- Work Track 4 - Next meeting will be 14 December at 3:00 UTC. The call will focus on the applicant reviews with a focus on applicant financial models. <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- Work Track 5 - WT5 had a meeting last Wednesday in which it discussed the Terms of Reference. In the next meeting on 20 December, the WT will do a second reading on the TOR document.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- Some GAC members were surprised by the response to the GAC conditions for participation in WT5. The GAC may provide a response on this issue.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- Request to return to issue of participation model contained in the Terms of Reference on the upcoming call.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- Additional work will need to be done to come to agreement on the Terms of Reference.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- There is a single Chartering Organization in the PDP, which is the GNSO. Measures have been put into place to ensure that all voices are heard in WT5. <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">Chat excerpt:<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>kavouss Arasteh: </b>I do not agree with your conclusions<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>kavouss Arasteh: </b>The issue of Georaphic name isc much beyound the leadership of GNSO<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>kavouss Arasteh: </b>The issue is disagreement on whether PDP is relevant here <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>kavouss Arasteh: </b>There seems to be that our concerns are not heard<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Greg Shatan: </b>This is a GNSO PDP Working Group. That is a fundamental fact. The issue of gTLD policy is the raisin d’etre for the GNSO.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>kavouss Arasteh: </b>It is a cross community issue and not GNSO issue<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Greg Shatan: </b>That is certainly your opinion, and thank you for your personal views.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>kavouss Arasteh: </b>I am speaking from my own side here<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Robin Gross: </b>We need to follow the rules, not break them in order to privilege one of the groups that isn't happy with them.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>kavouss Arasteh: </b>WHAT Rules Dear Mdam<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>kavouss Arasteh: </b>MADAM'<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Maxim Alzoba (FAITID ): </b>in any case GEO TLDs had to obtain letter of approval from the relevant local/federal governmental body<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Greg Shatan: </b>Robin, we don’t know that any group is asking for that. Only a single member of a group.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Maxim Alzoba (FAITID ): </b>or letter of non objection from the same governmental body<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>kavouss Arasteh: </b>It is not surprising that you want the domination of GNSO with its PDP Rules to be applied to Geographic names<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Steve Chan: </b>As referenced by Cheryl, GNSO Operating Procedures, which are inclusive of the GNSO Working Group Guidelines and PDP Manual: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_council_op-2Dprocedures-2D01sep16-2Den.pdf&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mBQzlSaM6eYCHFBU-v48zs-QSrjHB0aWmHuE4X4drzI&m=FN3L848cy2TmbBFv_xNVZIBUc--golVeGZZ7sSUJNxg&s=aqeivPdCVM1wsLkCttYXF2a-EUgTAXgXApliix4nTdU&e=" target="_blank"><span style="color:#954F72">https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf[gnso.icann.org]</span></a><span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>kavouss Arasteh: </b>Geographic names are not the property of any group. It belongs to the citizen of all countries<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Greg Shatan: </b>Cheryl is a member of ALAC. Not sure how that contributes to anyone’s lack of surprise.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Martin Sutton: </b>@ Kavous - the GNSO is the vehicle for addressing the policy issue but allows all to be involved. All concerns and views are taken into consideration. Ultimately, all of the 4 leading groups and other advisory groups will have further opportunities to comment on any output from WT5. <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Greg Shatan: </b>Kavouss, your personal views on that matter have been amply stated and heard.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>kavouss Arasteh: </b>Dear Greg, we have difference of view in that subject<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- The unique nature of WT5 was designed to provide leadership balance in recognition of the importance of this issue in different parts of the community<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">3. Overarching Issue: Application Types<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- Status Quo - Different Types in 2012: Standard application, community-based application, geographic names, specification 13 (.Brand)<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">Chat excerpt: <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Kurt Pritz: </b>I think we might distinquish between the policy-based (i.e., in the Guidebook) categories: Community and Geographic; vs thise that were inserted via independent discussion afterward: <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Donna Austin, Neustar: </b>Can we spell out NGPC please for some that weren't around in 2012<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Steve Chan: </b>NGPC = New gTLD Program Committee. Thanks Donna for the reminder.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Heather Forrest: </b>I agree that it is sensible to make the distinction that Kurt has raised between community policy-based and independent agreement<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>kavouss Arasteh: </b>There is no clear description on community<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>kavouss Arasteh: </b>If there is what is that?<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>kavouss Arasteh: </b>There is nalso no clear idea on how communities requirements to be compared with each other <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Kurt Pritz: </b>My point earlier was that there is consensus policy on geo and Community categories and no consensus policy on closed generics and brands so the latter "categories" deseverve more discussion and should not be considered a status quo consensus policy<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- Work Track related efforts: WT2 is considering Closed Generics, WT3 is considering Community applications, and WT5 is considering Geographic Names<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- On slide 6, AGB section 2.2.1.4.2 is mentioned in the slides, but additional sections of the AGB also address geographic names, and these will also fall within the scope of WT5 discussions. <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">Chat excerpt:<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>kavouss Arasteh: </b>Could one consider drug traffic group as a community?i<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Jim Prendergast: </b>While we did have some lenghty disucssions on closed generics in WT2, there is still some healthy oppostion to the concept so I dont know how settled that issue is.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Robin Gross: </b>I suppose a pharmacy group could apply as a community.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>kavouss Arasteh: </b>Those issues were written some 10 years ago and situation has changed drastically<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Maxim Alzoba (FAITID ): </b>AGB might change as result f some PDP work<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Marc Palau: </b>What about family names? that's not an strict community<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Marc Palau: </b>like .kim<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Steve Chan: </b>@Kavouss, the description of the AGB was to set the stage and to identify what took place in the 2012 round. As Maxim notes, things can change in the future as a result of the work of this PDP.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Maxim Alzoba (FAITID ): </b>it might depend on wealth of the family <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Greg Shatan: </b>@Maxim, exactly; that is why this PDP exists....<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>kavouss Arasteh: </b>Dear Colleagues, I am eligible to raise questions without being criticized or repressed is it not so?<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>avri doria: </b>Aren't there also other conditions in the AGB against crimminal behaviors and activities?<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>kavouss Arasteh: </b>We need to revisit the definition of community and revist various categories of communioties as they are not having the same conditions<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Maxim Alzoba (FAITID ): </b>I think GAC advise might play it's role irto prevent such bad actor's communities<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>kavouss Arasteh: </b>As soon as we raise a legitimate question , an valanch of disagreement comes up without giving a convincing argument<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- Work Track 3 is still working to define community. One thing we can say confidently is that however we define community, it will need to be in support of the public interest. <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- There are conditions in the AGB against criminal activities. <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- If there is no consensus on recommendations for change in this PDP, the status quo remains.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- Review of attributes for current application types.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- Null Hypothesis: If we changed nothing in the approach to categories in the AGB for Subsequent Procedures, would there be a problem?<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- We may not need new categories, but there may need to be tweaks to the AGB regarding the relevant sections of the guidebook<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- .Brands are not in consensus policy, for example, so we would need to tidy that up. Discussions on Closed Generics are still underway.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">Chat excerpt:<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Kurt Pritz: </b>If we change nothing in the Guidebook, there are no brand TLDs and no restrictions on closed generics - there is no consensus policies on these<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Greg Shatan: </b>@Kurt, why would keeping the status quo AGB result in changes in implementation?<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Greg Shatan: </b>We can add those to consensus policy, but the lack of consensus policy doesn’t roll back implementation.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- . Brands are not covered in previous policy, so we would need to work that into future application processes<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">Chat excerpt:<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Kurt Pritz: </b>@ Greg: Are you advocating that the GB remail silent on Brands and closed generics but conducting the round in the same way?<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Kurt Pritz: </b>I agree with Martin - the next round must encourage innovation by developing a flexible approach to accommodating new models<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Kurt Pritz: </b>I think categorization is rigid and exclusionary (is that a word)<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Martin Sutton: </b>Good point Donna - I agree that innovation should not be stifled through categorisation where it is not needed<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Christopher Wilkinson: </b>@AGB It is already clear that the definition of Geo-Names and associated decision making policies will have to evolve<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- It is important to reflect on what we witnessed in the 2012 Round. We cannot predict everything. For any new types that emerge, there will be an opportunity to evolve the system, but it is difficult to predict this now.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- We should also include generic as a category. It is intentionally broad. There were some things that happened after the application process closed that had an impact, and additional restrictions put in place following GAC Advice. There was no harm done by not having additional categories. <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- The GAC Advice could have been viewed as restrictive and reduced innovation<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- If we create too many rules or parameters around categories, we could further stifle innovation. We don't want to do that.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">-Slide 12: Preliminary List of Types (beyond existing)<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"> - Wouldn't it possible to address differences in different applications through specifications to the base agreement rather than creating categories, since these categories may have overlapping requirements. This seems to be a simpler approach. Are there any issues with this approach?<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">Chat excerpt:<span class="apple-converted-space"> </span><span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Robin Gross: </b>4 seems to lump two different groups together. Highly regulated industries have nothing to do with words that others may be "sensitive" to hearing.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Steve Chan: </b>@Robin, I believe that lumping together carries from GAC Advice. That of course would not prevent this WG from decoupling the two types.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Robin Gross: </b>Thanks, Steve. I think we wouldn't want to lump them together.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Kurt Pritz: </b>With regards to status quo and Cheryl’s mantra that if we don’t arrive at a consensus for change, we are left to the stars quo: we don’t have a policy on brands and closed generics and they are not in the Guidebook. It is not that I am against Brand TLDs, it is that I think the accommodations provided brands could also be afforded that don’t own trademarks but that deserve and need them for there business model. This should be discussed as a consensus policy<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- Agree that there may be different applications that warrant different provisions that might not upset the existing policy. It is possible to provide accommodations as needed for applications where it is appropriate. <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">Chat excerpt: <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>kavouss Arasteh: </b>I am referring to decision making process in Geo Names<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>kavouss Arasteh: </b>Is there any hope that such concerns be addressed?<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Donna Austin, Neustar: </b>@Kavouss, it would be great if you could give the process a chance. <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Annebeth Lange,WT5: </b>The problem, Kavouss, as I see it, is that GNSO, according to the bylaws of ICANN. is responsible for the new gTLD policy. So how to have a "true" cross community PDP, I am not sure how we can achieve this under the present bylaws. However, we should try to trust the process and see what can be achieved.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Donna Austin, Neustar: </b>@Annebeth, WT5 is a pro-active attempt to have a true cross community PDP and it is truly appreciated that the SO/ACs have responded positively to the request to participate.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Annebeth Lange,WT5: </b>*Donna, I agree. However, even if that is what is the intention, still many do not feel that it is a "true" CCWG. I trust the process, but there is still a feeling of "someone matters more than others" out there, unfortunately.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Donna Austin, Neustar: </b>@Annebeth, appreciate your thoughts and hopefully we can work together to dispell the myths. <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- One of the challenges is that there are 8 potential types of TLDs in the slides, and there would be more with geo, communities, and brands. If you develop different policies for each type, the administration will be significant. It will be harder to move through the process in a streamlined manner. It is also difficult on the backend for contractual compliance. Should the group consider the value, what are we trying to achieve, and what the potential impact will be.<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- The hope is that the full group conversation will provide additional input to the WTs that are considering some of the questions around categorization<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- Future Application Types - Potential Attributes (slide 13)<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- Attributes Matrix (slides 14, 15, 16)<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- Pros and Cons of categorization in general (slide 17)<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- Homework (slide 18): Share on the list if you believe it is critical to carve out exceptions for some of the identified types. WG members can help to identify pros/cons for specific proposed types and identify critical exceptions for specific proposed types<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- More homework (slide 20): WG members are encouraged to prposed use cases to test the predictability framework. <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">. AOB<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">- none<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"> <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"> <span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>Emily Barabas<span class="apple-converted-space"> </span></b>| Senior Policy Specialist<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b>ICANN</b><span class="apple-converted-space"> </span>| Internet Corporation for Assigned Names and Numbers<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white">Email:<span class="apple-converted-space"> </span><a href="mailto:emily.barabas@icann.org"><span style="color:#954F72">emily.barabas@icann.org</span></a><span class="apple-converted-space"> </span>| Phone: +31 (0)6
84507976<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt"> <o:p></o:p></span></p>
</div>
<p class="MsoNormal"><Application Types_11Dec2017 v3.pdf><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif;background:white">_______________________________________________</span><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif"><br>
<span style="background:white">Gnso-newgtld-wg mailing list</span><br>
</span><a href="mailto:Gnso-newgtld-wg@icann.org"><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif;color:#954F72;background:white">Gnso-newgtld-wg@icann.org</span></a><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif"><br>
</span><a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg"><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif;color:#954F72;background:white">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg</span></a><o:p></o:p></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
Gnso-newgtld-wg mailing list<br>
<a href="mailto:Gnso-newgtld-wg@icann.org">Gnso-newgtld-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg</a><o:p></o:p></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>