This README describes the purpose of the software and date files contained in file
rsvp_authentication_test_all.tar.gz.

The basic process is this:

There is an agent called rsvp_mpc installed in several routers along a 
reservation path.  rsvp_mpc has only one parameter, which is the value of 
ADSPEC for that node. 

After all agents are up and running, a source host will send out an RSVP PATH 
message.  The PATH message will be intercepted at each router by rsvp_mpc, which 
will process it and then forward to the next hop. When the receiver receives the 
PATH message, it will generate a RESERVE message and send back along the reverse 
path. 

The sample code has the following parameters:
	"request" (the requested bandwidth) 
	"mode" (multicast or unicast) 
	"dst addresses" (if unicast, only one addresss, if multicast, all addresses)

To evaluate RSVP performance, the sample code will send out 200 PATH
messages. rsvp_mpc agent will calculate the time spent from receiving the
PATH message to receiving the RESERVE message.
The data was collected in the attached time difference data files.

We tested several different scenarios in order to compare performance. One is
rsvp_mpc_none, in which no agent will encrypt the rsvp messages. One
is rsvp_mpc_MD5 in which each agent will use only MD5 to authenticate the 
messages.  The other one is rsvp_mpc_SDS, in which each agent uses the selective
digital signature scheme to authenticate each message.