RFC 3892: The Session Initiation Protocol (SIP) Referred-By Mechanism
In plain English — editorial summary, not part of the RFC
The Session Initiation Protocol (SIP) REFER method provides a mechanism where one party (the referrer) gives a second party (the referee) an arbitrary URI to reference. If that URI is a SIP URI, the referee will send a SIP request, often an INVITE, to that URI (the refer target). This document extends the REFER method, allowing the referrer to provide information about the REFER request to the refer target using the referee as an intermediary. This information includes the identity of the referrer and the URI to which the referrer referred. The mechanism utilizes S/MIME to help protect this information from a malicious intermediary. This protection is optional, but a recipient may refuse to accept a request unless it is present. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3892
- Published
- September 2004
- Authors
- R. Sparks
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 25
- 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 3891The Session Initiation Protocol (SIP) "Replaces" HeaderCurrent
September 2004
- RFC 3893Session Initiation Protocol (SIP) Authenticated Identity Body (AIB) FormatCurrent
September 2004
- RFC 3903Session Initiation Protocol (SIP) Extension for Event State PublicationUpdated
November 2004
- RFC 3911The Session Initiation Protocol (SIP) "Join" HeaderCurrent
October 2004
- RFC 3853S/MIME Advanced Encryption Standard (AES) Requirement for the Session Initiation Protocol (SIP)Current
July 2004
- RFC 3842A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP)Current
August 2004
- RFC 3841Caller Preferences for the Session Initiation Protocol (SIP)Current
August 2004
- RFC 3840Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)Current
August 2004
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?