Encrypted Key Transport for Secure RTP
draft-ietf-avtcore-srtp-ekt-03

 
Document Type Expired Internet-Draft (avtcore WG)
Last updated 2015-04-25 (latest revision 2014-10-22)
Replaces draft-ietf-avt-srtp-ekt
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream WG state WG Document Feb 2015
Revised I-D Needed - Issue raised by WG
Document shepherd Magnus Westerlund
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR 1 References Referenced by Nits Search lists

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-ietf-avtcore-srtp-ekt-03.txt

Abstract

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.

Authors

John Mattsson (john.mattsson@ericsson.com)
David McGrew (mcgrew@cisco.com)
Dan Wing (dwing@cisco.com)

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