Skip to main content

Encrypted Key Transport for Secure RTP

Document Type Expired Internet-Draft (avtcore WG)
Expired & archived
Authors John Preuß Mattsson , David McGrew , Dan Wing
Last updated 2015-04-25 (Latest revision 2014-10-22)
Replaces draft-ietf-avt-srtp-ekt
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Additional resources Mailing list discussion
Stream WG state WG Document
Revised I-D Needed - Issue raised by WG
Document shepherd Magnus Westerlund
IESG IESG state Expired
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:


Encrypted Key Transport (EKT) is an extension to Secure Real-time Transport Protocol (SRTP) that provides for the secure transport of SRTP master keys, Rollover Counters, and other information. This facility enables SRTP to work for decentralized conferences with minimal control. This note defines EKT, and also describes how to use it with SDP Security Descriptions, DTLS-SRTP, and MIKEY. With EKT, these other key management protocols provide an EKT key to everyone in a session, and EKT coordinates the SRTP keys within the session.


John Preuß Mattsson
David McGrew
Dan Wing

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