draft-ietf-sipcore-rfc3265bis-06.txt   draft-ietf-sipcore-rfc3265bis-07.txt 
Network Working Group A. B. Roach Network Working Group A. B. Roach
Internet-Draft Tekelec Internet-Draft Tekelec
Obsoletes: 3265 (if approved) February 27, 2012 Obsoletes: 3265 (if approved) February 27, 2012
Updates: 4660 (if approved) Updates: 4660 (if approved)
Intended status: Standards Track Intended status: Standards Track
Expires: August 30, 2012 Expires: August 30, 2012
SIP-Specific Event Notification SIP-Specific Event Notification
draft-ietf-sipcore-rfc3265bis-06 draft-ietf-sipcore-rfc3265bis-07
Abstract Abstract
This document describes an extension to the Session Initiation This document describes an extension to the Session Initiation
Protocol (SIP). The purpose of this extension is to provide an Protocol (SIP). The purpose of this extension is to provide an
extensible framework by which SIP nodes can request notification from extensible framework by which SIP nodes can request notification from
remote nodes indicating that certain events have occurred. remote nodes indicating that certain events have occurred.
Note that the event notification mechanisms defined herein are NOT Note that the event notification mechanisms defined herein are NOT
intended to be a general-purpose infrastructure for all classes of intended to be a general-purpose infrastructure for all classes of
skipping to change at page 26, line 8 skipping to change at page 26, line 8
immediately upon receipt of a SUBSCRIBE request, the state immediately upon receipt of a SUBSCRIBE request, the state
provided by polling is limited to the information that the provided by polling is limited to the information that the
notifier has immediate local access to when it receives the notifier has immediate local access to when it receives the
SUBSCRIBE request. If, for example, the notifier generally needs SUBSCRIBE request. If, for example, the notifier generally needs
to retrieve state from another network server, then that state to retrieve state from another network server, then that state
will be absent from the NOTIFY request that results from polling. will be absent from the NOTIFY request that results from polling.
4.4.4. Allow-Events header field usage 4.4.4. Allow-Events header field usage
The "Allow-Events" header field, if present, MUST include a The "Allow-Events" header field, if present, MUST include a
comprehensive and inclusive list of tokens for which the User Agent comprehensive and inclusive list of tokens which indicates the event
can act as a notifier. In other words, a user agent sending an packages for which the User Agent can act as a notifier. In other
"Allow-Events" header field is advertising that it can process words, a user agent sending an "Allow-Events" header field is
SUBSCRIBE requests and generate NOTIFY requests for all of the event advertising that it can process SUBSCRIBE requests and generate
packages listed in that header field. NOTIFY requests for all of the event packages listed in that header
field.
Any user agent that can act as a notifier for one or more event Any user agent that can act as a notifier for one or more event
packages SHOULD include an appropriate "Allow-Events" header field packages SHOULD include an appropriate "Allow-Events" header field
indicating all supported events in all methods which initiate dialogs indicating all supported events in all methods which initiate dialogs
and their responses (such as INVITE) and OPTIONS responses. and their responses (such as INVITE) and OPTIONS responses.
This information is very useful, for example, in allowing user This information is very useful, for example, in allowing user
agents to render particular interface elements appropriately agents to render particular interface elements appropriately
according to whether the events required to implement the features according to whether the events required to implement the features
they represent are supported by the appropriate nodes. they represent are supported by the appropriate nodes.
 End of changes. 2 change blocks. 
6 lines changed or deleted 7 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/