RFC 6738: Diameter IKEv2 SK: Using Shared Keys to Support Interaction between IKEv2 Servers and Diameter Servers
In plain English — editorial summary, not part of the RFC
The Internet Key Exchange Protocol version 2 (IKEv2) is a component of the IPsec architecture and is used to perform mutual authentication as well as to establish and to maintain IPsec Security Associations (SAs) between the respective parties. IKEv2 supports several different authentication mechanisms, such as the Extensible Authentication Protocol (EAP), certificates, and Shared Key (SK). Diameter interworking for Mobile IPv6 between the Home Agent (HA), as a Diameter client, and the Diameter server has been specified. However, that specification focused on the usage of EAP and did not include support for SK-based authentication available with IKEv2. This document specifies the IKEv2-server-to-Diameter-server communication when the IKEv2 peer authenticates using IKEv2 with SK. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6738
- Published
- October 2012
- Authors
- V. Cakulev; A. Lior; S. Mizikovsky
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6737The Diameter Capabilities Update ApplicationCurrent
October 2012
- RFC 6736Diameter Network Address and Port Translation Control ApplicationCurrent
October 2012
- RFC 6735Diameter Priority Attribute-Value PairsCurrent
October 2012
- RFC 6734Diameter Attribute-Value Pairs for Cryptographic Key TransportCurrent
October 2012
- RFC 6733Diameter Base ProtocolUpdated
October 2012
- RFC 6728Configuration Data Model for the IP Flow Information Export (IPFIX) and Packet Sampling (PSAMP) ProtocolsCurrent
October 2012
- RFC 6727Definitions of Managed Objects for Packet SamplingCurrent
October 2012
- RFC 6752Issues with Private IP Addressing in the InternetCurrent
September 2012
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?