<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:admin="http://webns.net/mvcb/"
	xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
	<channel>
		<title>Patrick Vande Walle &#45; CircleID</title>
		<link>http://www.circleid.com/</link>
		<description>Postings from Patrick Vande Walle on CircleID</description>
		<dc:language>en</dc:language>
		<dc:rights>Copyright 2008, unless where otherwise noted.</dc:rights>
		<dc:date>2008-08-09T08:44:00-08:00</dc:date>
		

		
		<item>
			<title> ICANN to Auction New Generic Top Level Domains (Featured Blog)</title>
			<guid isPermaLink="true">http://www.circleid.com/posts/88984_icann_auction_new_top_level_domains</guid>
			<link>http://www.circleid.com/posts/88984_icann_auction_new_top_level_domains</link>
			<description><![CDATA[<a href="http://www.icann.org">ICANN</a> has just <a href="http://icann.org/en/topics/economic-case-auctions-08aug08-en.pdf" >published a paper</a> from its contractor PowerAuctions LLC, regarding the use of auctions to award new Top Level Domains (TLD) strings in case of contention. I can understand what ICANN wants to avoid. In the past, it has been criticized for using the "beauty contest" model with the redelegation of the .net TLD... However, the auction model is based on the idea that whoever wins the auction will be able to recoup its investment on the sale... <a href="http://www.circleid.com/posts/88984_icann_auction_new_top_level_domains">More...</a>]]></description>
			<dc:date>2008-08-09T08:44:00-08:00</dc:date>
		</item>
		
		<item>
			<title> IPv6 Considered a Problem by Some Users (Featured Blog)</title>
			<guid isPermaLink="true">http://www.circleid.com/posts/ipv6_considered_a_problem</guid>
			<link>http://www.circleid.com/posts/ipv6_considered_a_problem</link>
			<description><![CDATA[I have a <a href="http://blogsearch.google.com/blogsearch_feeds?hl=en&q=IPv6&ie=utf-8&num=10&output=atom">Google Blog Search Alert</a> looking for posts over IPv6 in my RSS reader. What strikes me is the number of posts explaining how to disable IPv6 in Windows Vista, MacOSX, <a href="http://www.ubuntu.com/">Ubuntu</a> and other flavours of Linux. It looks like disabling IPv6 makes web browsing faster for a lot of people, independently of which operating system is being used. <a href="http://www.circleid.com/posts/ipv6_considered_a_problem">More...</a>]]></description>
			<dc:date>2008-08-07T11:18:00-08:00</dc:date>
		</item>
		
		<item>
			<title> Gartner on New Generic Top Level Domains (Featured Blog)</title>
			<guid isPermaLink="true">http://www.circleid.com/posts/87111_gartner_new_top_level_domains</guid>
			<link>http://www.circleid.com/posts/87111_gartner_new_top_level_domains</link>
			<description><![CDATA[<a href="http://www.gartner.com/">Gartner</a>, the well known IT consulting company, <a href="http://gartner.com/DisplayDocument?doc_cd=159489">has published a report on the new top level domains</a> that will appear some time next year. The report totally misses the mark. In a pure US centric vision, it focuses on ".com" as the must-have TLD, totally overlooking the fact that a ".com" is mostly worthless e.g. in Germany, where ".de" is the TLD one must have to succeed locally... <a href="http://www.circleid.com/posts/87111_gartner_new_top_level_domains">More...</a>]]></description>
			<dc:date>2008-07-11T12:22:00-08:00</dc:date>
		</item>
		
		<item>
			<title> New Generic Top-Level Domains and Internet Standards (Featured Blog)</title>
			<guid isPermaLink="true">http://www.circleid.com/posts/new_top_level_domains_internet_standards</guid>
			<link>http://www.circleid.com/posts/new_top_level_domains_internet_standards</link>
			<description><![CDATA[<a href="http://www.icann.org/en/announcements/announcement-4-26jun08-en.htm">The recent decision</a> by ICANN to start a new round of applications for new generic Top-Level Domains (gTLDs) is launching a <a href="http://www.ietf.org/mail-archive/web/ietf/current/maillist.html">round of questions</a> on the <a href="http://www.ietf.org">IETF</a> side about its consequences. One possible issue may be with vanity gTLDs like apple, ebay etc. Some expect that every Fortune 1,000,000 company will apply for its own TLD. My guess is rather the Fortune 1,000 for a start, but this does not change the nature of the issue, i.e. those companies may want to use email addresses like user@tld. <a href="http://www.circleid.com/posts/new_top_level_domains_internet_standards">More...</a>]]></description>
			<dc:date>2008-07-07T06:51:00-08:00</dc:date>
		</item>
		
		<item>
			<title> Proposal for .sport, a New Top-Level Domain (Featured Blog)</title>
			<guid isPermaLink="true">http://www.circleid.com/posts/icann_sport_top_level_domain</guid>
			<link>http://www.circleid.com/posts/icann_sport_top_level_domain</link>
			<description><![CDATA[OK. Now my lawyer has <a href="http://domainernews.net/?p=452">given me the green light</a>, I can officially announce I am working on a proposal for a <a href="http://www.dotsport.info/">.sport TLD</a>, to be submitted to <a href="http://www.icann.org/">ICANN</a> for consideration as a new TLD next year. There is still a long way to go in terms of getting the proposal ready, but I this this one is a winner... <a href="http://www.circleid.com/posts/icann_sport_top_level_domain">More...</a>]]></description>
			<dc:date>2008-06-12T15:18:00-08:00</dc:date>
		</item>
		
		<item>
			<title> Domain Names Users vs Domain Names Registrants (Featured Blog)</title>
			<guid isPermaLink="true">http://www.circleid.com/posts/domain_names_users_vs_registrants</guid>
			<link>http://www.circleid.com/posts/domain_names_users_vs_registrants</link>
			<description><![CDATA[Antony Van Couvering from <a href="http://www.namesatwork.com/about/nameswork-team/antony-van-couvering/">names@work</a> writes that <a href="http://www.icann.org/">ICANN</a>'s constituencies are a "<a href="http://www.namesatwork.com/blog/2008/06/08/icann-constituencies-bad-idea-whose-time-has-gone">bad idea</a>". While I am not sure to agree with him on the general principle, he makes some interesting remarks. Among others, he points out that the Generic Names Supporting Organization (GNSO) includes groups that seem to be redundant (the Business and Intellectual Property constituencies) and others like domainers which are not represented in the ICANN arena, yet are an integral part of the domain name business... <a href="http://www.circleid.com/posts/domain_names_users_vs_registrants">More...</a>]]></description>
			<dc:date>2008-06-09T06:36:00-08:00</dc:date>
		</item>
		
		<item>
			<title> European Commission Pushes IPv6 Forward (Featured Blog)</title>
			<guid isPermaLink="true">http://www.circleid.com/posts/85288_european_commission_pushes_ipv6</guid>
			<link>http://www.circleid.com/posts/85288_european_commission_pushes_ipv6</link>
			<description><![CDATA[The European Commission has released a <a href="http://ec.europa.eu/information_society/policy/ipv6/docs/european_day/communication_final_27052008_en.pdf">communication on IPv6</a>, in time for the <a href="http://ec.europa.eu/information_society/policy/ipv6/events/index_en.htm">IPv6 Day</a> in Brussels next 30th May. It goes in the same direction as the<a href="http://www.oecd.org/dataoecd/7/1/40605942.pdf"> report presented at the OECD Ministerial meeting</a> on "Future of the Internet Economy", that was held in Seoul, Korea earlier this month. At the same time, the <a href="http://ec.europa.eu/information_society/doc/factsheets/066-ipv6-en.pdf">Commission committed to make its own web services available on IPv6</a> by 2010. It is good to see that intergovermental organizations take the lead on this, after 10 years of failure of the private sector to actually deploy IPv6... <a href="http://www.circleid.com/posts/85288_european_commission_pushes_ipv6">More...</a>]]></description>
			<dc:date>2008-05-28T08:39:00-08:00</dc:date>
		</item>
		
		<item>
			<title> Are Domain Name Registrars Ready for IPv6? (Featured Blog)</title>
			<guid isPermaLink="true">http://www.circleid.com/posts/84410_domain_registrars_ipv6</guid>
			<link>http://www.circleid.com/posts/84410_domain_registrars_ipv6</link>
			<description><![CDATA[Now that <a href="http://www.icann.org">ICANN</a> has <a href="http://www.icann.org/announcements/announcement-04feb08.htm">added IPv6 name servers for the root zone</a>, and that many registries have enabled IPv6 on their DNS servers, I thought it would have been easy to update the DNS records pointing to my domain to mention a IPv6-only DNS server. This way, we could have native name resolution end-to-end in IPv6. We are not there yet, it seems. <a href="http://www.circleid.com/posts/84410_domain_registrars_ipv6">More...</a>]]></description>
			<dc:date>2008-04-04T11:13:00-08:00</dc:date>
		</item>
		
		<item>
			<title> Luxembourg to Offer Investor-friendly Legal Environment for Domain Names (Featured Blog)</title>
			<guid isPermaLink="true">http://www.circleid.com/posts/811110_luxembourg_investor_sdomain_names</guid>
			<link>http://www.circleid.com/posts/811110_luxembourg_investor_sdomain_names</link>
			<description><![CDATA[<a href="http://www.eurodns.com/">EuroDNS</a>, the Luxembourg registrar, used its well attended New Year party last Wednesday to invite the Minister of Telecoms, Jean-louis Schiltz to talk about a law voted at the end of December 2007. According to the Finance and Budget Commission Report on Draft Law 5801, Revenues generated from use of, or license to use, a Domain Name are exempted from Luxembourg corporate taxes up to 80%. <a href="http://www.circleid.com/posts/811110_luxembourg_investor_sdomain_names">More...</a>]]></description>
			<dc:date>2008-01-11T11:33:00-08:00</dc:date>
		</item>
		
		<item>
			<title> Whois: If You Want Privacy, Pay For It (Featured Blog)</title>
			<guid isPermaLink="true">http://www.circleid.com/posts/71199_whois_privacy_pay_for_it</guid>
			<link>http://www.circleid.com/posts/71199_whois_privacy_pay_for_it</link>
			<description><![CDATA[Netchoice, a lobbying group for the e-commerce industry had a <a href="http://www.netchoice.org/press/netchoice-responds-to-icann-decision-not-to-change-whois-service.html">strange reaction</a> on the failure of the <a href="http://gnso.icann.org/">GNSO</a> working group on Whois to reach a consensus. After all, they say, <em>"Privacy concerns with Whois that were identified years ago have already been addressed by in the marketplace"</em>... <a href="http://www.circleid.com/posts/71199_whois_privacy_pay_for_it">More...</a>]]></description>
			<dc:date>2007-11-09T10:39:00-08:00</dc:date>
		</item>
		
		<item>
			<title> Developing Internet Standards: How Can the Engineering Community and the Users Meet? (Featured Blog)</title>
			<guid isPermaLink="true">http://www.circleid.com/posts/79197_developing_internet_standards_engineers</guid>
			<link>http://www.circleid.com/posts/79197_developing_internet_standards_engineers</link>
			<description><![CDATA[There is currently a discussion going on between <a href="http://blog.internetgovernance.org/blog/_archives/2007/9/9/3217425.html">Milton Mueller</a> and <a href="http://stupid.domain.name/node/410">Patrik Fältström</a> over the deployment of DNSSEC on the root servers. I think the discussion exemplifies the difficult relation between those who develop standards and those who use them. On the one hand, Milton points out that the way the signing of the root zone will be done will have a great influence on the subjective trust people and nation states will have towards the system. On the other hand, Patrik states that "DNSSEC is just digital signatures on records in this database". Both are right, of course, but they do not speak the same language... <a href="http://www.circleid.com/posts/79197_developing_internet_standards_engineers">More...</a>]]></description>
			<dc:date>2007-09-19T08:57:00-08:00</dc:date>
		</item>
		
		<item>
			<title> The Inextricable Issue of Internationalized Domain Names (Featured Blog)</title>
			<guid isPermaLink="true">http://www.circleid.com/posts/inextricable_internationalized_domain_names</guid>
			<link>http://www.circleid.com/posts/inextricable_internationalized_domain_names</link>
			<description><![CDATA[<a href="http://www.icann.org/">ICANN</a> has embarked on the IDN boat at the same time it wants to introduce DNSSEC and new gTLDs. This promises lots of fun. Or grey hair, depending how you look at it. First is the issue of country code IDNs. The ISO-3166 table, based on two letter codes, is a western convention. Some cultures do not use abbreviations or acronyms. Some do not use a character-based alphabet, but a syllabic one. Hence, the next logical step would be to represent the full country name in local script, rather than a transliteration of the ISO string... Imagine the case of India, <a href="http://en.wikipedia.org/wiki/Languages_of_India">where there are 1.652 languages</a>, of which 24 are spoken by more than one million people... <a href="http://www.circleid.com/posts/inextricable_internationalized_domain_names">More...</a>]]></description>
			<dc:date>2007-07-05T10:08:00-08:00</dc:date>
		</item>
		
		<item>
			<title> What Prevents IPv6 Deployment in Europe (Featured Blog)</title>
			<guid isPermaLink="true">http://www.circleid.com/posts/what_prevents_ipv6_deployment_europe</guid>
			<link>http://www.circleid.com/posts/what_prevents_ipv6_deployment_europe</link>
			<description><![CDATA[<a href="http://news.zdnet.co.uk/communications/0,1000000085,39287566,00.htm">ZDNet UK</a> has an article on IPv6 and what may slow down its deployment. Jay Daley, from Nominet points out to the fact that the current IPv6 allocation policy used by <a href="http://www.ripe.net">RIPE</a> NCC is geared towards ISPs. This is a complaint I have heard time and time again. Under the current policy, you have to show to RIPE NCC that you are going to allocate 200 address blocks to your customers before you are allocated a /32 block. Obviously, a large corporate network cannot afford to renumber every time it switches ISPs... <a href="http://www.circleid.com/posts/what_prevents_ipv6_deployment_europe">More...</a>]]></description>
			<dc:date>2007-06-18T10:29:00-08:00</dc:date>
		</item>
		
		<item>
			<title> IPv6 for the Rest of Us (Featured Blog)</title>
			<guid isPermaLink="true">http://www.circleid.com/posts/deploying_ipv6_implementation_rest_of_us</guid>
			<link>http://www.circleid.com/posts/deploying_ipv6_implementation_rest_of_us</link>
			<description><![CDATA[IPv6 deployment is in a chicken and egg situation. On the one hand, there is no willingness from ISPs and commodity DNS router manufacturers to include IPv6 support in their infrastructure or equipment because "there is no demand". On the other hand, there is no demand because the average Joe Blow could not care less if he accesses a web site under IPv4 or IPv6. It should just work. The equipment and infrastructure should adapt transparently... What we users can do is to stop waiting for the industry to get its act together and work around its limitations... <a href="http://www.circleid.com/posts/deploying_ipv6_implementation_rest_of_us">More...</a>]]></description>
			<dc:date>2007-06-04T16:53:00-08:00</dc:date>
		</item>
		
		<item>
			<title> .XXX is Back on the Radar Screen (Featured Blog)</title>
			<guid isPermaLink="true">http://www.circleid.com/posts/xxx_back_on_radar_screen</guid>
			<link>http://www.circleid.com/posts/xxx_back_on_radar_screen</link>
			<description><![CDATA[The DoC seems to have finally realized it went too far by using ICANN to serve the interests of some conservative groups, as mentioned in a <a href="http://patrick.vande-walle.eu/internet/icann/xxx-and-conservative-groups/">previous post</a>. The new story is now that the ICANN board did not reject the .XXX application as such, but only the agreement negotiated between ICM Registry and the ICANN staff at that time. How subtle these things are... <a href="http://www.circleid.com/posts/xxx_back_on_radar_screen">More...</a>]]></description>
			<dc:date>2007-01-08T09:25:00-08:00</dc:date>
		</item>
		
	</channel>
</rss>