MIKEY-TICKET: Ticket-Based Modes of Key Distribution in Multimedia Internet KEYing (MIKEY)
RFC 6043
Document | Type |
RFC - Informational
(March 2011; No errata)
Updated by RFC 6309
Was draft-mattsson-mikey-ticket (individual in sec area)
|
|
---|---|---|---|
Authors | John Preuß Mattsson , Tian Tian | ||
Last updated | 2015-10-14 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 6043 (Informational) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Tim Polk | ||
Send notices to | (None) |
Internet Engineering Task Force (IETF) J. Mattsson Request for Comments: 6043 Ericsson Category: Informational T. Tian ISSN: 2070-1721 ZTE March 2011 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. Status of This Memo This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6043. Mattsson & Tian Informational [Page 1] RFC 6043 MIKEY-TICKET March 2011 Copyright Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction ....................................................4 2. Terminology .....................................................4 2.1. Definitions and Notation ...................................5 2.2. Abbreviations ..............................................6 2.3. Payloads ...................................................6 3. Design Considerations ...........................................7 4. MIKEY-TICKET ....................................................9 4.1. Overview ...................................................9 4.1.1. Modes ..............................................12 4.2. Exchanges .................................................13 4.2.1. Ticket Request .....................................13 4.2.2. Ticket Transfer ....................................16 4.2.3. Ticket Resolve .....................................19 5. Key Management Functions .......................................23 5.1. Key Derivation ............................................23 5.1.1. Deriving Forked Keys ...............................25 5.1.2. Deriving Keys from an Envelope Key/PSK/MPK .........26 5.1.3. Deriving Keys from a TGK/GTGK ......................27 5.2. CSB Updating ..............................................28 5.3. Ticket Reuse ..............................................29 5.4. Error Handling ............................................29 5.5. MAC/Signature Coverage ....................................30 6. Payload Encoding ...............................................31 6.1. Common Header Payload (HDR) ...............................31 6.1.1. The GENERIC-ID Map Type ............................33 6.2. Key Data Transport Payload (KEMAC) ........................34 6.2.1. Key Data Sub-Payload ...............................35 6.3. Timestamp Payload (T) .....................................36 6.4. Timestamp Payload with Role Indicator (TR) ................36 6.5. ID Payload (ID) ...........................................37 6.6. ID Payload with Role Indicator (IDR) ......................37Show full document text