@conference {
	title = {Automated Network Fault Management},
	author = {Baras, John S., Ball, Mike., Gupta, Sandeep., Viswanathan, P., Shah, Parthiv.},
	year = {1997},
	month = {11/1997},
	abstract = {Future military communication will have a mixture of backbone terrestrial, sattelite and wireless terrestrial networks. The speeds of these networks vary and they are very heterogeneous. As networks become faster, it is not enough to do reactive fault management. Our approach combines proactive and reactive fault management. Proactive fault management is implemented by dynamic and adaptive routing. Reactive fault management is implented by a combination of a neural network and an expert system. The system has been developed for the X.25 protocol. Several fault scenarios were modeled and included in the study: reduced switch capacity, increased packet gneration rate of a certain application, disabled switch in the X.25 cloud, disabled links. We also modeled occurence of alarms including severity of the problem, location of the event and a threshold. To detect and identify faults we use both numerical data associated with the perfomance objects (attributes) in the MIB as well as SNMP traps (alarms). Simulation experiments have been performed in order to understand the convergence of the algorithms, the training of the neural networks involved and the G2/NeurOn-Line software environment and MIB design.},
	address = {Monterey, CA},
	booktitle = {MILCOM \&rsquo;97},
	pages = {pp. 1244- 1250}
}
@conference {
	title = {Simple Calls for Flexible Constructs Using the Traditional File API},
	author = {Gupta, Sandeep., Baras, John S., Kelley, Steve., Roussopoulos, Nick.},
	year = {1996},
	month = {04/1996},
	abstract = {We present the design for a remote QOS/Control interface to the transport protocol using the read/write calls from the traditional file system API, with simple extensions resulting in a very flexible interface. We limit the interface to the kernel to be read/write, and introduce two cells, atleast~one of which needs to be a system service (dsplice system call or implemented otherwise). These calls use file descriptor as input and output parameters, and because of that have a much more flexible interface than the traditional ioctl/fcntl~interface. The resulting API can be used to construct efficient communication schemes and result in simpler and efficient ways for distributed interaction. Parts of this API have been implemented in our ongoing experiments. The adjoining figures outline the potential for flexibility.},
	address = {New Jersey},
	booktitle = {Open Signaling for ATM, Internet and Mobile Networks Workshop (OPENSIG)},
	organization = {Columbia University}
}
