Name.Space wrote:
>
> >Milton Mueller wrote:
> >>
> >> >From the article:
> >>
> >> "Since PGMedia filed its suit, however, the Internet landscape has
> >> changed drastically, throwing a monkey wrench into an
> >> already-complicated lawsuit. Last fall, the National Science
> >> Foundation passed responsibility for the Internet to Commerce
> >> Department, which in turn has laid out a plan to turn administration
> >> to a private company and open up registration competition. By March,
> >> five companies are slated to offer wholesale registration to addresses
> >> ending in ".com," ".net," and ".org," and by June, the field is slated
> >> to be opened to any accredited registrar."
> >>
> >> My reply:
> >> So what? Anybody can register names in com net and org now. New
> >> registrars don't add new TLDs.
> >>
> >> My further comment:
> >> Where are all those "shared TLD" advocates from the gTLD-MoU days?
> >> PGMedia is arguing for a completely open, shared namespace. Of course,
> >> it wouldn't be under the control of POC, PAB, or CORE--or ICANN. I
> >> guess that makes it kinda unattractive, eh?
> >>
> >> --MM
> >>
> >
>
> "John B. Reynolds" <[EMAIL PROTECTED]> wrote:
>
> >The reason for PGMedia's lack of support is that their stated plans are
> >simply not credible. Their version of shared registries depends upon
> >universal replacement of the existing DNS with their vaguely
> described and
> >questionably feasible SINDI and PAM protocols. Their "interim
> solution" in
> >the absence of these protocols would effectively give PGMedia absolute
> >authority over all new TLDs, thereby replacing the existing NSI monopoly
> >with an NSI/PGMedia duopoly.
>
> This assessment is totally inaccurate.
> SINDI does not replace BIND, it "helps" it.
> It has been tested in our lab and we are now
> working on a version for release. It works.
>
> PAM (Portable Address Manager) is already in existance and our
> users love it.
> Also, our sWhois is a big hit as well (http://swhois.net)
>
The information posted on your web site on these protocols consists solely
of a laundry list of what these products purportedly accomplish, some
aspects of which appear to be mutually exclusive (it's impossible to
accomplish the other goals of SINDI while still maintaining backward
compatibility with existing BIND versions). What is notably lacking is any
technical detail on how this is done. In the absence of that, there is no
reason to believe that SINDI is any more real than Jeff Williams's BIND+.
> Your conclusion that Name.Space and NSI will be a duopoly also
> shows a careless reading of our interim pre-sharing plan. This
> is clearly not our intent.
>
> Here is a direct quote from our proposal:
>
> [...]
>
> Interim solution:
>
> all registries up and running currently with tld's
> will have any populated zones added to the "." file
> either through court action against NSI, or through
> industry consensus, or both.
>
Your lawsuit seeks to implement this by adding all name.space TLDs to the
root under the auspices of PGMedia. Given that SINDI is not yet on the
market, this means that those 516 TLDs, and any you should choose to add in
the future, would be controlled exclusively by PGMedia. Existing technology
does not permit .web (for example) to be shared equally by PGMedia,
IODesign, and CORE.
If PGMedia were to win its lawsuit, any economic incentive it might have to
develop and release SINDI would be gone. In fact, the prospect of the loss
of its exclusive franchise on its TLDs would provide a strong disincentive
for such development.
> Committment to development:
>
> in the short term, there will be clusters of shared tld's,
> reselling (wholesale) agreements of legacy tld's, as well
> as new ones where sharing is not yet implemented.
>
> This puts people in business and makes new namespaces available
> in the short term to benefit the public, and doesn't stall the
> the birth of a new industry by virtue of a simple text edit.
>
> [...]
>
> reference: http://namespace.org/expand
>
> Please inform youself fully of the facts (not your biased interpretation)
> before you make such (wrong) public declarations about Name.Space.
>
> thank you.
>
> Paul Garrin,
> President
> Name.Space
> [EMAIL PROTECTED]
> http://name.space-beats-internic.net
>
>
> "Hack code, not people"
>
>
>
>
>
>
