Changeset 2794

Show
Ignore:
Timestamp:
10/30/09 17:20:57 (4 weeks ago)
Author:
stevedh
Message:

more nits

Location:
docs/Lowthane/ipsn10
Files:
5 modified

Legend:

Unmodified
Added
Removed

  • docs/Lowthane/ipsn10/abstract.tex

    r2751 r2794  
    1010 
    1111In this paper, we begin with collection routing as our foundation and 
    12 build up to point-to-point through a series of enhancements and 
     12build up point-to-point through a series of enhancements and 
    1313optimizations, preserving collection performance and mirroring 
    1414contemporary system architecture in the process.  We show that such 
    … …  
    1717workloads, and especially on the factors important in this regime -- 
    1818code and memory footprint, routing stretch, and protocol overhead.  We 
    19 implement our proposed protocol to route IPv6 traffic, evaluate it in 
    20 both simulation and on multiple deployments, and compare it with 
    21 TinyAODV in controlled settings. 
     19implement our proposed protocol to route IPv6 traffic, evaluate it on  
     20multiple deployments, and compare it to 
     21CTP and TinyAODV in controlled settings. 
    2222 
    2323%% Existing routing protocols for sensor networks either exclusively 

  • docs/Lowthane/ipsn10/design.tex

    r2785 r2794  
    120120{\lowthane} uses Router Advertisement and Router Solicitation messages to 
    121121achieve router discovery, extending existing IPv6 Neighbor 
    122 Discovery~\cite{ipv6-nd} mechanisms.  Router Solicitation messages are sent using binary exponential timers, and this timer is reset when either a node boots, or when no default route (\S~\ref{sssec:default-route}) to a {\controller} exists.  Nodes that receive a Router Solicitation respond with a Router Advertisement if they have a valid default route. 
     122Discovery mechanisms \cite{ipv6-nd}.  Router Solicitation messages are sent using binary exponential timers, and this timer is reset when either a node boots, or when no default route (\S~\ref{sssec:default-route}) to a {\controller} exists.  Nodes that receive a Router Solicitation respond with a Router Advertisement if they have a valid default route. 
    123123 
    124124We add two pieces of 
    … …  
    179179incurred on packets actually containing topology updates. 
    180180 
    181 The {\controller} aggregates these topology reports to create a global view of 
     181{\Controller}s aggregate these topology reports to create a global view of 
    182182the topology, known as the Link State Database.  Figure \ref{fig:arch} shows a 
    183183partial view of the LSDB maintained by controller 1: for instance, the link 
    … …  
    285285this prevents {\lowthane} from building up its confidence in the link cost 
    286286estimates of other default routes.  In order to remedy this, each time a 
    287 default route is needed, a node randomly selects 
    288 another entry in the table to use with some probability.  This route temporarily assumes the 
     287default route is needed, a node may select 
     288another entry in the table to use..  This route temporarily assumes the 
    289289role of Primary Default Route, and is used until it fails. 
    290290 

  • docs/Lowthane/ipsn10/discussion.tex

    r2785 r2794  
    1111\label{sec:extensions} 
    1212 
    13 Although this paper has concentrated on the mechanics of building up a robust 
    14 point-to-point routing protocol based on collection routing, having a 
    15 centralized routing database naturally lends itsself to a number of different 
    16 uses. 
     13% Although this paper has concentrated on the mechanics of building up a robust 
     14% point-to-point routing protocol based on collection routing, having a 
     15% centralized routing database naturally lends itsself to a number of different 
     16% uses. 
    1717 
    1818\subsubsection{Multicast Forwarding} 

  • docs/Lowthane/ipsn10/evaluation.tex

    r2788 r2794  
    504504Route Request messages.  Nodes along the path forward traffic, generating 
    505505Route Error messages back to the source when a link along the path fails.  A 
    506 comparison AODV's results in Figure \ref{fig:aodv-compr} show that it 
     506comparison with AODV's results in Figure \ref{fig:aodv-compr} show that it 
    507507achieves reasonable overall reliability, although far lower then {\lowthane}. 
    508508Since AODV forms routes based on a flood, it does not have the well-developed 
    … …  
    910910{\emph{Total Size}} & \multicolumn{2}{|c|}{138 Bytes} \\ \hline 
    911911\end{tabular} 
    912 \caption{{\lowthane} Node table sizes} 
     912\caption{Default {\lowthane} node table sizes.} 
    913913\label{tab:state} 
    914914\end{table} 
    … …  
    936936{\bf{Adver.}} & 3 & $\propto$ churn \\ \hline 
    937937\end{tabular} 
    938 \caption{{\lowthane} control overhead} 
     938\caption{Sizes of {\lowthane} table entries.} 
    939939\label{tab:control} 
    940940\end{table} 

  • docs/Lowthane/ipsn10/intro.tex

    r2788 r2794  
    4040while adding efficient point-to-point routing with a minimum of additional 
    4141cost.  This design is a step in the direction towards more hetrogeneous 
    42 networks where sensors, actuators, and controlls can directly communicate 
     42networks where sensors, actuators, and controls communicate directly 
    4343while standard tools are used for debugging. 
    4444 
    4545Our analysis of real-world 
    46 experiments seeks to answer the questions, how well does this general 
     46experiments seeks to answer two questions: how well does this general 
    4747architecture compare to specialized point solutions, and how robust is it?   
    4848We compare to other protocols which each solve a piece of the problem,