1. Dynamically Evolving Klaim Nets Lorenzo Bettini bettini@dsi.unifi.it Joint work with Michele Loreti, Rosario Pugliese Dipartimento di Sistemi ed Informatica, Firenze http://music.dsi.unifi.it

2. Dynamic Infrastructure It evolves over time: New nodes can get connected Existing nodes can disconnect Connections and disconnections can be temporary and unexpected A connection can be established on the fly with wireless devices Ad-hoc paths to services can be establish to enable communication among components

3. Dynamic Infrastructure The assumption that the underlying network is always available may be too strong; Permanent connection may not always be available; The knowledge of the address of a remote host may be not sufficient to communicate with it; Necessity of making Node Connectivity explicit in the language.

4. Communication Layer in Klaim is based on nodes’ location knowledge, is influenced by: Allocation environments; Tuple and Process distribution.

5. Connections and Disconnections TS s1s1 s2s2 Two nodes are disconnected if one doesn’t know the locality of the other

6. Connections and Disconnections TS s1s1 s2s2 s2s2 There is a (re)connection when one gets to know about the other

7. Connections and Disconnections TS s1s1 s2s2 Two nodes will be disconnected again when that knowledge is lost s2s2

8. Node “Mobility” TS s1s1 s2s2 s3s3 s3s3 s3s3 Node mobility corresponds to mobility of (knowledge of) links If a process, that knows a node, moves, then the known node moves too. s3s3

9. Clusters & SuperProcesses A Cluster is a collection of nodes There can be multiple clusters Two nodes can interact with each other only if they stay in the same cluster SuperProcesses are processes that: Can create new Clusters; Can add or remove their node to Clusters; Cannot move

10. New Actions Create a new cluster: newc(w) Add a node to a cluster: add(c) Remove a node from a cluster: rm(c) Not indexed with a locality They act on the node they are executed on.

11. s c2c2 s s Example c1c1 newc(w) add(c 2 ) rm(c 1 )

12. Syntax N ::= s ::  P  c :: {s}  N | N P ::= nil  out(et)  act.P  P | P  act.P + act.P  X  A SP ::= P  sact.SP  SP | SP act ::= out(t)@l  in(t)@l  read(t)@l  eval(P)@l  newloc(SP,u) sact::= add(c)  rm(c)  newc(w)

13. Connection Modes Tethered mode Disconnected mode Untethered mode

14. Tethered mode WAN connectivity is available Information can be accessed from any point at any time Idealized situation that takes place only for a limited computers in a network.

15. Disconnected mode WAN connectivity is available Users can work offline When online a user works like in Tethered Mode When a user goes online reconciliation and/or notification can be needed. Typical for a user that does not own a network access. The user works in isolation and, at some time, connects to Internet (e.g. via a modem).

16. Untethered mode WAN connectivity is unavailable Local-area connectivity may still be available Communication: is enabled by wireless devices is limited to those devices that are in a communication range Usual form for a mobile user, that from time to time enters different areas where connectivity is constrained (e.g. by firewalls).

17. Tethered mode All nodes are in the same cluster and there are no SuperProcesses.

18. Disconnected mode All nodes are in the same cluster Occasionally some node can be removed and added

19. Untethered mode Multiple clusters are available Nodes can change cluster

20. Scenarios Location dependent connection Ad-hoc networking Disconnection

21. Location-dependent Connection A mechanical engineer visits a plant in the Third World WAN connectivity is not available There is a single wireless access point When connected engineer can access plant’s resources (data and applications)

22. Location-dependent Connection 0101 Plant-access point 0101 add(c ap ) Private area c ap rm(c ap ) cpcp

23. Ad hoc networking A team of experts meet in a site where a new plant must be established Experts can interact locally by using an ad hoc network, sharing data and resources Occasionally connection to the headquarters might be needed to check additional information

24. Local area Ad hoc networking Headquarters Local area

25. Disconnection A software engineer works in isolation At a given point she dials up and gets reconnected to a virtual community server She downloads work updates She asks for help and goes offline Later she reconnects to the virtual community: She contacts one of the connected experts She establishes a synchronous communication After acquiring enough information she logs off Finally, when she ends her work, she logs on and uploads the artifacts

26. Disconnection s2s2 0100 s2s2 c add(c) rm(c) add(c) rm(c) add(c)

27. Remarks Proposed extensions can be “expressed” in standard Klaim; Klaim’s Logical framework can be automatically applied to extended Klaim; Klaim’s Types for Access Control can be easily extended too. Proposed extensions can be “expressed” in standard Klaim; Klaim’s Logical framework can be automatically applied to extended Klaim; Klaim’s Types for Access Control can be easily extended too.

28. Comparison with Ambients Clusters do not move Can intersect Represent a communication ability, not necessarily an environment Still locality-aware More similar to channels

29. Translation in standard Klaim A cluster c becomes a node s c If s belongs to c then tuple (s) is in the TS of s c and (cluster, s c ) in the TS of s newc becomes newloc add(c) becomes out(self)@s c.out(cluster, s c )@self rm(c) becomes in(self)@s c.in(cluster, s c )@self

30. Translation in standard Klaim Communication and migration operations are translated into sequences of operations that first test for the presence of a cluster and then perform the operation A counter should be used in order to exhaustively examine all the clusters to which a node belongs

31. Extending the implementation

32. Connecting to a Klava Net hostnet.dsi.unifi.it $> java client2 hostnet.dsi.unifi.it 9999 Connecting to hostnet.dsi.unifi.it:9999... Login as client2... Login successful! $> java Klava.Net Starting Net on port 9999 150.217.14.14

33. Communication in Klava Net s1s2

34. Extending the implementation s1 s2 Net s1s2

35. Extending the implementation s1 s2 c1 c2 s3 c1 s1s2 c2 s3

36. Future work Extend the implementation Apply the extensions to our existing frameworks Merge with Structured Nets

37. Structured Nets Ordering relation on nodes (<): is- parent-of Routing function (  ): the nodes that have to be crossed to reach a site System operations (sys(t)): to access and modify the structure of the net