RFC 5363: Framework and Security Considerations for Session Initiation Protocol (SIP) URI-List Services
In plain English — editorial summary, not part of the RFC
This document describes the need for SIP URI-list services and provides requirements for their invocation. Additionally, it defines a framework for SIP URI-list services, which includes security considerations applicable to these services. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5363
- Published
- October 2008
- Authors
- G. Camarillo; A.B. Roach
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 10
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5364Extensible Markup Language (XML) Format Extension for Representing Copy Control Attributes in Resource ListsUpdated
October 2008
- RFC 5362The Session Initiation Protocol (SIP) Pending Additions Event PackageCurrent
October 2008
- RFC 5361A Document Format for Requesting ConsentCurrent
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 5360A Framework for Consent-Based Communications in the Session Initiation Protocol (SIP)Updated
October 2008
- RFC 5359Session Initiation Protocol Service ExamplesCurrent
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?