<?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: DNSSEC for All Top Level .GOV Domains</title>
	<atom:link href="http://infosecevents.net/2008/08/29/dnssec-for-all-top-level-gov-domains/feed/" rel="self" type="application/rss+xml" />
	<link>http://infosecevents.net/2008/08/29/dnssec-for-all-top-level-gov-domains/</link>
	<description>Covering the Information Security Economy</description>
	<lastBuildDate>Fri, 10 Feb 2012 06:58:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Can you say knee jerk reaction? &#124; Nicholson Security</title>
		<link>http://infosecevents.net/2008/08/29/dnssec-for-all-top-level-gov-domains/comment-page-1/#comment-236</link>
		<dc:creator>Can you say knee jerk reaction? &#124; Nicholson Security</dc:creator>
		<pubDate>Wed, 03 Sep 2008 03:21:44 +0000</pubDate>
		<guid isPermaLink="false">http://infosecevents.net/2008/08/29/dnssec-for-all-top-level-gov-domains/#comment-236</guid>
		<description>[...] Now I am all for DNSSEC becuase at this time it is the best working model to reduce the risk that threaten traditional DNS.  My concern is how is this &#8220;mandate&#8221; going to be implemented?  DNSSEC is not a simple task to deploy and I can&#8217;t imagine that anyone is claiming that it won&#8217;t be a big deal.  You have the RRSIG, the DNSKEY, the DS, and the NSEC which are all new records that need to be created and validated.  In adition to the control of the private key used for signing.  InfoSecEvents has more about the top level .GOV domains moving to DNSSEC here. [...]</description>
		<content:encoded><![CDATA[<p>[...] Now I am all for DNSSEC becuase at this time it is the best working model to reduce the risk that threaten traditional DNS.  My concern is how is this &#8220;mandate&#8221; going to be implemented?  DNSSEC is not a simple task to deploy and I can&#8217;t imagine that anyone is claiming that it won&#8217;t be a big deal.  You have the RRSIG, the DNSKEY, the DS, and the NSEC which are all new records that need to be created and validated.  In adition to the control of the private key used for signing.  InfoSecEvents has more about the top level .GOV domains moving to DNSSEC here. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

