Re: [ga-roots] Why ICANN should Plan for the Future

[Jeff Williams <jwkckid1@ix.netcom.com>]

Leah and all,

L Gallegos wrote:

> Jeff:
>
> The webcast is provided by the Berkman center and there have been
> backbone problems.  Traceroutes have been very erratic.  I don't think
> we can blame ICANN staff for that.  Berkman has done a very good job
> considering the technical issues they have had to face with the
> connectivity problems they've had in Stockholm.  Had you been logged
> in to the IRC chat, you would have had the explanation.

  Berkman is providing this service for ICANN.  It has never been
good or reliable.  This time is no exception.  ICANN is just as
responsible as the Berkman Center.  I have and did participate
remotely in every ICANN meeting.  And at every one there were
outages the had they had a backup, would not of occurred.

>
>
> Leah
>
> On 2 Jun 2001, at 6:57, Jeff Williams wrote:
>
> > Patrick and all,
> >
> >   I think it has been made pretty clear that the ICANN staff has
> > serious problems with managing anything technical or operational,
> > given the recent problems with Webcast at ICANN meetings,
> > missing E-Mails from Comments@icann.org, and ICANN's
> > web page being down for a number of hours, just to name
> > a few.  I would hate to try to imagine what the ICANN
> > staff would do if a A-Root server went down for instance...
> > I wonder if they have a backup plan that the ICANN staff
> > can actually execute successfully....????
> >
> > Patrick Corliss wrote:
> >
> > > Hi William
> > >
> > > > Comparing this situation to car collisions has to be one of the most
> > > > outrageous analogies I've seen used.
> > >
> > > It doesn't matter what analogy people use there will always be other
> > > people who say the analogy is outrageous.  Personally I thought it was
> > > very apt.
> > >
> > > The comparison of the big bully car driver mowing down defenceless
> > > bicycle riders has more than a touch of satire.  Especially when the car
> > > gets damaged in the process.
> > >
> > > Here's another comparison.  The process of risk management.  There are
> > > several alternatives (not necessarily mutually exclusive) in a policy of
> > > risk management.  Taking an ordinary situation, perhaps, you can:
> > >
> > > (a)    Transfer the risk to somebody else (eg renting rather than buying)
> > > (b)    Defend against known hazards (eg install burglar alarms) (c)
> > > Lessen the likely damage (eg use fire-safe furniture) (d)    Spread the
> > > risk (eg take out insurance) (e)    Retrieve the situation (eg put out
> > > the fire quickly)
> > >
> > > Now it would seem to me that you are quite correct when you say:
> > >
> > > > As such any argument about new.net and its visibility is not relevant
> > > > to arguments about ICANN's stability or lack thereof right now.
> > >
> > > Sure.  But just because my house is not burning down *right now* doesn't
> > > mean that I should ignore aspects of future risk.  ICANN shouldn't
> > > either.
> > >
> > > I know you enjoy my stories so I'll tell you another one.  A few years
> > > ago I worked as an investigator with the Australian Securities Commission
> > > (as it was called then).  Any director who had been involved in the
> > > management of three or more "failed companies" had to show cause why they
> > > shouldn't be banned from corporate management for a period of up to 5
> > > years.
> > >
> > > When it came to the Tribunal hearing, they were always asked one simple
> > > question.  "Can you tell me what steps have you taken in relation to the
> > > management of your company should we decide to ban you right now?"
> > >
> > > Ninety percent would answer "I'm defending the case and don't expect to
> > > get banned.  I haven't taken any steps.  I'll work that out if and when
> > > it happens."
> > >
> > > You guessed it.  Such an answer demonstrated to the Tribunal that they
> > > weren't fit to manage a company.  Inevitably they were banned for up to 5
> > > years.  Quite appropriately, I would have thought.
> > >
> > > Anyone who provided a detailed contingency plan had a reasonable chance
> > > of avoiding being banned.  They had demonstrated a capacity for planning.
> > >
> > > It is fortunate, I guess, that the ICANN Directors are not subject to
> > > Australian law.  There are several provisions which would be very likely
> > > to get them prosecuted.  Not least is the requirement to anticipate
> > > problems.
> > >
> > > Actually, I'll bet dollars to donuts that you have a whole raft of
> > > sensible contingency plans for your own computer systems . . . .
> > >
> > > Thought so !!
> > >
> > > Best regards
> > > Patrick Corliss
> > >
> > > --
> > > This message was passed to you via the ga-roots@dnso.org list.
> > > Send mail to majordomo@dnso.org to unsubscribe
> > > ("unsubscribe ga-roots" in the body of the message).
> > > Archives at http://www.dnso.org/archives.html
> >
> > Regards,
> >
> > --
> > Jeffrey A. Williams
> > Spokesman for INEGroup - (Over 118k members strong!)
> > CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng.
> > Information Network Eng. Group. INEG. INC.
> > E-Mail jwkckid1@ix.netcom.com
> > Contact Number:  972-447-1800 x1894 or 214-244-4827
> > Address: 5 East Kirkwood Blvd. Grapevine Texas 75208
> >
> >
> > --
> > This message was passed to you via the ga-roots@dnso.org list.
> > Send mail to majordomo@dnso.org to unsubscribe
> > ("unsubscribe ga-roots" in the body of the message).
> > Archives at http://www.dnso.org/archives.html
> >
>
> --
> This message was passed to you via the ga-roots@dnso.org list.
> Send mail to majordomo@dnso.org to unsubscribe
> ("unsubscribe ga-roots" in the body of the message).
> Archives at http://www.dnso.org/archives.html

Regards,

--
Jeffrey A. Williams
Spokesman for INEGroup - (Over 118k members strong!)
CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng.
Information Network Eng. Group. INEG. INC.
E-Mail jwkckid1@ix.netcom.com
Contact Number:  972-447-1800 x1894 or 214-244-4827
Address: 5 East Kirkwood Blvd. Grapevine Texas 75208


--
This message was passed to you via the ga-roots@dnso.org list.
Send mail to majordomo@dnso.org to unsubscribe
("unsubscribe ga-roots" in the body of the message).
Archives at http://www.dnso.org/archives.html