RFC 6614: Transport Layer Security (TLS) Encryption for RADIUS
In plain English — editorial summary, not part of the RFC
This document specifies a transport profile for RADIUS using Transport Layer Security (TLS) over TCP as the transport protocol. This enables dynamic trust relationships between RADIUS servers. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6614
- Published
- May 2012
- Authors
- S. Winter; M. McCauley; S. Venaas; K. Wierenga
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- sec
- Pages
- 22
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7585Dynamic Peer Discovery for RADIUS/TLS and RADIUS/DTLS Based on the Network Access Identifier (NAI)Current
October 2015
- RFC 6065Using Authentication, Authorization, and Accounting Services to Dynamically Provision View-Based Access Control Model User-to-Group MappingsCurrent
December 2010
- RFC 6911RADIUS Attributes for IPv6 Access NetworksCurrent
April 2013
- RFC 7831Application Bridging for Federated Access Beyond Web (ABFAB) ArchitectureCurrent
May 2016
- RFC 7832Application Bridging for Federated Access Beyond Web (ABFAB) Use CasesCurrent
May 2016
- RFC 7833A RADIUS Attribute, Binding, Profiles, Name Identifier Format, and Confirmation Methods for the Security Assertion Markup Language (SAML)Current
May 2016
- RFC 5904RADIUS Attributes for IEEE 802.16 Privacy Key Management Version 1 (PKMv1) Protocol SupportCurrent
June 2010
- RFC 8658RADIUS Attributes for Softwire Mechanisms Based on Address plus Port (A+P)Current
November 2019
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?