SRTP Store-and-Forward Use Cases and Requirements
draft-mattsson-srtp-store-and-forward-04
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Rolf Blom , Yi Cheng , Fredrik Lindholm , John Preuß Mattsson , Mats Naslund , Karl Norrman | ||
| Last updated | 2011-03-14 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
The Secure Real-time Transport Protocol (SRTP) was designed to allow simple and efficient protection of RTP. To provide this, encryption and authentication of media and control signaling are tightly coupled to the RTP session, and the information in the RTP header. Hence, in general, it is not possible to perform store-and-forward of protected media using SRTP. This document gives, based on a use case analysis, requirements that SRTP and new SRTP transforms need to satisfy in order to allow secure store-and-forward operation. A first outline on how to introduce the needed new functionality and transforms in SRTP is also presented.
Authors
Rolf Blom
Yi Cheng
Fredrik Lindholm
John Preuß Mattsson
Mats Naslund
Karl Norrman
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)