I too don't generally feel it is necessary to discuss the particular backend details between CIRA and registrars in public. While it is certainly educational to domain investors to understand the life cycle better, I can also see how CIRA or really any business wouldn't want to air too much dirty laundry in public - with the caveat being that of course that only applies if the laundry is indeed being attended to. If the laundry is piled in the corner being ignored hoping it just disappears one day, well then that's what the forum is good for.
I also see that @bmetal
is trying to provide critical insight into a problem that he'd otherwise not be asked about since he's not a direct party to the current problem. But it seems clear that his expertise and experience fixing their own issues can provide insight into what possibly occurred between CIRA and MyID. So thank you for that.
Unfortunately, I felt I had to bring this issue to the forum's attention for a few reasons:
1. To try and determine the scope of the problem and see if anyone else was affected or noticed similar issues.
2. Get certain people's attentions to be sure it wasn't simply brushed under the rug.
3. I felt time was of the essence, as time can only makes the problem worse, not better.
4. If a problem like this happens to any one of our domains at no fault of our own, we all want to know it'll be fixed fairly, i.e. that CIRA has our backs.
Since at least the first two goals have been achieved, I agree with @richard.schreier
that it should be a private discussion going forward with CIRA, MyID and the registrant(s) and possibly @bmetal
for their experience and insight from another registrar's perspective.
Unfortunately, I did throw around some accusations without all of the facts. And I do want to apologize.
First at MyID. I assumed that CIRA certainly couldn't be wrong, so it must be MyID's fault, right? And based on MyID's initial response, and although they didn't come out and say it, I wouldn't completely blame them if they were thinking "our code has been working fine for years, certainly this cannot be our fault" and then initially deflected blame on the registrant. But eventually they took me seriously and did conclude that something indeed went wrong, but they weren't sure exactly what went wrong just yet.
I then accused CIRA, obviously because of the implication that changes were made by CIRA to the redemption/renewal procedures, which affected Baremetal. Then to think that the chances of MyID having a completely unrelated bug which coincidentally manifested itself and was detected in the weeks following the CIRA changes to the same general procedures regarding redemption/renewals seemed way too improbable to believe it was just coincidence. Not impossible, but also not likely. Unfortunately, Richard went on vacation and the silence made me nervous that CIRA was dragging their feet or hoping it would just go away. Of course, now I know that he wasn't blowing me off, he was just on vacation and is now back on the case. So my apologies to @richard.schreier
for making a stink about it without giving him a chance to fully investigate. In my defense, a quick message that he was going or already on vacay would have helped...
So I apologize for making accusations to both CIRA and MyID without all the facts. I guess I felt necessary at the time to help uncover the rest of the facts and bring attention to the issue.
And the one fact I think CIRA and MyID will now both agree to is that this was not the fault of the registrant. That leaves only CIRA and MyID. I don't care or even think its necessary if any blame is assigned at all, just that it get fixed. I feel like this is as minor as an oversight or miscommunication or however you want to characterize it so everyone comes out smelling like roses rather than turds. **** happens, I really don't see it as a big deal, no heads need to roll, no lawyers are on speed dial, we're all human, lets just cooperate, identify the issue, fix the mess, do the right thing, and move on. Easy peasy, no?