Authenticated Identity Management in the Session Initiation Protocol (SIP), February 2018
- File formats:
- PROPOSED STANDARD
- RFC 4474
- Updated by:
- RFC 8946
- J. Peterson
- stir (art)
Cite this RFC: TXT | XML | BibTeX
Discuss this RFC: Send questions or comments to the mailing list firstname.lastname@example.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 8224
The baseline security mechanisms in the Session Initiation Protocol (SIP) are inadequate for cryptographically assuring the identity of the end users that originate SIP requests, especially in an interdomain context. This document defines a mechanism for securely identifying originators of SIP requests. It does so by defining a SIP header field for conveying a signature used for validating the identity and for conveying a reference to the credentials of the signer.
This document obsoletes RFC 4474.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.