<?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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Ahh, The Ease of Introducing Global Routing Instability</title>
	<atom:link href="http://ddos.arbornetworks.com/2009/02/ahh-the-ease-of-introducing-global-routing-instability/feed/" rel="self" type="application/rss+xml" />
	<link>http://ddos.arbornetworks.com/2009/02/ahh-the-ease-of-introducing-global-routing-instability/</link>
	<description>A weblog dedicated to educating the community on security threats that matter</description>
	<lastBuildDate>Sun, 29 Jan 2012 02:23:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: blogger &#187; Blog Archive &#187; How a small company caused Internet disruption</title>
		<link>http://ddos.arbornetworks.com/2009/02/ahh-the-ease-of-introducing-global-routing-instability/comment-page-1/#comment-201704</link>
		<dc:creator>blogger &#187; Blog Archive &#187; How a small company caused Internet disruption</dc:creator>
		<pubDate>Tue, 24 Mar 2009 18:26:29 +0000</pubDate>
		<guid isPermaLink="false">http://asert.arbornetworks.com/?p=754#comment-201704</guid>
		<description>[...] Arbor Networks , noted in a blog post that the problem was the result of some versions of Cisco IOS not allocating enough buffer space &quot;for silly long&quot; AS paths. &quot;So they blow chunks when they receive the update,&quot; such as the one announced by [...]</description>
		<content:encoded><![CDATA[<p>[...] Arbor Networks , noted in a blog post that the problem was the result of some versions of Cisco IOS not allocating enough buffer space &quot;for silly long&quot; AS paths. &quot;So they blow chunks when they receive the update,&quot; such as the one announced by [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: My Freaky Mind &#187; Peering between SK and ISAT down regarding new bugs from Cisco router.</title>
		<link>http://ddos.arbornetworks.com/2009/02/ahh-the-ease-of-introducing-global-routing-instability/comment-page-1/#comment-200769</link>
		<dc:creator>My Freaky Mind &#187; Peering between SK and ISAT down regarding new bugs from Cisco router.</dc:creator>
		<pubDate>Wed, 18 Mar 2009 04:29:31 +0000</pubDate>
		<guid isPermaLink="false">http://asert.arbornetworks.com/?p=754#comment-200769</guid>
		<description>[...] And also read news from Arbor Networks: [...]</description>
		<content:encoded><![CDATA[<p>[...] And also read news from Arbor Networks: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Internet und tönerne Füße &#171; Impressionen</title>
		<link>http://ddos.arbornetworks.com/2009/02/ahh-the-ease-of-introducing-global-routing-instability/comment-page-1/#comment-197424</link>
		<dc:creator>Internet und tönerne Füße &#171; Impressionen</dc:creator>
		<pubDate>Tue, 24 Feb 2009 00:06:44 +0000</pubDate>
		<guid isPermaLink="false">http://asert.arbornetworks.com/?p=754#comment-197424</guid>
		<description>[...] erwies sich als lösbar und mittlerweile gibt es sogar einen Workaround. Es bleibt jedoch ein fahler Nachgeschmack, denn so stabil wie das Internet zu sein scheint, ist es nicht. Immerhin geschieht so etwas nicht [...]</description>
		<content:encoded><![CDATA[<p>[...] erwies sich als lösbar und mittlerweile gibt es sogar einen Workaround. Es bleibt jedoch ein fahler Nachgeschmack, denn so stabil wie das Internet zu sein scheint, ist es nicht. Immerhin geschieht so etwas nicht [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ivan Pepelnjak</title>
		<link>http://ddos.arbornetworks.com/2009/02/ahh-the-ease-of-introducing-global-routing-instability/comment-page-1/#comment-197003</link>
		<dc:creator>Ivan Pepelnjak</dc:creator>
		<pubDate>Fri, 20 Feb 2009 22:08:01 +0000</pubDate>
		<guid isPermaLink="false">http://asert.arbornetworks.com/?p=754#comment-197003</guid>
		<description>It was a previously unknown IOS bug. The preventive measure has been available for years and should have been used by everyone but was obviously not. See &lt;a href=&quot;http://blog.ioshints.info/2009/02/oversized-as-paths-cisco-ios-bug.html&quot; rel=&quot;nofollow&quot;&gt;Oversized AS paths: Cisco IOS bug details&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>It was a previously unknown IOS bug. The preventive measure has been available for years and should have been used by everyone but was obviously not. See <a href="http://blog.ioshints.info/2009/02/oversized-as-paths-cisco-ios-bug.html" rel="nofollow">Oversized AS paths: Cisco IOS bug details</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Long BGP AS paths causing commotion &#124; BGPmon.net Blog</title>
		<link>http://ddos.arbornetworks.com/2009/02/ahh-the-ease-of-introducing-global-routing-instability/comment-page-1/#comment-196757</link>
		<dc:creator>Long BGP AS paths causing commotion &#124; BGPmon.net Blog</dc:creator>
		<pubDate>Thu, 19 Feb 2009 05:46:30 +0000</pubDate>
		<guid isPermaLink="false">http://asert.arbornetworks.com/?p=754#comment-196757</guid>
		<description>[...] AS47868 was prepending it&#8217;s AS path many times, up to 252 times resulting in a AS path of 256. Although this is an insanely high number, considering that the average AS path length is about 4.3, It should definitely not cause the behavior we observed Monday. A number of routers that apparently run older software, were not capable to handle these long AS paths and as a result a fair number of BGP sessions started to flap, which caused a wave of updates (many times higher then normal) causing instability. A Good technical explanations can be found at renesys and arbor security. [...]</description>
		<content:encoded><![CDATA[<p>[...] AS47868 was prepending it&#8217;s AS path many times, up to 252 times resulting in a AS path of 256. Although this is an insanely high number, considering that the average AS path length is about 4.3, It should definitely not cause the behavior we observed Monday. A number of routers that apparently run older software, were not capable to handle these long AS paths and as a result a fair number of BGP sessions started to flap, which caused a wave of updates (many times higher then normal) causing instability. A Good technical explanations can be found at renesys and arbor security. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

