Root Zone KSK Rollover
Did anyone notice??? https://www.icann.org/ksk-rollover-status https://www.icann.org/resources/pages/ksk-rollover Alan
Hello all, speaking to Samiran Gupta, Head of India at ICANN, he received only a handful of reports from Indian ISPs, which were fixed rapidly. There were reports in the Indian Press that mentioned the KSK Rollover with a catchy title, but the reality of things was much less exciting, as in, very little happened... so far. Kindest regards, Olivier On 13/10/2018 01:38, Alan Greenberg wrote:
Did anyone notice???
https://www.icann.org/ksk-rollover-status
https://www.icann.org/resources/pages/ksk-rollover
Alan
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
-- Olivier MJ Crépin-Leblond, PhD http://www.gih.com/ocl.html
Normally the negative effect (if any) will be felt much later (within 48 to 72 hours), but so far I have not experienced nor heard of any major incidence! Regards Sent from my mobile Kindly excuse brevity and typos On Fri, 12 Oct 2018, 21:09 Alan Greenberg, <alan.greenberg@mcgill.ca> wrote:
Did anyone notice???
https://www.icann.org/ksk-rollover-status
https://www.icann.org/resources/pages/ksk-rollover
Alan
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
No Armageddon to be seen. On Fri, Oct 12, 2018 at 4:36 PM Seun Ojedeji <seun.ojedeji@gmail.com> wrote:
Normally the negative effect (if any) will be felt much later (within 48 to 72 hours), but so far I have not experienced nor heard of any major incidence!
Regards
Sent from my mobile Kindly excuse brevity and typos
On Fri, 12 Oct 2018, 21:09 Alan Greenberg, <alan.greenberg@mcgill.ca> wrote:
Did anyone notice???
https://www.icann.org/ksk-rollover-status
https://www.icann.org/resources/pages/ksk-rollover
Alan
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
Maarten Botterman, ICANN Board, member referred to the KSK Rollover in the GFCE event held at Delhi yesterday, only to state that there was "no news" and therefore it was all "good news". satish On Sat, Oct 13, 2018 at 2:07 AM Javier Rua <javrua@gmail.com> wrote:
No Armageddon to be seen.
On Fri, Oct 12, 2018 at 4:36 PM Seun Ojedeji <seun.ojedeji@gmail.com> wrote:
Normally the negative effect (if any) will be felt much later (within 48 to 72 hours), but so far I have not experienced nor heard of any major incidence!
Regards
Sent from my mobile Kindly excuse brevity and typos
On Fri, 12 Oct 2018, 21:09 Alan Greenberg, <alan.greenberg@mcgill.ca> wrote:
Did anyone notice???
https://www.icann.org/ksk-rollover-status
https://www.icann.org/resources/pages/ksk-rollover
Alan
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
Indeed. No news is the best news! Sounds like the terror story happened just before the year 2000 ... :) Kaili ----- Original Message ----- From: Satish Babu To: Javier Rua Cc: ALAC Working List ; Alan Greenberg Sent: Saturday, October 13, 2018 9:48 AM Subject: Re: [ALAC] Root Zone KSK Rollover Maarten Botterman, ICANN Board, member referred to the KSK Rollover in the GFCE event held at Delhi yesterday, only to state that there was "no news" and therefore it was all "good news". satish On Sat, Oct 13, 2018 at 2:07 AM Javier Rua <javrua@gmail.com> wrote: No Armageddon to be seen. On Fri, Oct 12, 2018 at 4:36 PM Seun Ojedeji <seun.ojedeji@gmail.com> wrote: Normally the negative effect (if any) will be felt much later (within 48 to 72 hours), but so far I have not experienced nor heard of any major incidence! Regards Sent from my mobile Kindly excuse brevity and typos On Fri, 12 Oct 2018, 21:09 Alan Greenberg, <alan.greenberg@mcgill.ca> wrote: Did anyone notice??? https://www.icann.org/ksk-rollover-status https://www.icann.org/resources/pages/ksk-rollover Alan _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...) _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...) _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...) ------------------------------------------------------------------------------ _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
Hi Alan, My office is at the .Ke Registry. The rollover was smooth. I haven't heard of any issues from the African region. Regards On Sat, 13 Oct 2018 07:45 Kan Kaili, <kankaili@gmail.com> wrote:
Indeed. No news is the best news!
Sounds like the terror story happened just before the year 2000 ... :)
Kaili
----- Original Message ----- *From:* Satish Babu <sb@inapp.com> *To:* Javier Rua <javrua@gmail.com> *Cc:* ALAC Working List <alac@atlarge-lists.icann.org> ; Alan Greenberg <alan.greenberg@mcgill.ca> *Sent:* Saturday, October 13, 2018 9:48 AM *Subject:* Re: [ALAC] Root Zone KSK Rollover
Maarten Botterman, ICANN Board, member referred to the KSK Rollover in the GFCE event held at Delhi yesterday, only to state that there was "no news" and therefore it was all "good news".
satish
On Sat, Oct 13, 2018 at 2:07 AM Javier Rua <javrua@gmail.com> wrote:
No Armageddon to be seen.
On Fri, Oct 12, 2018 at 4:36 PM Seun Ojedeji <seun.ojedeji@gmail.com> wrote:
Normally the negative effect (if any) will be felt much later (within 48 to 72 hours), but so far I have not experienced nor heard of any major incidence!
Regards
Sent from my mobile Kindly excuse brevity and typos
On Fri, 12 Oct 2018, 21:09 Alan Greenberg, <alan.greenberg@mcgill.ca> wrote:
Did anyone notice???
https://www.icann.org/ksk-rollover-status
https://www.icann.org/resources/pages/ksk-rollover
Alan
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
------------------------------
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
Although there may be some similarities (certainly in the end-result), the reason is very different. In the the case of the KSK Rollover, we had several unknowns. We had no idea how many servers did not have DNSSEC enabled (which meant they would not be affected) nor how many had it enabled and had the new key. Nor did we know how fast service would react if there was a problem. The last estimates were that a VERY tiny fraction of users would be affected, and that proved to be true. With Y2K, there was abundant evidence that in the absence of an intense work effort, there WOULD be problems - it was easy to see that a system that only stored two digits for the year would sort them out of order when once there was a "00". And a system that subtracted 1900 from the full year would suddenly have a 3-digit result. And there was plenty of code that did not recognize properly that 2000 was a leap year (so Feb 29, 2000 was another hurdle when some of us held their breath). Even many systems built in the mid-1990s were going to fail. Issues were not just software (where in many cases, the source code no longer existed) but hardware clocks which did not expect the change. It was estimated that for network equipment (primarily voice I think) only 50% produced prior to 1996 would function properly. And where the hardware would work, the billing might not. And unlike with DNSSEC (where you could opt out consciously or unconsciously be not using DNSSEC), you could not opt out of the year changing on Dec 31. In the end, there were relatively few problems, but that was because of an unbelievably intense effort that went into fixing potential problems or replacing or decommissioning systems. Alan At 13/10/2018 12:45 AM, Kan Kaili wrote:
Sounds like the terror story happened just before the year 2000 ... :)
Hi Guys, Following the successful KSK rollover, I wrote a short piece on it: http://www.circleid.com/posts/20181013_ksk_rollover_elliptical_curve_vulnera... Sala On Sun, 14 Oct 2018, 7:58 am Alan Greenberg, <alan.greenberg@mcgill.ca> wrote:
Although there may be some similarities (certainly in the end-result), the reason is very different.
In the the case of the KSK Rollover, we had several unknowns. We had no idea how many servers did not have DNSSEC enabled (which meant they would not be affected) nor how many had it enabled and had the new key. Nor did we know how fast service would react if there was a problem. The last estimates were that a VERY tiny fraction of users would be affected, and that proved to be true.
With Y2K, there was abundant evidence that in the absence of an intense work effort, there WOULD be problems - it was easy to see that a system that only stored two digits for the year would sort them out of order when once there was a "00". And a system that subtracted 1900 from the full year would suddenly have a 3-digit result. And there was plenty of code that did not recognize properly that 2000 was a leap year (so Feb 29, 2000 was another hurdle when some of us held their breath). Even many systems built in the mid-1990s were going to fail.
Issues were not just software (where in many cases, the source code no longer existed) but hardware clocks which did not expect the change. It was estimated that for network equipment (primarily voice I think) only 50% produced prior to 1996 would function properly. And where the hardware would work, the billing might not.
And unlike with DNSSEC (where you could opt out consciously or unconsciously be not using DNSSEC), you could not opt out of the year changing on Dec 31.
In the end, there were relatively few problems, but that was because of an unbelievably intense effort that went into fixing potential problems or replacing or decommissioning systems.
Alan
At 13/10/2018 12:45 AM, Kan Kaili wrote:
Sounds like the terror story happened just before the year 2000 ... :)
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
Hello all, as a follow-up on India, this was one of the focus worries with so many ISPs in the country. A rumour had spread, carried by some newspaper, that the Internet would shut down. The follow-up articles grabbed headline news with some of the front pages of newspapers dispelling the rumours. Here's a tweet I sent out earlier today, with a picture I took of one of the newspapers in Delhi: https://twitter.com/Olivier_CL/status/1051013447780052992https://twitter.com... A few hours later, Olaf Kolkman, ISOC CTO who is also participating at inSIG, shared his knowledge of reporting he has been tracking closely, that there were no major case reported so far, with only a few hours to go into the 48H propagation window. It is likely that some post event analysis will be required, but so far it looks like the decision to proceed forward was a good one and this has reinforced trust in DNSSEC. Perhaps it is also an opportunity to applaud the work that Teams at ICANN Org as well as Community members have done in preparing for this day. Failure to prepare is to prepare for failure. Clearly the opposite was true this week. Kindest regards, Olivier On 13/10/2018 07:18, Satish Babu wrote:
Maarten Botterman, ICANN Board, member referred to the KSK Rollover in the GFCE event held at Delhi yesterday, only to state that there was "no news" and therefore it was all "good news".
satish
On Sat, Oct 13, 2018 at 2:07 AM Javier Rua <javrua@gmail.com <mailto:javrua@gmail.com>> wrote:
No Armageddon to be seen.
On Fri, Oct 12, 2018 at 4:36 PM Seun Ojedeji <seun.ojedeji@gmail.com <mailto:seun.ojedeji@gmail.com>> wrote:
Normally the negative effect (if any) will be felt much later (within 48 to 72 hours), but so far I have not experienced nor heard of any major incidence!
Regards
Sent from my mobile Kindly excuse brevity and typos
On Fri, 12 Oct 2018, 21:09 Alan Greenberg, <alan.greenberg@mcgill.ca <mailto:alan.greenberg@mcgill.ca>> wrote:
Did anyone notice???
https://www.icann.org/ksk-rollover-status
https://www.icann.org/resources/pages/ksk-rollover
Alan
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org <mailto:ALAC@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...) <https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+%28A...>
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org <mailto:ALAC@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...) <https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+%28A...>
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org <mailto:ALAC@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...) <https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+%28A...>
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
-- Olivier MJ Crépin-Leblond, PhD http://www.gih.com/ocl.html
Well said Olivier... On Sun, Oct 14, 2018, 05:53 Olivier MJ Crépin-Leblond <ocl@gih.com> wrote:
Hello all,
as a follow-up on India, this was one of the focus worries with so many ISPs in the country. A rumour had spread, carried by some newspaper, that the Internet would shut down. The follow-up articles grabbed headline news with some of the front pages of newspapers dispelling the rumours. Here's a tweet I sent out earlier today, with a picture I took of one of the newspapers in Delhi: https://twitter.com/Olivier_CL/status/1051013447780052992 https://twitter.com/Olivier_CL/status/1051013447780052992
A few hours later, Olaf Kolkman, ISOC CTO who is also participating at inSIG, shared his knowledge of reporting he has been tracking closely, that there were no major case reported so far, with only a few hours to go into the 48H propagation window.
It is likely that some post event analysis will be required, but so far it looks like the decision to proceed forward was a good one and this has reinforced trust in DNSSEC. Perhaps it is also an opportunity to applaud the work that Teams at ICANN Org as well as Community members have done in preparing for this day. Failure to prepare is to prepare for failure. Clearly the opposite was true this week.
Kindest regards,
Olivier
On 13/10/2018 07:18, Satish Babu wrote:
Maarten Botterman, ICANN Board, member referred to the KSK Rollover in the GFCE event held at Delhi yesterday, only to state that there was "no news" and therefore it was all "good news".
satish
On Sat, Oct 13, 2018 at 2:07 AM Javier Rua <javrua@gmail.com> wrote:
No Armageddon to be seen.
On Fri, Oct 12, 2018 at 4:36 PM Seun Ojedeji <seun.ojedeji@gmail.com> wrote:
Normally the negative effect (if any) will be felt much later (within 48 to 72 hours), but so far I have not experienced nor heard of any major incidence!
Regards
Sent from my mobile Kindly excuse brevity and typos
On Fri, 12 Oct 2018, 21:09 Alan Greenberg, <alan.greenberg@mcgill.ca> wrote:
Did anyone notice???
https://www.icann.org/ksk-rollover-status
https://www.icann.org/resources/pages/ksk-rollover
Alan
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...) <https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+%28A...>
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...) <https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+%28A...>
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...) <https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+%28A...>
_______________________________________________ ALAC mailing listALAC@atlarge-lists.icann.orghttps://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
-- Olivier MJ Crépin-Leblond, PhDhttp://www.gih.com/ocl.html
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
Here in Russia we were watching the distribution and got no bad tickets. --andrei пт, 12 окт. 2018 г. в 23:09, Alan Greenberg <alan.greenberg@mcgill.ca>:
Did anyone notice???
https://www.icann.org/ksk-rollover-status
https://www.icann.org/resources/pages/ksk-rollover
Alan
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
-- Andrey Kolesnikov RIPN.NET
I guess we didn’t break the Internet! On Sat, Oct 13, 2018 at 9:06 AM Andrei Kolesnikov <andrei@rol.ru> wrote:
Here in Russia we were watching the distribution and got no bad tickets. --andrei
пт, 12 окт. 2018 г. в 23:09, Alan Greenberg <alan.greenberg@mcgill.ca>:
Did anyone notice???
https://www.icann.org/ksk-rollover-status
https://www.icann.org/resources/pages/ksk-rollover
Alan
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
-- Andrey Kolesnikov RIPN.NET
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
Indeed! Sent from my mobile Kindly excuse brevity and typos On Sat, 13 Oct 2018, 14:21 Javier Rua, <javrua@gmail.com> wrote:
I guess we didn’t break the Internet!
On Sat, Oct 13, 2018 at 9:06 AM Andrei Kolesnikov <andrei@rol.ru> wrote:
Here in Russia we were watching the distribution and got no bad tickets. --andrei
пт, 12 окт. 2018 г. в 23:09, Alan Greenberg <alan.greenberg@mcgill.ca>:
Did anyone notice???
https://www.icann.org/ksk-rollover-status
https://www.icann.org/resources/pages/ksk-rollover
Alan
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
-- Andrey Kolesnikov RIPN.NET
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
No issues detected in LAC as far as I can tell. Good user experience for a “scheduled server maintenance” as one note reported :P Kind regards León Enviado desde mi iPhone El oct. 13, 2018, a la(s) 6:05 a. m., Andrei Kolesnikov <andrei@rol.ru> escribió:
Here in Russia we were watching the distribution and got no bad tickets. --andrei
пт, 12 окт. 2018 г. в 23:09, Alan Greenberg <alan.greenberg@mcgill.ca>:
Did anyone notice???
https://www.icann.org/ksk-rollover-status
https://www.icann.org/resources/pages/ksk-rollover
Alan
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
-- Andrey Kolesnikov RIPN.NET
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
participants (11)
-
Alan Greenberg -
Andrei Kolesnikov -
Barrack Otieno -
Cheryl Langdon-Orr -
Javier Rua -
Kan Kaili -
León Felipe Sánchez Ambía -
Olivier MJ Crépin-Leblond -
Salanieta T. Tamanikaiwaimaro -
Satish Babu -
Seun Ojedeji