Avri,

On Thu, Apr 19, 2012 at 10:23 AM, Avri Doria <[log in to unmask]> wrote:
> Hi,
>
> I would also add that we might want to raise our voice in a demand for more information.
>
> Using my imagination as a once software engineer who spent years chasing glitches, we called them bugs, i know how the tiniest little bug in the SW can have a huge effect.  And my imagination is running overtime based on my own experience in small bugs with big effects.
>
> There is another assumption being made, that I ind problematic: that is that it is the people who created the system that are the ones hunting and auditing the glitch and its effects.   Again if my experience is anything to draw on, they have long since bought in an advanced group of specialist hunters/fixers.  I would be curious to know if that was the case.  ICANN has among its various contract crews some amazingly competent people, I trust (and hope I am right) that they have made outreach to the appropriate set of outside specialists.
>
> Besides, now that Rod has joined the glitch response team, as advertised in a ICANN tweet, we now know that this is something of presidential proportion.  Hence there is most definitely something to be sen here.


What I meant by my comment was that a software bug doesn't rise to the
level of involving the policy community, of which this list is part.

It's a procedural issue IMHO, not a policy issue that NCSG should
spend cycles on, but I guess it's too late for that ;-/


-- 
Cheers,

McTim
"A name indicates what we seek. An address indicates where it is. A
route indicates how we get there."  Jon Postel