<?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: Meetinghouse and Cisco Implications</title>
	<atom:link href="http://www.seanconvery.com/weblog/2006/07/07/meetinghouse-and-cisco-implications/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.seanconvery.com/weblog/2006/07/07/meetinghouse-and-cisco-implications/</link>
	<description>Ruminations on Information Technology</description>
	<lastBuildDate>Thu, 26 Feb 2009 14:43:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Sean Convery &#187; Blog Archive &#187; Cisco&#8217;s Supplicant Strategy</title>
		<link>http://www.seanconvery.com/weblog/2006/07/07/meetinghouse-and-cisco-implications/comment-page-1/#comment-19</link>
		<dc:creator>Sean Convery &#187; Blog Archive &#187; Cisco&#8217;s Supplicant Strategy</dc:creator>
		<pubDate>Wed, 25 Oct 2006 21:16:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.seanconvery.com/weblog/?p=30#comment-19</guid>
		<description>[...] Cisco has announced the branding of the Meetinghouse 802.1X supplicant. The &#8220;Cisco Secure Services Client&#8221; is now available. I wrote about the Meetinghouse and Cisco deal a while back. I was right when I predicted that Cisco would pull Meetinghouse out of the TCG / TNC; that happened pretty fast. However, I was wrong when I predicted that Cisco might sell their client for substantially less than Juniper&#8217;s offering or even give it away for free. My reasoning was that Cisco had far more to gain by selling switch migrations enabled by a supported supplicant, than they did in trying to recognize revenue per seat in connecting to those switches. [...]</description>
		<content:encoded><![CDATA[<p>[...] Cisco has announced the branding of the Meetinghouse 802.1X supplicant. The &#8220;Cisco Secure Services Client&#8221; is now available. I wrote about the Meetinghouse and Cisco deal a while back. I was right when I predicted that Cisco would pull Meetinghouse out of the TCG / TNC; that happened pretty fast. However, I was wrong when I predicted that Cisco might sell their client for substantially less than Juniper&#8217;s offering or even give it away for free. My reasoning was that Cisco had far more to gain by selling switch migrations enabled by a supported supplicant, than they did in trying to recognize revenue per seat in connecting to those switches. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

