RFC 7360: Datagram Transport Layer Security (DTLS) as a Transport Layer for RADIUS
In plain English — editorial summary, not part of the RFC
The RADIUS protocol defined in RFC 2865 has limited support for authentication and encryption of RADIUS packets. The protocol transports data in the clear, although some parts of the packets can have obfuscated content. Packets may be replayed verbatim by an attacker, and client-server authentication is based on fixed shared secrets. This document specifies how the Datagram Transport Layer Security (DTLS) protocol may be used as a fix for these problems. It also describes how implementations of this proposal can coexist with current RADIUS systems.
Document record
- Document ID
- RFC7360
- Published
- September 2014
- Authors
- A. DeKok
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- sec
- Pages
- 27
- Also known as
- —
- Updated by:
- RFC 9765
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7366Encrypt-then-MAC for Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)Current
September 2014
- RFC 7383Internet Key Exchange Protocol Version 2 (IKEv2) Message FragmentationCurrent
November 2014
- RFC 7321Cryptographic Algorithm Implementation Requirements and Usage Guidance for Encapsulating Security Payload (ESP) and Authentication Header (AH)Obsoleted
August 2014
- RFC 7301Transport Layer Security (TLS) Application-Layer Protocol Negotiation ExtensionUpdated
July 2014
- RFC 7296Internet Key Exchange Protocol Version 2 (IKEv2)Updated
October 2014
- RFC 7427Signature Authentication in the Internet Key Exchange Version 2 (IKEv2)Current
January 2015
- RFC 7268RADIUS Attributes for IEEE 802 NetworksUpdated
July 2014
- RFC 7457Summarizing Known Attacks on Transport Layer Security (TLS) and Datagram TLS (DTLS)Current
February 2015
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?