Encrypted Key Transport for Secure RTP
draft-ietf-avt-srtp-ekt-03
| Document | Type |
Replaced Internet-Draft
(avtcore WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dan Wing , David McGrew , Kai Fischer | ||
| Last updated | 2012-07-09 (Latest revision 2011-10-31) | ||
| Replaces | draft-mcgrew-srtp-ekt | ||
| Replaced by | draft-ietf-avtcore-srtp-ekt | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | Roni Even | ||
| IESG | IESG state | Replaced by draft-ietf-avtcore-srtp-ekt | |
| Consensus boilerplate | Unknown | ||
| 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
SRTP Encrypted Key Transport (EKT) is an extension to SRTP that provides for the secure transport of SRTP master keys, Rollover Counters, and other information, within SRTP or SRTCP. This facility enables SRTP to work for decentralized conferences with minimal control, and to handle situations caused by early media. This note defines EKT, and also describes how to use it with SDP Security Descriptions, DTLS-SRTP, and MIKEY. These other key management protocols provide an EKT key to everyone in a session, and EKT coordinates the keys within the session.
Authors
Dan Wing
David McGrew
Kai Fischer
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)