Source note · SRTP and media encryption negotiation
RFC 5763 relies on the integrity of the SDP fingerprint and recommends SIP Identity (RFC 4474) to stop intermediaries modifying it, with SIPS or S/MIME as alternatives.
Checked 2026-09-23
The SIP Identity mechanism can be used to protect the integrity of the fingerprint attribute from modification by intermediate proxies.
- Vendor
- IETF
- Product
- DTLS-SRTP with SIP
- Subsystem
- security considerations
- Deployment
- any
- Region
- not restricted
- Release range
- RFC 5763
- Checked
- 2026-09-23
Sources
- RFC 5763: Framework for Establishing a Secure Real-time Transport Protocol (SRTP) Security Context Using Datagram Transport Layer Security (DTLS) — IETF / RFC Editor · tier 1 standards and regulators · Sections 5-8 (fingerprint integrity discussion), unverified section number
Cite this note
APA
WarmTransfer. (2026, September 23). SRTP and media encryption negotiation: source note srtp-media-security-rfc5763-fingerprint-integrity. WarmTransfer. https://warmtransfer.net/knowledge/claims/srtp-media-security-rfc5763-fingerprint-integrity
BibTeX
@misc{warmtransfer-claim-srtp-media-security-rfc5763-fingerprint-integrity,
title = {SRTP and media encryption negotiation: source note srtp-media-security-rfc5763-fingerprint-integrity},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/srtp-media-security-rfc5763-fingerprint-integrity},
note = {Source note srtp-media-security-rfc5763-fingerprint-integrity, checked 2026-09-23}
}