		<rss version="2.0">
			<channel>
			<title><![CDATA[ HIgh PERformance COMmunications]]></title>
			<link><![CDATA[http://hipercom.thomasclausen.net/resteam/]]></link>
			<description><![CDATA[ HIgh PERformance COMmunications]]></description>
			<pubDate><![CDATA[Wed, 08 Sep 2010 09:34:20 GMT]]></pubDate>
			<lastBuildDate><![CDATA[Wed, 08 Sep 2010 09:34:20 GMT]]></lastBuildDate>
			<language><![CDATA[en-us]]></language>
<item>				<title><![CDATA[The Hipercom Team]]></title>
				<link><![CDATA[http://hipercom.thomasclausen.net/resteam/]]></link>
				<description><![CDATA[<img src="http://hipercom.thomasclausen.net/resteam/data/introduction_main_feature.jpg" border="0" width="250"><br><b>The Hipercom Team</b><br>Hipercom federates three groups of researchers, located at INRIA, LRI and at Ecole Polytechnique, forming a broad team on research in computer networks and telecommunications, in particular wireless and ad hoc networking. The combined size of the team is about 30 people, including staff researchers and students.<br />
For details of the activities within Hipercom @LIX, as well as information on our team members, please explore the menu on the left.]]></description>
				<category><![CDATA[Main Feature]]></category>
				<pubDate><![CDATA[Thu, 13 Mar 2008 20:29:51 GMT]]></pubDate>
				<guid isPermaLink="false"><![CDATA[mainfeature]]></guid>
</item><item>				<title><![CDATA[OSPF over Multi-Hop Ad Hoc Wireless Communications]]></title>
				<link><![CDATA[http://hipercom.thomasclausen.net/resteam/]]></link>
				<description><![CDATA[			
			<table width="100%">
				<tr>
					<td valign="top" nowrap>
			
						<img src="http://hipercom.thomasclausen.net/resteam/data/publications/37a91b096c3e145423fb8a3444da89d5.PNG" border="0" width="130">
			
					</td>
					<td width="100%" valign="top">
						<table width="100%">  
							<!-- publication date -->
							<tr>
								<td valign="top" nowrap>
									Publication date:
								</td>
								<td width="100%" valign="top">
									2010-09-01								</td>
							</tr>
							<!-- Authors -->
							<tr>
								<td valign="top" nowrap>
									Authors:
								</td>
								<td width="100%" valign="top">
									E. Baccelli; J. A. Cordero; P. Jacquet								</td>
							</tr>
							<!-- Published in  -->
							<tr>
								<td valign="top" nowrap>
									Published in:
								</td>
								<td width="100%" valign="top">
									International Journal of Computer Networks &amp; Communications								</td>
							</tr>							
												
							<!-- URL -->
							<tr>
								<td valign="top" valign="top" nowrap>
									URL:
								</td>
								<td width="100%" valign="top">
									<a target="_blank" href="http://airccse.org/journal/ijcnc.html">http://airccse.org/journal/ijcnc.html</a>
								</td>
							</tr>
			
						</table>
					</td>					
				</tr>
			</table>
			Efficient OSPF (Open Shortest Path First) operation on multi-hop ad hoc wireless networks has become
desirable, as wireless community mesh networks and vehicular networks emerge using OLSR (Optimized Link State Routing), a link state MANET routing protocol similar to OSPF in many aspects. OSPF is already extensively deployed and well known in wired IP networks, and could provide simple, seamless unification of wired and wireless IP networking routing-wise, if extended to operate efficiently on ad hoc networks. The IETF has thus proposed three different MANET extensions to the OSPF protocol, allowing heterogeneous networks encompassing both wired and wireless routers, which may self-organize as multi-hop wireless subnetworks, and be mobile. Two of these extensions are based on techniques derived from multi-point relaying (MPR). In the following, we compare and analyze these two extensions and we propose a unique, merged approach which out-performs the existing extensions.<br>
			<a target="_blank" href="../data/publications/37a91b096c3e145423fb8a3444da89d5.pdf"><b>Download File</b></a>
]]></description>
				<category><![CDATA[Selected publications]]></category>
				<pubDate><![CDATA[Wed, 08 Sep 2010 09:22:10 GMT]]></pubDate>
				<guid isPermaLink="false"><![CDATA[37a91b096c3e145423fb8a3444da89d5]]></guid>
</item><item>				<title><![CDATA[Security Issues in the Optimized Link State Routing Protocol Version 2 (OLSRV2)]]></title>
				<link><![CDATA[http://hipercom.thomasclausen.net/resteam/]]></link>
				<description><![CDATA[			
			<table width="100%">
				<tr>
					<td valign="top" nowrap>
			
						<img src="http://hipercom.thomasclausen.net/resteam/data/publications/5af5e0b980fe2949236afbfe9d80cace.jpg" border="0" width="130">
			
					</td>
					<td width="100%" valign="top">
						<table width="100%">  
							<!-- publication date -->
							<tr>
								<td valign="top" nowrap>
									Publication date:
								</td>
								<td width="100%" valign="top">
									2010-04-01								</td>
							</tr>
							<!-- Authors -->
							<tr>
								<td valign="top" nowrap>
									Authors:
								</td>
								<td width="100%" valign="top">
									U. Herberg, T. Clausen								</td>
							</tr>
							<!-- Published in  -->
							<tr>
								<td valign="top" nowrap>
									Published in:
								</td>
								<td width="100%" valign="top">
									International Journal of Network Security &amp; Its Applications (IJNSA)								</td>
							</tr>							
												
							<!-- URL -->
							<tr>
								<td valign="top" valign="top" nowrap>
									URL:
								</td>
								<td width="100%" valign="top">
									<a target="_blank" href="http://airccse.org/journal/jnsa10_current.html#apr">http://airccse.org/journal/jnsa10_cur...</a>
								</td>
							</tr>
			
						</table>
					</td>					
				</tr>
			</table>
			Mobile Ad hoc NETworks (MANETs) are leaving  the confines of research laboratories, to find  place in real-world deployments. Outside specialized domains (military, vehicular, etc.), city-wide community-networks are emerging, connecting regular Internet users with each other, and with the Internet, via MANETs. Growing to encompass more than a handful of ``trusted participants'', the question of preserving the MANET network connectivity, even when faced with careless or malicious participants, arises, and must be addressed. 

A first step towards protecting a MANET is to analyze the vulnerabilities of the routing protocol, managing the connectivity. By understanding how the algorithms of the routing protocol operate, and how these can be exploited by those with ill intent, countermeasures can be developed, readying MANETs for wider deployment and use.

This paper takes an abstract look at the algorithms that constitute the Optimized Link State Routing Protocol version 2 (OLSRv2), and identifies for each protocol element the possible vulnerabilities and attacks -- in a certain way, provides a ``cookbook'' for how to best attack an operational OLSRv2 network, or for how to proceed with developing protective countermeasures against these attacks.<br>
			<a target="_blank" href="../data/publications/5af5e0b980fe2949236afbfe9d80cace.pdf"><b>Download File</b></a>
]]></description>
				<category><![CDATA[Selected publications]]></category>
				<pubDate><![CDATA[Sat, 21 Aug 2010 07:25:24 GMT]]></pubDate>
				<guid isPermaLink="false"><![CDATA[5af5e0b980fe2949236afbfe9d80cace]]></guid>
</item><item>				<title><![CDATA[RFC5497: Representing Multi-Value Time in MANETs]]></title>
				<link><![CDATA[http://hipercom.thomasclausen.net/resteam/]]></link>
				<description><![CDATA[			
			<table width="100%">
				<tr>
					<td valign="top" nowrap>
			
						<img src="http://hipercom.thomasclausen.net/resteam/data/publications/6d07545c4293b6b83771ed3bdf53d3c9.png" border="0" width="130">
			
					</td>
					<td width="100%" valign="top">
						<table width="100%">  
							<!-- publication date -->
							<tr>
								<td valign="top" nowrap>
									Publication date:
								</td>
								<td width="100%" valign="top">
									2009-03-13								</td>
							</tr>
							<!-- Authors -->
							<tr>
								<td valign="top" nowrap>
									Authors:
								</td>
								<td width="100%" valign="top">
									T. Clausen, C. Dearlove								</td>
							</tr>
							<!-- Published in  -->
							<tr>
								<td valign="top" nowrap>
									Published in:
								</td>
								<td width="100%" valign="top">
									IETF - Std. Track RFC								</td>
							</tr>							
												
							<!-- URL -->
							<tr>
								<td valign="top" valign="top" nowrap>
									URL:
								</td>
								<td width="100%" valign="top">
									<a target="_blank" href="http://www.rfc-editor.org/rfc/rfc5497.txt">http://www.rfc-editor.org/rfc/rfc5497...</a>
								</td>
							</tr>
			
						</table>
					</td>					
				</tr>
			</table>
			This document describes a general and flexible TLV (type-length-value structure) for representing time-values, such as an interval or a duration, using the generalized Mobile Ad hoc NETwork (MANET) packet/message format.  It defines two Message TLVs and two Address Block TLVs for representing validity and interval times for MANET routing protocols.<br>
			<a target="_blank" href="../data/publications/6d07545c4293b6b83771ed3bdf53d3c9.pdf"><b>Download File</b></a>
]]></description>
				<category><![CDATA[Selected publications]]></category>
				<pubDate><![CDATA[Sat, 21 Aug 2010 07:25:24 GMT]]></pubDate>
				<guid isPermaLink="false"><![CDATA[6d07545c4293b6b83771ed3bdf53d3c9]]></guid>
</item><item>				<title><![CDATA[RFC5449 - OSPF Multipoint Relay (MPR) Extension for Ad Hoc Networks]]></title>
				<link><![CDATA[http://hipercom.thomasclausen.net/resteam/]]></link>
				<description><![CDATA[			
			<table width="100%">
				<tr>
					<td valign="top" nowrap>
			
						<img src="http://hipercom.thomasclausen.net/resteam/data/publications/4722a8a69536bb3e7f6caf5c4842173f.png" border="0" width="130">
			
					</td>
					<td width="100%" valign="top">
						<table width="100%">  
							<!-- publication date -->
							<tr>
								<td valign="top" nowrap>
									Publication date:
								</td>
								<td width="100%" valign="top">
									2009-02-09								</td>
							</tr>
							<!-- Authors -->
							<tr>
								<td valign="top" nowrap>
									Authors:
								</td>
								<td width="100%" valign="top">
									E. Baccelli, T. Clausen, P. Jacquet. D. Nguyen								</td>
							</tr>
							<!-- Published in  -->
							<tr>
								<td valign="top" nowrap>
									Published in:
								</td>
								<td width="100%" valign="top">
									IETF - Exp. RFC								</td>
							</tr>							
												
							<!-- URL -->
							<tr>
								<td valign="top" valign="top" nowrap>
									URL:
								</td>
								<td width="100%" valign="top">
									<a target="_blank" href="http://www.rfc-editor.org/rfc/rfc5449.txt">http://www.rfc-editor.org/rfc/rfc5449...</a>
								</td>
							</tr>
			
						</table>
					</td>					
				</tr>
			</table>
			This document specifies an OSPFv3 interface type tailored for mobile ad hoc networks.  This interface type is derived from the broadcast interface type, and is denoted the &quot;OSPFv3 MANET interface type&quot;. <br>
			<a target="_blank" href="../data/publications/4722a8a69536bb3e7f6caf5c4842173f.pdf"><b>Download File</b></a>
]]></description>
				<category><![CDATA[Selected publications]]></category>
				<pubDate><![CDATA[Sat, 21 Aug 2010 07:25:24 GMT]]></pubDate>
				<guid isPermaLink="false"><![CDATA[4722a8a69536bb3e7f6caf5c4842173f]]></guid>
</item><item>				<title><![CDATA[RFC5444 - Generalized Mobile Ad Hoc Network (MANET) Packet/Message Format]]></title>
				<link><![CDATA[http://hipercom.thomasclausen.net/resteam/]]></link>
				<description><![CDATA[			
			<table width="100%">
				<tr>
					<td valign="top" nowrap>
			
						<img src="http://hipercom.thomasclausen.net/resteam/data/publications/5df7d747858f4a76ca8774732c1c4bb7.png" border="0" width="130">
			
					</td>
					<td width="100%" valign="top">
						<table width="100%">  
							<!-- publication date -->
							<tr>
								<td valign="top" nowrap>
									Publication date:
								</td>
								<td width="100%" valign="top">
									2009-02-05								</td>
							</tr>
							<!-- Authors -->
							<tr>
								<td valign="top" nowrap>
									Authors:
								</td>
								<td width="100%" valign="top">
									T. Clausen, C. Dearlove, J. Dean, C. Adjih								</td>
							</tr>
							<!-- Published in  -->
							<tr>
								<td valign="top" nowrap>
									Published in:
								</td>
								<td width="100%" valign="top">
									IETF - Std. Track RFC								</td>
							</tr>							
												
							<!-- URL -->
							<tr>
								<td valign="top" valign="top" nowrap>
									URL:
								</td>
								<td width="100%" valign="top">
									<a target="_blank" href="http://www.ietf.org/rfc/rfc5444.txt">http://www.ietf.org/rfc/rfc5444.txt</a>
								</td>
							</tr>
			
						</table>
					</td>					
				</tr>
			</table>
			This document specifies a packet format capable of carrying multiple messages that may be used by mobile ad hoc network routing protocols.<br>
			<a target="_blank" href="../data/publications/5df7d747858f4a76ca8774732c1c4bb7.pdf"><b>Download File</b></a>
]]></description>
				<category><![CDATA[Selected publications]]></category>
				<pubDate><![CDATA[Sat, 21 Aug 2010 07:25:24 GMT]]></pubDate>
				<guid isPermaLink="false"><![CDATA[5df7d747858f4a76ca8774732c1c4bb7]]></guid>
</item><item>				<title><![CDATA[RFC5148: Jitter Considerations in Mobile Ad Hoc Networks (MANETs)]]></title>
				<link><![CDATA[http://hipercom.thomasclausen.net/resteam/]]></link>
				<description><![CDATA[			
			<table width="100%">
				<tr>
					<td valign="top" nowrap>
			
						<img src="http://hipercom.thomasclausen.net/resteam/data/publications/561a4951d6356d9b78e1c3c3ca818bf3.png" border="0" width="130">
			
					</td>
					<td width="100%" valign="top">
						<table width="100%">  
							<!-- publication date -->
							<tr>
								<td valign="top" nowrap>
									Publication date:
								</td>
								<td width="100%" valign="top">
									2008-02-27								</td>
							</tr>
							<!-- Authors -->
							<tr>
								<td valign="top" nowrap>
									Authors:
								</td>
								<td width="100%" valign="top">
									T. Clausen, C. Dearlove, B. Adamson								</td>
							</tr>
							<!-- Published in  -->
							<tr>
								<td valign="top" nowrap>
									Published in:
								</td>
								<td width="100%" valign="top">
									RFC								</td>
							</tr>							
												
							<!-- URL -->
							<tr>
								<td valign="top" valign="top" nowrap>
									URL:
								</td>
								<td width="100%" valign="top">
									<a target="_blank" href="http://www.rfc-editor.org/rfc/rfc5148.txt">http://www.rfc-editor.org/rfc/rfc5148...</a>
								</td>
							</tr>
			
						</table>
					</td>					
				</tr>
			</table>
			This document provides recommendations for jittering (randomly modifying timing) of control traffic transmissions in Mobile Ad hoc NETwork (MANET) routing protocols to reduce the probability of transmission collisions.  This memo provides information for the Internet community.

<br>
			<a target="_blank" href="../data/publications/561a4951d6356d9b78e1c3c3ca818bf3.pdf"><b>Download File</b></a>
]]></description>
				<category><![CDATA[Selected publications]]></category>
				<pubDate><![CDATA[Sat, 21 Aug 2010 07:25:24 GMT]]></pubDate>
				<guid isPermaLink="false"><![CDATA[561a4951d6356d9b78e1c3c3ca818bf3]]></guid>
</item><item>				<title><![CDATA[RFC3626: The Optimized Link State Routing Protocol]]></title>
				<link><![CDATA[http://hipercom.thomasclausen.net/resteam/]]></link>
				<description><![CDATA[			
			<table width="100%">
				<tr>
					<td valign="top" nowrap>
			
						<img src="http://hipercom.thomasclausen.net/resteam/data/publications/88178ac212e61f32f194f64e5718a6e1.jpg" border="0" width="130">
			
					</td>
					<td width="100%" valign="top">
						<table width="100%">  
							<!-- publication date -->
							<tr>
								<td valign="top" nowrap>
									Publication date:
								</td>
								<td width="100%" valign="top">
									2003-10-01								</td>
							</tr>
							<!-- Authors -->
							<tr>
								<td valign="top" nowrap>
									Authors:
								</td>
								<td width="100%" valign="top">
									T. Clausen, P. Jacquet								</td>
							</tr>
							<!-- Published in  -->
							<tr>
								<td valign="top" nowrap>
									Published in:
								</td>
								<td width="100%" valign="top">
									The Internet Engineering Task Force (IETF) - MANET Working Group								</td>
							</tr>							
												
							<!-- URL -->
							<tr>
								<td valign="top" valign="top" nowrap>
									URL:
								</td>
								<td width="100%" valign="top">
									<a target="_blank" href="http://www.ietf.org/html.charters/manet-charter.html">http://www.ietf.org/html.charters/man...</a>
								</td>
							</tr>
			
						</table>
					</td>					
				</tr>
			</table>
			This document describes the Optimized Link State Routing (OLSR) protocol for mobile ad hoc networks.  The protocol is an optimization of the classical link state algorithm tailored to the requirements of a mobile wireless LAN.  The key concept used in the protocol is that of multipoint relays (MPRs).  MPRs are selected nodes which forward broadcast messages during the flooding process.  This technique substantially reduces the message overhead as compared to a classical flooding mechanism, where every node retransmits each message when it receives the first copy of the message.  In OLSR, link state information is generated only by nodes elected as MPRs.  Thus, a second optimization is achieved by minimizing the number of control messages flooded in the network.  As a third optimization, an MPR node may chose to report only links between itself and its MPR selectors.  Hence, as contrary to the classic link state algorithm, partial link state information is distributed in the network.  This information is then used for route calculation.  OLSR provides optimal routes (in terms of number of hops).  The protocol is particularly suitable for large and dense networks as the technique of MPRs works well in this context.<br>
			<a target="_blank" href="../data/publications/88178ac212e61f32f194f64e5718a6e1.pdf"><b>Download File</b></a>
]]></description>
				<category><![CDATA[Selected publications]]></category>
				<pubDate><![CDATA[Sat, 21 Aug 2010 07:25:24 GMT]]></pubDate>
				<guid isPermaLink="false"><![CDATA[88178ac212e61f32f194f64e5718a6e1]]></guid>
</item><item>				<title><![CDATA[The OLSR Success Story]]></title>
				<link><![CDATA[http://hipercom.thomasclausen.net/resteam/]]></link>
				<description><![CDATA[<img src="http://hipercom.thomasclausen.net/resteam/data/secondary_features/3a298f148fa620b78b9fd2a942f95db1.jpg" border="0" width="130" align="left">A routing protocol for Mobile Ad hoc NETworks (MANETs) developed integrally by the Hipercom project team, OLSR has become standardised and widely adopted:  Google references OLSR with more than 450,000 hits, DARPA uses it as its reference protocol for its tactical networks, there are many urban deployments of OLSR based MESH WiFi networks, and industrial adoption of OLSR is significant.<br />
<br />
Indeed, the OLSR protocol is a rare example of IETF standardisation of a protocol driven from the very beginning (development of algorithms and ideas) to the very end (formal publication of a protocol specification as an RFC - an official document sanctioning the protocol as adopted by the IETF) by a single academic actor - the Hipercom project team.<br />
<br><a href="http://www.ietf.org/rfc/rfc3626.txt">+ More</a>]]></description>
				<category><![CDATA[Features]]></category>
				<pubDate><![CDATA[Tue, 16 Oct 2007 21:52:18 GMT]]></pubDate>
				<guid isPermaLink="false"><![CDATA[3a298f148fa620b78b9fd2a942f95db1]]></guid>
</item>			</channel>
		</rss>
