RFC 5763: Framework for Establishing a Secure Real-time Transport Protocol (SRTP) Security Context Using Datagram Transport Layer Security (DTLS)

Publisher

IETF / RFC Editor

URL

https://www.rfc-editor.org/rfc/rfc5763.html

Published

2010-05-01

Updated

unknown

Accessed

2026-09-23

HTTP status

200

License

IETF Trust Legal Provisions (BCP 78); no-redistribution; short excerpts and locators only

Source notes citing this source

• RFC 5763 requires the SIP offerer in DTLS-SRTP to use a=setup:actpass, and the answerer replies with setup:active or setup:passive. in context
• 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. in context
• RFC 5763 allows the DTLS certificates to be self-signed. Authentication comes from matching the handshake certificate against the a=fingerprint value carried in signalling, not from a certificate authority. in context
• RFC 5763 identifies SRTP keyed by DTLS over UDP with the SDP transport protocol UDP/TLS/RTP/SAVP. in context

Cite this source record

APA

WarmTransfer. (2010, May 1). RFC 5763: Framework for Establishing a Secure Real-time Transport Protocol (SRTP) Security Context Using Datagram Transport Layer Security (DTLS). WarmTransfer. https://warmtransfer.net/knowledge/sources/rfc-5763-dtls-srtp-framework

BibTeX

@misc{warmtransfer-rfc-5763-dtls-srtp-framework,
  title  = {RFC 5763: Framework for Establishing a Secure Real-time Transport Protocol (SRTP) Security Context Using Datagram Transport Layer Security (DTLS)},
  author = {{WarmTransfer}},
  year   = {2010},
  url    = {https://warmtransfer.net/knowledge/sources/rfc-5763-dtls-srtp-framework},
  note   = {IETF / RFC Editor, accessed 2026-09-23}
}