ICANN - The Case for Replacing its Management

Although I reserve comment on some of the specific recommendation offered
by the author, this is an otherwise extremely timely, well-articulated
view into the history of ICANN to present written by the former Chair of
the General Assembly.

http://www.icannworld.org

P.S. Yes Virgina, the resultant outcome of this mess could actually affect
how you configure your router(s) some day....

/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
                               Patrick Greenwell
         Asking the wrong questions is the leading cause of wrong answers
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/

Which leads me to ask again why large ISPs are taking such passive
position? They are the only party with resources, expertise, long history
of cooperation, huge interest in keeping Internet stable, and, finally,
the power to direct traffic to whatever root nameservers they choose (even
if it means injecting few host routes in their BGP tables).

A self-appointed "governance" bodies, frankly, have no business in
deciding how Internet should be ran. They got no interest in it but as
means for self-perpetuating.

The whole registration & name allocation process can be completely
automated, and very cheap. The silly dispute-resoultion policies are not,
in fact, needed if few rules are enforced automatically:

1) first-come first-served registration
2) credit-card payment _only_, with payer's address in the country of the
   domain, and issued by a bank accredited in the country.
3) publishing of verified payer information (i.e. credit card holder's
   name and address)
4) exponential fee increments for registering domains with the same
   payer's physical address and/or name.
5) voluntary re-assignment of domain names.
6) forced reassignment of domain names if owner on record fails to respond
   to (rate-limited) dispute notifications made by any party through the
   registry's system. Such responces must include re-validation of
   payer's name & address (using the credit cards, again).
7) periodic automatic renewal, with e-mail notifications. It is
   responsibility of the domain holder to keep contact information up to
   date.

The rule 1 is the basic algorithm.

The rules 2 and 3 validate contact information and point to a real person
or registered corporation, so they can be easily traced down if a dispute
arises. Perpetuating "international" TLDs like .COM makes no sense
whatsoever; existing foreighn domain name holders may have a grace period
to migrate to national domains or to secure a credit card for payment in
US. This problem does not exist with ISO-3166 domains.

The rule 4 is, obviously, designed to take care of squatters. They can
get only as many credit cards with different addresses before triggering
alarms of financial supervision bodies.

The rule 5 is the usual method of ending a dispute. An appropriate court
of law (they know their jurisdictions, and have methods of resolving
jurisdictional disputes) issues a transfer order, and the old domain
holder complies with the order. If he doesn't this is a contempt of
court, and the state has means to enforce futher compliance. One of the
recourses against unreacheable parties is invalidation of their payment
instruments (i.e. credit cards).

The rule 6 takes care of reassignment of dormant domains and
non-cooperating unreacheable parties (following court-ordered of
invalidation of their payment instruments). Because such invalidation is
carried out in the same country as the registry, and registry accepts only
payments with instruments issued by banks in the same national
jurisdiction, the national courts can take effective measures to force
payment-based validation to fail.

The rule 7 is also quite obvious.

None of those rules require any manual processing or registry's
involvement in the dispute resolution. By the virtue of being automatic,
they also strengthen registry's protection from liability claims (i.e.
registry does not make decisions who should own what while providing a
method of recourse through existing legal system).

--vadim

4) exponential fee increments for registering domains with the same
   payer's physical address and/or name.

Yeah so I don't like this suggestion at all. What if a company has several business units each with its own domain name, with the same address, and with a shared accounting department. Or an ISP that offers to pay for its customers domain if they prepay for a year. Or someone like me who owns several domains?
Nope I really dont' like this suggestion, the other ones seem to be more thought out.

-Vince

What right does the government have in preventing people from having
multiple domains and trading/selling them? Thats none of your (or)
the government's business.

Although debating the latest personal diatribes about ICANN may be
entertaining, there's a closer threat on the horizon:

HR 1542 is up for vote tomorrow!

http://www.newnetworks.com/TauzinDingellisevil.htm

Have you called your representative(s)?

Have you asked your customers to call/email theirs?

Shouldn't the Tauzin/Dingell Bill really be renamed "2002 Death of the
CLEC Act"? This is just plain bad legislation anyway you cut it.

-dan
"The opinions are mine and not my employer's"

Vadim,

   Without sounding condecending, I think your view of this is rather
simplistic. The automatic assumption that ISPs can serve this role is
wrong at its very basis, since each ISP is first and foremost interested
in making money. If not, it wont last. With this set of priorities, an ISP
cannot hold this function.

   I can go on about this topic for quite a long time, but since it's
NANOG, I'll spare you all, and Vadim and I can take it to private
channels.

--Ariel

Although debating the latest personal diatribes about ICANN may be
entertaining, there's a closer threat on the horizon:

Thankfully it's not an OR operation...

HR 1542 is up for vote tomorrow!

index2001.html

Have you called your representative(s)?

I did, and hope all you do too. Took all of 30 seconds(you should have a
brief one or two sentences on your position.) There is a link off of
the site William offered that will help you locate your representative.

/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
                               Patrick Greenwell
         Asking the wrong questions is the leading cause of wrong answers
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/

Unfortunately, the concept is totally borked right here, mostly
because of the use of DNS as a yellow-pages. Two companies that own
trademarks in different fields of business both have to register under
.COM (ok, so they *could* register under .US - hah), with the obvious
outcomes we've known to love and enjoy (Anybody remember who the
*original* owner of abc.com was?)

There's no way you can pile 23 million (or however many it is now) things
into one level of namespace and actually expect people to play nicely.

> 1) first-come first-served registration

Unfortunately, the concept is totally borked right here, mostly
because of the use of DNS as a yellow-pages. Two companies that own
trademarks in different fields of business both have to register under
.COM (ok, so they *could* register under .US - hah), with the obvious
outcomes we've known to love and enjoy (Anybody remember who the
*original* owner of abc.com was?)

That's the point. Two (or more) companies don't *HAVE* to fight for identical flat space. This unique naming thing is all fine and good, but it is highly explosive/toxic within a confined space - especially one that is artificially constrained. The name space is fortunately flexible enough to accommodate competing companies and identical marks.

The alt.roots have already provided a working proof of concept without all the B.S. I'd even to so far as to say Randy Bush's recent description of an ideal ICANN ("icann only needs to a) coordinate allocation of address space to the RIRs, b) maintain the root zone file, c) slowly try to get MOUs with the folk icann actually serves") describes ORSC far better than it does ICANN.

There's no way you can pile 23 million (or however many it is now) things
into one level of namespace and actually expect people to play nicely.

Aw... now you're preaching to the choir... :wink:

Best Regards,

Simon

You can always have as many domains as you wish -- inside your zone.
Short words is a scarce resource, and therefore their use must be
rationed in some way. The pure market approach (i.e. selling them for
flat rate) doesn't seem to be sufficient for squatter deterrence (they
nearly always lose in court, but this may be prohibitively expensive for
those who have legitimate reasons for obtaining those domain names).

--vadim

ISPs have interest in making money, right. To make money they have to
provide a useful service to customer. Internet w/o functioning DNS is not
useful. Therefore ISPs have quite strong interest in keeping DNS
infrastructure running.

The ICANN silliness in regard to dispute resolution policies left
registrars exposed to various kinds of litigation, which can concievably
cause serious disruptions in name service operation. Besides, ISPs spend
significant amount of resources helping their customers to deal with
Network Solutions and other registrars. It is all costs, and no gain.

--vadim

Yep, I agree. Replacing DNS completely with hyperlinks from various
directories would be a good thing. But, unfortunately, most of the
existing software won't work w/o DNS.

--vadim

Simon,

You can always have as many domains as you wish -- inside your zone.
Short words is a scarce resource, and therefore their use must be
rationed in some way.

Thats up to the TLD holder to decide, not for some regulatory body
that claims to have the right to control what all TLD Holders do.

Thats why we have multiple root server networks now, because ICANN
wont recognize established TLDs unless these registries sign their lives
away (and the rights/lives of their registrars and registrants) to ICANN.

ICANN is a monopoly at the root level. In its current form, it MUST die
if the internet is to remain free. The proposed new form is even more
hideous.

We operate one of the ORSC root servers (H.ROOT-SERVERS.ORSC) and
have seen a FIVE FOLD increase in traffic since the "big announcement"
yesterday.

The pure market approach (i.e. selling them for
flat rate) doesn't seem to be sufficient for squatter deterrence (they
nearly always lose in court, but this may be prohibitively expensive for
those who have legitimate reasons for obtaining those domain names).

Squatter = = someone who swipes a domain name that is someone else's
trademark. I'm not talking about those. There are people who register
common words like HOUSES.USA and GREEN.EARTH. There is
nothing wrong with that. Our registry WILL NOT impose unneccessary
restrictions on our customers.

--vadim

John

Two of the major root server networks are: ORSC (http://www.open-rsc.org)
and PacificRoot (http://www.pacroot.net)
We are at www.adns.net

David,

> That's the point. Two (or more) companies don't *HAVE* to fight for
> identical flat space.

Most people want to be able to get to the same server when they type the
same domain name from two different places.

Yes. That's how it's supposed to work. What exactly is your point here?

Sorry this doesn't conform with the way you want things to work.

Um... actually it does. You must be reading the Cliff notes for either Kent Crispin's "Complete Idiot's Guide to Alt.Roots", or Stuart Lynn's "The Emperor's Dress Code."

The bottom line is that expanding the name space with additional TLDs solves this problem. Then "Two (or more) companies don't *HAVE* to fight for identical flat space" - because they are each given unique space. Duh!

Holding onto an artificially constrained flat space makes things worse. It's a really bad, bad, bad idea. Why would you even consider supporting such a thing?

Best Regards,

Simon

Last week, I told you about the bill allowing ILECs to stop selling us
lines for "high speed" networks, HR 1542.

http://www.newnetworks.com/TauzinDingellisevil.htm

Unfortunately, it passed the House, and now we have to kill it in the
Senate.

Well, here's what Dingell said about CLECs and ISPs on the House floor:

"There has been a great deal of whining and complaining by a group of
monopolists, would-be monopolists and parasites who do not want the
legislation. " [Congressional Record, Page: H573, Time: 11:45]

There is a chance to defeat this joker in the August Michigan primary.
Lynn Rivers is redistricted together with him, and she has a small
lead in the polling (at this time). Lynn lives near Merit in Ann Arbor,
and has been supportive of ISP and Internet issues for as long as I've
known her. (I'm very biased, I first met her when she invited
Honeyman and I to participate in an Internet privacy roundtable 7+ years
ago.)

However, Dingell has gotten a lot of money from the big 4 ILECs --
they are his biggest contributors, even bigger than auto companies.
Most of his contributions are from PACs (merely 9 individual
contributions from people that could vote for him last reporting
period). He'll be spending big bucks on TV time. That could turn
things around for him.

Lynn actually has taken very little PAC money over the years. Most of
her donations are from thousands of individuals from her district.

ISPs are going to have to step up to the plate and help. I know that
ISPs in Michigan are working on this, but we need some sort of
national effort to defeat a national problem.

It's time again for us "parasites" to swarm together.

http://www.rivers4congress.com/

In my earlier message, I used a "political term-of-art" incorrectly.
Lynn Rivers has a "demographic" advantage in her race with Dingell.

Also, Rivers for Congress does take PAC money and some PACs have been
very helpful in past years. But she relies on individual contributions
to a greater degree than most Congressional campaigners.

There, now the lawyers will rest more easily.... and you were bored
with trivia. Sorry.

The point remains, ISPs need to band together on these political issues
before we are crushed. AFAIK, the only organization we've joined
(ISP/C) doesn't do that sort of thing. Is there a group that does?

Am I the only one who is uncomfortable with turning NANOG into a political
tirade? Opposing legislation is one thing, turning it into an opportunity
to elect your favorite candidate is another.