Requirements for Limiting the Rate of Event Notifications
draft-ietf-sipping-event-throttle-reqs-00

Document Type Expired Internet-Draft (sipping WG)
Author Aki Niemi 
Last updated 2003-09-09
Stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-sipping-event-throttle-reqs-00.txt

Abstract

All event packages are required to specify a maximum rate at which event notifications are generated by a single notifier. Such a limit is provided in order to reduce network congestion. In addition to the fixed limits introduced by specific event packages, further mechanisms for limiting the rate of event notification are also allowed to be defined by event package specifications but none have been specified so far. This memo discusses the requirements for a throttle mechanism that allows a subscriber to further limit the rate of event notification.

Authors

Aki Niemi (aki.niemi@nokia.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)