Merit Network
Can't find what you're looking for? Search the Mail Archives.
  About Merit   Services   Network   Resources & Support   Network Research   News   Events   Home

Discussion Communities: Merit Network Email List Archives

North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: ICANN on the panix.com theft

  • From: David Lesher
  • Date: Sun Mar 27 16:30:27 2005

Speaking on Deep Background, the Press Secretary whispered:
> 
I said:
> > I also don't see any discussion on what ICANN was during during the
.................................................oops doing during
> > hijack situation; maybe I missed that part.
> 
> i dont believe this is icanns responsibility.. it is however their 
> responsibility to ensure proper registry procedures are put in place to prevent 
> this kind of occurance and provide emergency procedures for reversals when 
> problems such as suspected hijacks are encountered.

We could get clear off-scale on the OffTopic alarm really fast;
so I'll leave this by saying: 

a) Exactly what's ICANN function/purpose/jurisdiction is an
Interesting Question, suited for long debate...elsewhere.

b) Direct mandated responsibility is only one motivator. "It's
not my job, man..." is a narrow way to accomplish anything,
no matter what the goal.

c) I was merely pointing out the ICANN report might have left some
things out. Say, when did what ICANN official learn of the hijack,
and what if anything did {s}he do & when? [i.e call anyone else,
notify X, etc...]



-- 
A host is a host from coast to coast.................wb8foz@nrk.com
& no one will talk to a host that's close........[v].(301) 56-LINUX
Unless the host (that isn't close).........................pob 1433
is busy, hung or dead....................................20915-1433






Discussion Communities


About Merit | Services | Network | Resources & Support | Network Research
News | Events | Contact | Site Map | Merit Network Home


Merit Network, Inc.