On 1/25/19 3:28 PM, John R Levine wrote: >> The final decision on this is planned to be made in April: >> >> https://community.icann.org/pages/viewpage.action?pageId=88574682&preview=/88574682/102142026/EPDP_summary_timeline_20190116.pdf > > Not that it's relevant here, but I am a member of the ICANN SSAC subcommittee > that supports the SSAC reps on the EPDP group, and I talk to them about its > progress or lack thereof several times a week. I think it's fair to assume > that I know at least as much about what it's doing as anyone else here.
I do not doubt anything of this. Would you agree that the decision of the EPDP impacts how RDAP reverse search should be developed and implemented? > I was also a member of the IAOC when we figured out what the IETF needed to > do to be GDPR compliant (not much.) > Because the IETF does not implement the protocols or holds the data. But if the IETF produces protocols which are non-GDPR compliant upon implementation, and are violating human rights, that is imho not something we should want. Best, Niels > But once again, the IETF is not ICANN, working groups are not GDPR data > controllers, nor are we GDPR data processors. This entire argument is a > waste of everyone's time. > > Regards, > John Levine, jo...@taugh.com, Taughannock Networks, Trumansburg NY > Please consider the environment before reading this e-mail. https://jl.ly -- Niels ten Oever Researcher and PhD Candidate Datactive Research Group University of Amsterdam PGP fingerprint 2458 0B70 5C4A FD8A 9488 643A 0ED8 3F3A 468A C8B3 _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
