| | At Large Membership and Civil Society Participation in ICANN |
|
| |
|
|
|
|
This discussion has been archived.
No new comments can be posted.
|
|
Using the UDRP, when a registrar owns the domain
|
Log in/Create an Account
| Top
| 11 comments
|
Search Discussion
|
|
|
|
The Fine Print:
The following comments are owned by whoever posted them.
We are not responsible for them in any way.
|
|
 |
You don't understand how Pool.com operates. They, and their registrar network, target expiring domain names based on expressions of interest from a "pool" of customers. If the Pool network is successful in registering the domain name, it is assigned to the winner of an auction among those customers who initially wanted to register the domain name. Pool is not registering domain names for "itself" - it is indeed registering domain names in response to requests received from prospective registrants. The problem is that you are so gung-ho to go after the domain name (which you failed to pick up via Snapnames), that you aren't waiting to find out who it is that wins the assignment process.
The presence of this question on Icannwatch underscores the growing disconnect between people who knew "how things worked" four or five years ago, and people who know how they work today.
Pay attention. The ball moves.
|
|
|
|
[ Reply to This | Parent
]
|
|
|
|
|
| Starting Score: |
1 |
point |
| Moderation |
|
+1 |
|
| Extra 'Insightful' Modifier |
|
0 |
|
| Karma-Bonus Modifier |
|
+1 |
|
| Total Score: |
|
3 |
|
|
|
|
This is a good point. People need to pay attention.
The .NET is on the move. Some people are still
living in the past. They think the Internet is
composed of dial-up users connecting via ex-BBS
operators who can now afford better equipment.
The .NET is now an always-on broadband cloud
run by large telecom carriers. Packets going in
one side of the cloud may emerge from the other
side of the cloud WITHOUT a change in TTL and
without any clue what IP addresses (nodes) they
traversed.
Users are given /32 dynamic IP addresses with
a Netmask of 255.255.255.255 meaning ALL of the
bits are network address bits. The telco is
essentially handing out a temporary *handle*
to be used at the edge of the cloud. Those
handles may resemble an IP address from 10
years ago, but they are not the same. The game
has changed. The ball moves and so does the .NET.
ICANN has relied on the strong-arm network of
RIRs to enforce their DNS policies in the
ISP's DNS servers. That is no longer possible.
The always-on consumer, with one or more
high-speed links, is not beholden to an RIR
and indirectly ICANN. They get their single
IP address from their telco carrier and it is
a meaningless dynamic *handle*. The consumer's
edge device begins to shape their view of
"Internet Governance", if there is such a thing.
Consumers can now collaborate with their
high-speed always-on connections via their
edge devices. The cloud is no longer part of
the nodes they see in the collaboration. In
the old days, the cloud was made up of the
nodes. That is no longer the case. The cloud
can now be more and more opaque. That makes it
more stable and secure and removes control
and operations of the cloud from the hands of
groups like the ISOC. NANOG operators now sit
on the side-lines telling war stories about
the good old days. They no longer define the .NET.
The good news is that the telcos and broadband
carriers will create a dumb, opaque and level
playing field. The bad news is that it will
initially be a wasteland in terms of DNS and
people will naturally rush in to fill the voids.
Consumers are going to be welcomed with a wide
range of TLDs and new DNS services. ICANN will
have no say and some may observe that the free
market appears to be mass confusion, and long
for the good old days of no change and the
iron-fist rule of the IANA dictators. Eventually,
the free market will settle down and what will
emerge will be what consumers desire and define
in their edge appliances. The ISOC leaders will
of course rant and rave about trivial end-to-end
notions and claim that the edge appliances can
not be useful or made to collectively collaborate.
The ISOC leaders far underestimate the average
netizen's desire to push every boundary and their
ability to route around the blockades constructed
in the core network which is no longer there. It
is now a cloud. The ball has moved. ICANN is
frozen in time, with no place or purpose and
no ability to ever get their hands on the ball
again.
|
|
|
|
[ Reply to This | Parent
]
|
|
|
|
|
I understand what "pool.com" says they do, and some of what they actually do. It looks like what they actually do is that they have an arrangement with a registrar to allow them to register names without providing registrant data. This would appear to violate the ICANN Registrar Agreement,
section 3.7.
|
|
|
|
[ Reply to This | Parent
]
|
| |
|
|
"Pool is not registering domain names for "itself" - it is indeed registering domain names in response to requests received from prospective registrants."
Disagree with you interpretation, pool is very much registering names for itself. They are essentially a domain reseller who go after in demand names with their registrar partners then try to sell them off to the highest bidder. Showing a blank whois while the sales process is being undertaken doesn't change that.
|
|
|
|
[ Reply to This | Parent
]
|
|
|
Privacy Policy: We will not knowingly give out your personal data -- other than identifying your postings in the way you direct by setting your configuration options -- without a court order. All logos and trademarks in this site are property of their
respective owner. The comments are property of their posters, all the rest © 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 by ICANNWatch.Org. This web site was made with Slashcode, a web portal system written in perl. Slashcode is Free Software released under the GNU/GPL license.
You can syndicate our headlines in .rdf, .rss, or .xml. Domain registration services donated by DomainRegistry.com
|
