%% You should probably cite draft-ietf-avtcore-srtp-ekt instead of this I-D. @techreport{ietf-avt-srtp-ekt-03, number = {draft-ietf-avt-srtp-ekt-03}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-avt-srtp-ekt/03/}, author = {Dan Wing and David McGrew and Kai Fischer}, title = {{Encrypted Key Transport for Secure RTP}}, pagetotal = 53, year = 2011, month = oct, day = 31, 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.}, }