<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Apr 5, 2019, 12:10 AM Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com">seun.ojedeji@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div dir="auto">Hello Carlton,<div dir="auto"><br></div><div dir="auto">I hear you loud and clear, but if we are being realistic, I think the level of representation that exist within the ePDP may be a factor on how far one can push these things.</div></div></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">We need to say what needs to be said irrespective of perceptions of limitations.</div><div dir="auto"><br></div><div dir="auto">Sivasubramanian M</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div dir="auto"><div dir="auto"> I have heard a couple of times that the numbers don't matter but how loud we "constructively" <span style="font-family:sans-serif">scream</span>, well within ICANN, that's probably nothing more than a good motivational speech.</div><div dir="auto"><br></div><div dir="auto">Attempts has been made to get this through via the ePDP without luck and since ALAC practically has a milk teeth on ePDP, I don't think it will be out of order to utilize that which we've always been reminded of as being our role, which is to advice; hopefully there are still some permanent teeth left in there.</div><div dir="auto"><br>Regards<br><div data-smartmail="gmail_signature" dir="auto">Sent from my mobile<br>Kindly excuse brevity and typos</div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 4 Apr 2019, 17:54 Carlton Samuels, <<a href="mailto:carlton.samuels@gmail.com" rel="noreferrer noreferrer" target="_blank">carlton.samuels@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">Thick WHOIS made sense back then - and some of us were savaged for taking that position! - and still does today, if only because if every GTLD operator has the same obligations it is easier to check compliance. <div dir="auto"><br></div><div dir="auto">The distinction between legal and natural persons and why that would matter is, um, well, I am loathe to commit 2 more brain cells to that argument. </div><div dir="auto"><br></div><div dir="auto">The wave and momentum of national data privacy law and regulations is tacking the EU way. So in the final analysis a geographic distinction has no long term value.</div><div dir="auto"><br></div><div dir="auto">Do we have a new solution to offer anywhere? </div><div dir="auto"><br></div><div dir="auto">And why does this 'advise the Board request/require' sound so much like we got popped in the mouth in the schoolyard and ran to teacher for justice?</div><div dir="auto"><br></div><div dir="auto">A better posture is to make the arguments we favour sharper and put them on the wire for the WG to see. </div><div dir="auto"><br></div><div dir="auto">Orchestrate and manufacture consent!</div><div dir="auto"><br></div><div dir="auto">Carlton.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 3 Apr 2019, 8:59 am Alan Greenberg, <<a href="mailto:alan.greenberg@mcgill.ca" rel="noreferrer noreferrer noreferrer" target="_blank">alan.greenberg@mcgill.ca</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
Please find attached a draft of the ALAC Advice to the Board related to the EPDP.<br>
<br>
Note that the highlighting (inadvertantly missing in the third case) gives two alternative pheasings to be discussed.<br>
<br>
Hadia has reviewed it and supports it.<br>
<br>
Alan<br>
-- <br>
Sent from my mobile. Please excuse brevity and typos.
</div>
_______________________________________________<br>
CPWG mailing list<br>
<a href="mailto:CPWG@icann.org" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">CPWG@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cpwg" rel="noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/cpwg</a><br>
_______________________________________________<br>
registration-issues-wg mailing list<br>
<a href="mailto:registration-issues-wg@atlarge-lists.icann.org" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">registration-issues-wg@atlarge-lists.icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/registration-issues-wg" rel="noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/registration-issues-wg</a><br>
</blockquote></div>
_______________________________________________<br>
CPWG mailing list<br>
<a href="mailto:CPWG@icann.org" rel="noreferrer noreferrer noreferrer" target="_blank">CPWG@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cpwg" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/cpwg</a><br>
</blockquote></div></div>
_______________________________________________<br>
CPWG mailing list<br>
<a href="mailto:CPWG@icann.org" target="_blank" rel="noreferrer">CPWG@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cpwg" rel="noreferrer noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/cpwg</a><br>
_______________________________________________<br>
registration-issues-wg mailing list<br>
<a href="mailto:registration-issues-wg@atlarge-lists.icann.org" target="_blank" rel="noreferrer">registration-issues-wg@atlarge-lists.icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/registration-issues-wg" rel="noreferrer noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/registration-issues-wg</a><br>
</blockquote></div></div></div>