Hi Board Readiness Small Team,
Sorry this was not meant for the small team. Terri’s e-mail expanded to the small team list instead of her personal e-mail.
My bad. Please ignore or read if you are interested
😊.
Best,
Thomas
Von:
Thomas Rickert | rickert.law <thomas@rickert.law>
Datum: Dienstag, 29. Juli 2025 um 09:58
An: GNSO-Secs <gnso-secs@icann.org>, Caitlin Tubergen <caitlin.tubergen@icann.org>, Terri Agnew via Gnso-board-readiness-smallteam <gnso-board-readiness-smallteam@icann.org>
Betreff: LEA disclosure requests at the global level
Dear Caitlin and Terri, all,
Following up on our discussion in Prague Let me summarize how I think we can frame and advance the discussion in preparation for the August meeting.
ICANN and the issue of handling LEA disclosure requests at the global level.
When it comes to processing disclosure requests from law enforcement authorities (LEAs) there still seems to be a lot of confusion and different expectations by different parts of
the ICANN community with respect to process and outcome.
The topic was discussed in the EPDP, in related IRT (currently with respect to urgent requests) and in the RDRS Standing Committee. The issue is also relevant to work on DNS Abuse.
The two main areas of concern seem to be:
Whilst the community spent considerable time discussing LEA interaction, a structured analysis of the legal implications in particular and work on solutions has never occurred. However,
both questions need to be answered in order for the interactions between CPs and LEAs to work.
Even if there were a mechanism for authenticating LEAs (which does not currently exist), a distinction needs to be made between various scenarios. These are:
Depending on the case in question
So far, our discussion does not seem to have that level of nuance, but it appears that it not possible to use an approach that works at the global level.
The risk for ICANN and its community
ICANN can produce policies that are binding for the CPs. However, in order for LEA interaction to work at the global level, measures need to be taken by LEAs and governments, but
these cannot be obliged by ICANN to act.
Not only does the ICANN community need LEA’s / governments’ support with an authentication regime for LEAs, but it may also be the case that the legal instruments that currently
exist do not allow for an efficient collaboration between LEAs and CPs at the global level.
If this issue is not flagged and worked on, we as the GNSO Council, will allow for a perception within and outside our community to be solidified that the GNSO and ICANN is not able
to come to workable solutions to this issue, that the multistakeholder approach is now effective and that CPs are not willing to cooperate with LEAs.
A constructive way forward
The GNSO Council should take the initiative and invite the GAC / PSWG and the ICANN Board to a meeting or a series of meetings to flag the issue and manage expectations. If other
fora should be used or the discussion should be triggered differently, we should discuss these.
We should highlight that ICANN cannot task third-parties, but that third-party support is needed. We should emphasize that ICANN and its community will continue to work on framework
and technical solution that can facilitate the match-making between LEAs and CPs, but that we need to base this on a thorough analysis of the legal implications for CPs and ICANN taking into account the risks of unlawful disclosure for registrants.
Best,
Thomas