Notification of General Events Using the Session Initiation Protocol (SIP) Event Notification Framework

Document Type Expired Internet-Draft (individual)
Authors Miguel García  , Henning Schulzrinne 
Last updated 2007-05-14
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


The SIP event notification framework is specified in RFC 3265. The framework restricts usage to notifications of events related to the SIP state. However, there is growing interest in the community for relaxing that constraint and using the SIP event notification framework for reporting changes in state that is not directly related to SIP. For example, it has been suggested a usage of the framework for reporting events related to a vehicle state, files stored in a device, calendar events, and Sieve notifications. This memo discusses the benefits of a mechanism for general event notifications using SIP.


Miguel García (
Henning Schulzrinne (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)