Subject: [Simple] Notification Rate limiting - how many solutions and where?

From: [email-masked]
Date: Tue, 18 Feb 2003 10:48:03 -0600

Greetings,

Regarding notification filtering and the requirement to limit the frequency of notifications, a couple of solutions are available. 
Below are a few such proposals with some pros/cons.  Your feedback is appreciated.

A case for rate limiting in the SIP header
This idea is to create a new parameter which specifies the rate limit in a SIP SUBSCRIBE request header or possibly a new header.

* can be used for any sip request method other than Subscribe
* is package independent so no need to put into content part of request
* simple text implementation
* others?

A case for rate limiting in the Content (body of Subscribe)
This idea is to create a rule specifying the rate limit in a SIP SUBSCRIBE request body.

* permits explicit definition of rules involving rate limiting and other trigger criteria such as value reached -> easier debugging & understandability
* may be used for any package if no package specific rules are used
* other generic criteria besides time (time since last notification), such as location, can be done using same constructs
* permits easier inter-working with other Presence & Instant Messaging systems that do not use SIP
* others?

A case for both rate limiting solutions.
* ???

Tim Moran

_______________________________________________
Simple mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/simple