RFC 5362: The Session Initiation Protocol (SIP) Pending Additions Event Package
In plain English — editorial summary, not part of the RFC
This document defines the SIP Pending Additions event package. This event package is used by SIP relays to inform user agents about the consent-related status of the entries to be added to a resource list. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5362
- Published
- October 2008
- Authors
- G. Camarillo
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5363Framework and Security Considerations for Session Initiation Protocol (SIP) URI-List ServicesCurrent
October 2008
- RFC 5361A Document Format for Requesting ConsentCurrent
October 2008
- RFC 5360A Framework for Consent-Based Communications in the Session Initiation Protocol (SIP)Updated
October 2008
- RFC 5364Extensible Markup Language (XML) Format Extension for Representing Copy Control Attributes in Resource ListsUpdated
October 2008
- RFC 5359Session Initiation Protocol Service ExamplesCurrent
October 2008
- RFC 5365Multiple-Recipient MESSAGE Requests in the Session Initiation Protocol (SIP)Current
October 2008
- RFC 5366Conference Establishment Using Request-Contained Lists in the Session Initiation Protocol (SIP)Current
October 2008
- RFC 5367Subscriptions to Request-Contained Resource Lists in the Session Initiation Protocol (SIP)Current
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?