<<<
Chronological Index
>>> <<<
Thread Index
>>>
[registrars] Continued Existence of Registrars?
I believe the following thread of postings on the GA is rather interesting
and should be of great interest to registrars since there seem to be a
number of people that believe that registrars are obsolete.
Mike
-----Original Message-----
From: owner-ga@dnso.org [mailto:owner-ga@dnso.org]On Behalf Of Michael
Froomkin - U.Miami School of Law
Sent: Tuesday, April 09, 2002 11:45 PM
To: Marc Schneiders
Cc: Gomes, Chuck; DannyYounger@cs.com; ga@dnso.org
Subject: RE: [ga] Time to regulate the Re-Sellers
I agree - the time for ICANN-accredited registrars is soon to be past. The
registries should manage the relationship at least in all new TLDs, just
so long as we have enough to make the market really competitive ... some
issues about legacy registries perhaps having a competitive edge that
requires they be last to be deregulated. Schedule that for 200_ (fill in
blank).
On Wed, 10 Apr 2002, Marc Schneiders wrote:
> Why are there ICANN accredited registars? Does this mere fact not make
> ICANN a bit responsible for what those registrars do? After all, it is a
> regulated market...
>
> Marc
>
> On Tue, 9 Apr 2002, at 14:57 [=GMT-0400], Gomes, Chuck wrote:
>
> > It seems to me that there is a principle that could reasonably be
applied
> > here: If there are already mechanisms in place with various
jurisdictions
> > around the world to deal with particular issues, then it is unnecessary
for
> > ICANN to duplicate the associated functions. For example, I believe
that
> > most jurisdictions have anti-trust laws and agencies to enforce those,
so it
> > is unnecessary for ICANN to get involved in anti-trust issues.
Similarly, I
> > believe that there are consumer protection mechanisms already in place
in
> > most major regions of the world, so it is unnecessary for ICANN to get
> > involved in consumer protection.
> >
> > Therefore, I agree with Michael that the "appropriate place to complain
is
> > the regulatory authorities in the home of the offender" and not ICANN.
> >
> > Chuck
> >
> > > -----Original Message-----
> > > From: Michael Froomkin - U.Miami School of Law
> > > [mailto:froomkin@law.miami.edu]
> > > Sent: Tuesday, April 09, 2002 1:09 PM
> > > To: DannyYounger@cs.com
> > > Cc: ga@dnso.org
> > > Subject: Re: [ga] Time to regulate the Re-Sellers
> > >
> > >
> > > Sure, and while we are regulating people, let's regulate
> > > fraudulent web
> > > pages, all spammers (they use the dns, don't they), and blasphemers.
> > >
> > > In other words, NO THANKS. This is not ICANN's mission. It is not a
> > > technical issue AT ALL -- it's a commercial/regulatory issue and the
> > > appropriate place to complain is the regulatory authorities
> > > in the home of
> > > the offender.
> > >
> > > On Tue, 9 Apr 2002 DannyYounger@cs.com wrote:
> > >
> > > > The following post has appeared on the registrars list:
> > > >
> > > > A Registrar (most probably a reseller of ICANN accredited
> > > Registrar) caused
> > > > one of the most severe massive SPAMs we have ever seen. It
> > > goes by those two
> > > > names.
> > > >
> > > > http://www.affordable-domains.com
> > > > http://www.renewmydomains.com
> > > >
> > > > it took our mail server down for couple of hours today.
> > > For those who are
> > > > curious, two SPAM messages are attached below. (see
> > > >
> > > http://www.dnso.org/clubpublic/registrars/Arc01/msg02287.html
> > > for details).
> > > > If one of our Resellers would do this we would terminate them.
> > > > -----------------------------------------------
> > > >
> > > > A subsequent post to the registrar's list
> > > >
> > > http://www.dnso.org/clubpublic/registrars/Arc01/msg02289.html
> > > revealed that
> > > > the reseller operates on behalf of SRSPlus... a Verisign company.
> > > >
> > > > In my opinion, it is time to regulate the re-seller
> > > community to the same
> > > > degree that we regulate the activities of registrars. If
> > > registrars take no
> > > > action to police their own industry, and if they are not
> > > held accountable for
> > > > the actions of their re-sellers, then this industry is
> > > surely begging for the
> > > > same type of governmental intervention that impacted the
> > > telecommunications
> > > > industry.
> > > >
> > > > I, for one, do not seek an enhanced role for governments.
> > > It is ICANN's
> > > > responsibility to manage the Domain Name system. Resellers
> > > acting as loose
> > > > cannons do not serve this industry well, and should be
> > > brought under control.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > 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
> > > >
> > > >
> > >
> > > --
> > > Please visit http://www.icannwatch.org
> > > A. Michael Froomkin | Professor of Law | froomkin@law.tm
> > > U. Miami School of Law, P.O. Box 248087, Coral Gables, FL 33124 USA
> > > +1 (305) 284-4285 | +1 (305) 284-6506 (fax) | http://www.law.tm
> > > -->It's hot here.<--
> > >
> > > --
> > > 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@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
> >
> >
>
>
--
Please visit http://www.icannwatch.org
A. Michael Froomkin | Professor of Law | froomkin@law.tm
U. Miami School of Law, P.O. Box 248087, Coral Gables, FL 33124 USA
+1 (305) 284-4285 | +1 (305) 284-6506 (fax) | http://www.law.tm
-->It's hot here.<--
--
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
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|