Abstract
197 Abstract. To use a network service class, an application must determine which service is suitable and provide a concise description of traffic characteristics required by the service class. Applications may find it difficult to do this if accurate a priori knowledge of traffic is not available or if the traffic characteristics will change over time. Both of these difficulties can be addressed by a renegotiated service that supports changes in the traffic contract over time. We focus in this paper on applications that have known, but changing, service requirements, thus they can use off-line processing. We survey existing work and present new algolithms for determining when to renegotiate the service and what new traffic contract to supply. We evaluate the performance of our work and the work of others using a common set of application streams.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
