name: DTLS-SRTP
full_form: DTLS Extension to Establish Keys for SRTP
context: the WebRTC IMS Client is required to include the indication "e2ae-security requested by UE" in every offer it creates. It is assumed that the eP-CSCF is aware of the fact the IMS UE is a WebRTC IMS Client and automatically applies e2ae security for terminating calls. Therefore, unlike the existing e2ae security for RTP and MSRP, there is no need for the IMS UE to explicitly indicate support of e2ae security during registration. NOTE 1: Two DTLS-SRTP handshakes are needed if RTP and RTCP are sent over separate transport flows. If RTP/RTCP multiplexing is used, only a single DTLS-SRTP handshake is needed. NOTE 2: In this release, DTLS-SRTP is only intended to be used by WebRTC IMS Clients. Use of DTLS-SRTP by other types of IMS UEs may be studied in future releases. The DTLS-SRTP profile to use is described in Annex B of this document. Figure 6.2.1.2-1: E2ae protection of RTP based on DTLS-SRTP
description: DTLS-SRTP (Datagram Transport Layer Security - Secure Real-time Transport Protocol) is a protocol used for securing real-time communications, such as voice and video calls. It is an extension of the DTLS protocol to establish keys for SRTP, providing end-to-end encryption for RTP traffic.
explanation: The context mentions DTLS-SRTP in relation to securing RTP traffic, indicating its role as a protocol for establishing secure connections. The mention of handshakes and profiles further solidifies its classification as a protocol.
section_title: 6.2.1.2	e2ae security for RTP using DTLS-SRTP
biotag_Context: O,B-Device,I-Device,I-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,B-Device,O,O,B-Device,I-Device,I-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,B-Network,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,B-Protocol,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,B-Network,O,O,O,B-Protocol,O,O,O,O,B-Network,B-Device,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,B-Protocol
biotag_Description: B-Protocol,O,B-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,B-Protocol,O