<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/1.5.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: iFCP vs FCIP?</title>
	<link>http://storageadvisors.adaptec.com/2006/01/25/ifcp-vs-fcip/</link>
	<description>Storage Solutions for Real World IT Professionals</description>
	<pubDate>Sat, 20 Mar 2010 12:16:53 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.2</generator>

	<item>
 		<title>Comment on iFCP vs FCIP? by: Matthew</title>
		<link>http://storageadvisors.adaptec.com/2006/01/25/ifcp-vs-fcip/#comment-143</link>
		<pubDate>Thu, 23 Mar 2006 09:36:10 +0000</pubDate>
		<guid>http://storageadvisors.adaptec.com/2006/01/25/ifcp-vs-fcip/#comment-143</guid>
					<description>From your description above, it would seem that iFCP is more efficient than FCIP in terms of usefull data per IP packet. I assume this because from you description, iFCP removes FCIP headers and transports only the data portion of the FCP packet. Can you confirm this and are there any performance comparisons available that you know of? I understand that the two protocols have different end point considerations but if the performance is significantly different it could lend weight to one solution design over another.

Thanks for your site :)</description>
		<content:encoded><![CDATA[	<p>From your description above, it would seem that iFCP is more efficient than FCIP in terms of usefull data per IP packet. I assume this because from you description, iFCP removes FCIP headers and transports only the data portion of the FCP packet. Can you confirm this and are there any performance comparisons available that you know of? I understand that the two protocols have different end point considerations but if the performance is significantly different it could lend weight to one solution design over another.</p>
	<p>Thanks for your site <img src='http://storageadvisors.adaptec.com/wp-images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
