Skip to main content

Push Notifications in the Session Initiation Protocol (SIP)

Document Type Expired Internet-Draft (individual)
Author Viktor Ivanov
Last updated 2016-10-09 (Latest revision 2016-04-07)
Stream (None)
Intended RFC status (None)
Expired & archived
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


The Session Initiation Protocol (SIP) allows User Agents to register for inbound requests. However, the existence of firewalls and Network Address Translators (NATs) prevent servers from reaching the User Agents unless the User Agents keep connections to the server alive. To keep such connections alive User Agents employ various methods, most of which require constant uptime resulting in high energy cost. This is especially a problem on mobile platforms that operate entirely on battery power. To resolve these issues many mobile manufacturers have provided a cost effective way of pushing messages to their devices. This specification defines behaviors for User Agents, registrars and proxy servers that allow a User Agent to provide a Push Notification Configuration to its Registrar.


Viktor Ivanov

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