Extended Traffic Control Interface for RSVP
Key: SA98-2
Author: Jens Schmitt, Javier Antich
Date: July 1998
Kind: @techreport
Abstract: Internet and ATM both aim at providing integrated services. Therefore they independently (more or less) developed QoS architectures. A realistic assumption certainly is that both will take their place and that they will coexist for quite some time. A likely place for ATM is in the backbone, while IP will probably keep its dominance on the desktop. It is thus valid to assume an overlay model for the interaction between the two QoS architectures. Crucial components of the QoS architecture of the Internet are its signalling protocol RSVP and the IP multicast architecture. There are several hard problems when trying to overlay this combination over an ATM subnetwork. In particular, the problem of matching RSVP's heterogeneous receiver concept onto the homogeneous point-to-multipoint VCs of ATM is such a problem. One solution to this problem is to provide VC management strategies to bridge that gap. However in order to be able to implement such VC management strategies RSVP's Traffic Control Interface and its message processing rules need to be extended to provide the necessary flexibility. These extensions will be presented in this report.
View Full paper (PDF) | Download Full paper (PDF)

The documents distributed by this server have been provided by the contributing authors as a means to ensure timely dissemination of scholarly and technical work on a non-commercial basis. Copyright and all rights therein are maintained by the authors or by other copyright holders, not withstanding that they have offered their works here electronically. It is understood that all persons copying this information will adhere to the terms and constraints invoked by each author's copyright. These works may not be reposted without the explicit permission of the copyright holder.