Changes between Version 5 and Version 6 of BaseDemos

Timestamp:

Nov 23, 2010, 8:22:45 AM (14 years ago)

Author:

huebsch

Comment:

--

BaseDemos

@@ -8 +8 @@
 '''
 
-The main intention of the demonstration is to show how
-ariba eases application deployment upon heterogeneous net-
-works. We consider an exemplary scenario (as shown in
-Figure 2) that consists of two LANs, one running IPv4 and
-one running IPv6, respectively. Furthermore, one WLAN
-attached to notebook N1 and a bluetooth device connected
-to notebook N3 are deployed. The WLAN uses NAT to
-multiplex the single IP address of the access point to mul-
-tiple wireless devices. Furthermore, we employ native RF-
-COMM for communication between N3 and P2, using MAC
-addresses. Notebook N2 and N4 are dual-stacked and con-
-nected to both, the IPv4 and IPv6 LAN.
+The main intention of the demonstration is to show how ariba eases application deployment upon heterogeneous networks. We consider an exemplary scenario (as shown in Figure 2) that consists of two LANs, one running IPv4 and one running IPv6, respectively. Furthermore, one WLAN attached to notebook N1 and a bluetooth device connected to notebook N3 are deployed. The WLAN uses NAT to multiplex the single IP address of the access point to multiple wireless devices. Furthermore, we employ native RFCOMM for communication between N3 and P2, using MAC addresses. Notebook N2 and N4 are dual-stacked and connected to both, the IPv4 and IPv6 LAN.
 All end-systems in this scenario run an application that
 requires end-to-end connectivity. In the following we refer
@@ -82 +71 @@
 so called Connectivity Domains—and assigns a Connectivity
 Domain Identifier (CDID) to each Connectivity Domain.
-Using a gossip mechanism nodes inform each other about
+Using a gossip mechanism nodes inform each other about changes in connectivity characteristics (i. e., a Connectivity
+Domain split or merge) and resolve conflicting CDIDs. All
+nodes include CDIDs in their routing information. Thus
+other nodes can immediately decide whether they can com-
+municate directly with a certain node by comparing CDIDs,
+which can also be used to discover shorter relay paths [3].
+For demonstration purpose, the network settings shown in
+Figure 2 can be modified by connecting and removing relay-
+ing nodes, as well as connecting nodes to different networks
+interactively. ariba will automatically sustain connectivity
+between nodes. To visualize internal protocol functionality
+the application additionally shows its local view of the net-
+work: relay paths traversing the node and logical neighbors.
+In its current form our approach has the following open
+issues: First, the overlay re-join mechanisms may suffer from
+overlay partitioning, and second, relay paths may degrade
+in case of network setting reconfiguration. However, our
+approach is feasible in a practical setting and allows easy
+deployment, as shown in the demonstration.
+