<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>e-sygoing.link — Uniform Domain Name Dispute Resolution Policy</title>
  <link>https://e-sygoing.link</link>
  <description>Latest links in the Uniform Domain Name Dispute Resolution Policy category</description>
  <language>en-us</language>
  <lastBuildDate>Sun, 24 May 2026 15:18:59 -0400</lastBuildDate>
  <atom:link href="https://e-sygoing.link/rss.php?type=new&amp;cid=92874"
             rel="self" type="application/rss+xml"/>
    <item>
    <title>Domain Name Dispute Process Called Into Question</title>
    <link>https://e-sygoing.link/link/5729929-domain-name-dispute-process-called-into-question</link>
    <description>&quot;The Register has an article about a study of the domain name dispute resolution process. The study accuses domain arbitrators of &#039;actively choosing judges who favoured complainants (trademark holders).&#039;&quot; News and discussion forum. [Slashdot]</description>
    <pubDate>Thu, 02 Apr 2026 16:11:32 -0400</pubDate>
    <guid isPermaLink="false">https://e-sygoing.link/go/5729929</guid>
  </item>
    <item>
    <title>Evaluating the Uniform Domain Name Dispute Resolution Policy</title>
    <link>https://e-sygoing.link/link/5729928-evaluating-the-uniform-domain-name-dispute-resolution-policy</link>
    <description>Students affiliated with Harvard Law School&#039;s Berkman Center for Internet &amp; Society drew up this presentation for a panel discussion of ICANN&#039;s policy agenda.</description>
    <pubDate>Sun, 02 Nov 2025 07:42:42 -0500</pubDate>
    <guid isPermaLink="false">https://e-sygoing.link/go/5729928</guid>
  </item>
    <item>
    <title>Balancing the Crucible</title>
    <link>https://e-sygoing.link/link/5729933-balancing-the-crucible</link>
    <description>Explores the conflict concerning the control of trademarked domain names and the relationship between businesses and non-mark holder uses under the Uniform Domain Name Resolution Policy. [Requires frames.]</description>
    <pubDate>Wed, 09 Jul 2025 10:05:34 -0400</pubDate>
    <guid isPermaLink="false">https://e-sygoing.link/go/5729933</guid>
  </item>
    <item>
    <title>ICANN: UDRP</title>
    <link>https://e-sygoing.link/link/5729922-icann-udrp</link>
    <description>Official documents about and records of proceedings under the UDRP.</description>
    <pubDate>Tue, 13 May 2025 09:28:36 -0400</pubDate>
    <guid isPermaLink="false">https://e-sygoing.link/go/5729922</guid>
  </item>
    <item>
    <title>Fair Domain-Dispute Arbitration Firm Quits the Business</title>
    <link>https://e-sygoing.link/link/5729931-fair-domain-dispute-arbitration-firm-quits-the-business</link>
    <description>&quot;EResolution has decided to quit the Domain Name Dispute- Resolution business because its reputation for being fair has driven away its potential customers - the trademark holders who are filing the complaints.&quot; News and reader discussion. [Slashdot]</description>
    <pubDate>Sun, 08 Sep 2024 08:11:17 -0400</pubDate>
    <guid isPermaLink="false">https://e-sygoing.link/go/5729931</guid>
  </item>
    <item>
    <title>The UDRP: Is It Un-Fair.com?</title>
    <link>https://e-sygoing.link/link/5729927-the-udrp-is-it-un-faircom</link>
    <description>News and reader comments about law professor&#039;s findings of bias in the domain-dispute resolution process. [Slashdot]</description>
    <pubDate>Sat, 22 Jun 2024 22:15:36 -0400</pubDate>
    <guid isPermaLink="false">https://e-sygoing.link/go/5729927</guid>
  </item>
    <item>
    <title>UDRPinfo.com</title>
    <link>https://e-sygoing.link/link/5729919-udrpinfocom</link>
    <description>Practical policy and statistical information relating to the  ICANN&#039;s UDRP (Uniform Domain-Name Dispute Resolution Policy), links to UDRP providers, policies, decisions, panelist profiles and an e-mail update service.</description>
    <pubDate>Thu, 04 Apr 2024 02:16:11 -0400</pubDate>
    <guid isPermaLink="false">https://e-sygoing.link/go/5729919</guid>
  </item>
  </channel>
</rss>
