Movatterモバイル変換


[0]ホーム

URL:


Search RFCs

Advanced Search

RFC Editor

RFC 8599

Push Notification with the Session Initiation Protocol (SIP),May 2019

File formats:
icon for text fileicon for PDFicon for HTMLicon for inline errata
Status:
PROPOSED STANDARD
Authors:
C. Holmberg
M. Arnold
Stream:
IETF
Source:
sipcore (art)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC8599

Discuss this RFC: Send questions or comments to the mailing listsipcore@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 8599


Abstract

This document describes how a Push Notification Service (PNS) can beused to wake a suspended Session Initiation Protocol (SIP) User Agent(UA) with push notifications, and it also describes how the UA cansend binding-refresh REGISTER requests and receive incoming SIPrequests in an environment in which the UA may be suspended. Thedocument defines new SIP URI parameters to exchange PNS informationbetween the UA and the SIP entity that will then request that pushnotifications be sent to the UA. It also defines the parameters totrigger such push notification requests. The document also definesnew feature-capability indicators that can be used to indicatesupport of this mechanism.


For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.




IABIANAIETFIRTFISEISOCIETF Trust
ReportsPrivacy StatementSite MapContact Us

Advanced Search

[8]ページ先頭

©2009-2026 Movatter.jp