RFC 5989: A SIP Event Package for Subscribing to Changes to an HTTP Resource

The Session Initiation Protocol (SIP) is increasingly being used in systems that are tightly coupled with Hypertext Transport Protocol (HTTP) servers for a…

Read RFC 5989 on the RFC Editor

Outgoing relationships (13 related RFCs)

Normative reference — RFC 3261: SIP: Session Initiation Protocol
Normative reference — RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1
Normative reference — RFC 3265: Session Initiation Protocol (SIP)-Specific Event Notification
Normative reference — RFC 5988: Web Linking
Normative reference — RFC 4287: The Atom Syndication Format
Normative reference — RFC 4662: A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists
Normative reference — RFC 4826: Extensible Markup Language (XML) Formats for Representing Resource Lists
Normative reference — RFC 5367: Subscriptions to Request-Contained Resource Lists in the Session Initiation Protocol (SIP)
Informative reference — RFC 2818: HTTP Over TLS
Informative reference — RFC 5751: Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification
Informative reference — RFC 4918: HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)
Informative reference — RFC 3903: Session Initiation Protocol (SIP) Extension for Event State Publication
Informative reference — RFC 5630: The Use of the SIPS URI Scheme in the Session Initiation Protocol (SIP)

Incoming relationships (2 related RFCs)

Normatively referenced by — RFC 6011: Session Initiation Protocol (SIP) User Agent Configuration
Informatively referenced by — RFC 7641: Observing Resources in the Constrained Application Protocol (CoAP)