40 likes | 60 Views
This draft outlines requirements for efficient handling of large presence documents, state changes notifications, and network resource utilization in partial notifications delivery for presence services. It emphasizes the need for minimal impact on basic network functionalities while optimizing performance. Client and server requirements focus on subscriber negotiation for receiving only changes in the presence document and support for partial notifications. 8
E N D
Partial NotificationsIETF 56SIMPLE WGdraft-lonnfors-simple-presinfo-deliv-reqs-00draft-lonnfors-simple-partial-notify-00 Mikko Lönnfors mikko.lonnfors@nokia.com
Requirements (1) • General requirements: • The presence service MUST allow mechanisms for efficient handling of large contents of presence documents • The mechanism MUST allow the subscriber to get information about state changes (modifications, removals, and additions) of presence information and its structure. • The mechanism MUST NOT affect the requirements of basic network functionalities such as security, and charging
Requirements (2) • Performance Requirements: • The presence service MUST allow efficient utilization of the network resources (radio links). The presence service SHOULD avoid additional or unnecessary round-trips for receiving changed presence information. • The presence service MUST be able to be utilized by devices with low data processing capabilities, small display and limited battery power.
Requirements (3) • Client and server requirements: • The subscriber MUST be able to negotiate, during the subscription phase, to receive only changes of the presence document. • The subscriber MUST be able to indicate support for partial notification. • The subscriber SHOULD be able to request, during the subscription phase, that the Presence Agent sends only changes to the presence document.