IBAKE: Identity-Based Authenticated Key Exchange
RFC 6539, “IBAKE: Identity-Based Authenticated Key Exchange”, is an Informational document published in March 2012 by V. Cakulev, G. Sundaram, I. Broustis. The canonical text is published by the RFC Editor.
Abstract
Cryptographic protocols based on public-key methods have been traditionally based on certificates and Public Key Infrastructure (PKI) to support certificate management. The emerging field of Identity-Based Encryption (IBE) protocols allows simplification of infrastructure requirements via a Private-Key Generator (PKG) while providing the same flexibility. However, one significant limitation of IBE methods is that the PKG can end up being a de facto key escrow server, with undesirable consequences. Another observed deficiency is a lack of mutual authentication of communicating parties. This document specifies the Identity-Based Authenticated Key Exchange (IBAKE) protocol. IBAKE does not suffer from the key escrow problem and in addition provides mutual authentication as well as perfect forward and backward secrecy. This document is not an Internet Standards Track specification; it is published for informational purposes.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 6539 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6538 The Host Identity Protocol Experiment Report
- RFC 6540 IPv6 Support Required for All IP-Capable Nodes
- RFC 6537 Host Identity Protocol Distributed Hash Table Interface
- RFC 6541 DomainKeys Identified Mail Authorized Third-Party Signatures
- RFC 6536 Network Configuration Protocol Access Control Model
- RFC 6542 Kerberos Version 5 Generic Security Service Application Program Interface Channel Binding Hash Agility
- RFC 6535 Dual-Stack Hosts Using "Bump-in-the-Host"
- RFC 6543 Reserved IPv6 Interface Identifier for Proxy Mobile IPv6