There are of course varying degrees of failure, so what you can and can’t do will differ significantly from one event to the next, flexibility on
how to act is IMHO critical here. I don’t think we want the parties involved (ICANN, The EBERO and the failed registry) to air all the details in public and therefore we have to enact a certain level of trust.
Brett
--
Brett Carr
System Development Manager UK-DNS.
From:
gtld-tech <gtld-tech-bounces@icann.org> on behalf of Michele Neylon - Blacknight via gtld-tech <gtld-tech@icann.org>
Reply to: Michele Neylon - Blacknight <michele@blacknight.com>
Date: Friday, 20 October 2023 at 10:53
To: Wes Hardaker <wjhns1@hardakers.net>, Dr Eberhard W Lisse via gtld-tech <gtld-tech@icann.org>
Subject: RE: [EXTERNAL] [gtld-tech] .DESI to Be Placed in the Emergency Back-end Registry Operator Program
|
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless
you can confirm the sender and know the content is safe. |
EBERO kicks in when the world is on fire and the registry has failed.
I don’t see how you can force a failed registry to do anything
--
Mr Michele Neylon
Blacknight Solutions
Hosting, Colocation & Domains
Intl. +353 (0) 59 9183072
Direct Dial: +353 (0)59 9183090
Personal blog: https://michele.blog/
Some thoughts: https://ceo.hosting/
-------------------------------
Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845
I have sent this email at a time that is convenient for me. I do not expect you to respond to it outside of your usual working hours.