ICANN on the panix.com theft
ICANN Blames Melbourne IT for Panix Domain Hijacking Panix had its domain hijacked over the weekend of January 15-16. Its domain was registered with Dotster, a registrar based in Washington. By January 17, the domain had been restored. Melbourne IT has admitted that it was to blame for the incident as one of its resellers failed to follow the process for seeking authorisation for a domain name transfer request. <http://www.smh.com.au/news/Breaking/ICANN-asked-to-probe-all-transfer-problems/2005/03/17/1110913706318.html?oneclick=true> I used lynx to avoid registration hassles. obdisclaimer: Happy Panix customer... -- 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
nuance.
ICANN Blames Melbourne IT for Panix Domain Hijacking
ICANN's current RAA (Registrar Accreditation Agreement) lacks a profound amount of teeth. If it had any, that is, if "ICANN Blames <insert any registrar here>" ment anything, Domain Registry of America' (remember them) registrars (note the plural) would be on the dock for something. MITs sins are pretty small in the grand scheme of things, and they didn't cause the race regime that was the root cause for PANIX.COM needing defense. ICANN is dorking the registry contracts for new sTLDs, and has dorked with the ccTLD contracts, and is now dorking with the registrar contracts. You all may wonder if ICANN is "bottom up" and these contracts reflect "consensus polices", if not caring about the DNSO circus for another round is really in your best interests. YMMV, as always. Eric
Speaking on Deep Background, the Press Secretary whispered:
nuance.
ICANN Blames Melbourne IT for Panix Domain Hijacking
ICANN's current RAA (Registrar Accreditation Agreement) lacks a profound amount of teeth.
I make no judgement but do note: http://www.icann.org/correspondence/tonkin-to-cole-27jan05.htm The CEO of Melbourne IT received a call from the the CEO of panix.com on Sunday. This was referred to the legal team which informed the CEO of panix.com that Melbourne IT staff would first need to investigate the authenticity of the claims made. Staff performed further checks to authenticate the request, and reverted the DNS information to its orginal state as stored in Melbourne IT's systems around 9:30am on Monday. Melbourne IT also received calls from Verisign staff on Monday morning (AEST). In other words, they delayed a full day before acting to mitigate the damage. I also don't see any discussion on what ICANN was during during the hijack situation; maybe I missed that part. -- 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
On Sat, 26 Mar 2005, David Lesher wrote:
ICANN Blames Melbourne IT for Panix Domain Hijacking
I also don't see any discussion on what ICANN was during during the 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. Steve
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
participants (3)
-
David Lesher -
Eric Brunner-Williams in Portland Maine -
Stephen J. Wilcox