Skip to main content

Push Notification with the Session Initiation Protocol (SIP)
RFC 8599

Revision differences

Document history

Date By Action
2022-09-20
(System) Received changes through RFC Editor sync (added Errata tag)
2019-08-19
Gunter Van de Velde Closed request for Last Call review by OPSDIR with state 'Overtaken by Events'
2019-08-19
Gunter Van de Velde Assignment of request for Last Call review by OPSDIR to Fred Baker was marked no-response
2019-05-24
(System) IANA registries were updated to include RFC8599
2019-05-23
(System)
Received changes through RFC Editor sync (created alias RFC 8599, changed abstract to 'This document describes how a Push Notification Service (PNS) can be …
Received changes through RFC Editor sync (created alias RFC 8599, changed abstract to '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.', changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2019-05-23, changed IESG state to RFC Published)
2019-05-23
(System) RFC published