RFC 4596: Guidelines for Usage of the Session Initiation Protocol (SIP) Caller Preferences Extension
In plain English — editorial summary, not part of the RFC
This document contains guidelines for usage of the Caller Preferences Extension to the Session Initiation Protocol (SIP). It demonstrates the benefits of caller preferences with specific example applications, provides use cases to show proper operation, provides guidance on the applicability of the registered feature tags, and describes a straightforward implementation of the preference and capability matching algorithm specified in Section 7.2 of RFC 3841. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4596
- Published
- July 2006
- Authors
- J. Rosenberg; P. Kyzivat
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 40
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4597Conferencing ScenariosCurrent
August 2006
- RFC 4598Real-time Transport Protocol (RTP) Payload Format for Enhanced AC-3 (E-AC-3) AudioCurrent
July 2006
- RFC 4589Location Types RegistryCurrent
July 2006
- RFC 4588RTP Retransmission Payload FormatCurrent
July 2006
- RFC 4587RTP Payload Format for H.261 Video StreamsCurrent
August 2006
- RFC 4585Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)Updated
July 2006
- RFC 4582The Binary Floor Control Protocol (BFCP)Obsoleted
November 2006
- RFC 4579Session Initiation Protocol (SIP) Call Control - Conferencing for User AgentsCurrent
August 2006
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?