Why RTP Does Not Mandate a Single Security Mechanism
draft-perkins-avt-srtp-not-mandatory-01

Document Type Replaced Internet-Draft (individual)
Last updated 2008-10-06 (latest revision 2008-07-14)
Replaced by draft-ietf-avt-srtp-not-mandatory
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf 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
https://www.ietf.org/archive/id/draft-perkins-avt-srtp-not-mandatory-01.txt

Abstract

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.

Authors

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.)