M. Hicks et al. PLANet: An Active Network Testbed. http://www.cis.upenn.edu/~switchware/papers/planet.ps, 1998.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....the above requirements may not be enough to provide security in an active network environment. However, it will remove the costly run time checks that many current languages have. Since performance is a key issue, this is very important. PLAN Programming Language for active networks (PLAN) [31, 30] is an example of a language specifically deployed for active networks that tries to address the security and safety issues from a programming point of view. PLAN is a new language for programs that form the packets of a programmable network. These programs replace the packet headers used in ....

M.Hicks et al., PLANet: An Active Network Testbed, http://www.cis. upenn.edu/switchware/papers/planet.ps

....we will need to give some general introduction to the requirements, design, programming model, applications, and implementation of PLAN, but details are best obtained from the project home page. 2 PLAN is part of the SwitchWare Active Network Architecture; the language design was introduced in [8,9] and the overall architecture in [1] In this paper we discuss two of the primary attributes of PLAN that are interesting for its specification, namely its type system and its model for reasoning about global properties based on available service layer functions. After general discussion of each ....

....connecting to a different network and with a different IP address for each. Packets usually travel through the internetwork with the help of routing tables maintained on the routers; such tables specify the next router to visit to get to a given destination. A PLAN active network (PLANet, [9]) is based on the same philosophy, with the difference that packets now contain programs that need to be executed rather than forwarded or routed. The PLAN specification models this network through a multiset of messages. Each message is of the form emit(dev, packet) where dev is the interface ....

[Article contains additional citation context not shown here]

Mike Hicks, Jonathan T. Moore, Scott Alexander, Carl A. Gunter, and Scott Nettles. Planet: An active network testbed. www.cis.upenn.edu/ ~switchware/papers/planet.ps, February 1998.

....of the apparent AO security enjoyed by the Internet protocols may be lost if programmability of routers is available to outsiders and the right kinds of operations are made available to them. For example, researchers in the SwitchWare Project at the University of Pennsylvania have experimented [15, 7] with downloadable OCaml modules capable of dynamically altering switching and queuing strategies on routers. Undoubtably the privilege to use such a function will be limited by some form of cryptographic authorization system [6] but the underlying capabilities easily accommodate a ....

Mike Hicks, Jonathan T. Moore, Scott Alexander, Carl A. Gunter, and Scott Nettles. Planet: An active network testbed. www.cis.upenn.edu/~switchware/papers/planet.ps, February 1998.

....provides a powerful programming style which we describe in [21] and have illustrated in PLANet. PLAN provides very efficient, light weight mobile agents that invoke services to achieve flexible network utilization that can be customized to the needs of particular users or applications. PLANet [23] is an internetwork in which PLAN forms the interoperability layer over various (virtual) link layers (currently we support Ethernet and IP) In order to implement the PLAN semantics of remote evaluation, we provide active extension based im plementations of various internetworking tasks, such ....

....resolution, name resolution, etc. Each PLANet active node has the following components: 1) packet processing core (2) network functions (3) the PLAN interpreter (4) library of service routines Packet Processing Core The operation of a PLANet node is depicted in Figure 2, which is drawn from [23]. In its idle state, an Routing Extension PLAN interpreter PLAN program(s) PLAN layer Link layer Extensions Active Ethernet IP Figure 2: PLANet node architecture active node has one thread running for each network interface type, waiting for input on that interface 2 . Once a packet arrives, the ....

Michael Hicks, Jonathan T. Moore, Scott Alexander, Carl A. Gunter, and Scott Nettles. Planet: A active network testbed. 1998.

....provides a powerful programming style which we describe in [21] and have illustrated in PLANet. PLAN provides very efficient, light weight mobile agents that invoke services to achieve flexible network utilization that can be customized to the needs of particular users or applications. PLANet [23] is our implementation of an internet work in which PLAN forms the interoperability layer over various (virtual) link layers (currently we support Ethernet and IP) In order to implement the PLAN semantics of remote evaluation, we provide active extension based implementations of various ....

....resolution, name resolution, etc. Each PLANet active node has the following components: 1) packet processing core (2) network functions (3) the PLAN interpreter (4) library of service routines Packet Processing Core The operation of a PLANet node is depicted in Figure 2, which is drawn from [23]. In its idle state, an Routing Extension PLAN interpreter PLAN program(s) PLAN layer Link layer Extensions Active Ethernet IP Figure 2: PLANet node architecture active node has one thread running for each network interface type, waiting for input on that interface 2 . Once a packet arrives, the ....

Michael Hicks, Jonathan T. Moore, Scott Alexander, Carl A. Gunter, and Scott Nettles. Planet: A active network testbed. 1998.

No context found.

M. Hicks et al. PLANet: An Active Network Testbed. http://www.cis.upenn.edu/~switchware/papers/planet.ps, 1998.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC