<?xml version="1.0" encoding="UTF-8" ?>

<rss version="2.0"
  xmlns:ent="http://www.purl.org/NET/ENT/1.0/"
  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
  <title>Random Bytes...by Ross Rader</title>
  <link>http://www.byte.org/blog</link>
  <description>Ross Wm. Rader&#39;s current home page. Odds and sods of current interest without much thought given to rhyme or reason. Hey, it keeps me out of trouble, hopefully it keeps you interested ;)</description>
  <language>en-us</language>
  <lastBuildDate>Tue, 05 Jan 2010 12:57:15 -0500</lastBuildDate>
  <category domain="http://www.byte.org/blog/random_bytes/Code">Code</category>
  <generator>Blogware</generator>
  
  <item>
    <dc:creator>Ross</dc:creator>
    <title>This Category has been moved.</title>
    <link>http://www.byte.org/blog/_archives/2005/11/9/1365086.html</link>
    <guid>http://www.byte.org/blog/_archives/2005/11/9/1365086.html</guid>
    <pubDate>Wed, 09 Nov 2005 10:46:00 -0500</pubDate>
    <description>&lt;p&gt;&lt;/p&gt;&lt;p&gt;&lt;img alt=&quot;Moving-truck&quot; src=&quot;http://www.byte.org/images/moving_2Dtruck.jpg&quot; align=&quot;left&quot; border=&quot;0&quot; height=&quot;157&quot; hspace=&quot;3&quot; vspace=&quot;3&quot; width=&quot;250&quot;&gt;If you are reading this, you&#8217;ll probably want to know that I&#8217;ve moved this subcategory to its own blog.&lt;/p&gt;&lt;p&gt;The web site is available at &lt;a href=&quot;http://code.byte.org/&quot;&gt;http://code.byte.org&lt;/a&gt; and the RSS 2.0 feed is available at &lt;a href=&quot;http://code.byte.org/blog/index.xml&quot;&gt;http://code.byte.org/blog/index.xml&lt;/a&gt;&lt;/p&gt;</description>
    
    <category domain="http://www.byte.org/blog/random_bytes/Code">Code</category>
    
    
    
    
  </item>
  
  <item>
    <dc:creator>Ross</dc:creator>
    <title>Verisign/ICANN Settlement: Registrars to Twomey - we&#39;re not on board</title>
    <link>http://www.byte.org/blog/_archives/2005/11/4/1343272.html</link>
    <guid>http://www.byte.org/blog/_archives/2005/11/4/1343272.html</guid>
    <pubDate>Fri, 04 Nov 2005 15:12:00 -0500</pubDate>
    <description>&lt;p&gt;&lt;a href=&quot;http://gnso.icann.org/mailing-lists/archives/registrars/msg03564.html&quot;&gt;Registrar Constituency&lt;/a&gt;: &amp;ldquo;&amp;hellip;&lt;em&gt;your statements have created some confusion within the community. We are now hearing further reports from third parties that the registrar community is generally on board with moving forward with this proposed settlement arrangement&amp;hellip;To help us resolve this confusion, we would like to request that these statements be substantiated&amp;hellip;&amp;rdquo;&lt;/em&gt;&lt;/p&gt;</description>
    
    <category domain="http://www.byte.org/blog/random_bytes/Code">Code</category>
    
    
    
    
  </item>
  
  <item>
    <dc:creator>Ross</dc:creator>
    <title>Verisign/ICANN Settlement: Complicated Name Game</title>
    <link>http://www.byte.org/blog/_archives/2005/11/3/1339483.html</link>
    <guid>http://www.byte.org/blog/_archives/2005/11/3/1339483.html</guid>
    <pubDate>Thu, 03 Nov 2005 13:21:00 -0500</pubDate>
    <description>&lt;p&gt;&lt;a href=&quot;http://www.thestreet.com/tech/internet/731641.html&quot;&gt;TheStreet.com&lt;/a&gt;: &amp;ldquo;&lt;em&gt;&quot;$12 to me is absolutely insane,&quot; says Tom McDonald, founder of domainwatch.com, a service that tracks the domain name registrations of all registrars. &quot;Who knows? They&#39;ll probably get it. They&#39;ve got quite a bit of pull and they&#39;ve been around a while.&quot; McDonald says a fair price would be less than $1 a year.&amp;rdquo;&lt;/em&gt;&lt;/p&gt;&lt;p&gt;Truer words have never been spoken. I&amp;rsquo;m surprised that we are still having this same conversation 7 years later. This article was written in 1999.&lt;/p&gt;</description>
    
    <category domain="http://www.byte.org/blog/random_bytes/Code">Code</category>
    
    
    
    
  </item>
  
  <item>
    <dc:creator>Ross</dc:creator>
    <title>More on the Verisign/Snapnames connection</title>
    <link>http://www.byte.org/blog/_archives/2005/10/31/1333829.html</link>
    <guid>http://www.byte.org/blog/_archives/2005/10/31/1333829.html</guid>
    <pubDate>Mon, 31 Oct 2005 23:59:00 -0500</pubDate>
    <description>&lt;p&gt;&lt;strike&gt;&lt;a href=&quot;http://www.verisign.com/printablePages/page_2003121709382311.html&quot;&gt;VeriSign PR:&lt;/a&gt;&amp;nbsp;&#8220;&lt;em&gt;VeriSign, Inc., the world&#39;s leading provider of domain name registration services, announced today that it has begun offering SnapNames.com, Inc.&#39;s SnapBack service&#8221;&lt;/em&gt;&lt;/strike&gt;&lt;/p&gt;&lt;p&gt;&lt;strike&gt;Is &lt;a href=&quot;http://www.byte.org/blog/_archives/2005/10/28/1328765.html&quot;&gt;a bigger deal &lt;/a&gt;&amp;nbsp;right around the corner?&lt;/strike&gt;&lt;/p&gt;Stupid news alerts. Apparently Google can&#39;t tell the difference between news from 2001 and news from today. Relevancy *AND* timeliness would be nice :)</description>
    
    <category domain="http://www.byte.org/blog/random_bytes/Code">Code</category>
    
    
    
    
  </item>
  
  <item>
    <dc:creator>Ross</dc:creator>
    <title>Verisign/ICANN Agreement: Something for Everyone</title>
    <link>http://www.byte.org/blog/_archives/2005/10/31/1333782.html</link>
    <guid>http://www.byte.org/blog/_archives/2005/10/31/1333782.html</guid>
    <pubDate>Mon, 31 Oct 2005 23:33:00 -0500</pubDate>
    <description>&lt;img height=&quot;333&quot; alt=&quot;Verisign-easter-egg-hunt&quot; hspace=&quot;3&quot; src=&quot;http://www.byte.org/images/verisign_2Deaster_2Degg_2Dhunt.jpg&quot; width=&quot;300&quot; align=&quot;right&quot; vspace=&quot;3&quot; border=&quot;0&quot; /&gt;The &lt;a href=&quot;http://wikipedia.org/&quot;&gt;Wikipedia&lt;/a&gt; defines &lt;a href=&quot;http://en.wikipedia.org/wiki/Easter_egg_(virtual)&quot;&gt;an Easter Egg &lt;/a&gt;as being &amp;ldquo;&amp;hellip;a hidden message or feature in an object such as a &lt;a title=&quot;Film&quot; href=&quot;http://en.wikipedia.org/wiki/Film&quot;&gt;movie&lt;/a&gt;, &lt;a title=&quot;Book&quot; href=&quot;http://en.wikipedia.org/wiki/Book&quot;&gt;book&lt;/a&gt;, &lt;a title=&quot;Compact disc&quot; href=&quot;http://en.wikipedia.org/wiki/Compact_disc&quot;&gt;CD&lt;/a&gt;, &lt;a title=&quot;DVD&quot; href=&quot;http://en.wikipedia.org/wiki/DVD&quot;&gt;DVD&lt;/a&gt;, or &lt;a title=&quot;Computer program&quot; href=&quot;http://en.wikipedia.org/wiki/Computer_program&quot;&gt;computer program&lt;/a&gt;.&amp;rdquo;&lt;p&gt;&lt;/p&gt;&lt;p&gt;I think they should add &amp;ldquo;settlement agreements&amp;rdquo; to the list of places where Easter Eggs are&amp;nbsp;hidden. &lt;/p&gt;&lt;p&gt;In preparing my overview of the puts and takes of &lt;a href=&quot;http://www.icann.org/tlds/agreements/verisign/settlement-agreements.htm&quot;&gt;the proposed Verisign/ICANN settlement agreements&lt;/a&gt;, I eventually made my way to &lt;a href=&quot;http://www.icann.org/tlds/agreements/verisign/registry-agmt-app5-22sep05.pdf&quot;&gt;Appendix 5&lt;/a&gt; of the new Registry Operator Agreement that Verisign and the ICANN Staff want to implement as part of the settlement. This far into the agreement, I was&amp;nbsp;expecting a fairly routine run down of Verisign&amp;rsquo;s obligations to provide Whois service and the standards it would employ in executing these functions.&lt;/p&gt;&lt;p&gt;What I got was distinctly different &amp;ndash; there is an entire new set of obligations tacked onto &lt;a href=&quot;http://www.icann.org/tlds/agreements/verisign/registry-agmt-appo-com-16apr01.htm&quot;&gt;the old 2001 language&lt;/a&gt;!&lt;img height=&quot;216&quot; alt=&quot;Icann-pdp-us-legal-system&quot; hspace=&quot;3&quot; src=&quot;http://www.byte.org/images/icann_2Dpdp_2Dus_2Dlegal_2Dsystem.jpg&quot; width=&quot;146&quot; align=&quot;left&quot; vspace=&quot;3&quot; border=&quot;0&quot; /&gt; These new clauses specify that Verisign will turn over the COM Whois file, in bulk, to a third party for the purpose of creating a centralized Whois that includes all TLD data.&lt;/p&gt;&lt;blockquote dir=&quot;ltr&quot; style=&quot;MARGIN-RIGHT: 0px&quot;&gt;&lt;p&gt;&lt;font size=&quot;1&quot;&gt;&lt;em&gt;&lt;strong&gt;excerpted from the Verisign/ICANN Settlement Agreement, Appendix 5;&lt;/strong&gt;&lt;/em&gt;&lt;/font&gt; &lt;em&gt;&amp;ldquo;Registry Operator shall provide bulk access to up-to-date data concerning domain name and nameserver registrations maintained by Registry Operator in connection with the Registry TLD on a daily schedule, only for purposes of providing free public query-based access to up-to-date data concerning domain name and nameserver registrations in multiple TLDs, to a party designated from time to time in writing by ICANN.&amp;rdquo; &lt;/em&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;p&gt;The thing is, this is being implemented despite a clear and contrary&amp;nbsp;mandate from the community that is &lt;a href=&quot;http://www.icann.org/nsi/nsi-registry-agreement-04nov99.htm#9C&quot;&gt;backed up by the original ICANN/NSI Registry contract &lt;/a&gt;which explicitly states that such a centralized system would only be implemented &amp;ldquo;&lt;em&gt;&amp;hellip;if&amp;nbsp;[the distributed Whois&amp;nbsp;system]&amp;nbsp;implemented by registrars on a distributed basis does not within a reasonable time provide reasonably robust, reliable and convenient access to accurate and up-to-date registration data&lt;/em&gt;&amp;rdquo;. It also goes on to say that the&amp;nbsp;deployment of the centralized system would be undertaken pursuant to the establishment of&amp;nbsp;Consensus Policy.&lt;/p&gt;&lt;p&gt;Will&amp;nbsp;&lt;a href=&quot;http://www.icann.org/general/bylaws.htm#AnnexA&quot;&gt;the ICANN GNSO Policy Development Process&lt;/a&gt; be replaced by a contractual negotiation process, or more simply become a process of appealing to the U.S. legal system?&amp;nbsp;Or are we there already?&amp;nbsp;&lt;/p&gt;&lt;div class=&quot;tuneage&quot;&gt;&lt;strong&gt;Now playing:&lt;/strong&gt; Blues Traveler - Psycho Joe &lt;/div&gt;</description>
    
    <category domain="http://www.byte.org/blog/random_bytes/Code">Code</category>
    
    
    
    
  </item>
  
</channel>
</rss>
