<rdf:RDF
 xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
 xmlns="http://purl.org/rss/1.0/"
 xmlns:dc="http://purl.org/dc/elements/1.1/"
 xmlns:cc="http://web.resource.org/cc/"
 >
<!--
	This ontology document is licensed under the Creative Commons
	Attribution License. To view a copy of this license, visit
	http://creativecommons.org/licenses/by/2.0/ or send a letter to
	Creative Commons, 559 Nathan Abbott Way, Stanford, California
	94305, USA.
-->
 <channel rdf:about="http://ebiquity.umbc.edu//tags/html/?t=cross-layer+analysis">
  <cc:license rdf:resource="http://creativecommons.org/licenses/by/2.0/" />
  <title><![CDATA[UMBC ebiquity RSS Tag Search]]></title>
  <link><![CDATA[http://ebiquity.umbc.edu//tags/html/?t=cross-layer+analysis]]></link>
  <description><![CDATA[UMBC ebiquity RSS Tag Search for cross-layer analysis]]></description>
  <items>
    <rdf:Seq>
      <rdf:li resource="http://ebiquity.umbc.edu/event/html/id/117/Cross-layer-Analysis-for-Detecting-Wireless-Misbehavior"/>
      <rdf:li resource="http://ebiquity.umbc.edu/project/html/id/74/Distributed-Trust-Management-in-Mobile-Ad-Hoc-Networks"/>
      <rdf:li resource="http://ebiquity.umbc.edu/paper/html/id/267/Cross-layer-Analysis-for-Detecting-Wireless-Misbehaviour"/>
      <rdf:li resource="http://ebiquity.umbc.edu/resource/html/id/150/Cross-layer-Analysis-for-Detecting-Wireless-Misbehavior"/>
      <rdf:li resource="http://ebiquity.umbc.edu/resource/html/id/151/Cross-layer-Analysis-for-Detecting-Wireless-Misbehavior"/>
      <rdf:li resource="http://ebiquity.umbc.edu/resource/html/id/177/Detecting-Misbehavior-in-MANETs-Through-Cross-Layer-Analysis-May-2006-"/>
    </rdf:Seq>
  </items>
 </channel>
 <item rdf:about="http://ebiquity.umbc.edu/event/html/id/117/Cross-layer-Analysis-for-Detecting-Wireless-Misbehavior">
  <title><![CDATA[Cross-layer Analysis for Detecting Wireless Misbehavior]]></title>
  <link>http://ebiquity.umbc.edu/event/html/id/117/Cross-layer-Analysis-for-Detecting-Wireless-Misbehavior</link>
  <description><![CDATA[Intrusion Detections 
Systems(IDSs) in ad hoc networks monitor other devices for
intentional deviation from protocol, i.e., misbehavior. This process
is complicated due
to limited radio range and mobility of nodes. Unlike conventional
IDSs, it is not
possible to monitor nodes for long durations. As a result IDSs suffer from
a large number of false positives. Moreover other environmental conditions like
radio interference and congestion increase false positives,
complicating classific...]]></description>
  <dc:date>2005-10-19</dc:date>
 </item>
 <item rdf:about="http://ebiquity.umbc.edu/project/html/id/74/Distributed-Trust-Management-in-Mobile-Ad-Hoc-Networks">
  <title><![CDATA[Distributed Trust Management in Mobile Ad Hoc Networks]]></title>
  <link>http://ebiquity.umbc.edu/project/html/id/74/Distributed-Trust-Management-in-Mobile-Ad-Hoc-Networks</link>
  <dc:date>2004-12-01</dc:date>
 </item>
 <item rdf:about="http://ebiquity.umbc.edu/paper/html/id/267/Cross-layer-Analysis-for-Detecting-Wireless-Misbehaviour">
  <title><![CDATA[Cross-layer Analysis for Detecting Wireless Misbehaviour]]></title>
  <link>http://ebiquity.umbc.edu/paper/html/id/267/Cross-layer-Analysis-for-Detecting-Wireless-Misbehaviour</link>
  <description><![CDATA[Intrusion detections systems (IDSs) in ad hoc networks monitor other devices for
significant deviation from protocol -- misbehavior. This process is complicated due
to limited radio range and mobility of nodes. Unlike conventional IDSs, it is not
possible to monitor nodes for long durations. As a result IDSs suffer from 
a large number of false positives. Moreover other environmental conditions like
radio interference and congestion increase false positives, complicating classification
...]]></description>
  <dc:date>2006-01-06</dc:date>
 </item>
 <item rdf:about="http://ebiquity.umbc.edu/resource/html/id/150/Cross-layer-Analysis-for-Detecting-Wireless-Misbehavior">
  <title><![CDATA[Cross-layer Analysis for Detecting Wireless Misbehavior]]></title>
  <link>http://ebiquity.umbc.edu/resource/html/id/150/Cross-layer-Analysis-for-Detecting-Wireless-Misbehavior</link>
  <description><![CDATA[Intrusion Detections Systems(IDSs) in ad hoc networks monitor other devices for
intentional deviation from protocol, i.e., misbehavior. This process
is complicated due
to limited radio range and mobility of nodes. Unlike conventional
IDSs, it is not
possible to monitor nodes for long durations. As a result IDSs suffer from
a large number of false positives. Moreover other environmental conditions like
radio interference and congestion increase false positives,
complicating classificat...]]></description>
  <dc:date>2005-10-19</dc:date>
 </item>
 <item rdf:about="http://ebiquity.umbc.edu/resource/html/id/151/Cross-layer-Analysis-for-Detecting-Wireless-Misbehavior">
  <title><![CDATA[Cross-layer Analysis for Detecting Wireless Misbehavior]]></title>
  <link>http://ebiquity.umbc.edu/resource/html/id/151/Cross-layer-Analysis-for-Detecting-Wireless-Misbehavior</link>
  <description><![CDATA[Intrusion Detections Systems(IDSs) in ad hoc networks monitor other devices for
intentional deviation from protocol, i.e., misbehavior. This process
is complicated due
to limited radio range and mobility of nodes. Unlike conventional
IDSs, it is not
possible to monitor nodes for long durations. As a result IDSs suffer from
a large number of false positives. Moreover other environmental conditions like
radio interference and congestion increase false positives,
complicating classificat...]]></description>
  <dc:date>2005-10-19</dc:date>
 </item>
 <item rdf:about="http://ebiquity.umbc.edu/resource/html/id/177/Detecting-Misbehavior-in-MANETs-Through-Cross-Layer-Analysis-May-2006-">
  <title><![CDATA[Detecting Misbehavior in MANETs Through Cross-Layer Analysis (May 2006)]]></title>
  <link>http://ebiquity.umbc.edu/resource/html/id/177/Detecting-Misbehavior-in-MANETs-Through-Cross-Layer-Analysis-May-2006-</link>
  <description><![CDATA[Poster for the CSEE Research Review.]]></description>
  <dc:date>2006-05-04</dc:date>
 </item>
</rdf:RDF>
