[ICANN-CSC] [Ext] Re: Emergency Response

Gaurav Vedi gaurav.vedi at gmail.com
Wed Mar 9 20:28:23 UTC 2022


Thanks Kim for sharing the info.

Regards,
Gaurav

On Wed, Mar 9, 2022 at 3:14 PM Brett Carr via ICANN-CSC <icann-csc at icann.org>
wrote:

> Thanks Kim, useful to know.
>
>
>
> Brett
>
>
>
> --
> Brett Carr
> Manager DNS Engineering
> Nominet UK
>
>
>
>
>
> *From: *Kim Davies <kim.davies at iana.org>
> *Date: *Wednesday, 9 March 2022 at 19:00
> *To: *Brett Carr <brett.carr at nominet.uk>, icann-csc at icann.org <
> icann-csc at icann.org>
> *Subject: *Re: [Ext] Re: Emergency Response
>
> Hi Brett,
>
>
>
> I wrote to them earlier today explaining the order of events, indicating
> that I think their summary gives an inaccurate picture, and asking for
> feedback on where they think the process could be improved. Hopefully they
> can provide us with additional insight into their experience so we can look
> for potential improvements. I am mindful and sympathetic to the reality
> that in an emergency situation there is potentially a lot of confusion in
> the moment that only becomes clearer afterward.
>
>
>
> kim
>
>
>
> *From: *Brett Carr <brett.carr at nominet.uk>
> *Date: *Wednesday, March 9, 2022 at 10:05
> *To: *Kim Davies <kim.davies at iana.org>, "icann-csc at icann.org" <
> icann-csc at icann.org>
> *Subject: *[Ext] Re: Emergency Response
>
>
>
> Thanks for the update Kim really appreciated.
>
>
>
> It sounds like everything went to plan and there were no
> issues/escalations in related to your processes would that be a fair
> assessment.
>
>
>
> Will you be suggesting .fj update their website to reflect the real
> situation.
>
>
>
> Thanks
>
>
>
> Brett
>
>
>
> --
> Brett Carr
> Manager DNS Engineering
> Nominet UK
>
>
>
>
>
> *From: *ICANN-CSC <icann-csc-bounces at icann.org> on behalf of Kim Davies
> via ICANN-CSC <icann-csc at icann.org>
> *Date: *Wednesday, 9 March 2022 at 16:44
> *To: *icann-csc at icann.org <icann-csc at icann.org>
> *Subject: *[ICANN-CSC] Emergency Response
>
> Dear colleagues,
>
>
>
> I wanted to provide you some insight into an issue with .fj, that the
> operators have summarized at https://www.domains.fj/index.php/announcements/3/.fj-Domains-Outage.html
> [secure-web.cisco.com]
> <https://urldefense.com/v3/__https:/secure-web.cisco.com/1jam3Pz6UUAzJT3jaSvuKOabUQBp2bNyUkgwDzhd5fcDLSQWsNjv1OR626Y8xRabdKcWj6AzBN_0NNEsQylX2vCANB6YtE-FEs64egodrFnwfITFSRkrffqZMiDmppbrHUZphlV5LzH92lk52x1k0kX6F16NXfV_A9s_eNzZc610v87wfQHwyVoOC77tIHFdnBjW4er2RJo3iE4LT9ToKk9uJYh8PWkRlyycJ_qov0FHWO-Ku10qmFQYQdrGmj9SdbH6w5WBbPLE4D8hQw9MQnp-jhaws2vKkePNRIy6zJRM/https*3A*2F*2Fwww.domains.fj*2Findex.php*2Fannouncements*2F3*2F.fj-Domains-Outage.html__;JSUlJSUlJQ!!PtGJab4!vgCTb3RsFwgJj24ghLvO0ZAwLzeW3OtdL5IcqUrCMOpNpPEE3qpRXuRAZl6egr6fNTJPw2I$>
> and has been re-reported at https://domainincite.com/27628-dnssec-claims-another-victim-as-entire-tld-disappears
> [secure-web.cisco.com]
> <https://urldefense.com/v3/__https:/secure-web.cisco.com/1T-OXUo2slmbZEtq3563mfPj318sFQ4tkVpvsmf2mVjZy965I3DjXjvT7QwD_tlclI88Jmk2_QuhlFCBfahhYMRShWp_c4HzLmvnDxSLGkyUdkNlRNY5maIyLUZ8lmrp3jZynrpKeeHde8D79Dxg_I9Dvb6DIff6spP9gnZwnbeLGjJI7EybvaFYMWfpK-6IyjU74sqUvt57NR-f5Nox2J5Sck63edGAIkiHwtk4xyi5CWuaLWtNOOP-w8wygUS5Iq36xdSxnRiwOvDs6M4DO_DqHfdMxIHX00V0f4DZnOus/https*3A*2F*2Fdomainincite.com*2F27628-dnssec-claims-another-victim-as-entire-tld-disappears__;JSUlJQ!!PtGJab4!vgCTb3RsFwgJj24ghLvO0ZAwLzeW3OtdL5IcqUrCMOpNpPEE3qpRXuRAZl6egr6fExcc3Ag$>
>
>
>
> Of particular interest to us is the implication that this request had to
> wait for our normal business hours to be processed.
>
>
>
> We operate a 24x7 emergency line, and it was used in this instance. The
> .fj manager called this number at approximately 3am our local time, and our
> team started processing their ticket just a few minutes after that. There
> wasn’t any delay caused by a need to wait for our regular working hours.
>
>
>
> Please let us know if you have any questions.
>
>
>
> kim
>
> --
>
> Kim Davies
>
> VP, IANA Services, ICANN
>
> President, PTI
> _______________________________________________
> ICANN-CSC mailing list
> ICANN-CSC at icann.org
> https://mm.icann.org/mailman/listinfo/icann-csc
>
> _______________________________________________
> 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.



-- 
Regards,
Gaurav Vedi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/icann-csc/attachments/20220309/c655236e/attachment.html>


More information about the ICANN-CSC mailing list