[NCSG-PC] Review NCSG Comment on KSK Rollover Draft

Ayden Férdeline icann at ferdeline.com
Sat Mar 24 23:10:16 EET 2018


Hi all,

Thanks to those who drafted this.

From what I understand, delaying the now overdue KSK rollover yet again would increase the risk of key compromise. Security best practices suggest that ICANN should rollover the key on a regular basis. Are there any dangers to us supporting another postponement?

I think our recommendation that the publication of a "monthly trust anchor report will give those Internet users who identify their local operators as “not ready” an opportunity to reach out to them directly prior to the root KSK rollover date" is far-fetched. I doubt any end-users will read it and take action. I believe the onus should be on ICANN (and possibly the GAC) to reach out to local operators who are not ready...

Best wishes,

Ayden

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On 21 March 2018 6:28 PM, Rafik Dammak <rafik.dammak at gmail.com> wrote:

> Hi all,
>
> A draft we have to review for endorsment  asap,  the deadline for submission is the 2nd April.
>
> Best,
>
> Rafik
>
> ---------- Forwarded message ---------
> From: Louise Marie Hurel <louise.marie.hsd at gmail.com>
> Date: Thu, Mar 22, 2018, 3:23 AM
> Subject: [Public Comments] NCSG Comment on KSK Rollover Draft
> To: <NCSG-DISCUSS at listserv.syr.edu>
> Cc: Tomslin Samme-Nlar <mesumbeslin at gmail.com>, Dina Solveig Jalkanen <icann at thomascovenant.org>, Rafik Dammak <rafik.dammak at gmail.com>
>
> Hi all,
>
> Comments on the Plan to Restart the Root Key Signing Key (KSK) Rollover Process opened early February [this year](https://www.icann.org/public-comments/ksk-rollover-restart-2018-02-01-en). For those who have not been following the process that closely, KSK serves as a trust anchor for DNSSEC and was last (and for the first time) signed in 2010. ICANN had scheduled to implement a new key in October. However, they decided to postpone the signing of new cryptographic keys for the DNS after finding that the resolvers used by ISPs and network operators were still not ready and there's a need for more data in prepping for it.
>
> While the comment is narrow and highly technical in its scope, the overall idea of the process can be read as taking the next step in consolidating a way of periodically changing keys -- thus enhancing security and resilience in the DNS.
>
> Tomslin, Dina and I have worked on [this draft](https://docs.google.com/document/d/1VNxn4UJlk8z196Kz56ucAdgyWp0ua9NmdHexRE1Wkhc/edit) and would be happy to get more comments edits, suggestions on this. Feel free to jump in.
>
> For more info, see [here](https://www.icann.org/news/announcement-2017-09-27-en) and [here](https://www.icann.org/en/system/files/files/plan-continuing-root-ksk-rollover-01feb18-en.pdf).
>
> All the best,
>
> Louise Marie Hurel
>
> Cybersecurity Project Coordinator | Igarapé Institute
>
> London School of Economics (LSE) Media and Communications (Data and Society)
>
> Skype: louise.dias
> +44 (0) 7468 906327
> l.h.dias at lse.ac.uk
> louise.marie.hsd at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20180324/85567292/attachment.html>


More information about the NCSG-PC mailing list