Il 25/01/2019 15:39, Niels ten Oever ha scritto:
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?
No because I don't believe that someone is thinking to an uncontrolled
implementation and, even if someone is so crazy to do that, he will be
responsible for that, not the capability. RDAP was born to overcome the
WHOIS limitations. The policies described in RFC7481 allow RDAP servers
to provide capabilities according the user profiles and there are a
number of operators legitimated (in terms of GDPR lawful bases) to use
RDAP reverse search.
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.
According to that view, WHOIS should have been stopped even before the
entry into force of GDPR and, after that time, also fully GDPR compliant
WHOIS implementations should have been switched off because other
non-GDPR compliant implementations were still running.
Can we distinguish between the technology and the use/misuse of the
technology ? If we don't make this distinction, why don't we shutdown
Internet ??
Anyway, a new version of the draft will be available soon. Hopefully,
this new version will fix the controversial points.
Regards,
mario
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
--
Dr. Mario Loffredo
Servizi Internet e Sviluppo Tecnologico
CNR - Istituto di Informatica e Telematica
via G. Moruzzi 1, I-56124 PISA, Italy
E-Mail: mario.loffr...@iit.cnr.it
Phone: +39.0503153497
Web: http://www.iit.cnr.it/mario.loffredo
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
