<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Dot .tel Top Level Domain Names December Sunrise</title>
	<atom:link href="http://website101.com/domain-name/dot-tel-top-level-domain-names-december-sunrise/feed/" rel="self" type="application/rss+xml" />
	<link>http://website101.com/domain-name/dot-tel-top-level-domain-names-december-sunrise/</link>
	<description>Entrepreneurs &#38; Innovation</description>
	<lastBuildDate>Mon, 24 Oct 2011 22:27:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Justin Hayward</title>
		<link>http://website101.com/domain-name/dot-tel-top-level-domain-names-december-sunrise/comment-page-1/#comment-75</link>
		<dc:creator>Justin Hayward</dc:creator>
		<pubDate>Sun, 22 Jun 2008 13:23:00 +0000</pubDate>
		<guid isPermaLink="false">http://website101.com/uncategorized/dot-tel-top-level-domain-names-december-sunrise/#comment-75</guid>
		<description>Mike,&lt;br /&gt;&lt;br /&gt;Thanks very much for the very quick and articulate analysis you&#039;ve provided.  You&#039;ve hit the nail on the head and we&#039;re very pleased about that.&lt;br /&gt;&lt;br /&gt;A couple of points.  On the privacy aspect, we&#039;re using industry standard encryption to 1028 bit for contact details stored in the DNS.  In fact, we could have used 2048, but the mobile aspect (i.e. the capability of existing devices to cope at the speed we wanted) was lacking - we may well move to that in future.  We&#039;ll continue to focus on doing the right thing from a privacy perspective for the .tel community.&lt;br /&gt;&lt;br /&gt;As to the uniqueness of the .tel domain, from an individual consumer perspective there are a host of names that can be used - from real names through to nicknames that friends give you or your gaming handles.  Yes, it&#039;s first-come, first-served, but there are other opportunities if people really think about it.  There&#039;s also the ability to describe yourself in free keywords and free text boxes to make sure that if you don&#039;t get your own name people can still find you and you can still use your .tel to be discoverable - which is what it&#039;s all about.&lt;br /&gt;&lt;br /&gt;Thanks again for your analysis&lt;br /&gt;&lt;br /&gt;Justin&lt;br /&gt;Telnic Limited</description>
		<content:encoded><![CDATA[<p>Mike,</p>
<p>Thanks very much for the very quick and articulate analysis you&#8217;ve provided.  You&#8217;ve hit the nail on the head and we&#8217;re very pleased about that.</p>
<p>A couple of points.  On the privacy aspect, we&#8217;re using industry standard encryption to 1028 bit for contact details stored in the DNS.  In fact, we could have used 2048, but the mobile aspect (i.e. the capability of existing devices to cope at the speed we wanted) was lacking &#8211; we may well move to that in future.  We&#8217;ll continue to focus on doing the right thing from a privacy perspective for the .tel community.</p>
<p>As to the uniqueness of the .tel domain, from an individual consumer perspective there are a host of names that can be used &#8211; from real names through to nicknames that friends give you or your gaming handles.  Yes, it&#8217;s first-come, first-served, but there are other opportunities if people really think about it.  There&#8217;s also the ability to describe yourself in free keywords and free text boxes to make sure that if you don&#8217;t get your own name people can still find you and you can still use your .tel to be discoverable &#8211; which is what it&#8217;s all about.</p>
<p>Thanks again for your analysis</p>
<p>Justin<br />Telnic Limited</p>
]]></content:encoded>
	</item>
</channel>
</rss>

