<?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: Domain name geekery</title>
	<atom:link href="http://blog.dominicsayers.com/2009/01/27/domain-name-geekery/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.dominicsayers.com/2009/01/27/domain-name-geekery/</link>
	<description></description>
	<lastBuildDate>Tue, 27 Jul 2010 20:53:53 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dominic Sayers</title>
		<link>http://blog.dominicsayers.com/2009/01/27/domain-name-geekery/comment-page-1/#comment-386</link>
		<dc:creator>Dominic Sayers</dc:creator>
		<pubDate>Tue, 27 Jan 2009 11:04:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dominicsayers.com/?p=358#comment-386</guid>
		<description>OK, I&#039;ve answered my own question. RFC 1035 is &quot;liberalized&quot; by RFC 1123, specifically to allow domain labels to begin with a digit.

The confusion arises because the comparitively recent RFC 5321 refers back to RFC 1035 as its host name authority without mentioning RFC 1123. RFC 1035 is NOT marked as updated by RFC 1123.

So anybody reading RFC 5321 (i.e. me) could be forgiven for thinking that RFC 1035 was still in full effect.

It isn&#039;t. Sort it out, IETF.</description>
		<content:encoded><![CDATA[<p>OK, I&#8217;ve answered my own question. RFC 1035 is &#8220;liberalized&#8221; by RFC 1123, specifically to allow domain labels to begin with a digit.</p>
<p>The confusion arises because the comparitively recent RFC 5321 refers back to RFC 1035 as its host name authority without mentioning RFC 1123. RFC 1035 is NOT marked as updated by RFC 1123.</p>
<p>So anybody reading RFC 5321 (i.e. me) could be forgiven for thinking that RFC 1035 was still in full effect.</p>
<p>It isn&#8217;t. Sort it out, IETF.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
