%% You should probably cite draft-ietf-perc-srtp-ekt-diet instead of this I-D.
@techreport{jennings-perc-srtp-ekt-diet-01,
    number =    {draft-jennings-perc-srtp-ekt-diet-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-jennings-perc-srtp-ekt-diet/01/},
    author =    {John Preuß Mattsson and David McGrew and Dan Wing and Cullen Fluffy Jennings},
    title =     {{Encrypted Key Transport for Secure RTP}},
    pagetotal = 17,
    year =      2016,
    month =     apr,
    day =       20,
    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.},
}