[] TAS Interruption - Update (17 April 2012)

[Adam Peake]

Doesn't seem much point in speculating, blaming until the facts are
known.  Perhaps it was pretty much unforeseeable, just bad luck (like
Airbus' wings crack, Rolls Royce engines blow up…)  Or it might have
been the result of dumb decisions.  I think given the money involved
--already in ICANN's account from applicants, the money applicants
have spent preparing, business plans, etc-- there won't be a cover-up.
Applicants will want answers and expect they'll nag until the answers
make sense (or they'll go to the courts.)  And I'm anyway of the
happy-set who believes ICANN anyway wouldn't cover things up :-)

Best,

Adam



On Thu, Apr 19, 2012 at 10:07 PM, Carlos A. Afonso <ca at cafonso.ca> wrote:
> With due respect for McTim's esprit de corps for what he dismisses as a
> technical problem, my main worry is the pile of legal cases Icann might
> have to confront because of this "simple glitch" (so simple, in fact,
> that has the entire organization running around for a week).
>
> fraternal regards
>
> --c.a.
>
> On 04/18/2012 05:15 PM, Avri Doria wrote:
>> Hi,
>>
>> And some of us have reflexive protective instinct that seems to indicate no cIr manager can do wrong.
>>
>> At this point there most certainly is something to be seen here.  This was not a simple glitch that was fixed in a day.  This is a major event that is still ongoing with no end in sight.  I do not beleive in judging before the whole story is reveled, but do insist that the whole story be revealed.
>>
>> avri
>>
>>
>>
>> On 18 Apr 2012, at 16:02, McTim wrote:
>>
>>> On Wed, Apr 18, 2012 at 12:50 PM, Avri Doria <avri at acm.org> wrote:
>>>> Hi,
>>>>
>>>> Do we actually know this?
>>>
>>> of course not, this list just has to reflexively kick ICANN in the
>>> 'nads when they are already on the ground....for me this whole TAS
>>> thing is mountain out of a molehill....nothing to see folks, kindly
>>> move along.
>>>
>>> --
>>> Cheers,
>>>
>>> McTim
>>> "A name indicates what we seek. An address indicates where it is. A
>>> route indicates how we get there."  Jon Postel
>>>
>>