RFC 6267: MIKEY-IBAKE: Identity-Based Authenticated Key Exchange (IBAKE) Mode of Key Distribution in Multimedia Internet KEYing (MIKEY)
In plain English — editorial summary, not part of the RFC
This document describes a key management protocol variant for the Multimedia Internet KEYing (MIKEY) protocol that relies on a trusted key management service. In particular, this variant utilizes Identity-Based Authenticated Key Exchange (IBAKE) framework that allows the participating clients to perform mutual authentication and derive a session key in an asymmetric Identity-Based Encryption (IBE) framework. This protocol, in addition to providing mutual authentication, eliminates the key escrow problem that is common in standard IBE and provides perfect forward and backward secrecy. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6267
- Published
- June 2011
- Authors
- V. Cakulev; G. Sundaram
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 30
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6287OCRA: OATH Challenge-Response AlgorithmCurrent
June 2011
- RFC 6233IS-IS Registry Extension for PurgesCurrent
May 2011
- RFC 6071IP Security (IPsec) and Internet Key Exchange (IKE) Document RoadmapCurrent
February 2011
- RFC 6008Authentication-Results Registration for Differentiating among Cryptographic ResultsCurrent
September 2010
- RFC 5998An Extension for EAP-Only Authentication in IKEv2Current
September 2010
- RFC 6541DomainKeys Identified Mail (DKIM) Authorized Third-Party SignaturesCurrent
February 2012
- RFC 6577Authentication-Results Registration Update for Sender Policy Framework (SPF) ResultsObsoleted
March 2012
- RFC 5923Connection Reuse in the Session Initiation Protocol (SIP)Current
June 2010
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?