<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
   <channel>
      <title>Renesys Blog</title>
      <link>http://www.renesys.com/blog/</link>
      <description></description>
      <language>en</language>
      <copyright>Copyright 2008</copyright>
      <lastBuildDate>Tue, 15 Apr 2008 13:17:47 -0500</lastBuildDate>
      <generator>http://www.sixapart.com/movabletype/?v=3.2</generator>
      <docs>http://blogs.law.harvard.edu/tech/rss</docs> 

            <item>
         <title>The Day the Youtube Died: The Video</title>
         <description><![CDATA[<p>Randy Epstein of <a href="http://host.net/">Host.net</a> and <a href="http://wvfiber.com">WVFiber</a> graciously (or perhaps maliciously, given the quality of the performance) filmed and did the post-production on the recent performance at the <a href="http://peeringforum.com/">Global Peering Forum</a>.  If I had a virtual tip jar, I would set it out.  Enjoy:
</p>
<p>
<object width="425" height="355"><param name="movie" value="http://www.youtube.com/v/JJ-nSCl1UMc&hl=en"></param><param name="wmode" value="transparent"></param><embed src="http://www.youtube.com/v/JJ-nSCl1UMc&hl=en" type="application/x-shockwave-flash" wmode="transparent" width="425" height="355"></embed></object></p>]]></description>
         <link>http://www.renesys.com/blog/2008/04/the_day_the_youtube_died_video.shtml</link>
         <guid>http://www.renesys.com/blog/2008/04/the_day_the_youtube_died_video.shtml</guid>
         <category>Society</category>
         <pubDate>Tue, 15 Apr 2008 13:17:47 -0500</pubDate>
      </item>
            <item>
         <title>The Day the YouTube Died</title>
         <description><![CDATA[<p>
At the recent <a href="http://peeringforum.com">Global Peering Forum</a> I performed a spoof song based on the recent YouTube hijacking.  (I'm told that video will eventually be available, at which point I'm sure I'll have to go into hiding at an undisclosed location.)
</p>
<p>
American Pie was previously <a href="http://www.youtube.com/watch?v=phSpBCdWq1U">parodied at a RIPE meeting</a> and now is practically a tradition, much to Mike Hughes's chagrin, as he thinks it's overdone already.  The great thing about the original song is that it's choc full of <a href="http://www.fiftiesweb.com/amerpie-1.htm">references</a> in the music industry.  I tried to pepper several more into my version (and I have a few additional verses in progress that I just didn't finish).  
</p>
<p>
What links would you provide to these references?  What additional references do you think are important and missing (given the history of the Internet theme)?
</p>
<p><h3>The Day the YouTube Died</h3></p>
<p>
<br />A long long time ago
<br />I can still remember how the videos used to make me smile.
<br />And I knew if I had my chance, 
<br />I'd watch the <a href="http://www.youtube.com/watch?v=hMnk7lh9M3o">prison thriller dance</a>
<br />and maybe I'd be happy for a while.
<br />But February made me shiver with every packet I'd deliver
<br /><a href="http://www.renesys.com/blog/2008/02/pakistan_hijacks_youtube_1.shtml">bad routes in the tables</a>, the paths they were not stable.
<br />I can't remember if I cried when I saw my request was denied
<br />but boredom welled up deep inside
<br /><a href="http://www.news.com/8301-10784_3-9877614-7.html">the day the YouTube died</a>.
</p>
]]></description>
         <link>http://www.renesys.com/blog/2008/04/the_day_the_youtube_died_1.shtml</link>
         <guid>http://www.renesys.com/blog/2008/04/the_day_the_youtube_died_1.shtml</guid>
         <category>Society</category>
         <pubDate>Mon, 14 Apr 2008 15:34:00 -0500</pubDate>
      </item>
            <item>
         <title>Telia and Cogent Kiss and Make Up</title>
         <description><![CDATA[<p>
On March 28th at 17:52 UTC, 
we saw the peering link between Telia and Cogent come back up.
Recently, peering disputes, especially with Cogent, tend to be all about traffic ratios:
as long as both parties send roughly the same amount of traffic to each other, 
life is good.
But when the ratios get out of whack, someone's feelings get hurt 
(more specifically someone's business model is threatened).
Before the de-peering,
we would typically see Cogent using Telia to reach around 2700 networks (prefixes). 
Now that count has dropped to just about 1450 networks.
On the other hand, 
Telia used to reach approximately 7000 networks via Cogent and that number has now increased to almost 8600.
So was Cogent sending too much traffic to Telia before?
Did Telia then do something to provoke Cogent to turn them off (like send a bill)?
We'll never know definitively, but someone blinked and the Internet is now whole again.
</p>

<p>
While this is good for the Internet,
Cogent claimed that this dispute was about 
<a href="http://blog.wired.com/27bstroke6/2008/03/isp-quarrel-par.html">capacity issues</a> and no one orders and installs new high capacity circuits in a week,
especially during a contract dispute.
So if there was a capacity issue, 
there is <em>still</em> a capacity issue.
As a result, the situation is bound to be very fluid for the next few weeks.
We'll update this blog as we analyze the resulting shifts in routing.
</p>]]></description>
         <link>http://www.renesys.com/blog/2008/03/telia_and_cogent_kiss_and_make_1.shtml</link>
         <guid>http://www.renesys.com/blog/2008/03/telia_and_cogent_kiss_and_make_1.shtml</guid>
         <category>Engineering</category>
         <pubDate>Fri, 28 Mar 2008 16:09:36 -0500</pubDate>
      </item>
            <item>
         <title>He said, she said: Cogent vs. Telia</title>
         <description><![CDATA[<p>
As in most lovers' quarrels, 
it is difficult to objectively evaluate the claims of the combatants.
Naturally, we tend to side with the person we know best, 
as it's their viewpoint we hear most often and are inclined to be sympathetic towards.
Both Cogent and Telia are claiming to be the aggrieved party in their
<a href="http://www.renesys.com/blog/2008/03/you_cant_get_there_from_here_1.shtml">
peering dispute</a> and are now making their case in
<a href="http://www.washingtonpost.com/wp-dyn/content/article/2008/03/19/AR2008031901741.html"> the court of public opinion</a>.
We will almost certainly never know the details of their private business relationship, 
but we can make a few more inferences from the data.
Let me state up front that, like many major ISPs,
Telia and Cogent are customers of Renesys and we love them both equally.
Everything we report in our blogs is based on objective analysis of our global data, 
independent of our own business relationships.
</p>]]></description>
         <link>http://www.renesys.com/blog/2008/03/he_said_she_said_cogent_vs_tel.shtml</link>
         <guid>http://www.renesys.com/blog/2008/03/he_said_she_said_cogent_vs_tel.shtml</guid>
         <category>Engineering</category>
         <pubDate>Fri, 21 Mar 2008 11:10:31 -0500</pubDate>
      </item>
            <item>
         <title>You can&apos;t get there from here</title>
         <description><![CDATA[<p>
Cogent and Telia are having a lover's quarrel and, as a result,
the Internet is partitioned.
That means customers of Cogent and Telia cannot necessarily reach one another.
This was <b>not</b> due to a configuration error or a physical cable break.
This is the 
<a href="http://www.renesys.com/blog/2005/12/peering_the_fundamental_archit.shtml">way the Internet works</a> and sometimes doesn't work.
If the businesses that run the show don't play nice with one another,
their customers can pay the price of being cut off from parts of the 'net.
At least when 
<a href="http://www.renesys.com/blog/2008/02/pakistan_hijacks_youtube_1.shtml">Pakistan mistakenly hijacked YouTube,</a>
the matter was sorted out in hours and did not require the cooperation of Pakistan.
The Cogent/Telia tiff has been going on for 4 days now and only they can resolve their differences.  
The rest of the world can only hope for full connectivity to be restored.
</p>]]></description>
         <link>http://www.renesys.com/blog/2008/03/you_cant_get_there_from_here_1.shtml</link>
         <guid>http://www.renesys.com/blog/2008/03/you_cant_get_there_from_here_1.shtml</guid>
         <category>Engineering</category>
         <pubDate>Mon, 17 Mar 2008 23:01:53 -0500</pubDate>
      </item>
            <item>
         <title>Pakistan hijacks YouTube</title>
         <description><![CDATA[<p>
Late in the (UTC) day on 24 February 2008, Pakistan Telecom (AS 17557) began advertising a small part of YouTube's (AS 36561) assigned network.  This story is almost as old as BGP.  Old hands will recognize this as, fundamentally, the same problem as the  <a href="
http://merit.edu/mail.archives/nanog/1997-04/msg00380.html">infamous AS 7007 from 1997</a>, a <a href="http://www.renesys.com/blog/2006/01/coned_steals_the_net.shtml">more recent ConEd mistake of early 2006</a> and even <a href="http://www.renesys.com/blog/2005/12/internetwide_nearcatastrophela.shtml">TTNet's Christmas Eve gift 2004</a>.
</p>

<p>
Just before 18:48 UTC, Pakistan Telecom, in response to <a href="http://www.renesys.com/blog/pakistan_blocking_order.pdf">government order</a> to block access to YouTube (see <a href="http://ca.news.yahoo.com/s/afp/080224/world/denmark_media_islam_pakistan_internet_youtube">news item</a>) started advertising a route for 208.65.153.0/24 to its provider, PCCW (AS 3491).  For those unfamiliar with BGP, this is a more specific route than the ones used by YouTube (208.65.152.0/22), and therefore most routers would choose to send traffic to Pakistan Telecom for this slice of YouTube's network.
</p>]]></description>
         <link>http://www.renesys.com/blog/2008/02/pakistan_hijacks_youtube_1.shtml</link>
         <guid>http://www.renesys.com/blog/2008/02/pakistan_hijacks_youtube_1.shtml</guid>
         <category>Engineering</category>
         <pubDate>Sun, 24 Feb 2008 19:50:21 -0500</pubDate>
      </item>
            <item>
         <title>On the road again:  Diary of an itinerant Internet transit sales guy</title>
         <description><![CDATA[<table align="left">
<tr>
<td>
<a href="http://www.renesys.com/about/management.shtml">
<img src="http://www.renesys.com/blog/bob/travel/Bob.jpg" width="150" height="194"></a>
</td>
</tr>
<tr>
<td align="center"><em>Bob, the sales guy.</em>
</td>
</tr>
</table>

<p>
Ditched my #@!%$! cell in Stockholm. Verizon CDMA does not work in Europe! Upside: I now have a shiny, new World Edition Blackberry GSM/CDMA. I call it Trixie.
</p>

<blockquote>
<table><tr><td bgcolor=#99FFFF>
<em>Road Tip:</em> Just say NO! to mouth-searing kimchi or Indian curry for breakfast. No matter how polite you're trying to be.
</td></tr></table>
</blockquote>

<p>
With barely enough time to recharge Trixie after calls in Denver, Albuquerque, Stockholm and Bonn, I hopped a jet for Tokyo, Hong Kong and Kuala Lumpur. (Trixie and I barely made it out of KL alive. Cab driver must have been conserving gas; tried to piggyback car in front.) Beginning to feel like Marco Polo on 'roids, but I gotta check out LA and  DC before catching a shuttle back home to Boston (close enough) . 
</p>

<p>
Trixie is overloaded with commentary, observations, insider scoops, and . . . new NSP sales and marketing contacts! (Hey, I'm a sales guy.) Time to download and see what comes out . . .
</p>

]]></description>
         <link>http://www.renesys.com/blog/2008/02/on_the_road_again_diary_of_an_1.shtml</link>
         <guid>http://www.renesys.com/blog/2008/02/on_the_road_again_diary_of_an_1.shtml</guid>
         <category>Business</category>
         <pubDate>Thu, 21 Feb 2008 07:45:45 -0500</pubDate>
      </item>
            <item>
         <title>Cable Breaks: Lessons Learned </title>
         <description><![CDATA[<p>
In the past 14 months, 
the world has seen two catastrophic failures of its global telecommunications systems:
the  
<a href="http://www.renesys.com/blog/2007/01/the_shape_of_disaster_on_the_n.shtml">Taiwan quakes</a>,
which snapped 7 of 9 important cables in Asia in December 2006,
and a series of mishaps in the 
<a href="http://www.renesys.com/blog/2008/01/mediterranean_cable_break.shtml">Mediterranean</a>
and the 
<a href="http://www.telegeography.com/cu/article.php?article_id=21567">Gulf</a>,
damaging several others.
In a world increasingly dependent on global trade and communications,
what lessons can we learn from all of this and what measures should we take?
</p>

<p>
I'll discuss these questions in what follows, 
but let me warn you in advance.
There is <em>nothing</em> earth-shattering here.
In fact, I can save you time and sum up the entire discussion with three bullet points:
</p>
<ul>
<li>You get what you pay for.</li>
<li>Entropy happens.</li>
<li>Geography matters.</li>
</ul>
<p>
We've seen a lot of comments and discussion that fail to take into account one or more of these basics truths.
Let's look at each point in detail.
</p>]]></description>
         <link>http://www.renesys.com/blog/2008/02/cable_breaks_lessons_learned_1.shtml</link>
         <guid>http://www.renesys.com/blog/2008/02/cable_breaks_lessons_learned_1.shtml</guid>
         <category>Business</category>
         <pubDate>Mon, 11 Feb 2008 13:30:36 -0500</pubDate>
      </item>
            <item>
         <title>Mediterranean Cable Break - Part IV</title>
         <description><![CDATA[<p>
We started this blog thread last week, when we <em>only</em> had two broken cables to consider, but since that time there have been 
<a href="http://www.telegeography.com/cu/article.php?article_id=21567">reports</a>
of several more failures and they seem to keep 
<a href="http://www.khaleejtimes.com/DisplayArticle.asp?xfile=data/theuae/2008/February/theuae_February155.xml&section=theuae">coming in.</a>
As far as this thread is concerned, the first two parts
(<a href="http://www.renesys.com/blog/2008/01/mediterranean_cable_break.shtml">here</a>
and 
<a href="http://www.renesys.com/blog/2008/01/mediterranean_cable_break.shtml">here</a>)
focused on the countries and local providers most impacted on the day of the first two cable failures.
We then looked at the providers of some of the
<a href="http://www.renesys.com/blog/2008/02/mediterranean_cable_break_part.shtml">harder-hit countries</a>
and how they were able to restore connectivity (or not) during the subsequent 48 hours.
And along the way, we felt obliged to counter some nonsense circulating on the Internet <a href="http://www.renesys.com/blog/2008/02/attention_iran_is_not_disconne_1.shtml">claiming that Iran had been cut off.</a>
It's been a busy week and we've barely scratched the surface.
But plowing ahead, 
we will take an extended look at two local providers, Bharti in India and DCI in Iran,
and how they weathered the storm.
One week later, how are these two local providers gaining access to the global Internet?
What has changed?  
We will use these examples to provide a glimpse into what can be discovered by collecting up enough public routing data from enough carefully selected places,
combining it with geo-location information and then doing an enormous amount of processing.
</p>
]]></description>
         <link>http://www.renesys.com/blog/2008/02/mediterranean_cable_break_part_3.shtml</link>
         <guid>http://www.renesys.com/blog/2008/02/mediterranean_cable_break_part_3.shtml</guid>
         <category>Engineering</category>
         <pubDate>Thu, 07 Feb 2008 14:58:00 -0500</pubDate>
      </item>
            <item>
         <title>ATTENTION: Iran is not disconnected!</title>
         <description><![CDATA[<p>
Let me repeat, Iran is <em>not</em> disconnected from the Internet!
</p>
<p>
We have gotten a few queries about why we did not highlight Iran in our review of the network outages that resulted from the cable breaks.
(See
<a href="http://www.renesys.com/blog/2008/01/mediterranean_cable_break.shtml">here</a>,
<a href="http://www.renesys.com/blog/2008/01/mediterranean_cable_break_part_1.shtml">here</a> and
<a href="http://www.renesys.com/blog/2008/02/mediterranean_cable_break_part.shtml">here</a>.)
Like most countries in the region,
the outages in Iran were very significant, but for the most part they did not exceed 20% of their total number of networks.
Now 20% is a significant loss, but in the context of an event where countries lost almost all of their connectivity, such a loss did not place Iran into the top 10 of impacted countries.
So we focused most of our attention where the losses where the highest.
</p>
]]></description>
         <link>http://www.renesys.com/blog/2008/02/attention_iran_is_not_disconne_1.shtml</link>
         <guid>http://www.renesys.com/blog/2008/02/attention_iran_is_not_disconne_1.shtml</guid>
         <category>Engineering</category>
         <pubDate>Sun, 03 Feb 2008 18:15:55 -0500</pubDate>
      </item>
            <item>
         <title>Mediterranean Cable Break - Part III</title>
         <description><![CDATA[<p>
Our first two blog entries on this topic focused on the events of 30 January 2008, when two submarine cables systems were damaged.  These systems provided much of the capacity into the Middle East and the Indian subcontinent from the west.  Although some countries were hurt more than others, the loss of connectivity was extensive and very widespread.  Some countries and a few providers were almost completely knocked off the Internet.  As Day 1 came to a close, it was clear that the damaged cables were not going to be repaired anytime soon and the impacted parties would have to look for alternatives to waiting it out.
</p>
<p>
Day 2 and 3 saw a frenzy of activity as local providers in the region tried to broker agreements with anyone who still had capacity.
They were under intense pressure to restore service to local governments and businesses.
In turn, global and regional providers with surviving capacity into the region were busy hunting for new customers.
We definitely had a seller's market.
At Renesys, we watched all of the activity with great interest and decided to wait until the end of Day 3 to report on the winners and losers, after the initial deals were made and things had settled down to some degree.
</p>
]]></description>
         <link>http://www.renesys.com/blog/2008/02/mediterranean_cable_break_part.shtml</link>
         <guid>http://www.renesys.com/blog/2008/02/mediterranean_cable_break_part.shtml</guid>
         <category>Engineering</category>
         <pubDate>Sat, 02 Feb 2008 06:17:24 -0500</pubDate>
      </item>
            <item>
         <title>Mediterranean Cable Break - Part II</title>
         <description><![CDATA[<p>
After looking at the countries most impacted by the cable cut in our first blog on this topic, we now turn our attention to the Internet service providers in the region and how they fared.  Due to differences in network architecture, cable ownership, and transit purchasing, carriers in the same country may not all experience the same degree of outage.  <em>For all of the following, we consider a network to be "outaged" when it is unreachable from the perspective of the broader Internet&mdash;as represented by Renesys's 250 peering sessions.</em>
</p>
<p>
The following two tables provide the top 15 providers with the largest number of outaged networks.  We list the provider's name, the country in which most of their unreachable networks are located and their autonomous system number (ASN), an assigned number that uniquely identifies their organization on the Internet.
</p>
In the first table, we list the providers in decreasing order by total number of outaged networks.  
In the second table, we list them by decreasing order of the percentage of their networks that are unreachable.
</p>
<p>
Not surprisingly, the hardest hit providers are located primarily in the hardest hit countries: Egypt, Kuwait, India and Pakistan.  One local provider in each of Egypt and Kuwait lost essentially all of their Internet connectivity.
</p>
]]></description>
         <link>http://www.renesys.com/blog/2008/01/mediterranean_cable_break_part_1.shtml</link>
         <guid>http://www.renesys.com/blog/2008/01/mediterranean_cable_break_part_1.shtml</guid>
         <category>Engineering</category>
         <pubDate>Thu, 31 Jan 2008 19:20:05 -0500</pubDate>
      </item>
            <item>
         <title>Mediterranean Cable Break</title>
         <description><![CDATA[<p>
Early this morning local time, 
<a href="http://www.bloomberg.com/apps/news?pid=20601085&sid=aWe706hsLNdY&refer=europe">two cable systems north of Alexandria, Egypt were severed</a>,
greatly impacting both Internet and voice traffic to the region.
The broken cables are operated by Flag Telecom and SEA-ME-WEA 4, 
and if <a href="http://www.renesys.com/tech/presentations/pdf/Plenary2-Underwood.pdf">past undersea cable cuts</a> 
are any measure, 
repair time will be measured in weeks, not days.
This is a preliminary report on the countries most impacted by this failure, 
as seen from the perspective of Internet routing.
</p>]]></description>
         <link>http://www.renesys.com/blog/2008/01/mediterranean_cable_break.shtml</link>
         <guid>http://www.renesys.com/blog/2008/01/mediterranean_cable_break.shtml</guid>
         <category>Engineering</category>
         <pubDate>Wed, 30 Jan 2008 18:53:22 -0500</pubDate>
      </item>
            <item>
         <title>15th Century Routing</title>
         <description><![CDATA[<table align=right>
<tr>
<td align=center>
<img src="http://www.renesys.com/blog/hike/sign.jpg" width="295" height="221" />
<em>Which way is up?</em>
</td>
</tr>
</table>

<p>
Since I sometimes find myself hopelessly lost, 
I tend to wonder about global navigation in the days before GPSes or even 
accurate maps.  
I imagine you started off with just a general idea of where you wanted to go 
(e.g., "The New World"), 
crude navigational aids (the stars, Sun and Moon when you could see them), 
and hearsay from your fellow travelers or the locals about your proposed course.
In addition, you only had a view of the world from your current location,
limited by the curvature of the earth.
</p>]]></description>
         <link>http://www.renesys.com/blog/2008/01/15th_century_routing.shtml</link>
         <guid>http://www.renesys.com/blog/2008/01/15th_century_routing.shtml</guid>
         <category>Engineering</category>
         <pubDate>Wed, 23 Jan 2008 14:14:05 -0500</pubDate>
      </item>
            <item>
         <title>Cascading Failures: Believe It or Not!</title>
         <description><![CDATA[<p>
Maybe it speaks to a risk-averse nature, but I've always been interested in 
failure and in learning from the mistakes of others - obviously so I don't have
to learn such lessons first hand.  This is particularly important when you 
engage in activities where bad decisions can kill you.  But generally, as any 
<a href="http://www.forewordmagazine.com/reviews/viewreviews.aspx?reviewID=1845">
	book on mountaineering mishaps</a> demonstrates, it takes a series of 
errors in the "correct order" and at the wrong times to cause you serious harm.
</p>

<p>
In high risk activities under adverse conditions, it's not hard to make poor
decisions that you would never contemplate from the comfort of your favorite
living room chair.  But while there is little risk to life and limb on the 
Internet, its very connectedness means that the blunders of pretty much anyone 
can impact you.  What is important in this environment is the half-life and the 
reach of the mistakes.  Those that are local and die out quickly have little 
chance of resulting in global mayhem.  Others compound with all the other endless 
screw-ups regularly going on and eventually become a giant avalanche careening 
down hill, collecting mass and bearing down on the sleeping village below.  
This is one of those stories.  It might be true or it might not.  Your opinion
depends on how much imagination you think we have!
</p>]]></description>
         <link>http://www.renesys.com/blog/2007/09/cascading_failures_believe_it.shtml</link>
         <guid>http://www.renesys.com/blog/2007/09/cascading_failures_believe_it.shtml</guid>
         <category>Engineering</category>
         <pubDate>Tue, 25 Sep 2007 17:00:00 -0500</pubDate>
      </item>
      
   </channel>
</rss>
