[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Tired of Waiting




Hi Chris,

> How about a counterproposal? CORE and IOD negotiate what
> is, to CORE, acceptable terms for .web. These terms are
> reevaluated every year, and if IOD is meeting them, nothing
> changes. Only if IOD fails to meet the terms, is the contract
> rebid?
> 
> That prevents CORE from just selecting another "bidder" because
> of any personal choices, rather than negotiated terms.
> 
> I don't speak for IOD on this, but as a shareholder, I would bring
> it to the board.

I wish I had as much clout. I'm just a lowly PAB member.

> PS: ietf list removed at the request of Fred Baker.
> --
> Christopher Ambler, Personal Opinion Only

Note that CORE is the conglomerate of ALL the registrars, or said in another
word it is ALL the customers of the registry.
So, within the spirit of competition (which is what EVERYONE seems to want
to promote), you can't come to the table with a known un-negotiable outcome
of "IOD *WILL* be the .web registry for CORE".
Any contract set out by CORE must be open for public bidding by any company.
If two companies can accomplish all the terms set out in the public bid,
and both can give the same guarantees, then in all common sense the company
that can offer it at the better price should win.
There's already one contract in place with Emergent.
Could someone give us the details of this contract (ie, when does it come
under revision or go up for grabs again)? If so, I would argue forcefully
for IOD to be a bidder for being a registry as soon as it comes around
again.
Comments?
Why IOD didn't bid in the first place I can't understand... A series of
requirements were drawn up for what the database/interface had to do and
were handed around so that companies could bid. A few showed interest, but I
think that only one (Emergent) in the end actually put together a serious
proposal, which is why they were "lumped" with the job... (I may be mistaken
in my appreciations, so corrections are welcome).

Yours, John Broomfield.


Privacy Policy | Terms of Service | Cookies Policy