<?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: Sprint, Cogent Resume Peering, Keep Arguing</title>
	<atom:link href="http://www.datacenterknowledge.com/archives/2008/11/02/sprint-cogent-resume-peering-keep-arguing/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.datacenterknowledge.com/archives/2008/11/02/sprint-cogent-resume-peering-keep-arguing/</link>
	<description>News and analysis about data centers, cloud computing, managed hosting and disaster recovery</description>
	<lastBuildDate>Tue, 14 Feb 2012 04:07:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: WAVE IS</title>
		<link>http://www.datacenterknowledge.com/archives/2008/11/02/sprint-cogent-resume-peering-keep-arguing/comment-page-1/#comment-2720</link>
		<dc:creator>WAVE IS</dc:creator>
		<pubDate>Wed, 28 Jan 2009 18:08:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.datacenterknowledge.com/?p=4512#comment-2720</guid>
		<description>And now Embarq wants our IP addresses back because they want to &quot;retire them&quot; when it&#039;s Sprint that wants them back. We are screaming, crying, pleading. Thousands of our customers have the IP address configured in their computers, what are we going to do is now the urgent question. Shame on Embarq, and shame on Sprint.</description>
		<content:encoded><![CDATA[<p>And now Embarq wants our IP addresses back because they want to &#8220;retire them&#8221; when it&#8217;s Sprint that wants them back. We are screaming, crying, pleading. Thousands of our customers have the IP address configured in their computers, what are we going to do is now the urgent question. Shame on Embarq, and shame on Sprint.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sprint and Cogent reconnect, but for how long? - Security and the Net</title>
		<link>http://www.datacenterknowledge.com/archives/2008/11/02/sprint-cogent-resume-peering-keep-arguing/comment-page-1/#comment-1634</link>
		<dc:creator>Sprint and Cogent reconnect, but for how long? - Security and the Net</dc:creator>
		<pubDate>Mon, 03 Nov 2008 18:58:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.datacenterknowledge.com/?p=4512#comment-1634</guid>
		<description>[...] Center Knowledge has a slightly more positive take on this:  The good news is that the two companies appear willing to try and work out their [...]</description>
		<content:encoded><![CDATA[<p>[...] Center Knowledge has a slightly more positive take on this:  The good news is that the two companies appear willing to try and work out their [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stick</title>
		<link>http://www.datacenterknowledge.com/archives/2008/11/02/sprint-cogent-resume-peering-keep-arguing/comment-page-1/#comment-1630</link>
		<dc:creator>stick</dc:creator>
		<pubDate>Mon, 03 Nov 2008 16:35:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.datacenterknowledge.com/?p=4512#comment-1630</guid>
		<description>Sprint depeered from Cogent! This is a unilateral action. A class action is a good idea. If anyone hears of one let me know.</description>
		<content:encoded><![CDATA[<p>Sprint depeered from Cogent! This is a unilateral action. A class action is a good idea. If anyone hears of one let me know.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: logman</title>
		<link>http://www.datacenterknowledge.com/archives/2008/11/02/sprint-cogent-resume-peering-keep-arguing/comment-page-1/#comment-1629</link>
		<dc:creator>logman</dc:creator>
		<pubDate>Mon, 03 Nov 2008 16:20:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.datacenterknowledge.com/?p=4512#comment-1629</guid>
		<description>boater85,
You obviously have no clue how the internet actually works.  I suggest you  file a lawsuit against Sprint and see how far that gets.  Also, read your contracts, as I will gladly pay your &quot;$1000 for the 4 day interruption&quot; if you can show that Sprint guarantees 100% access to the entire internet.  

If you still don&#039;t understand, how about this...do you have customers that you contract with where you guarantee 100% access to your content?  I&#039;m willing to bet no, because you can&#039;t guarantee the performance and reachability of any network except for your own internal network.  Perhaps your customers should actually sue YOU because for all they know, you provide them their content and it&#039;s none of their concern that you didn&#039;t do your homework and chose to use a hosting provider that FREQUENTLY has this happen to them.</description>
		<content:encoded><![CDATA[<p>boater85,<br />
You obviously have no clue how the internet actually works.  I suggest you  file a lawsuit against Sprint and see how far that gets.  Also, read your contracts, as I will gladly pay your &#8220;$1000 for the 4 day interruption&#8221; if you can show that Sprint guarantees 100% access to the entire internet.  </p>
<p>If you still don&#8217;t understand, how about this&#8230;do you have customers that you contract with where you guarantee 100% access to your content?  I&#8217;m willing to bet no, because you can&#8217;t guarantee the performance and reachability of any network except for your own internal network.  Perhaps your customers should actually sue YOU because for all they know, you provide them their content and it&#8217;s none of their concern that you didn&#8217;t do your homework and chose to use a hosting provider that FREQUENTLY has this happen to them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rob</title>
		<link>http://www.datacenterknowledge.com/archives/2008/11/02/sprint-cogent-resume-peering-keep-arguing/comment-page-1/#comment-1623</link>
		<dc:creator>rob</dc:creator>
		<pubDate>Mon, 03 Nov 2008 13:47:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.datacenterknowledge.com/?p=4512#comment-1623</guid>
		<description>@boarer805: I highly doubt your contract guarantees that.  They can&#039;t guarantee that since Cogent or any other ISP could null route Sprint traffic.  Sprint can only guarantee reliability of it&#039;s own network.  That&#039;s why carrier neutral facilities are so popular.  Connect your servers to multiple networks and this isn&#039;t an issue.</description>
		<content:encoded><![CDATA[<p>@boarer805: I highly doubt your contract guarantees that.  They can&#8217;t guarantee that since Cogent or any other ISP could null route Sprint traffic.  Sprint can only guarantee reliability of it&#8217;s own network.  That&#8217;s why carrier neutral facilities are so popular.  Connect your servers to multiple networks and this isn&#8217;t an issue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: boater805</title>
		<link>http://www.datacenterknowledge.com/archives/2008/11/02/sprint-cogent-resume-peering-keep-arguing/comment-page-1/#comment-1609</link>
		<dc:creator>boater805</dc:creator>
		<pubDate>Mon, 03 Nov 2008 06:24:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.datacenterknowledge.com/?p=4512#comment-1609</guid>
		<description>I am a sprint customer and was unable to reach any site who&#039;s IP was within the cogent IP ciDr blocks.  Sprint has a contractural obligation to me as one of its paid users and to all internet users as a contractual internet backbone provider to provide routing to all legitimate internet IP addresses REGARDLESS of the existence or lack of same for any peering agreements and load balancing issues.  Sprint&#039;s failure to provide alternative routing outside the peering agreement was and is in its sole control and should have been undertaken prior to blackholing the cogent IP netblocks.  Its failure to do so was a major violation of its contractural obligations to all its paid users and should be the basis of a major class action lawsuit on behalf of ALL sprint customers for their breach of fiduciary duty to protect their paid customers interests above their own desires when there is a conflict and it is within their power to do so.  I will be glad to sign onto such a suit as a class member if anyone puts one together.  My personal damages I estimate at about $1000 for the 4 day interruption in access to my congent IP block hosted domains.</description>
		<content:encoded><![CDATA[<p>I am a sprint customer and was unable to reach any site who&#8217;s IP was within the cogent IP ciDr blocks.  Sprint has a contractural obligation to me as one of its paid users and to all internet users as a contractual internet backbone provider to provide routing to all legitimate internet IP addresses REGARDLESS of the existence or lack of same for any peering agreements and load balancing issues.  Sprint&#8217;s failure to provide alternative routing outside the peering agreement was and is in its sole control and should have been undertaken prior to blackholing the cogent IP netblocks.  Its failure to do so was a major violation of its contractural obligations to all its paid users and should be the basis of a major class action lawsuit on behalf of ALL sprint customers for their breach of fiduciary duty to protect their paid customers interests above their own desires when there is a conflict and it is within their power to do so.  I will be glad to sign onto such a suit as a class member if anyone puts one together.  My personal damages I estimate at about $1000 for the 4 day interruption in access to my congent IP block hosted domains.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

