<div dir="auto"><div dir="auto">Hi Niels, </div><div dir="auto">Below is a practical example.</div><div dir="auto"><br></div><a href="http://www.itrealms.com.ng/2016/09/no-privacy-breach-in-votersng-says.html?m=1">http://www.itrealms.com.ng/2016/09/no-privacy-breach-in-votersng-says.html?m=1</a><div dir="auto"><br></div><div dir="auto">It may interest you that when the news broke in Nigeria there was a lot of tension in the air especially concerning the data privacy protection if over 120m but because we have to investigate the WHOIS details and got hold of the purported owners and do the relevant profiling to ensure that the contact is actually the owner of the domain name in question, it gives a kind of balanced diet.</div><div dir="auto">As far as we are concerned the WHOIS was very helpful. This is just one of many cases, especially when the petitioner was alleging denial of its request based on the Freedom of Information Act.</div><div dir="auto">Looking at the domain/content thereof, one should have thought may be its owned or must be domicile within govt agencies.</div><div dir="auto">Secondly the name of the organisation does not have any relationship with the project. These were some of the initial doubts that were overcame with the aid of WHOIS in the process of balancing the act and exploring the contact details.</div><div dir="auto">I hope this helps.</div><div dir="auto">Remmy</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 6 Jul 2017 13:04, "Niels ten Oever" <<a href="mailto:lists@digitaldissidents.org">lists@digitaldissidents.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Remmy,<br>
<br>
Is this an absract or a concrete example?<br>
<br>
Is this a criminal inquiry run by authorities? And how does the PII help<br>
determine whether it is for 'public good/fraud purposes'?<br>
<br>
Best,<br>
<br>
Niels<br>
<br>
On 07/06/2017 12:18 PM, Remmy Nweke wrote:<br>
> Hi Niels<br>
> In the cause of media activism for instance it's VIP to have a trusted<br>
> repository to be used for verifications especially on event where a<br>
> domain is not used for public good/fraud purposes at times it's crucial<br>
> to do under the roof verification to ascertain those behind such and<br>
> link that up with possible profiling of such individuals or organisation<br>
> as the case may be in exposing such crimes or incidents.<br>
> Hope this helps.<br>
><br>
> On 6 Jul 2017 09:54, "Niels ten Oever" <<a href="mailto:lists@digitaldissidents.org">lists@digitaldissidents.org</a><br>
> <mailto:<a href="mailto:lists@digitaldissidents.org">lists@<wbr>digitaldissidents.org</a>>> wrote:<br>
><br>
> Can you give examples? I find that in important cases, WHOIS data is<br>
> always wrong, or data on sites is more reliable.<br>
><br>
> Cheers,<br>
><br>
> Niels<br>
><br>
> On 07/06/2017 10:32 AM, Remmy Nweke wrote:<br>
> > Hi Ayden<br>
> > I think WHOIS has been very useful especially in the area of cyber<br>
> > rights advocacy/media rights activism by ensuring and helping to<br>
> resolve<br>
> > domain related use and misuse or even on conflict claims, it's VIP to<br>
> > know who precisely is the owners and names behind the domains and<br>
> > attempt to know why and for what purpose such domains were meant<br>
> for at<br>
> > least for putting the records straight and eventual profiling.<br>
> > Regards<br>
> > Remmy<br>
> ><br>
> > On 4 Jul 2017 11:37, "Ayden Férdeline" <<a href="mailto:icann@ferdeline.com">icann@ferdeline.com</a><br>
> <mailto:<a href="mailto:icann@ferdeline.com">icann@ferdeline.com</a>><br>
> > <mailto:<a href="mailto:icann@ferdeline.com">icann@ferdeline.com</a> <mailto:<a href="mailto:icann@ferdeline.com">icann@ferdeline.com</a>>>> wrote:<br>
> ><br>
> > Greetings, all-<br>
> ><br>
> > Along with Stephanie Perrin and Wendy Seltzer, I am a part of the<br>
> > ICANN GDPR Compliance Consultation Group. This group has been<br>
> formed<br>
> > to help ICANN gather the information it needs to engage with data<br>
> > protection authorities and to obtain actionable legal advice.<br>
> ><br>
> > I committed last week to keeping the NCSG updated on the<br>
> activities<br>
> > of the Consultation Group over the coming months.<br>
> ><br>
> > In our first meeting, we committed to participating in a data<br>
> > gathering exercise to identify the existing users of WHOIS, what<br>
> > data elements they use, and for what purpose. At this time we are<br>
> > not making the determination as to whether a purpose is legitimate<br>
> > or illegitimate, though that call will come, or if a data element<br>
> > comprises personally identifiable information. For now we are<br>
> simply<br>
> > trying to include all user categories to get the most complete set<br>
> > of data points.<br>
> ><br>
> > We are interested in understanding how non-commercial Internet<br>
> > users, who we in the NCSG purport to represent the interests<br>
> of, use<br>
> > WHOIS. We have conducted some informal consultation among our<br>
> peers<br>
> > and have been provided with a few use cases, but not too many.<br>
> It is<br>
> > possible that end users do not use WHOIS widely [and that has been<br>
> > the assumption that has informed previous exercises like this<br>
> one],<br>
> > but if you, as an end user, do use WHOIS, we would be curious to<br>
> > know for what purpose and which data elements you rely on. Please<br>
> > share your thoughts either on-list or with me privately, if<br>
> you prefer.<br>
> ><br>
> > We have a very short turnaround time for this exercise. Our next<br>
> > call is this Thursday, and ICANN staff envision this entire task<br>
> > being completed by next week. The time for you to provide input is<br>
> > thus now. Thanks!<br>
> ><br>
> > Best wishes,<br>
> ><br>
> > Ayden Férdeline<br>
> > <a href="http://linkedin.com/in/ferdeline" rel="noreferrer" target="_blank">linkedin.com/in/ferdeline</a> <<a href="http://linkedin.com/in/ferdeline" rel="noreferrer" target="_blank">http://linkedin.com/in/<wbr>ferdeline</a>><br>
> <<a href="http://www.linkedin.com/in/ferdeline" rel="noreferrer" target="_blank">http://www.linkedin.com/in/<wbr>ferdeline</a><br>
> <<a href="http://www.linkedin.com/in/ferdeline" rel="noreferrer" target="_blank">http://www.linkedin.com/in/<wbr>ferdeline</a>>><br>
> ><br>
> ><br>
><br>
> --<br>
> Niels ten Oever<br>
> Head of Digital<br>
><br>
> Article 19<br>
> <a href="http://www.article19.org" rel="noreferrer" target="_blank">www.article19.org</a> <<a href="http://www.article19.org" rel="noreferrer" target="_blank">http://www.article19.org</a>><br>
><br>
> PGP fingerprint 8D9F C567 BEE4 A431 56C4<br>
> 678B 08B5 A0F2 636D 68E9<br>
><br>
><br>
<br>
--<br>
Niels ten Oever<br>
Head of Digital<br>
<br>
Article 19<br>
<a href="http://www.article19.org" rel="noreferrer" target="_blank">www.article19.org</a><br>
<br>
PGP fingerprint 8D9F C567 BEE4 A431 56C4<br>
678B 08B5 A0F2 636D 68E9<br>
</blockquote></div></div>