@misc{rfc4916,
    series =    {Request for Comments},
    number =    4916,
    howpublished =  {RFC 4916},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC4916},
    url =       {https://www.rfc-editor.org/info/rfc4916},
    author =    {John Elwell},
    title =     {{Connected Identity in the Session Initiation Protocol (SIP)}},
    pagetotal = 24,
    year =      2007,
    month =     jun,
    abstract =  {This document provides a means for a Session Initiation Protocol (SIP) User Agent (UA) that receives a dialog-forming request to supply its identity to the peer UA by means of a request in the reverse direction, and for that identity to be signed by an Authentication Service. Because of retargeting of a dialog-forming request (changing the value of the Request-URI), the UA that receives it (the User Agent Server, UAS) can have a different identity from that in the To header field. The same mechanism can be used to indicate a change of identity during a dialog, e.g., because of some action in the Public Switched Telephone Network (PSTN) behind a gateway. This document normatively updates RFC 3261 (SIP). {[}STANDARDS-TRACK{]}},
}