MIKEY-TICKET

John Mattsson and Tian Tian proposed MIKEY-TICKET: Ticket-Based Modes of Key Distribution in Multimedia Internet KEYing (MIKEY), RFC 6043 to get the MIKEY key from a trusted key management service.

Prajwol Kumar Nakarmi implemented and evaluated this in the context of a secure VoIP client (based on Sipdroid) in his Master's thesis “Evaluation of VoIP Security for Mobile Devices: In the context of IMS” [Nakarmi 2011]. 3GPP's Generic Bootstrapping Architecture (GBA) (TS 33.220) and GBA Digest (TR 33.914) were used for authentication bootstrapping.

His GBA client written in C took only ~40 ms to bootstrap

<500 ms of additional delay in the call setup
<500 µs of additional overhead for every 160 bytes of voice data

Slide Notes

John Mattsson and Tian Tian, MIKEY-TICKET: Ticket-Based Modes of Key Distribution in Multimedia Internet KEYing (MIKEY), Internet Request for Comments, ISSN 2070-1721, RFC 6043, RFC Editor, March 2011, http://www.rfc-editor.org/rfc/rfc6043.txt Links to an external site.

Prajwol Kumar Nakarmi, Evaluation of VoIP Security for Mobile Devices: In the context of IMS, Masters thesis, Royal Institute of Technology (KTH), School of Information and Communications Technology, Stockholm, Sweden, TRITA-ICT-EX-2011:111, June 2011, https://urn.kb.se/resolve?urn=urn%3Anbn%3Ase%3Akth%3Adiva-43721 Links to an external site.

3GPP. Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA). TS 33.220, 3rd Generation Partnership Project (3GPP), June 2010.

3GPP. SSO for Application Security for IMS - based on SIP Digest, TR 33.914, 3rd Generation Partnership Project (3GPP), May 2011.

Transcript

[slide415] Now, MIKEY was combined together with something called Ticket, the Ticket mode of key distribution in something called MIKEY-Ticket. You can read about it. And Prajwol Nakarmi did his thesis on it. And one of the cool features is he basically says, well, actually, do I need to exchange my key via my telecom provider? Do I want my telecom provider to ever have my keys? No. I can have a third party who's my trusted provider, and they deal with the keys, and now I simply use those keys with my telecommunication service, and now they're completely separate. And basically the inspiration for this is, have any of you used Kerberos? Right, the advantage is we can have Kerberos tickets for which we can then use to get a key, and now we can access file systems or printers or whatever other resources, but we have a separate trust entity who's dealing with our master key for that, and they just give us a ticket that lets us then proceed to communicate. And he showed that it's relatively little additional delay, less than 500 milliseconds, and the overhead per block of traffic is very, very small.