[NCAP-Discuss] ICANN’s thoughts on controlled interruption

Justine Chew justine.chew.icann at gmail.com
Sat Feb 12 03:40:03 UTC 2022


Hi Heather,

Thanks for this.

I'd like to ask please, in your review of reports, advisories etc relevant
to Controlled Interruptions and Enhanced Controlled Interruptions, did you
come across any explanations (preferably not exclusively in technical
language) of the privacy and legal risks associated with the honeypot
approach? Might this have been highlighted in SAC 062 (although I didn't
quite spot any in a quick scan of this), or perhaps in SAC 066 and/or the
JAS report?

Thanks in advance for the assist,

Justine

On Fri, 11 Feb 2022 at 05:52, Heather Flanagan <
hlf at sphericalcowconsulting.com> wrote:

> In the chat of yesterday’s call, Ruben wanted to know why ICANN had
> decided against Enhanced Controlled Interruption in the past. The
> information I was thinking of is in their Name Collision Framework from
> July 2014:
>
> "ICANN is interested in maintaining the reliability, security and
> stability of the DNS and the Internet.
> As such, ICANN is interested in providing a good notification measure for
> those parties that may be
> leaking queries intended for private namespaces to the public DNS.
> However, ICANN is also aware of
> the privacy and legal risks associated with the honeypot approach
> described in SAC 062 and 066 and
> the JAS report. ICANN has decided on balancing the good notification
> features  offered by  using  the
> loopback address option with its superior privacy protection vs. the use
> of a honeypot. "
>
>
> https://www.icann.org/en/system/files/files/name-collision-framework-30jul14-en.pdf
>
>
> I think the text will need to be clear in our recommendations why the
> discussion group thinks this decision by ICANN must be revisted by the
> Board.
>
> Heather Flanagan
> Spherical Cow Consulting
> <http://linkedin.com/in/hlflanagan/> <http://twitter.com/sphcow>
>
>
>
>   Translator of Geek to Human
>   hlf at sphericalcowconsulting.com
>
>
>
>> _______________________________________________
> NCAP-Discuss mailing list
> NCAP-Discuss at icann.org
> https://mm.icann.org/mailman/listinfo/ncap-discuss
>
> _______________________________________________
> By submitting your personal data, you consent to the processing of your
> personal data for purposes of subscribing to this mailing list accordance
> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and
> the website Terms of Service (https://www.icann.org/privacy/tos). You can
> visit the Mailman link above to change your membership status or
> configuration, including unsubscribing, setting digest-style delivery or
> disabling delivery altogether (e.g., for a vacation), and so on.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/ncap-discuss/attachments/20220212/1a493361/attachment.html>


More information about the NCAP-Discuss mailing list