RFC 5367: Subscriptions to Request-Contained Resource Lists in the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
This document specifies a way to create subscription to a list of resources in SIP. This is achieved by including the list of resources in the body of a SUBSCRIBE request. Instead of having a subscriber send a SUBSCRIBE request for each resource individually, the subscriber defines the resource list, subscribes to it, and gets notifications about changes in the resources' states using a single SUBSCRIBE dialog. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5367
- Published
- October 2008
- Authors
- G. Camarillo; A.B. Roach; O. Levin
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 9
- Also known as
- —
- Updates:
- RFC 3265
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5368Referring to Multiple Resources in the Session Initiation Protocol (SIP)Updated
October 2008
- RFC 5366Conference Establishment Using Request-Contained Lists in the Session Initiation Protocol (SIP)Current
October 2008
- RFC 5365Multiple-Recipient MESSAGE Requests in the Session Initiation Protocol (SIP)Current
October 2008
- RFC 5369Framework for Transcoding with the Session Initiation Protocol (SIP)Current
October 2008
- RFC 5364Extensible Markup Language (XML) Format Extension for Representing Copy Control Attributes in Resource ListsUpdated
October 2008
- RFC 5370The Session Initiation Protocol (SIP) Conference Bridge Transcoding ModelCurrent
October 2008
- RFC 5363Framework and Security Considerations for Session Initiation Protocol (SIP) URI-List ServicesCurrent
October 2008
- RFC 5371RTP Payload Format for JPEG 2000 Video StreamsCurrent
October 2008
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?