Changes between Version 12 and Version 13 of BaseDemos

Timestamp:

Nov 23, 2010, 8:41:48 AM (14 years ago)

Author:

huebsch

Comment:

--

BaseDemos

@@ -31 +31 @@
 In our demonstration we use two off-the-shelf servers as legacy applications: a web server on P2 using bluetooth, and a Jabber server on notebook N1 connected to the IPv4 WLAN access point and the IPv6 LAN. For setting up these servers without ariba several issues have to be addressed: To access those servers from any device participating in the demo is subject to manual configuration and error-prone. For example, to connect to the IPv4 LAN using bluetooth a personal area daemon (pand) is needed. Furthermore, a translation mechanism is required to forward IPv4 packets to the IPv6 network. Servers located behind NAT middleboxes would impose further problems that require manual configuration such as port forwarding.
 
+Through the integration of ariba with OCALA the presented scenario is handled in a self-organizing and transparent way. Consider a scenario, when P1 wants to access the web server on P2 using a web browser: first, the web browser issues a DNS request for p2.spovnet.aribaocd. OCALA captures this request and uses the OC-D implementation to map
+it to an ariba node identifier and return a private IP destination address to the legacy application. Second, ariba transparently establishes a relay path between P1 and P2 using N1, N2 or N4, and N3 to provide end-to-end connectivity across the heterogeneous network. This is accomplished by ariba in a self-organizing manner without infrastructure-support or
+manual configuration.
+
+As mentioned before ariba is able to adapt when the network topology changes. Therefore it is possible to interactively remove or establish new connections between the devices by
+plugging and unplugging Ethernet cables. For example, N2 may get disconnected from the IPv6 network. ariba detects such network dynamics and transparently establishes new routes in a collaborative fashion to re-route traffic: Now, traffic that formerly traversed N2 is now sent through N4. Note that without ariba topology changes would require manual re-configuration of gateways. During that time connectivity is not available to the application.
+