Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC4916
Discuss this RFC: Send questions or comments to the mailing listsipcore@ietf.org
Other actions:Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 4916
This document provides a means for a Session Initiation Protocol(SIP) User Agent (UA) that receives a dialog-forming request tosupply its identity to the peer UA by means of a request in thereverse direction, and for that identity to be signed by anAuthentication Service. Because of retargeting of a dialog-formingrequest (changing the value of the Request-URI), the UA that receivesit (the User Agent Server, UAS) can have a different identity fromthat in the To header field. The same mechanism can be used toindicate a change of identity during a dialog, e.g., because of someaction in the Public Switched Telephone Network (PSTN) behind agateway. This document normatively updates RFC 3261 (SIP). [STANDARDS-TRACK]
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.