Re: [ga] Ambiguous resolutions

[PacificRoot Hostmaster <idno@tallship.net>]

Thanks Roeland, for your very objective observation :)

And you may not realize it, but you do paint a metaphor below as to why
IRAQ invaded KUWAIT When a US diplomat said we had "no interest' there.

As far as how to corral the horses? Well, I certainly cannot speak for
ARNI, but I suspect that they would be willing to pay a dollar or two for
ICANN's .biz ;), with the fate of the unfortunate souls that participated
in ICANN's illegal Lottery in those 'pre'registrations subject to
negotiations. Then everyone could think about going home happy.

On Fri, 26 Oct 2001, Roeland Meyer wrote:

> Aside from this being the strangest product launch that I have ever
> witnessed, it highlights a serious point; ICANN has said, by its actions,
> that data integrity on the internet isn't important.
> 
> About one year ago, before the New.Net launch, I made the argument that
> ICANN's action, of deliberately causing collisions between existing
> registries, would lead to massive potential confusion that technology might
> not be able to rescue us from. Shortly after that, New.Net was launched with
> yet more colliders at the TLD level. Since MHSC doesn't use any part of
> New.Net in its zone files, I cannot say exactly where those collision are.
> However, the fact that New.Net felt encouraged to do so, by reason of the
> ICANN's lack of care in TLD delegation, is both the point and the problem.
> Had ICANN re-enforced the concept of avoiding TLD collisions, in their
> lottery at the last MdR meeting, I doubt very much that we would be at this
> impass. It is likely that New.Net would have avoided the conflict, due to a
> lack of willingness to be the first one to break the implied policy.
> However, the ICANN was the first to break that ice and New.Net simply
> followed the ICANN lead. Ergo, that policy is now effectively voided and we
> are now reaping the early results, with more confusion yet to follow.
> 
> With INFO going live MHSC has to, for the very first time, filter the import
> of certain entries from the DOC root zone, because they conflict with these;
> 
> db.root.2001092700.zone:INFO. 172800 IN NS TLD1.NOMINUM.COM.
> db.root.2001092700.zone:INFO. 172800 IN NS TLD2.NOMINUM.COM.
> 
> Since INFO and BIZ are the two entries that the ICANN deliberately endowed,
> for the explicit purpose of creating this conflict, MHSC has chozen to honor
> the existing entries, rather than the new entries in the legacy DOC
> root-zone files. This action carries forward to all recipients of the MHSC
> zone-file, including those that modify that zone-file for their specific
> use.
> 
> The only problem we have currently is with this list. One of the members has
> chosen to use their INFO address in their ReplyTo and that address does not
> resolve from MHSC mail servers, for the reasons that I have just stated. I
> might point out that Richard Sexton caught absolute hell for doing the same
> thing a few years ago. 
> 
> MHSC has long advocated a First-Come-First-Served (FCFS) policy and has
> implemented that policy, in its root registry. We have yet to hear
> alternative policies that are fair, consistent, and don't involve massive
> litigation costs. MHSC would rather not have to settle liability claims or
> otherwise become distracted with litigatious issues that do not further MHSC
> business plans. I have never countinenced revenue-by-litigation business
> models.
> 
> As a direct result of FCFS, MHSC will continue to filter those TLDs that
> fail to meet that policy and all of their progeny as well. While MHSC
> supports the PacificRoot, MHSC continues to reference the ORSC root as a
> base-line, until otherwise stated. The referenced plug-in, while
> interesting, circumvents FCFS. It enhances the confusion-factor for the
> end-users. MHSC feels that it is unfortunate that the ICANN has condoned
> this circumstance, by their actions. Therefore, MHSC cannot condemn this
> evolution of events. However, we believe this this goes in the direction of
> chaos. Chaos is bad for business, as it leads to uncertainty. I might add
> that this course was predicted over two years ago.
> 
> Should this plug-in gain wide acceptance then all providers have a serious
> problem, MHSC included.
> 
> ICANN has let the horses out of the barn AND started a fire. I am unclear
> how we can corral the horses and prevent the barn from burning down. Time is
> not on our side. The choice is to either corral the horses or save the barn.
> But, a barn without the horses is an empty shell, useless to all. I don't
> think that doing both is within the realm of possibility. IMHO, that is the
> optimistic view.
> 
> |> From: PacificRoot Hostmaster [mailto:idno@tallship.net]
> |> Sent: Friday, October 26, 2001 7:24 AM
> |> 
> |> Yes, We're trying to accommodate non-colliding SLD.TLDs at 
> |> this time where
> |> possible.
> |> 
> |> For tech support issues, or general questions, it's best to 
> |> direct queries
> |> to our Hostmaster Team, Hostmaster@PacificRoot.com, as we 
> |> don't monitor
> |> this list very often for anything other than political follies :) 
> |> 
> |> On Fri, 26 Oct 2001 steinle@smartvia.de wrote:
> |> 
> |> > I use pacificroot DNS, not your plug-in.
> |> > Could you please explain me why I get Afilias .info 
> |> domains and domainisland .info names.
> |> > www.info takes me to domainisland
> |> > nic.info takes me to afilias
> |> > 
> |> > Thanks!
> |> > 
> |> > 
> |> > I was asked to put the download link for the plug-in near 
> |> the top so
> |> > everyone wouldn't have to read the whole document, so here it is ;)
> |> > 
> |> > http://www.PacificRoot.com/updatedns.shtml 
> |> > 
> |> > (and select automatic upgrade, and either save to disk or 
> |> install from
> |> > d/l - yes you can uninstall it too from control panel=>add/remove
> |> > programs). Yes it works with newnet domains too ;)
> |> > 
> |> > the best part is, it makes a great stocking stuffer for 
> |> friends and family
> |> > around Christmas time.
> |> > 
> |> > Now you truly have two .BIZs :)
> |> > 
> |> 
> |> Bradley D. Thornton
> |> Chief Technology Officer
> |> The PacificRoot/Joint Technologies Ltd.
> |> http://www.PacificRoot.com
> |> http://www.JointTech.com
> 
> 

Bradley D. Thornton
Chief Technology Officer
The PacificRoot/Joint Technologies Ltd.
http://www.PacificRoot.com
http://www.JointTech.com

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