Home / Blogs

Brussels Mandate: Community-Developed Tmch Gains Ascendancy

ICANN has tentatively agreed to proceed with the community-developed Trademark Clearinghouse (TMCH) model following two days of discussions at a specially organised informal meeting in Brussels last week.

I believe this is an important breakthrough for the intellectual property, registry and registrar communities as it provides the best harmony between technical implementation and best practice trademark protection policy.

While it is yet to be ratified, the decision to support the processes described in the community TMCH model paves the way for discussions to now focus on how to technically implement this model.

The extraordinary and somewhat unprecedented level of collaboration and negotiation from all parties involved in the TMCH discussions over the past four months warrants congratulation, as does the leadership of ICANN CEO Fadi Chehadé who has been instrumental in facilitating this agreement.

The Brussels TMCH mandate

Just weeks after holding productive workshops at ICANN 45 in Toronto, representatives from the intellectual property and business constituencies, registries, registrars and senior ICANN representatives gathered again in Brussels on 1 and 2 November to negotiate a solution to the stalemate over exactly how the TMCH should be implemented.

The aim of the meeting was to discuss issues related to the implementation of the TMCH as it is described in the Guidebook. This excluded all policy related issues regarding rights protection mechanisms outside of what has already been agreed upon in the Guidebook.

At the top of the agenda were talks to find agreement about which TMCH model best serves the interests of stakeholders—the original ICANN model or the recently published alternative community-developed model.

Concerns have been raised about the feasibility of the original ICANN model. I, and a number of other registries and registrars, have been vocal opponents of ICANN’s original TMCH model because we believe it is too complex and burdensome in the way it achieves its objectives.

In September, we released three whitepapers which described the flaws associated with ICANN’s model and offered an overview of why the community-developed implementation model would achieve the same objectives without these burdens.

After many hours of deliberation, agreement was formed to support the community-developed model and proceed with discussions about how to technically implement it.

The next step

The decision to move forward with the community-developed model means we are now one (big) step closer to building a fully functional TMCH in time for the first delegation of new Top-Level Domains (TLD) which is set to occur in 2013.

This should come as welcome news to all new TLD applicants.

As agreed in Brussels last week, the next step in this process will be a meeting in Los Angeles on 15 and 16 of November to finalise the technical details of the implementation of the TMCH. These details have been missing from all previous discussions because of the lack of certainty about which model would be utilised.

Now that there is agreement on the implementation as described in the community-developed model, we can proceed with discussions about the nitty-gritty technical details involving the integration between registries, registrars and the clearinghouse provider.

Following the Los Angeles meeting, work will begin on writing the TMCH implementation specifications. ICANN will then finalise contractual agreements with the TMCH provider in anticipation of go-live shortly thereafter.

This is a remarkable turnaround in events considering the entire new TLD program was at risk if a workable solution could not be found. There is now light at the end of the tunnel and this is credit to the extensive collaboration that has been seen throughout the development of the TMCH.

Congratulations to everyone involved and well done. We are nearly there.

Filed Under

Comments

Comment Title:

  Notify me of follow-up comments

We encourage you to post comments and engage in discussions that advance this post through relevant opinion, anecdotes, links and data. If you see a comment that you believe is irrelevant or inappropriate, you can report it using the link at the end of each comment. Views expressed in the comments do not represent those of CircleID. For more information on our comment policy, see Codes of Conduct.

CircleID Newsletter The Weekly Wrap

More and more professionals are choosing to publish critical posts on CircleID from all corners of the Internet industry. If you find it hard to keep up daily, consider subscribing to our weekly digest. We will provide you a convenient summary report once a week sent directly to your inbox. It's a quick and easy read.

I make a point of reading CircleID. There is no getting around the utility of knowing what thoughtful people are thinking and saying about our industry.

VINTON CERF
Co-designer of the TCP/IP Protocols & the Architecture of the Internet

Related

Topics

Brand Protection

Sponsored byCSC

IPv4 Markets

Sponsored byIPv4.Global

New TLDs

Sponsored byRadix

DNS

Sponsored byDNIB.com

Threat Intelligence

Sponsored byWhoisXML API

Domain Names

Sponsored byVerisign

Cybersecurity

Sponsored byVerisign