ICANN is neither Star Trek’s Starship Enterprise nor Nanny ICANN. In response to Stephanie’s questions here are short comments. For RDS ICANN is not going where nobody has gone before and it is not some sort of global Internet Nanny. ICANN should restrict itself to the minimum dataset it needs to conduct its business with Registries and Registrars within it DNS Remit. Full Stop!
Agreed regarding the restriction to a minimum data set.
Let Registries and Registrars deal with the “how to authenticate law enforcement requests” at the national and multilateral level. ICANN can, in the public interest, advise one and all on best policy there but it cannot weld an authentication process into its contracts. Within its remit ICANN has no right to do so. One might suspect that the Registries and Registrars are trying to off load onto ICANN work they should be sorting out among themselves, both nationally and multilaterally. That is how the rest of the world does it. There seems to be a tendency toward ICANN exceptionalism here. What ICANN does is important but it is not exceptional, it is business in the public interest. How it does it is exceptional: consensus policy (within the REMIT) based on a multistakeholder process.
I disagree that the problem of how to authenticate law enforcement requests should be dumped at the doorstep of contracted parties. The policy must be complete and give structure to this issue.
Lastly, and this is important, this process is not about fixing something that is broken. Much of what works badly is actually at the national and multilateral level and outside ICANN’s remit in any event. At best the goal here is to improve a process, but there is no urgency. The work can be tiring but in the absence of urgency the rational decision is to slow the process down, to make it less burdensome and not result in hasty rash bad decisions.
Agreed that ICANN should not solve the problem of international law enforcement information requests and jurisdictional issues. These should be left to the governmental level. If governments want to improve how these existing systems work, they can do so by means of multi-lateral agreements, not by influencing ICANN policy.
Sam L. NPOC/CSIH
_______________________________________________ gnso-rds-pdp-wg mailing list gnso-rds-pdp-wg@icann.org https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
-- Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung. Mit freundlichen Grüßen, Volker A. Greimann - Rechtsabteilung - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann@key-systems.net Web: www.key-systems.net / www.RRPproxy.net www.domaindiscount24.com / www.BrandShelter.com Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook: www.facebook.com/KeySystems www.twitter.com/key_systems Geschäftsführer: Alexander Siffrin Handelsregister Nr.: HR B 18835 - Saarbruecken Umsatzsteuer ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen. -------------------------------------------- Should you have any further questions, please do not hesitate to contact us. Best regards, Volker A. Greimann - legal department - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann@key-systems.net Web: www.key-systems.net / www.RRPproxy.net www.domaindiscount24.com / www.BrandShelter.com Follow us on Twitter or join our fan community on Facebook and stay updated: www.facebook.com/KeySystems www.twitter.com/key_systems CEO: Alexander Siffrin Registration No.: HR B 18835 - Saarbruecken V.A.T. ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone.