October 2018 - ksk-rollover

Informal meeting at IETF 103
by Paul Hoffman Nov. 11, 2018

Nov. 11, 2018

There will be an informal discussion of DNS root KSK futures at IETF 103 on Friday, November 9, at 0900 local (Bangkok) time in room Chitlada 3. The purpose is to allow IETF participants to ask questions and propose ideas for how the DNS root KSK should be maintained in the future. Suggestions from the mic lines at recent meeting include suggestions for fixed rollover schedules, suggestions for data collection before the next rollover, standby KSKs and how they would affect the rollover schedule, and how resolver software vendors' actions can be taken into account. The discussion is expected to last for one hour or less. Unfortunately, there is no remote participation for the Friday sessions, so the meeting will be limited to those in the room. However, I will make a recording to create notes on what is said. --Paul Hoffman

11 21

The Recent KSK Rollover: Summary and Next Steps
by Paul Hoffman Oct. 31, 2018

Oct. 31, 2018

Here's a blog post from today that summarizes what we saw and what happens next. No one on this list needs to follow the suggestion in the last paragraph and subscribe a second time. :-) https://www.icann.org/news/blog/the-recent-ksk-rollover-summary-and-next-st… --Paul Hoffman

2 1

First Root KSK Rollover Successfully Completed
by Edward Lewis Oct. 19, 2018

Oct. 19, 2018

LOS ANGELES – 15 October 2018 – The Internet Corporation for Assigned Names and Numbers (ICANN) has determined that the first-ever changing of the cryptographic key that helps protect the Domain Name System (DNS) has been completed with minimal disruption of the global Internet. It was the first time the key has been changed since it was first put in use in 2010. After evaluation of the available data, there does not appear to be a significant number of Internet end-users who have been persistently and negatively impacted by the changing of the key. The few issues that have arisen appear to have been quickly mitigated and none suggested a systemic failure that would approach the threshold (as defined by the ICANN community) to initiate a reversal of the roll. In that context, it appears the rollover to the new Key Signing Key, known as KSK 2017, has been a success. At this point, there are no indications it is necessary to back out of the rollover and ICANN will now proceed to the next step in the rollover process: revoking the old KSK, known as KSK 2010 during the next key ceremony in the first quarter of 2019. "This successful exercise of the infrastructure necessary to roll the root zone's key has demonstrated it is possible to update the key globally," said David Conrad, ICANN's Chief Technology Officer. "It also provided important insights that will help us with future key rolls," The final decision to roll the root zone Key Signing Key (KSK) was made by ICANN President and CEO Göran Marby after reviewing the outcomes of the efforts of ICANN and others, particularly in the Domain Name System (DNS) technical community. These outcomes were the result of significant global outreach efforts, in consultation with the ICANN community, and after extensive analysis of available data. With the final approvals in place, ICANN implemented the 16 September 2018 resolution of ICANN's Board. The resolution stated that the organization should proceed with its revised plans to change or "roll" the key for the DNS root on 11 October 2018. To learn more about the Root KSK Rollover, visit its dedicated webpage and primary source of information: http://www.icann.org/kskroll About ICANN ICANN's mission is to help ensure a stable, secure, and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world. https://www.icann.org/news/announcement-2018-10-15-en

13 15

Re: [ksk-rollover] 答复: First Root KSK Rollover Successfully Completed
by Edward Lewis Oct. 17, 2018

Oct. 17, 2018

In general, reason for any service outage would need explanation by the service provider. Service provisioning is so complicated (layers upon layers) that what's seen on the surface is hardly representative of what's inside. A rule from years of developing monitoring scripts: It's one thing to detect and measure symptoms, it's an entirely different thing to make a diagnosis. On 10/16/18, 11:50, "ksk-rollover on behalf of Davey Song(宋林健)" <ksk-rollover-bounces(a)icann.org on behalf of ljsong(a)biigroup.cn> wrote: I had several bounce mails today from my Gmail to IETF's mail. It's weird. The response from the remote server was: 550 5.7.1 mail w9G8HQ5a028992 from 2607:f8b0:4864:20::72a rejected by DCC The bounce may irrelevant with KSK. But an question came up to my mind that how can a user identify a failure caused by KSK rollover? Davey > -----邮件原件----- > 发件人: ksk-rollover [mailto:ksk-rollover-bounces@icann.org] 代表 Edward > Lewis > 发送时间: 2018年10月16日 0:08 > 收件人: ksk-rollover(a)icann.org > 主题: [ksk-rollover] First Root KSK Rollover Successfully Completed > > LOS ANGELES – 15 October 2018 – The Internet Corporation for Assigned > Names and Numbers (ICANN) has determined that the first-ever changing of > the cryptographic key that helps protect the Domain Name System (DNS) has > been completed with minimal disruption of the global Internet. It was the first > time the key has been changed since it was first put in use in 2010. > > After evaluation of the available data, there does not appear to be a significant > number of Internet end-users who have been persistently and negatively > impacted by the changing of the key. > > The few issues that have arisen appear to have been quickly mitigated and > none suggested a systemic failure that would approach the threshold (as > defined by the ICANN community) to initiate a reversal of the roll. In that > context, it appears the rollover to the new Key Signing Key, known as KSK 2017, > has been a success. > > At this point, there are no indications it is necessary to back out of the rollover > and ICANN will now proceed to the next step in the rollover process: revoking > the old KSK, known as KSK 2010 during the next key ceremony in the first > quarter of 2019. > > "This successful exercise of the infrastructure necessary to roll the root zone's > key has demonstrated it is possible to update the key globally," said David > Conrad, ICANN's Chief Technology Officer. "It also provided important insights > that will help us with future key rolls," > > The final decision to roll the root zone Key Signing Key (KSK) was made by > ICANN President and CEO Göran Marby after reviewing the outcomes of the > efforts of ICANN and others, particularly in the Domain Name System (DNS) > technical community. These outcomes were the result of significant global > outreach efforts, in consultation with the ICANN community, and after > extensive analysis of available data. > > With the final approvals in place, ICANN implemented the 16 September 2018 > resolution of ICANN's Board. The resolution stated that the organization should > proceed with its revised plans to change or "roll" the key for the DNS root on 11 > October 2018. > > To learn more about the Root KSK Rollover, visit its dedicated webpage and > primary source of information: https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_kskroll&d… > > About ICANN > ICANN's mission is to help ensure a stable, secure, and unified global Internet. > To reach another person on the Internet, you need to type an address – a name > or a number – into your computer or other device. That address must be > unique so computers know where to find each other. ICANN helps coordinate > and support these unique identifiers across the world. ICANN was formed in > 1998 as a not-for-profit public-benefit corporation with a community of > participants from all over the world. > > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann… > > _______________________________________________ > ksk-rollover mailing list > ksk-rollover(a)icann.org > https://mm.icann.org/mailman/listinfo/ksk-rollover _______________________________________________ ksk-rollover mailing list ksk-rollover(a)icann.org https://mm.icann.org/mailman/listinfo/ksk-rollover

2 1

Re: [ksk-rollover] 56-hour status check
by Davey宋 Oct. 14, 2018

Oct. 14, 2018

1 0

56-hour status check
by Paul Hoffman Oct. 14, 2018

Oct. 14, 2018

Even after 56 hours after the rollover, there were very few reports of problems, and those were mostly fixed quickly. --Paul Hoffman

1 0

24-hour status check
by Paul Hoffman Oct. 12, 2018

Oct. 12, 2018

In the first 24 hours after the rollover, there were very few reports of problems, and those were mostly fixed quickly. --Paul Hoffman

5 4

Re: [ksk-rollover] 答复: Chat session during KSK Rollover? Re: Reporting - Root KSK Rollover
by Medel Ramirez Oct. 12, 2018

Oct. 12, 2018

I think this is more exciting, going out Of your comfort “zone” . 0.02. ++++++ Sent from my V6 Engine! メデルラミレズ On 12 Oct 2018, at 7:50 AM, Davey Song(宋林健) <ljsong(a)biigroup.cn> wrote: It is easy to setup a non-validating resolver at hand. -----邮件原件----- 发件人: ksk-rollover [mailto:ksk-rollover-bounces@icann.org <ksk-rollover-bounces(a)icann.org>] 代表 Evan Hunt 发送时间: 2018年10月11日 6:08 收件人: Dan York 抄送: ksk-rollover(a)icann.org; Ralf Weber 主题: Re: [ksk-rollover] Chat session during KSK Rollover? Re: Reporting - Root KSK Rollover On Wed, Oct 10, 2018 at 08:50:47PM +0000, Dan York wrote: And so we confront the terrible state of real-time messaging best captured by this XKCD comic: https://xkcd.com/1810/ I know it's going to go fine and everything, but I can't help finding it amusing that every single suggestion for keeping in touch in case the internet breaks has been an internet service. Shouldn't we be using tin cans and string? :) -- Evan Hunt -- each(a)isc.org Internet Systems Consortium, Inc. _______________________________________________ ksk-rollover mailing list ksk-rollover(a)icann.org https://mm.icann.org/mailman/listinfo/ksk-rollover _______________________________________________ ksk-rollover mailing list ksk-rollover(a)icann.org https://mm.icann.org/mailman/listinfo/ksk-rollover -- This e-mail message (including attachments, if any) is intended for the use of the individual or the entity to whom it is addressed and may contain information that is privileged, proprietary, confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender and delete this E-mail message immediately.

1 0

The root KSK roll has occurred
by Matt Larson Oct. 11, 2018

Oct. 11, 2018

On behalf of the root zone management partners (ICANN and Verisign), I would like to report that the root KSK rollover occurred at 1600 UTC today, 11 October, with the publication of the root zone with serial number 2018101100. For the 48 hours after the rollover, we will be monitoring several mailing lists, including this one, so please reply here with any issues or concerns. Matt -- Matt Larson, VP of Research ICANN Office of the CTO

2 1

Reporting - Root KSK Rollover
by Jacques Latour Oct. 11, 2018

Oct. 11, 2018

Hi all, If we notice any outages perhaps we should notify the outage mailing list @ outages(a)outages.org along with the resolution path. Good luck! Jacques

18 20