[Tmch-iag] T1 Data Locations

[Chris Wright]

Coming in late here I know,

The problem with your calculations Tom is that you have used average loads, systems need to be designed to sustain peak loads, not average load otherwise they go down. This is something that Registries are all too familiar with. Also, at least in our experience, your ratio of check to create commands is off by a very large factor its more in the region of 500-1000:1.

Thanks


Chris Wright
Chief Technology Officer
---------------------------------------------------------------------------------------
ARI REGISTRY SERVICES
Level 8, 10 Queens Road. Melbourne. Victoria. Australia. 3004.
P  +61 3 9866 3710  F  +61 3 9866 1970  M  +61 401 873 798
E  chris.wright at ariservices.com
ariservices.com
---------------------------------------------------------------------------------------
ARI Registry Services is an evolution of AusRegistry International.
Follow us on Twitter
---------------------------------------------------------------------------------------
The information contained in this communication is intended for the named recipients only. It is subject to copyright and may contain legally privileged and confidential information and if you are not an intended recipient you must not use, copy, distribute or take any action in reliance on it. If you have received this communication in error, please delete all copies from your system and notify us immediately.


-----Original Message-----
From: tmch-iag-bounces at icann.org [mailto:tmch-iag-bounces at icann.org] On Behalf Of Tom Barrett
Sent: Tuesday, 31 January 2012 9:37 AM
To: tmch-iag at icann.org
Subject: [Tmch-iag] T1 Data Locations



IAG T1 comments - Distribution of TMCH Data January 30, 2012 Tom Barrett - EnCirca

The main topic of discussion for the IAG last week was concerned with distribution of TMCH data.

After comparing estimates of the maximum volumes for the TMCH to the query volume, uptime and responsiveness of existing registries, it seems very clear that the TMCH data could be kept solely in a central database utilizing a technical architecture similar in scale to some of the existing smaller gTLD registries, such as .MOBI and .TEL.  This level of architecture for the TMCH could ensure the uptime and responsiveness required by registries and registrars while satisfying the trademark owner concerns for data security.

We agree with and confirm the following:
. The TMCH data is proprietary to trademark owners and is not currently in the public domain . Prevention of data mining should be a priority for the TMCH . Distributing the TMCH data makes data mining impossible to prevent . Distribution of the TMCH data is not even necessary given the expected scale of the TMCH

Please see the attached document for a detailed examination of these issues, including an analysis of how big the TMCH needs to be compared to existing gTLD registries.

I look forward to your comments.

Best regards,

Tom Barrett
EnCirca