1 / 6

Notification Rate Control (draft-ietf-sipcore-event-rate-control-00)

aki.niemi@nokia.com krisztian.kiss@nokia.com salvatore.loreto@ericsson.com 76th IETF, Hiroshima November 2009. Notification Rate Control (draft-ietf-sipcore-event-rate-control-00). Recap. The draft defines the following three “Event” header field parameters:

pennie
Download Presentation

Notification Rate Control (draft-ietf-sipcore-event-rate-control-00)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. aki.niemi@nokia.com krisztian.kiss@nokia.com salvatore.loreto@ericsson.com 76th IETF, Hiroshima November 2009 Notification Rate Control(draft-ietf-sipcore-event-rate-control-00)

  2. Recap • The draft defines the following three “Event” header field parameters: • min-interval: minimum notification time period between two notifications, in seconds. • max-interval: maximum notification time period between two notifications, in seconds. • average-interval: an average cadence at which notification are desired, in seconds.

  3. Recap • A Subscriber that wishes to apply a “rate-control” to notifications MUST construct a SUBSCRIBE that includes the parameter and the relative value in the Event header. • A Notifier that supports the “rate-control” mechanism MUST extract the value from a SUBSCRIBE request, use it and • reflect back the used value in a Subscription-State header field of the subsequent NOTIFY request.

  4. Update rate control parameters • All the set rate-control parameters can be updated • including the parameter and the updated value in an Event header field in any 200-class responses to a NOTIFY request.

  5. Other changes • Emphasized that rate control parameters can be changed at any time by the notifier based on local policy or implementation-determined constraints. • In minimum rate mechanism, the NOTIFY request may contain partial or full state depending on what the event package specifies.

  6. Questions ?

More Related