The Session Initiation Protocol Referred-By Mechanism
RFC 3892, “The Session Initiation Protocol Referred-By Mechanism”, is a Proposed Standard document published in September 2004 by R. Sparks. It has since been updated by RFC 8217. The canonical text is published by the RFC Editor.
Abstract
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 3892 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3891 The Session Initiation Protocol "Replaces" Header
- RFC 3893 Session Initiation Protocol Authenticated Identity Body Format
- RFC 3890 A Transport Independent Bandwidth Modifier for the Session Description Protocol
- RFC 3894 Sieve Extension: Copying Without Side Effects
- RFC 3895 Definitions of Managed Objects for the DS1, E1, DS2, and E2 Interface Types
- RFC 3888 Message Tracking Model and Requirements
- RFC 3896 Definitions of Managed Objects for the DS3/E3 Interface Type
- RFC 3887 Message Tracking Query Protocol