@misc{rfc3892,
    series =    {Request for Comments},
    number =    3892,
    howpublished =  {RFC 3892},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC3892},
    url =       {https://www.rfc-editor.org/info/rfc3892},
    author =    {Robert Sparks},
    title =     {{The Session Initiation Protocol (SIP) Referred-By Mechanism}},
    pagetotal = 25,
    year =      2004,
    month =     sep,
    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{]}},
}