ICANN/DNSO
DNSO Mailling lists archives

[ga-full]


<<< Chronological Index >>>    <<< Thread Index >>>

Re: Re[4]: [ga] Call for a Working Group


Jeff - I think you are wrong here.

The only requests that should be honored are requests to REMOVE COLLIDERS
and to avoid entering them in the first place.

It is perfectly proper for PacificRoot (and ORSC and anyone else) to list
PUBLIC information about
published resources, ie:
    COM can be found at A.GTLD-SERVERS.NET, B.GTLD-SERVERS.NET.... etc

No, no one should remove delegations for TLDs as long as they are
delegations as specified by their
RIGHTFUL CUSTODIANS.

ICANN, by virtue of being assigned by the DoC to manage .COM/.NET/.ORG, is
the authority for
what is the right glue for those tlds. Leah is the correct authority for
.BIZ - do you get it?

John
----- Original Message -----
From: "Jeff Field" <jfield@aaaq.com>
To: <ga@dnso.org>
Cc: "Christopher Ambler" <cambler-dompol@iodesign.com>; "William X. Walsh"
<william@userfriendly.com>; <jandl@jandl.com>; "PacificRoot Hostmaster"
<idno@tallship.net>
Sent: Saturday, April 14, 2001 10:21 PM
Subject: RE: Re[4]: [ga] Call for a Working Group


> > -----Original Message-----
> > From: PacificRoot Hostmaster [mailto:idno@tallship.net]
> > Sent: Saturday, April 14, 2001 6:50 PM
> > To: Jeff Field
> > Cc: ga@dnso.org; Christopher Ambler; William X. Walsh; jandl@jandl.com
> > Subject: RE: Re[4]: [ga] Call for a Working Group
> >
> >
> > On Sat, 14 Apr 2001, Jeff Field wrote:
> >
> > > All this McDonalds/Burger King food talk got me thinking (a sometimes
> > > dangerous thing)...
> > >
> > > Today you have the ICANN root (McDonalds), the PacificRoot root
(Burger
> > > King), and perhaps some other roots (Wendys, Jack In The Box,
etc....but
> > > let's keep this simple).  Well, if I'm McDonalds, I don't sell
> > Burger King
> > > food (unless I want to and have an agreement with Burger King
> > that allows me
> > > to do so).  And, if I'm Burger King, I don't sell McDonalds
> > food (unless I
> > > want to and have an agreement with McDonalds that allows me to
> > do so).  On
> > > that, I think we can all agree.
> >
> >
> > No, the majority of the ccTLDs are carried in both The PacificRoot and
the
> > ICANN root witout benefit of contract, obligation, or liability. The
> > PacificRoot is willing to enter into Service Level Agreements with any
> > additional ISO-3166 ccTLDs that seek guarantees of service and will
> > provide resolution for their TLDs under contract for free and in
> > perpetuity.
>
> IMO, you are absolutely correct.  Any country, I would have to believe, is
> free to use whichever root they desire.  They could even start their own.
> Additionally, I also believe that ICANN will gladly recommend to the DoC,
> upon the request of any country, to have that country's respective ccTLD
> removed from the ICANN root systems.
>
> In the absence of a contract with any ccTLD or gTLD carried by the ICANN
> root, will PacificRoot honor any such removal request from either ICANN
> regarding .com, .net, and .org, for which they do have contracts, or any
> country regarding their respective ccTLD?
>
> Regards,
>
> Jeff
> --
> jeff field
> 925-283-4083
> jfield@aaaq.com
>
> > But otherwise, and in general, if it exists (a TLD) we will reslove it
> > anyway as a public service benefitting the Internet community at large.
> >
> > But it was a nice thought Jeff and I thank you for your time and effort.
> >
> > Kindest regards,
> >
> > Bradley D. Thornton
> > Chief Technology Officer
> > The PacificRoot/Joint Technologies Ltd.
> > The ONLY root that resolves all roots!
> > Upgrade your DNS for FREE today at:
> > 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
>
>

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



<<< Chronological Index >>>    <<< Thread Index >>>