<?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: iSCSI Part 3 (or is it part 4)</title>
	<atom:link href="http://thestoragearchitect.com/2007/02/16/iscsi-part-3-or-is-it-part-4/feed/" rel="self" type="application/rss+xml" />
	<link>http://thestoragearchitect.com/2007/02/16/iscsi-part-3-or-is-it-part-4/</link>
	<description>Storage, Virtualisation &#38; Cloud</description>
	<lastBuildDate>Fri, 10 Feb 2012 17:47:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Killchad</title>
		<link>http://thestoragearchitect.com/2007/02/16/iscsi-part-3-or-is-it-part-4/#comment-38</link>
		<dc:creator>Killchad</dc:creator>
		<pubDate>Tue, 03 Jul 2007 14:39:00 +0000</pubDate>
		<guid isPermaLink="false">http://thestoragearchitect.wordpress.com/2007/02/16/iscsi-part-3-or-is-it-part-4/#comment-38</guid>
		<description>Hello - I&#039;ve yet to see IPSec (or even CHAP for that matter) deployed in small-mid scale iSCSI deployments.   While it seems to me that CHAP is a no brainer, and IPSec seems to make logical sense - the tradeoffs go against one of the primary benefits of iSCSI - simple config and ease of use.&lt;br/&gt;&lt;br/&gt;IPSec adds some &quot;finicky-ness&quot; - greater dependencies on specific iSCSI targets, and starts to impose a heavy burden on the software initiators (which is also the much, much more widely deployed model)&lt;br/&gt;&lt;br/&gt;Just a comment from someone who sees a lot of iSCSI in production environments.&lt;br/&gt;&lt;br/&gt;Chad</description>
		<content:encoded><![CDATA[<p>Hello &#8211; I&#8217;ve yet to see IPSec (or even CHAP for that matter) deployed in small-mid scale iSCSI deployments.   While it seems to me that CHAP is a no brainer, and IPSec seems to make logical sense &#8211; the tradeoffs go against one of the primary benefits of iSCSI &#8211; simple config and ease of use.</p>
<p>IPSec adds some &#8220;finicky-ness&#8221; &#8211; greater dependencies on specific iSCSI targets, and starts to impose a heavy burden on the software initiators (which is also the much, much more widely deployed model)</p>
<p>Just a comment from someone who sees a lot of iSCSI in production environments.</p>
<p>Chad</p>
]]></content:encoded>
	</item>
</channel>
</rss>

