Why RTP Does Not Mandate a Single Security Mechanism
draft-perkins-avt-srtp-not-mandatory-01
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Colin Perkins , Magnus Westerlund | ||
Last updated | 2008-10-06 (Latest revision 2008-07-14) | ||
Replaced by | draft-ietf-avt-srtp-not-mandatory | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
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 | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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
Magnus Westerlund
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)