<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Easy to Read Articles &#187; mesh</title>
	<atom:link href="http://www.easyreadarticles.com/Tags/mesh/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.easyreadarticles.com</link>
	<description>Best Technical Writing Online , Easy Reading Books and much more!</description>
	<lastBuildDate>Fri, 10 Feb 2012 03:40:00 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>The Babel Routing Protocol</title>
		<link>http://www.easyreadarticles.com/twitter/the-babel-routing-protocol/#utm_source=articlesfeed&#038;utm_medium=articlesfeed&#038;utm_campaign=articlesfeed</link>
		<comments>http://www.easyreadarticles.com/twitter/the-babel-routing-protocol/#comments</comments>
		<pubDate>Wed, 16 Sep 2009 05:47:29 +0000</pubDate>
		<dc:creator>Easy Read</dc:creator>
				<category><![CDATA[Twitter]]></category>
		<category><![CDATA[babel]]></category>
		<category><![CDATA[mesh]]></category>
		<category><![CDATA[olsr]]></category>
		<category><![CDATA[routing protocol]]></category>

		<guid isPermaLink="false">http://www.easyreadarticles.com/?p=349</guid>
		<description><![CDATA[The Babel Routing Protocol]]></description>
			<content:encoded><![CDATA[<p>This was something interesting that was posted in our <a rel="nofollow" href="http://the-mesh.org/cgi-bin/cgiirc/irc.cgi">Mesh IRC chat room</a>; The Babel routing protocol.</p>
<p>Pretty cool stuff and if you have some time, have a read <img src='http://www.easyreadarticles.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Basically between our use (<a rel="nofollow" href="http://www.the-mesh.org">The Mesh</a>) of the dynamic routing protocol <a rel="nofollow" href="http://the-mesh.org/tiki-index.php?page=WirelessRoutingProtocolOLSR&amp;highlight=olsr">OLSR</a> or <a rel="nofollow" href="http://the-mesh.org/tiki-index.php?page=WirelessRoutingProtocolOLSR&amp;highlight=olsr">Optimized Link State Routing protocol</a> <em>babel is extremely robust in the presence of mobility: only under very exceptional situations circumstances will Babel cause a transient routing loop. (This is unlike <a rel="nofollow" href="http://en.wikipedia.org/wiki/OLSR">OLSR</a>, which will cause transient routing loops just after a mobility event before the new topology information is flooded throughout the network.)</em></p>
<p>I&#8217;ve always like using the method<strong> &#8220;Prevention is better than the cure&#8221; </strong>and the name Babel seems appropriate?</p>
<p>If you do not know:  <strong>OLSR</strong> is an IP routing protocol which is optimized for mobile ad-hoc networks but can also be used on other wireless ad-hoc networks. OLSR is a proactive link-state routing protocol which uses Hello and Topology Control (TC) messages to discover and then disseminate link state information throughout the mobile ad-hoc network. Individual nodes use this topology information to compute next hop destinations for all nodes in the network using shortest hop forwarding paths. &#8211; Wikipedia</p>
<p>Here are a couple of pointed links for your perusal:</p>
<p><a rel="nofollow" href="http://www.pps.jussieu.fr/~jch/software/babel/draft-chroboczek-babel-routing-protocol-01.html">http://www.pps.jussieu.fr/~jch/software/babel/draft-chroboczek-babel-routing-protocol-01.html</a></p>
<p><a rel="nofollow" href="http://www.pps.jussieu.fr/~jch/software/babel/">http://www.pps.jussieu.fr/~jch/software/babel/</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.easyreadarticles.com/twitter/the-babel-routing-protocol/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

