RFC 6251: Using Kerberos Version 5 over the Transport Layer Security (TLS) Protocol
In plain English — editorial summary, not part of the RFC
This document specifies how the Kerberos V5 protocol can be transported over the Transport Layer Security (TLS) protocol in order to provide additional security features. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6251
- Published
- May 2011
- Authors
- S. Josefsson
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6880An Information Model for Kerberos Version 5Current
March 2013
- RFC 8143Using Transport Layer Security (TLS) with Network News Transfer Protocol (NNTP)Current
April 2017
- RFC 6394Use Cases and Requirements for DNS-Based Authentication of Named Entities (DANE)Current
October 2011
- RFC 6012Datagram Transport Layer Security (DTLS) Transport Mapping for SyslogUpdated
October 2010
- RFC 6803Camellia Encryption for Kerberos 5Current
November 2012
- RFC 7250Using Raw Public Keys in Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)Current
June 2014
- RFC 7457Summarizing Known Attacks on Transport Layer Security (TLS) and Datagram TLS (DTLS)Current
February 2015
- RFC 7465Prohibiting RC4 Cipher SuitesUpdated
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?