Index: script.txt
==================================================================
--- script.txt
+++ script.txt
@@ -40,12 +40,13 @@
 - Also includes nodes in participating research centres.
 - All linked together over the FEDERICA research backbone.
 - All its software and documentation is “free as in freedom”, anyone can setup
   a CONFINE testbed like Community-Lab.
 
-* Challenges and requirements
-CNs pose unique challenges for a testbed.  How to
+* Requirements and challenges
+A testbed has requirements that are challenged by the unique characteristics
+of CNs.  For instance, how to
 
 ** Simple management vs. Distributed node ownership
 - manage devices belonging to diverse owners?
 
 ** Features vs. Lightweight, low cost
@@ -118,52 +119,55 @@
     runs no routing protocol).
 - The research device
   - Usually more powerful than CD, since experiments run here.
   - A separated RD minimizes tampering with CN infrastructure.
     - Also experiments can't crash the CD.
-  - Runs OpenWrt firmware customized by CONFINE.
+  - Runs the versatile, light and free OpenWrt distro, customized by CONFINE.
   - Slivers are implemented as lightweight Linux containers.
-    - Provide a familiar and flexible env for researchers.
+    - So researchers get root access to a familiar environment.
   - Direct interfaces allow low-level interaction of experiments with the CN
     bypassing the CD.
   - Control software
-    - Uses LXC tools on containers to enforce resource limitation, resource
+    - Uses LXC tools to manage containers and enforce resource limits,
       isolation and node stability.
     - Uses traffic control, filtering and anonymization to ensure network
       stability, isolation and privacy (partialy implemented).
 - The recovery device (not implemented) can force a remote hardware reboot of
   the RD in case it hangs.  It also helps with upgrade and recovery.
 
-* Supported experiments
+* Experiments support
 # Node simplified diagram, hover to interesting parts.
 Researchers can configure slivers with different types of network interfaces
 depending on the connectivity needs of experiments.  For instance, to
 
-- mimic a home PC: use the private interface, which has traffic forwarded
+- mimic a home PC: use the private interface, which has L3 traffic forwarded
   using NAT to the CN but filtered to ensure network stability.
 - implement a network service: create a public interface, which has a CN
-  address and traffic routed directly to the CN but filtered to ensure network
-  stability.
+  address and L3 traffic routed directly to the CN but filtered to ensure
+  network stability.
 - experiment with routing algorithms: create an isolated interface, which uses
-  a VLAN on top of a direct interface.  All traffic is allowed, but only
+  a VLAN on top of a direct interface.  All L2 traffic is allowed, but only
   between other slivers of the same slice with isolated interfaces on the same
   physical link.
 
-Not yet implemented:
+These were demonstrated with BitTorrent and mesh routing experiments at IEEE
+P2P'12 Conference.  Future support is planned for experiments that:
 
 - analyze traffic: create a passive interface to capture traffic on a direct
   interface, which is filtered and anonymized to ensure network privacy.
 - perform low-level testing: the sliver is given free raw access to a direct
   interface.  For privacy, isolation and stability reasons this should only be
   allowed in exceptional occasions.
 
-RDs will soon be able to provide link quality and bandwidth usage measurements
-for all their interfaces through the DLEP protocol.
+# List example experiments, add these.
+Besides experiments run in slices, researchers will soon be able to collect
+link quality and bandwidth usage measurements of all RDs' interfaces through
+the DLEP protocol.
 
-Finally, the server and nodes publish management information through an API
-that can be used to study the testbed itself, or to implement external
-services like node monitoring and selection.
+Moreover, the server and nodes will soon publish management information
+through an API that would be used to study the testbed itself, or to implement
+external services like node monitoring and selection.
 
 ** An example experiment
 # Event diagram, hover over components explained.
 To show how the testbed works: two slivers which ping each other.
 

Index: slides.svg
==================================================================
--- slides.svg
+++ slides.svg
cannot compute difference between binary files