RFC 6448: The Unencrypted Form of Kerberos 5 KRB-CRED Message
In plain English — editorial summary, not part of the RFC
The Kerberos 5 KRB-CRED message is used to transfer Kerberos credentials between applications. When used with a secure transport, the unencrypted form of the KRB-CRED message may be desirable. This document describes the unencrypted form of the KRB-CRED message. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6448
- Published
- November 2011
- Authors
- R. Yount
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 4
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5588Generic Security Service Application Program Interface (GSS-API) Extension for Storing Delegated CredentialsCurrent
July 2009
- RFC 5403RPCSEC_GSS Version 2Updated
February 2009
- RFC 6440The EAP Re-authentication Protocol (ERP) Local Domain Name DHCPv6 OptionCurrent
December 2011
- RFC 6421Crypto-Agility Requirements for Remote Authentication Dial-In User Service (RADIUS)Current
November 2011
- RFC 6407The Group Domain of InterpretationObsoleted
October 2011
- RFC 6402Certificate Management over CMS (CMC) UpdatesObsoleted
November 2011
- RFC 6394Use Cases and Requirements for DNS-Based Authentication of Named Entities (DANE)Current
October 2011
- RFC 6520Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) Heartbeat ExtensionUpdated
February 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?