All,

  These comments seem to parrot some my earlier comments in this
regard.  But given the delirious tendencies of the poster in
this particular case, they should most likely be viewed with suspicion.

Dr Eberhard W Lisse wrote:

> David
>
> In message <001101be6838$06f920c0$[EMAIL PROTECTED]>, "David Schutt" writes:
> > I'd go one step further -
> >
> > (this only refers to gtld's)
> >
> > I'd recommend that ICANN be a registration authority only. The keeper of
> > lists of unique entries.
>
> It has to set policy too.
>
> > ICANN controls the collection, not the individual entries. ICANN does not
> > publish (provide name resolution service).
>
> I'd not have a problem with ICANN owning the Primary of the root Servers.
>
> > ICANN licenses the right to publish (provide name resolution service for)
> > entries in its list to one or more service providers. What the provider is
> > licensing is not the name, but the quality of uniqueness guaranteed by
> > ICANN.
>
> Been saying this since ages.
>
> > I or my organization registers a name with ICANN, and they add it to the
> > list, guaranteeing that it will remain unique in the context of that list.
> > That's it. I pay once.
>
> I can even live with a maintenance fee as long as it is not generating
> *PROFIT*. They are a non-profit organization anyway.
>
> > I or my organization then decide that the entry should be published
> > (someone should provide name service) so I contact one of the
> > licensed name service providers, and request that they provide name
> > resolution service for my entry in the ICANN list. I pay
> > periodically to maintain name resolution service.
>
> This way you will have to live with someone making profit.
>
> el

Regards,

--
Jeffrey A. Williams
CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng.
Information Network Eng. Group. INEG. INC.
E-Mail [EMAIL PROTECTED]
Contact Number:  972-447-1894
Address: 5 East Kirkwood Blvd. Grapevine Texas 75208

Reply via email to