RFC 4508: Conveying Feature Tags with the Session Initiation Protocol (SIP) REFER Method
In plain English — editorial summary, not part of the RFC
The SIP "Caller Preferences" extension defined in RFC 3840 provides a mechanism that allows a SIP request to convey information relating to the originator's capabilities and preferences for handling of that request. The SIP REFER method defined in RFC 3515 provides a mechanism that allows one party to induce another to initiate a SIP request. This document extends the REFER method to use the mechanism of RFC 3840. By doing so, the originator of a REFER may inform the recipient as to the characteristics of the target that the induced request is expected to reach. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4508
- Published
- May 2006
- Authors
- O. Levin; A. Johnston
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 6
- Also known as
- —
- Updated by:
- RFC 8217
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4497Interworking between the Session Initiation Protocol (SIP) and QSIGUpdated
May 2006
- RFC 4488Suppression of Session Initiation Protocol (SIP) REFER Method Implicit SubscriptionCurrent
May 2006
- RFC 4485Guidelines for Authors of Extensions to the Session Initiation Protocol (SIP)Current
May 2006
- RFC 4484Trait-Based Authorization Requirements for the Session Initiation Protocol (SIP)Current
August 2006
- RFC 4483A Mechanism for Content Indirection in Session Initiation Protocol (SIP) MessagesCurrent
May 2006
- RFC 4482CIPID: Contact Information for the Presence Information Data FormatCurrent
July 2006
- RFC 4481Timed Presence Extensions to the Presence Information Data Format (PIDF) to Indicate Status Information for Past and Future Time IntervalsCurrent
July 2006
- RFC 4480RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF)Current
July 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?