RFC 8599: Push Notification with the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8599
- Published
- May 2019
- Authors
- C. Holmberg; M. Arnold
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 40
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8291Message Encryption for Web PushCurrent
November 2017
- RFC 8765DNS Push NotificationsCurrent
June 2020
- RFC 6468Sieve Notification Mechanism: SIP MESSAGECurrent
February 2012
- RFC 8498A P-Served-User Header Field Parameter for an Originating Call Diversion (CDIV) Session Case in the Session Initiation Protocol (SIP)Current
February 2019
- RFC 8497Marking SIP Messages to Be LoggedCurrent
November 2018
- RFC 8396Managing, Ordering, Distributing, Exposing, and Registering Telephone Numbers (MODERN): Problem Statement, Use Cases, and FrameworkCurrent
July 2018
- RFC 8816Secure Telephone Identity Revisited (STIR) Out-of-Band Architecture and Use CasesCurrent
February 2021
- RFC 8373Negotiating Human Language in Real-Time CommunicationsUpdated
May 2018
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?