<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><meta http-equiv="Content-Type" content="text/html; charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Really helpful Marita, thank you.<div class=""><br class=""></div><div class="">James</div><div class=""><br class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">On Jul 2, 2020, at 12:31 PM, Marita Moll <<a href="mailto:mmoll@ca.inter.net" class="">mmoll@ca.inter.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" class="">
<div class=""><p class=""><font face="Times New Roman, Times, serif" class="">Thanks Darlene for
weighing in. I am sure people are thinking "what on earth could
they be talking about all night???" In response to that I am
attaching a file on At Large talking points for this meeting --
i.e. these were the issues we were concentrating on in
discussions either in plenaries or with other specific
constituencies like the Government Advisory Committee, the ICANN
Board, the Non-Commercial Stakeholders Group, etc. <br class="">
</font></p><p class=""><font face="Times New Roman, Times, serif" class="">This PDF is not that
user friendly and (sadly) the links don't work. It has been an
issue for years that there is a great need for documents that
are accessible to any person in the general public who might
want to know what goes on at ICANN meetings. We are not there
yet, so here is my little attempt to demystify things. <br class="">
</font></p><p class=""><font face="Times New Roman, Times, serif" class="">In summary, At Large
concentrated on 5 topics:</font></p><p class=""><font face="Times New Roman, Times, serif" class="">1. DNS Abuse -- this
is an attempt to get <a href="http://icann.org/" class="">ICANN.org</a> to take more responsibility for
abusive practices like pharming, phishing, botnets, etc. that
circulate on the web by tightening up contracts and contract
enforcement. Seems like a no brainer. But when it comes to
relationships between the contracted parties, ICANN, end-users
and others -- everyone has a different version of the problem
and how to fix it.</font></p><p class=""><font face="Times New Roman, Times, serif" class="">2. Privacy and data
protection -- this is in response to the European General Data
Protection Rules (GDPR) concerning the release of data about who
owns and/or is responsible for domain names in the European
context. It is a tug of war between the need to protect
individual privacy and the need to make sure bad actors can be
identified quickly and dealt with. I have not been deeply
involved in this discussion -- came to it a bit late. But I can
tell you, it is a very fraught discussion that seems intractable
as there are hardliners on both sides.</font></p><p class=""><font face="Times New Roman, Times, serif" class="">3. Subsequent
procedures -- this is an awkward name for a very complex
negotiation going on to reset the rules that would allow ICANN
to begin another round of selling top level domain names -- i.e.
that string after the last dot. -- .books, .hotels, etc. I am
involved in this discussion in trying to make it easier for some
of these opportunities to be taken up by communities of various
kinds -- e.g. indigenous, various minorities, language groups,
smaller clusters of interest, etc. -- who don't have the deep
pockets of commercial applicants. these is a community support
program and a community priority evaluation process but they did
not really work the last time around. This discussion also
includes the contentious geonames issue.</font></p><p class=""><font face="Times New Roman, Times, serif" class="">4. Registry voluntary
commitments (formerly called Public Interest Commitments) --
sometimes, an applicant for a top level domain name offers
public benefits in return for being assigned the name. Best
example I have of this is the fact that the .amazon issue was
finally resolved with <a href="http://amazon.org/" class="">amazon.org</a> offering concessions to the
people of the amazon region with respect to the use of second
level domains, local languages, etc. The issue here is around
the enforceability of these commitments. <br class="">
</font></p><p class=""><font face="Times New Roman, Times, serif" class="">5. Universal
Acceptance -- You can have a domain name in non-latin characters
but 80% of websites are not set up to recognize them. This is an
awareness raising issue, not something that ICANN can resolve
except by supporting advocates around the world who try to
contact non-compliant websites. Because At Large is an end user
constituency, At Large members are best positioned to play this
role.</font></p><p class=""><font face="Times New Roman, Times, serif" class="">Hope this sheds some
light on some very protracted discussions. Progress on any of
these issues is as slow as "molasses in January." <br class="">
</font></p><p class=""><font face="Times New Roman, Times, serif" class="">Marita<br class="">
</font></p>
<div class="moz-cite-prefix">On 7/1/2020 10:23 AM, Darlene Thompson
wrote:<br class="">
</div>
<blockquote type="cite" cite="mid:CAAjE1KV4sM3wOy+Q9X5eaRmSzSAQ9j+hd=V49XtxZugOaCc-YQ@mail.gmail.com" class="">
<meta http-equiv="content-type" content="text/html; charset=UTF-8" class="">
<div dir="ltr" class="">I, too, think that TC should be part of this
process. If there is any way that I can help, just let me know.
<div class=""><br class="">
</div>
<div class="">Thank you for being the one staying up all night at an
ICANN meeting - been there, done that and came up looking like
something the cat dragged in!</div>
<div class=""><br class="">
</div>
<div class="">Darlene</div>
<div class=""><br class="">
</div>
</div>
<br class="">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sat, Jun 27, 2020 at 9:57
PM Marita Moll <<a href="mailto:mmoll@ca.inter.net" moz-do-not-send="true" class="">mmoll@ca.inter.net</a>> wrote:<br class="">
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello
advisors. Hope you are all well and managing your way through
this <br class="">
co-vid crisis. I have just finished a week of middle of the
night <br class="">
meetings at virtual ICANN68 -- Kuala Lumpar time zone. This is
the <br class="">
future of international meetings for some time to come, I'm
afraid. It <br class="">
is simply too dangerous to have such gatherings until a
reliable vaccine <br class="">
is found.<br class="">
<br class="">
Here is an opportunity for us to lend our voices to a national
campaign. <br class="">
Open Media has started a coalition to lobby for reliable high
speed <br class="">
access for all Canadians. Please take a look and let me know
if you <br class="">
think TC should be part of this coalition.<br class="">
<br class="">
<a href="https://action.openmedia.org/page/60429/petition/1?ea.tracking.id=vurl" rel="noreferrer" target="_blank" moz-do-not-send="true" class="">https://action.openmedia.org/page/60429/petition/1?ea.tracking.id=vurl</a><br class="">
<br class="">
I think it would be highly appropriate<br class="">
<br class="">
Marita<br class="">
<br class="">
_______________________________________________<br class="">
Advisors mailing list<br class="">
<a href="mailto:Advisors@tc.ca" target="_blank" moz-do-not-send="true" class="">Advisors@tc.ca</a><br class="">
<a href="http://victoria.tc.ca/mailman/listinfo/advisors" rel="noreferrer" target="_blank" moz-do-not-send="true" class="">http://victoria.tc.ca/mailman/listinfo/advisors</a><br class="">
</blockquote>
</div>
<br class="">
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Advisors mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Advisors@tc.ca">Advisors@tc.ca</a>
<a class="moz-txt-link-freetext" href="http://victoria.tc.ca/mailman/listinfo/advisors">http://victoria.tc.ca/mailman/listinfo/advisors</a>
</pre>
</blockquote>
</div>
</div></blockquote></div></div></div></body></html>