Please Whitelist This Site?

I know everyone hates ads. But please understand that I am providing premium content for free that takes hundreds of hours of time to research and write. I don't want to go to a pay-only model like some sites, but when more and more people block ads, I end up working for free. And I have a family to support, just like you. :)

If you like The TCP/IP Guide, please consider the download version. It's priced very economically and you can read all of it in a convenient format without ads.

If you want to use this site for free, I'd be grateful if you could add the site to the whitelist for Adblock. To do so, just open the Adblock menu and select "Disable on tcpipguide.com". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||tcpipguide.com^$document". Then just click OK.

Thanks for your understanding!

Sincerely, Charles Kozierok
Author and Publisher, The TCP/IP Guide


NOTE: Using software to mass-download the site degrades the server and is prohibited.
If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.

The Book is Here... and Now On Sale!

Searchable, convenient, complete TCP/IP information.
The TCP/IP Guide

Custom Search







Table Of Contents  The TCP/IP Guide
 9  TCP/IP Application Layer Protocols, Services and Applications (OSI Layers 5, 6 and 7)
      9  Name Systems and TCP/IP Name Registration and Name Resolution
           9  TCP/IP Name Systems: Host Tables and Domain Name System (DNS)
                9  TCP/IP Domain Name System (DNS)
                     9  DNS Name Registration, Public Administration, Zones and Authorities

Previous Topic/Section
DNS Second-Level and Lower Domains, Delegation of Registration Authority and Public Registration
Previous Page
Pages in Current Topic/Section
123
4
Next Page
DNS Name Space Administrative Hierarchy Partitioning: DNS Zones of Authority
Next Topic/Section

DNS Public Registration Disputes (Conflicts, Cybersquatting, "Deceptive Naming", Etc.) and Dispute Resolution
(Page 4 of 4)

The Uniform Domain Name Dispute Resolution Policy

Lawsuits are expensive and time consuming, so there was a desire that some other mechanism exist for resolving these conflicts as well. Since the authority for each TLD controls what happens within it, it also has the right to create its own policies for how to deal with these sorts of issues. For the generic TLDs, the original registering authority, the InterNIC, had a dispute resolution policy that allowed someone with a complaint to challenge a domain name registration if they had a trademark interest in that name. The policy was controversial for a number of reasons, not the least of which because it led to some domain names being successfully challenged even if there was no proof of trademark infringement.

The current authority for the generic TLDs, IANA/ICANN, created a new Uniform Domain Name Dispute Resolution Policy (UDRP) in 1999, to better handle domain name conflicts. This policy specifies a procedure whereby a company that has a valid trademark can challenge a domain name if it either infringes on the trademark, is confusingly similar to it, or if the name was registered by someone else in bad faith. At the same time, it also lists ways that the original registrant can prove that the registration is valid and should be maintained. This new system eliminates many of the real problems described above, such as deceptive naming, “corporate warfare” and cybersquatting, while not automatically allowing a second-comer to shut down a legitimate domain.

Disputes as a Motivation for New Generic TLDs

Incidentally, it was all this nonsense that led, in part, to the clamor for new generic top level domains. In the interest of fairness, I also want to mention that even though more complicated TLDs like the old strictly hierarchical .US are not very popular, they have a huge advantage over the generic domains. Since all registrations there are geographic, there are far fewer conflicts, because a dispute requires that two organizations have the same name and also be in the same state and town.

For example, you could still have three “Joe's Pizza Parlor”s in Chicago duke it out, but it's not likely that you'd see big companies on the mat in .US. For example, the ACME Furniture Company might use “acme.seattle.wa.us”, the ACME Restaurant Supply Corporation “acme.mendocino.ca.us” and ACME Footwear, Inc. could go with “acme.anchorage.ak.us”.


Previous Topic/Section
DNS Second-Level and Lower Domains, Delegation of Registration Authority and Public Registration
Previous Page
Pages in Current Topic/Section
123
4
Next Page
DNS Name Space Administrative Hierarchy Partitioning: DNS Zones of Authority
Next Topic/Section

If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support!
Donate $2
Donate $5
Donate $10
Donate $20
Donate $30
Donate: $



Home - Table Of Contents - Contact Us

The TCP/IP Guide (http://www.TCPIPGuide.com)
Version 3.0 - Version Date: September 20, 2005

© Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.