<div dir="ltr">Hi Katrin and Liz<div><br></div><div>To me this is a logical process by which to approach Phase A with useful mechanisms to provide checkpoints along the way, that as you say enhance transparency and predictability.</div><div>Its a starting point and makes sense for moving forward.</div><div><br></div><div>Maureen</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 13, 2018 at 8:37 PM, Katrin Ohlmer | DOTZON GmbH <span dir="ltr"><<a href="mailto:ohlmer@dotzon.com" target="_blank">ohlmer@dotzon.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="DE" link="blue" vlink="purple" style="word-wrap:break-word;line-break:after-white-space">
<div class="m_7141110391985474078WordSection1">
<p class="MsoNormal"><span>Dear Liz,<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">in my opinion it is our task as working group to enhance your described situation about Phase A as this caused apparently issues in the last round:<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">“</span><span lang="EN-US">In Phase A, my sense is that it is an applicant’s job to be really thorough in its risk management and engagement strategy which
<b>may </b>include speaking to public authority representatives.”</span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">A desireable outcome of our work would be to increase the predictability and transparency of the application process – both for applicants and the ICANN community. So why should we keep
what it is in the AGB 2012 and not consider means which help to reduce issues and enhance the process? Proposals by different WT members which have been made in this context included
<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">+ geo database to check whether the intended applied-for name equates a geoName
<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">+ geo Advisory panel<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">+ include check if the intended applied-for name equates a geoName<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Kind regards<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Katrin<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></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" target="_blank">ohlmer@dotzon.consulting</a><br>
<a href="http://www.dotzon.consulting" target="_blank">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><u></u><u></u></p>
</div>
<p class="MsoNormal"><span><u></u> <u></u></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-wt5 [mailto:<a href="mailto:gnso-newgtld-wg-wt5-bounces@icann.org" target="_blank">gnso-newgtld-wg-wt5-<wbr>bounces@icann.org</a>]
<b>Im Auftrag von </b>Liz Williams<br>
<b>Gesendet:</b> Donnerstag, 14. Juni 2018 01:18<span class=""><br>
<b>An:</b> Icann Gnso Newgtld Wg Wt5 <<a href="mailto:gnso-newgtld-wg-wt5@icann.org" target="_blank">gnso-newgtld-wg-wt5@icann.org</a><wbr>><br>
<b>Betreff:</b> Re: [Gnso-newgtld-wg-wt5] Notes and Action Items - New gTLD Subsequent Procedures PDP Work Track 5 - 13 June 2018<u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Hello everyone <u></u><u></u></p><div><div class="h5">
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I have a slightly different take on who has responsibility for monitoring applications for new TLDs. Governments and public authorities monitor things all the time…that is their job in everything from fishing quota compliance to handing
out car registrations. If we argue that governments have national public policy responsibilities (which I believe that they do) then it is also a “responsibility” to take notice of things like a new TLD process which happens very infrequently. We should
be confident that with the ever-growing GAC membership, we have a set of stakeholders who are paying attention to the expansion of the domain name system as a platform for economic growth (amongst many other things) for their citizens.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">And if we were to extend slightly the conversation we had yesterday, we can easily identify where “focus” could come in a new TLD process. I spoke about Phase A (application), Phase B (evaluation) and Phase C (compliance). If governments
are also applicants then they are involved in all three phases (and we already have examples of this precise case). If a national government is interested in Phase B as an objector which is entirely possible, then we should have obvious mechanisms for any
objector to express their objection and have it handled fairly and appropriately. In Phase A, my sense is that it is an applicant’s job to be really thorough in its risk management and engagement strategy which
<b>may </b>include speaking to public authority representatives.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">This situation applies for all kinds of applications…not just for labels which could be perceived as representing some geographic element.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Liz<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal"><br>
<span style="font-size:9.0pt;font-family:"Avenir",serif;color:black">….<br>
Dr Liz Williams | International Affairs<br>
.au Domain Administration Ltd<br>
M: +61 436 020 595 | +44 7824 877757<br>
E: <a href="mailto:liz.williams@auda.org.au" target="_blank">liz.williams@auda.org.au</a> <a href="http://www.auda.org.au" target="_blank">ww<wbr>w.auda.org.au</a><br>
<br>
Important Notice<br>
This email may contain information which is confidential and/or subject to legal privilege, and is intended for the use of the named addressee only. If you are not the intended recipient, you must not use, disclose or copy any part of this email. If you have
received this email by mistake, please notify the sender and delete this message immediately.</span>
<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><br>
<br>
<u></u><u></u></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">On 14 Jun 2018, at 1:46 am, <a href="mailto:lists@christopherwilkinson.eu" target="_blank">
lists@christopherwilkinson.eu</a> Wilkinson <<a href="mailto:lists@christopherwilkinson.eu" target="_blank">lists@christopherwilkinson.eu</a><wbr>> wrote:<u></u><u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">Dear Julie Hedlund and WT5 colleagues:<u></u><u></u></p>
<p class="MsoNormal">Thankyou for these notes.<u></u><u></u></p>
<p class="MsoNormal">1. Regarding protection of Geo-Names, please refer to point 2.2 of the paper dated 7 June, which I read into the record of the meeting.<br>
<br>
2. > Why is monitoring not possible for public entities, yet expected for everyone else?<u></u><u></u></p>
<p class="MsoNormal">2.1 It is not expected for 'everyone else'. I believe that it is mainly the trademark industry who finance professional monitoring. Their reaction against GDPR suggests that in
the past their monitoring has been conducted without respect for privacy laws, notably through WhoIs.<br>
<br>
2.2 There is no comparable, financed, legal industry that could monitor the new GTLD programme on behalf of all interested stakeholders, world wide. (Except, perhaps the ICANN staff). Which is why under point 2.4 of the 7 June paper, we have the case for preventive
('a priori') rights, rather than curative ('ex-post') rights.<u></u><u></u></p>
<p class="MsoNormal">Regards<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">CW<u></u><u></u></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="margin-bottom:12.0pt">El 13 de junio de 2018 a las 8:09 Julie Hedlund <<a href="mailto:julie.hedlund@icann.org" target="_blank">julie.hedlund@icann.org</a>> escribió:<u></u><u></u></p>
<div>
<p class="m_7141110391985474078ox-9056d36b86-msoplaintext"><span style="font-size:12.0pt">Dear Work Track 5 members,</span><u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><u></u><u></u></p>
</div>
<p class="m_7141110391985474078ox-9056d36b86-msoplaintext"><span style="font-size:12.0pt">Please see below the action items and notes from the meeting today (13 June). <em><span style="font-family:"Calibri",sans-serif">These high-level notes are designed to help WG members navigate
through the content of the call and are not a substitute for the recording, transcript, or the chat, which will be posted on the wiki.</span></em>
</span><u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><u></u><u></u></p>
</div>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">See also the slides posted on the wiki above, as well as the Working Document.</span><u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><u></u><u></u></p>
</div>
<p class="m_7141110391985474078ox-9056d36b86-msoplaintext"><span style="font-size:12.0pt">Kind regards,</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msoplaintext"><span style="font-size:12.0pt">Julie</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msoplaintext"><span style="font-size:12.0pt">Julie Hedlund, Policy Director</span><u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><u></u><u></u></p>
</div>
<p class="m_7141110391985474078ox-9056d36b86-msoplaintext"><span style="font-size:12.0pt">------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>----------</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msoplaintext"><strong><span style="font-size:12.0pt;font-family:"Calibri",sans-serif">Notes/Action Items:</span></strong><u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><u></u><u></u></p>
</div>
<p class="m_7141110391985474078ox-9056d36b86-msoplaintext"><strong><span style="font-size:12.0pt;font-family:"Calibri",sans-serif">Action Items:</span></strong><span style="font-size:12.0pt">
</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msoplaintext"><span style="font-size:12.0pt">-- WT5 members should review and comment on the collaborative working document (google document, and attached).</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msoplaintext">-- Staff will ask on the list who might be traveling during next week’s meeting (1400 UTC, 20 June).<u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><u></u><u></u></p>
</div>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><strong><span style="font-size:12.0pt;font-family:"Calibri",sans-serif">Notes:</span></strong><u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><u></u><u></u></p>
</div>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">1. Welcome/Agenda Review/SOI Review: No SOI updates</span><u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><u></u><u></u></p>
</div>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">2. Capital City Names
</span><u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><u></u><u></u></p>
</div>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- Coming back to this so we can see where we stand.</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- In 2012 they were restricted because they required a letter of support or non-objection.</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- Some downsides to how that worked because sometimes it was hard to find the authority.</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- Careful to not talk about "cities" because the notion of cities brings in how big, how small, what are we going to do with it, etc.</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- Viewing capital cities as unique and exceptional could see that as a category that should remain as it was.</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- The WT found some convergence on the idea of not abandoning the current treatment of Capital Cities”.</span><u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><u></u><u></u></p>
</div>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">3. Non-Capital Cities
</span><u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><u></u><u></u></p>
</div>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- Diverging opinions: Some would say no controls and some would say additional controls over what was in 2012.</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- Some have suggested a quantitative measure around the size of population.</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- Broader than just capital city name, so possibility to match a generic or branded term.</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- Looking for ideas of how to navigate the different opinions and how to improve the next application round.</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- If we want to reach a solution for everyone for city names we should try to look into a requirement that would help meet all the different interests at stake.</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- Monitoring is not workable for all authorities.</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- Need guidance of what is or what is not a city.</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- Need guidance on how to treat intended use, etc.</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- Try to define the requirements and see if there is a package that would cover everything.</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- Let's see if we can make a distinction between pre-emptive conditions going into a process which discounts potential applications/applicants and then conditions in an evaluation process.
I don't think any one is arguing for open slather. I think we're looking for clarity in an open process and then sensible measures to evaluate applications.</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- On cities I feel we could work on parameters or requirements that would serve to meet all the different interests at stake, e.g. having clarity/predictability on what is a city, on the need
of prior/early contact between all interested parties, possible means of resolving "conflicts", etc.</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- How should we take into account that many cities have been out there for much longer than brands and quite some brand names derived from a city name (rather than the opposite)?</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">--W hy is monitoring not possible for public entities, yet expected for everyone else?</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- Look at the issues where you have an applicant that is related to the city as a city, and another that wants to use it for purposes not related to the city as a city. Contrast that to an
applicant who wants to use it for unrelated geographic reasons, and then one not related to the city authority.</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- Public interest commitment -- no applying to use it for a geographic use, so wouldn't need the letter of non-objection, but then used it for a geographic purpose, that would be against the
intent.</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- Divide the analysis into three parts 1) control and compliance; 2) objection and contention process -- objection to an applicant and contention sets; 3) control in providing potential applicants
about the types of names and the warnings, that would go into an evaluation process.</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- It may mean that we need to look at contractual restrictions to address concerns.</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- There are different areas of control that can be applied.</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- Part of a solution could be to restore the different interests in a way that is agreeable to everyone, but first acknowledge that there are different interest at stake.</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- Then define the parameters for the requirements for each interest group.</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- The purpose of the process flow was to look at the different areas of processing and note that there are different ways to solve issues.</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- Different ways to protect are not mutually exclusive.</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- Documents current protections, but doesn't document those that could match a geographic term but is applied for in a geographic way -- even where that intent wasn't stated.</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- Think about how to deal with time frame A, B, and C. Identity who are the actors impacted in each of those time frames. Each of these are very different. Here are the three parts again...A)
application B) evaluation C) compliance...we could do a little flow chart on this and we will rapidly see where we have agreement...</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- Look at something different from the process flow in 2012 -- come up with something for the next call where the pressure points are for particular stakeholders at particular points in time.</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- In the attribution to one party of a unique resource the key is at the start of the process (requirements) - later phases (objections/control) are just curative measures, which only will be
helpful if the requirements have made sure that all interested parties have had a fair say in the requirements phase.</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- Look at the different parts of the process in the process flow and build agreement in the Work Track -- such as basis of protection and how it applies to different terms, which require support
or non-objections, challenge mechanisms, etc.</span><u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><u></u><u></u></p>
</div>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">4. ICANN62 Planning:
</span><u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><u></u><u></u></p>
</div>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- Check the schedule online. There is remote participation.</span><u></u><u></u></p>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">-- Planning the activities for each session.</span><u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><u></u><u></u></p>
</div>
<p class="m_7141110391985474078ox-9056d36b86-msonormal"><span style="font-size:12.0pt">5. AOB: Staff will send an email to the list to see who might be traveling next week.
</span><u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><u></u><u></u></p>
</div>
</div>
</blockquote>
<p class="MsoNormal"><br>
<u></u><u></u></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">______________________________<wbr>_________________<br>
Gnso-newgtld-wg-wt5 mailing list<br>
<a href="mailto:Gnso-newgtld-wg-wt5@icann.org" target="_blank">Gnso-newgtld-wg-wt5@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-newgtld-wg-wt5</a><u></u><u></u></p>
</blockquote>
</div>
<p class="MsoNormal">______________________________<wbr>_________________<br>
Gnso-newgtld-wg-wt5 mailing list<br>
<a href="mailto:Gnso-newgtld-wg-wt5@icann.org" target="_blank">Gnso-newgtld-wg-wt5@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-newgtld-wg-wt5</a><u></u><u></u></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div></div></div>
</div>
<br>______________________________<wbr>_________________<br>
Gnso-newgtld-wg-wt5 mailing list<br>
<a href="mailto:Gnso-newgtld-wg-wt5@icann.org">Gnso-newgtld-wg-wt5@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-newgtld-wg-wt5</a><br></blockquote></div><br></div>