<?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: SBC traceroute weirdness</title>
	<atom:link href="https://ward.vandewege.net/blog/2006/03/sbc-traceroute-weirdness/feed/" rel="self" type="application/rss+xml" />
	<link>https://ward.vandewege.net/blog/2006/03/sbc-traceroute-weirdness/</link>
	<description></description>
	<lastBuildDate>Tue, 03 Mar 2015 22:55:12 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: jag</title>
		<link>https://ward.vandewege.net/blog/2006/03/sbc-traceroute-weirdness/comment-page-1/#comment-3</link>
		<dc:creator><![CDATA[jag]]></dc:creator>
		<pubDate>Mon, 27 Mar 2006 17:46:49 +0000</pubDate>
		<guid isPermaLink="false">http://ward.vandewege.net/blog/2006/03/27/40/#comment-3</guid>
		<description><![CDATA[Traceroutes aren&#039;t necessarily a good way to determine route efficiency these days, because it only looks at layer 3 switching. It does nothing to report ATM switching, which can have as much overhead with virtual path rewrites as next-hop information on an IP packet. The Speakeasy path might include just as many ATM switches as you saw hops in California&#039;s SBC routes -- you just wouldn&#039;t know it.

-jag]]></description>
		<content:encoded><![CDATA[<p>Traceroutes aren&#8217;t necessarily a good way to determine route efficiency these days, because it only looks at layer 3 switching. It does nothing to report ATM switching, which can have as much overhead with virtual path rewrites as next-hop information on an IP packet. The Speakeasy path might include just as many ATM switches as you saw hops in California&#8217;s SBC routes &#8212; you just wouldn&#8217;t know it.</p>
<p>-jag</p>
]]></content:encoded>
	</item>
</channel>
</rss>
