<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hello advisors. I spend a lot of time reading stuff that comes
out of ICANN or is about what is happening at ICANN, but I rarely
find anything that sums up some of the major issues currently at
play in that forum in a somewhat accessible way. I thought this
article was worth circulating. I hope it might spark some interest
in some of the battles that are being waged under the radar of
most internet end-users, the results of which will somehow, affect
all of us eventually.</p>
<p><i>ICANN at a crossroads: GDPR and Human Rights</i><i><br>
</i></p>
<p style="margin: 0px; padding: 0px 0px 1em; border: 0px;
line-height: 24px; color: rgb(0, 0, 0); font-family: Helvetica,
Arial, sans-serif; font-size: 16px; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: 400; letter-spacing: normal; orphans: 2; text-align:
start; text-indent: 0px; text-transform: none; white-space:
normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width:
0px; background-color: rgb(255, 255, 255); text-decoration-style:
initial; text-decoration-color: initial;"><i>All internet users
have dealings with the Internet Corporation for Assigned Names
and Numbers, yet the vast majority have never heard of ICANN.
Responsible for deciding how the Domain Name System (DNS) is
run, ICANN may be a technical standard-setting body, but its
policies and activities acquire political nuances more often
than not. At its core, there is a distinction between ICANN the
organisation, incorporated in California, and the ICANN
community, a multistakeholder group of volunteers who develop
the policies that are subsequently implemented by the
organisation.</i></p>
<p style="margin: 0px; padding: 0px 0px 1em; border: 0px;
line-height: 24px; color: rgb(0, 0, 0); font-family: Helvetica,
Arial, sans-serif; font-size: 16px; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: 400; letter-spacing: normal; orphans: 2; text-align:
start; text-indent: 0px; text-transform: none; white-space:
normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width:
0px; background-color: rgb(255, 255, 255); text-decoration-style:
initial; text-decoration-color: initial;"><i>Fifteen years ago,
and only a few years after ICANN was established, European data
protection regulators had already</i><i><span> </span></i><i><a
href="http://ec.europa.eu/justice/article-29/documentation/opinion-recommendation/files/2003/wp76_en.pdf"
style="outline: none; text-decoration: none; color: rgb(102,
51, 102); border-bottom: 1px solid rgb(187, 187, 187);">spotted
the flaws</a></i><i><span> </span></i><i>with ICANN's WHOIS
service, a public database of registrants' contact details. At
the end of 2017, mere months before European General Data
Protection Regulation (GDPR) came into effect, ICANN had yet to
devise a plan to make its WHOIS registrant database compliant.
However, this is no longer the era of paltry fines for violating
data protection laws, when compliance was at best facultative.</i></p>
<p>Read more at: <a moz-do-not-send="true"
href="http://www.circleid.com/posts/20180719_icann_at_a_crossroads_gdpr_and_human_rights/"><font
face="Times New Roman, Times, serif">http://www.circleid.com/posts/20180719_icann_at_a_crossroads_gdpr_and_human_rights/</font></a></p>
<p><font face="Times New Roman, Times, serif">Marita<br>
</font></p>
<p><font face="Times New Roman, Times, serif"></font><br>
</p>
</body>
</html>