Why RTP Does Not Mandate a Single Security Mechanism

Document Type Replaced Internet-Draft (individual)
Authors Colin Perkins  , Magnus Westerlund 
Last updated 2008-10-06 (latest revision 2008-07-14)
Replaced by RFC 7202
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-avt-srtp-not-mandatory
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


This memo discusses the problem of securing real-time multimedia sessions, and explains why the Real-time Transport Protocol (RTP) does not mandate a single media security mechanism.


Colin Perkins (csp@csperkins.org)
Magnus Westerlund (magnus.westerlund@ericsson.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)