Registries must be allowed to extend the sunrise in case of unexpected events, even on the last day

[Werner Staub <werner@xxxxxxxx>]

This is a technical point:


Clause 2.2.3 in draft-rpm-requirements-06aug13-en.pdf says:

 Following commencement of the Sunrise Period, including any
 extensions thereto, Registry Operator MAY NOT shorten the duration
 of the Sunrise Period, but it MAY extend the duration of the
 Sunrise Period by providing updated TLD Startup Information to
 ICANN and the TMCH Sunrise and Claims Operator at least four (4)
 calendar days prior to the effective date of the extension.

This minimum 4 day prior notice requirement might prevent a registry
from dealing appropriately with unexpected situations.

Experience has shown, for instance, that sometimes there is an
unexpected and uncontrollable last-minute onslaught of
sunrise registrations.

There may be other emergencies, such as malicious attacks against
registrars or the registry, or simply technical problems.

In such case, the registry must be able to extend the sunrise
period in order to maintain a fair and orderly registration
process.

The extension of the sunrise period must be possible even shortly
AFTER it was scheduled to end. The only needed requirement in this
case is that the registry notify all affected parties (e.g.
registrars, ICANN, the TMCH, the public)and that the extension
be of an appropriate length to ensure that no party is
disenfranchised.


Werner Staub