notification
Click on the red underlined text to get to the source
...
The ability to request asynchronous notification of events proves
useful in many types of SIP services ...
... methods described in this document provide a framework by which
notification of these events can be ordered.
The event notification ...
... notification of these events can be ordered.
The event notification mechanisms defined herein are NOT intended to
be a general-purpose infrastructure for all classes of event
...
... be a general-purpose infrastructure for all classes of event
subscription and notification. Meeting requirements for the general
problem set of subscription and notification ...
... notification. Meeting requirements for the general
problem set of subscription and notification is far too complex for a
single protocol. Our goal is to provide a SIP ...
... SIP-specific framework for
event notification which is not so complex as to be unusable for
simple features, but which is still flexible enough to provide
powerful services ...
... framework may define arbitrarily elaborate rules which govern the
subscription and notification for the events or classes of events
they describe.
...
... network,
and those entities (or entities acting on their behalf) can send
notifications when those states change.
A typical flow ...
... event packages, including itself.
Notification: Notification is the act of a notifier sending a NOTIFY
message to a subscriber ...
...
Notification: Notification is the act of a notifier sending a NOTIFY
message to a subscriber to inform the subscriber ...
... State agents always have complete state information for the
resource for which they are creating notifications.
Subscriber ...
... SIP [1]. It also contains
enough information to identify the resource for which event
notification is desired, but not necessarily enough information to
uniquely identify the nature of the event (e.g.,
"sip:adam@dynamicsoft.com" would be an appropriate URI ...
... response, this indicates that the subscription has been terminated
and that the subscriber did not receive notification of this fact.
In this case, the subscriber should consider the subscription
...
... not a "407;" notifiers always act as a user agents when accepting
subscriptions and sending notifications.
Of course, when acting as a proxy ...
...
If no refresh for a notification address is received before its
expiration time, the subscription is removed ...
...
Identification of events being reported in a notification is very
similar to that described for subscription to events (see section
3.1.2.).
...
... headers will contain a
single event package name for which a notification is being
generated. The package name in the "Event" header ...
... for matching NOTIFY requests with subscriptions that create a new
dialog are described in section 3.3.4. Notifications for
subscriptions which were created inside an existing dialog match if
...
... semantics for "noresource".
Once the notification is deemed acceptable to the subscriber, the
subscriber ...
... event package using the methods described in this
document for event notification, it is important to consider: is SIP
an appropriate mechanism for the problem set? Is SIP ...
...
defining event packages for notifications related to, for example,
network management or the temperature inside your car's engine, you
...
... SIP network is
generally going to be provisioned for a reasonable signalling volume;
sending a notification every time a user's GPS position changes by
one hundredth of a second could easily overload ...
... When designing event packages, it is important to consider the type
of information which will be conveyed during a notification.
A natural temptation is to convey merely the event (e.g., "a new
...
... decisions from users, and whether state information is complete or
deltas for notifications; see section 4.3. Such a section is
required.
...
...
In the case that multiple subscriptions are allowed, the event
package MUST specify whether merging of the notifications to form a
single state is required, and how such merging is to be performed.
...
... Rate of notifications ...
... requirement (SHOULD or
MUST strength) which defines an absolute maximum on the rate at which
notifications are allowed to be generated by a single notifier.
Each package MAY further define a throttle mechanism which allows
...
... Each package MAY further define a throttle mechanism which allows
subscribers to further limit the rate of notification.
...
... event packages and template-packages
defined in "SIP-Specific Event Notification" [RFC3265prop]. Each name is
designated as a package or a template-package under "Type".
...
...
This section describes the syntax extensions required for event
notification in SIP. Semantics are described in section 3. Note
...
... method is used to request asynchronous
notification of an event or set of events at a later time.
...