<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Can Cloud IP Address Be Damaged Goods?</title>
	<atom:link href="http://roman.stanek.org/2008/12/06/can-cloud-ip-address-be-damaged-goods/feed/" rel="self" type="application/rss+xml" />
	<link>http://roman.stanek.org/2008/12/06/can-cloud-ip-address-be-damaged-goods/</link>
	<description>BI, SaaS, travel and everything else...</description>
	<lastBuildDate>Wed, 17 Feb 2010 02:14:10 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Fred Baker</title>
		<link>http://roman.stanek.org/2008/12/06/can-cloud-ip-address-be-damaged-goods/#comment-264</link>
		<dc:creator>Fred Baker</dc:creator>
		<pubDate>Mon, 27 Apr 2009 17:06:10 +0000</pubDate>
		<guid isPermaLink="false">http://roman.stanek.org/?p=208#comment-264</guid>
		<description>I don&#039;t know that IPv6 will instantly be a panacea for this. Yes, it provides more addresses. That said, if spam is coming from a prefix (a /64, /48, or /32) I could easily imagining an ISP blocking the prefix, not the actual addresses. Reason: privacy addresses, such as are implemented in Windows, change daily, and can be changed on a per-tcp-session basis. Nobody is going to want to go through the trouble of disabling this computer but not that if the vetting is lost in less than 24 hours.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know that IPv6 will instantly be a panacea for this. Yes, it provides more addresses. That said, if spam is coming from a prefix (a /64, /48, or /32) I could easily imagining an ISP blocking the prefix, not the actual addresses. Reason: privacy addresses, such as are implemented in Windows, change daily, and can be changed on a per-tcp-session basis. Nobody is going to want to go through the trouble of disabling this computer but not that if the vetting is lost in less than 24 hours.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
