The ARP (Active Reservation Protocol) project explored the use
of portable and dyamically-extensible protocol code for network control
protocols, especially for signaling protocols. In particular, the
project developed a general-purpose active networks Execution
Environment (EE), called the Active
Signaling Protocol EE or ASP EE. The ASP EE was designed to
control active applications (AAs) executing in the control plane.
Security and isolation are important issues in the design
of the ASP EE. Different AAs executing within the EE are effectively
isolated, and the standard Java `sand-boxing' severely restricts the mischief
that an AA can cause. We believe that we will ultimately be able
to allow arbitrary AAs to be executed within the ASP EE.
The ASP EE is compatible with the ABone and deployed as
a permanent EE in a group of ABone nodes.
The ARP project has developed two significant AAs to execute
under the ASP EE.
A basic set of
node query functions, including
active versions of the familiar ping and traceroute, has been developed.
Jrsvp implements the Internet signaling protocol RSVP.
Except for framing, its network packet formats are compatible with the
Jrip implements the routing protocol RIP. This protocol
is implemented as an AA but it sets the default forwarding table used by
the ASP EE for ASP active packets. . This is accomplished
using a "Network Management Interface" (NMI) to the ASP EE.
contains a web form which can be used to generate the topology files for the
of the ASP EE and related AA's was narrowly released. (12/03/1999)
release 1.1 of the ASP EE and related AA's and UA's. (03/17/2000)
release 1.2 of the ASP EE and related AA's and UA's. (08/11/2000)
release 1.3 of the ASP EE and related AA's and UA's. (11/17/2000)
release 1.3.2 of the ASP EE and related AA's and UA's. (3/20/2001)
release 1.4 of the ASP EE and related AA's and UA's. (5/22/2001)
release 1.5 of the ASP EE and related AA's and UA's. (11/28/2001)
release 1.6 of the ASP EE and related AA's and UA's. (10/14/2002)