1 / 4

Update on .SUBSCRIBE/NOTIFY: Changes and Future Work

This document outlines the changes made to the .SUBSCRIBE/NOTIFY protocol since the last draft, including the disallowance of multiple contacts per SUBSCRIBE message and the requirement of a contact header in NOTIFY messages. It also covers the removal of distinctions between third-party/call member events and call-related/resource-related events. The document discusses the expectation of NOTIFY messages before the SUBSCRIBE transaction completes and the addition of an immediate NOTIFY message after a successful SUBSCRIBE. It also addresses the concept of "undefined state" before a NOTIFY arrives and provides a mechanism for notifiers to shorten or cancel outstanding subscriptions. The document removes all discussion of out-of-band subscriptions and includes a brief discussion of event state polling. Open issues, future work, and possible working group items are mentioned.

joesnyder
Download Presentation

Update on .SUBSCRIBE/NOTIFY: Changes and Future Work

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. SUBSCRIBE/NOTIFY 49th IETF San Diego, CA 12/12/2000 Adam.Roach@Ericsson.com

  2. Changes since last draft • Multiple contacts per SUBSCRIBE message disallowed. • Contact header now required in NOTIFY messages. • Distinction between third party/call member events removed. • Distinction between call-related/resource-related events removed. • Clarified that subscribers must expect NOTIFY messages before the SUBSCRIBE transaction completes. • Added immediate NOTIFY message after successful SUBSCRIBE. • Added discussion of “undefined state” (before a NOTIFY arrives). • Added mechanism for notifiers to shorten/cancel outstanding subscriptions. • Removed all discussion of out-of-band subscriptions. • Added brief discussion of event state polling.

  3. Open Issues • Event Agents • Generic Event Throttling Mechanism

  4. Future Work • Working group item? • Formal BOF?

More Related