Options for Securing RTP Sessions
Draft of message to be sent after approval:
From: The IESG <firstname.lastname@example.org> To: IETF-Announce <email@example.com> Cc: RFC Editor <firstname.lastname@example.org>, avtcore mailing list <email@example.com>, avtcore chair <firstname.lastname@example.org> Subject: Document Action: 'Options for Securing RTP Sessions' to Informational RFC (draft-ietf-avtcore-rtp-security-options-10.txt) The IESG has approved the following document: - 'Options for Securing RTP Sessions' (draft-ietf-avtcore-rtp-security-options-10.txt) as Informational RFC This document is the product of the Audio/Video Transport Core Maintenance Working Group. The IESG contact persons are Richard Barnes and Gonzalo Camarillo. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-security-options/
Technical Summary The Real-time Transport Protocol (RTP) is used in a large number of different application domains and environments. This heterogeneity implies that different security mechanisms are needed to provide services such as confidentiality, integrity and source authentication of RTP/RTCP packets suitable for the various environments. The range of solutions makes it difficult for RTP-based application developers to pick the most suitable mechanism. This document provides an overview of a number of security solutions for RTP, and gives guidance for developers on how to choose the appropriate security mechanism. Working Group Summary This document complements draft-ietf-avt-srtp-not-mandatory providing information about security options. It was reviewed by the WG members and the WG security experts and there are no issues from the WG that is worth noting. Document Quality This document is an overview document and I would like to mention that Dan Wing and Alan Johnston did a review and made helpful comments that helped with the quality of the document. Personnel Document Shepherd is Roni Even and the responsible AD is Richard Barnes.