MIKEY-TICKET: Ticket-Based Modes of Key Distribution in Multimedia Internet KEYing (MIKEY)

Abstract

The Multimedia Internet KEYing (MIKEY) specification describes a key management scheme for real-time applications. In this document, we note that the currently defined MIKEY modes are insufficient to address deployment scenarios built around a centralized key management service. Interest in such deployments is increasing. Therefore, a set of new MIKEY modes that work well in such scenarios are defined. The new modes use a trusted key management service and a ticket concept, similar to that in Kerberos. The new modes also support features used by many existing applications, where the exact identity of the other endpoint may not be known at the start of the communication session.

Lightweighted and energy-aware MIKEY-Ticket for e-health applications in the context of internet of things

“…In the following, we present a succinct description of each field contained in the Mikey Ticket header. We refer to RFC3038 [ALNN04] and RFC6043 [MT11] for a more detailed description:…”

“…However, the lack of energy power and computational capabilities in such kind of environment hinder the deployment of classic developed security solutions. [MT11] is a key management protocol characterized by its simplicity and adaptation to centralized architectures. In fact, these architectures are interesting to be considered for resource constrained environments, as there is no need to pre-distribute credentials.…”

Options for Securing RTP Sessions

“…TICKET: Ticket Payload (TICKET) [RFC6043] is a MIKEY extension using a trusted centralized key management service (KMS). The initiator and responder do not share any credentials; instead, they trust a third party, the KMS, with which they both have or can establish shared credentials.…”

Transaction-based authentication and key agreement protocol for inter-domain VoIP

“…Furthermore, the responder usually needs to perform (at least) one cryptographic operation for checking the validity of the received message. Recently, a new MIKEY mode denoted KMS was proposed in [29]. It is a ticket-based approach with a trusted third party, inspired from Kerberos [32], which can also be integrated into the VoIP call establishment.…”

“…Equations 13, 15). Then, the corresponding filtering values FV(TI S1 , Ai) and FV(TI S1 , S1) are obtained from Equations (28,29,30). On its side, S1 maintains a single transaction window for all Ai entities containing the ∆ acceptable indexes ATI S1,k (t) obtained from Equation (11).…”