Push Notification with the Session Initiation Protocol
RFC 8599, “Push Notification with the Session Initiation Protocol”, is a Proposed Standard document published in May 2019 by C. Holmberg, M. Arnold. The canonical text is published by the RFC Editor.
Abstract
This document describes how a Push Notification Service (PNS) can be used to wake a suspended Session Initiation Protocol (SIP) User Agent (UA) with push notifications, and it also describes how the UA can send binding-refresh REGISTER requests and receive incoming SIP requests in an environment in which the UA may be suspended. The document defines new SIP URI parameters to exchange PNS information between the UA and the SIP entity that will then request that push notifications be sent to the UA. It also defines the parameters to trigger such push notification requests. The document also defines new feature-capability indicators that can be used to indicate support of this mechanism.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 8599 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8598 Split DNS Configuration for the Internet Key Exchange Protocol Version 2
- RFC 8600 Using Extensible Messaging and Presence Protocol for Security Information Exchange
- RFC 8597 Cooperating Layered Architecture for Software-Defined Networking
- RFC 8601 Message Header Field for Indicating Message Authentication Status
- RFC 8596 MPLS Transport Encapsulation for the Service Function Chaining Network Service Header
- RFC 8602 Update to the Telephony Routing over IP IANA Registry Rules regarding Postal Addresses
- RFC 8595 An MPLS-Based Forwarding Plane for Service Function Chaining
- RFC 8603 Commercial National Security Algorithm Suite Certificate and Certificate Revocation List Profile