Here is an example:
(all times are in Pacific)
From Friday, 1:20 PM Pacific Time, until Sunday 9:36 AM, -- NO REPLY FROM
[EMAIL PROTECTED], follow the timeline below:
-------------------------------
1. Email sent to [EMAIL PROTECTED] telling them that a .ca domain isn't
upgradeable via a pre-registration, eventhough it should be (since no other
3rd or 4th level domains exist)
This happens on Friday, 1:03 PM
-------------------------------
2. An e-mail is received from [EMAIL PROTECTED] saying that the reason it
isn't upgradeable is "probably" because another 3rd or 4th level domain
already exists.
(This is a generic canned answer -- they didn't check for this domain)
This happens on Friday, 1:14 PM
-------------------------------
3. An e-mail is sent to [EMAIL PROTECTED] saying that a 3rd or 4th level
does not actually exist -- and that they should check on this matter.
This happens on Friday, 1:20 PM
==============================================
POOF! It is now Friday, 5:20 PM Eastern, and
all regular OpenSRS staff go home for the weekend.
==============================================
From Friday, 1:20 PM Pacific Time, until Sunday 9:36 AM, -- STILL NO REPLY
FROM [EMAIL PROTECTED]
By their standards, this is a non-emergency issue (especially since
November 1st is the pre-registration deadline). However, this means I must
"queue" up these issues and overload them on Monday.
This is the point -- I think that someone should be answering what is sent
to [EMAIL PROTECTED], 7 days a week, within a few hours of receiving a
non-emergency message.
If OpenSRS doesn't have the funds to employ persons 24x7, then they should
offer support contracts to do that, and let it be optional to the RSP's to
purchase one.
