Sanjai Narain
ABSTRACT
COTS (commercial off-the-shelf) devices, including middleware components, are capable of executing powerful, distributed algorithms. Very large, adaptive systems can be created by simply integrating these devices, not by creating new devices, algorithms or external control systems. The principal integration method is configuration: every device is designed to have a finite set of configuration parameters that can be set to definite values. These parameters are static in that, unlike the device's dynamic state, these do not change during the device's normal operation. Inspite of the ubiquity of the configuration method, there is no "science" for it. There are no tools which let one specify global, end-to-end system functionality requirements at a high level, reason about these, and have these compiled into device configurations. On the other hand, it is inherently difficult to develop this science because of the large conceptual gap between global, end-to-end requirements and device configurations. A middleware is needed to bridge this gap in the form of specification, reasoning, compilation and diagnostic tools.This position paper sketches a technique called Service Grammar for developing such middleware for a given domain. It is based on the idea that algorithms for implementing end-to-end functional requirements can be expressed as the enforcement of a set of fundamental requirements. These are upon the existence of definite high-level relationships between configuration parameters of various devices. We can collect these into a Requirements Library. By mixing and matching items from it we can define algorithms for implementing a very wide range of end-to-end functional requirements. This Library can also simplify design of the reasoning, compilation and diagnostic tools. This plan is illustrated by analyzing how realistic service requirements are implemented in a Virtual Private Network via configuration steps.First, a network of "resilient", secure tunnels is set up by composing capabilities of protocols OSPF, GRE and IPSec. Then, quality of service guarantees are established by composing capabilities of MPLS, RSVP and DiffServ. Finally, as an example of configuring middleware components themselves, an example is presented from CORBA security.
- 1.Cisco Systems. A Primer for Implementing a Cisco Virtual Private Network. http://www.cisco.com/warp/public/cc/so/neso/vpn/vpne/vpn21_rg .htm.Google Scholar
- 2.Cohen, E., Narain, S. Temporal logic. Encyclopedia of Electrical And Electronics Engineering, volume 21, ed. John Webster. John Wiley & Sons, 1999.Google ScholarCross Ref
- 3.Doraswamy, N., Harkins, D. IPSec: The New Security Standard For The Internet, Intranets and Virtual Private Networks. Prentice Hall, 1999. Google ScholarDigital Library
- 4.Huitema, C. Routing in the Internet. Prentice Hall, Englewood Cliffs, New Jersey, 1995. Google ScholarDigital Library
- 5.Narain, S., Shareef, A., Rangadurai, M. Diagnosing Configuration Errors in Virtual Private Networks. Proceedings of IEEE International Communications Conference, Helsinki, Finland, 2001.Google Scholar
- 6.Schmidt, D., Kachroo, V., Krishnamurthy, Y., Kuhns, F. Developing Next Generation Distributed Applications With QoS-Enabled DPE Middleware, IEEE Communications Magazine, Vol. 38, No. 10, October 2000. Google ScholarDigital Library
- 7.Whetten, B., Basavaiah, M., Paul, S., Montgomery, T., Rastogi, N., Conlan, J., Yeh, T. "The RMTP-II Protocol," Internet Draft, draft-whetten-rmtp-ii-00.txt, dated April 1998.Google Scholar
- 8.IVPN Service Backbones: The Operations Cost Angle. Data Communications Report Vol. 13, No. 19, Yankee Group, December 1998Google Scholar
- 9.S. Blake, D. Black, M. Carlson, E. Davies, Z. Wang, W. Weiss, An Architecture for Differentiated Services, RFC 2475, December 1998. Google ScholarDigital Library
- 10.D. Awduche, J. Malcolm, J. Agobua, M. O'Dell, J. McManus, Requirements for Traffic Engineering for Traffic Engineering for MPLS, RFC 2702, September 1999. Google ScholarDigital Library
- 11.E. Rosen, A. Viswanathan & R. Callon, Multiprotocol Label Switching Architecture, RFC 3031, January 2001 Google ScholarDigital Library
Index Terms
- Middleware For Building Adaptive Systems Via Configuration
Recommendations
Middleware For Building Adaptive Systems Via Configuration
LCTES '01: Proceedings of the ACM SIGPLAN workshop on Languages, compilers and tools for embedded systemsCOTS (commercial off-the-shelf) devices, including middleware components, are capable of executing powerful, distributed algorithms. Very large, adaptive systems can be created by simply integrating these devices, not by creating new devices, algorithms ...
Middleware For Building Adaptive Systems Via Configuration
COTS (commercial off-the-shelf) devices, including middleware components, are capable of executing powerful, distributed algorithms. Very large, adaptive systems can be created by simply integrating these devices, not by creating new devices, algorithms ...
Dynamic end-to-end QoS management middleware for distributed multimedia systems
In this paper, we present a separable, reusable middleware solution that provides coordinated, end-to-end QoS management over any type of service component, and can use existing (legacy) QoS management solutions (by using wrappers) in a distributed ...
Comments