Encrypted Key Transport for Secure RTP
draft-jennings-perc-srtp-ekt-diet-01

Document Type Replaced Internet-Draft (individual)
Last updated 2016-04-20
Replaced by draft-ietf-perc-srtp-ekt-diet
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-perc-srtp-ekt-diet
Telechat date
Responsible AD (None)
Send notices to (None)

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-jennings-perc-srtp-ekt-diet-01.txt

Abstract

IMPORTANT: This draft is just a cut down version of draft-ietf- avtcore-srtp-ekt-03 to help discussion about the key parts of EKT for the PERC WG. Any changes decided here would need to be synchronized with the draft-ietf-avtcore-srtp-ekt draft. Nearly all the text here came from draft-ietf-avtcore-srtp-ekt and the authors of that draft. 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 within SRTP. This facility enables SRTP to work for decentralized conferences with minimal control by allowing a common key to be used across multiple endpoints.

Authors

John Mattsson (john.mattsson@ericsson.com)
David McGrew (mcgrew@cisco.com)
Dan Wing (dwing@cisco.com)
Cullen Jennings (fluffy@iii.ca)

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