RFC 3961: Encryption and Checksum Specifications for Kerberos 5
In plain English — editorial summary, not part of the RFC
This document describes a framework for defining encryption and checksum mechanisms for use with the Kerberos protocol, defining an abstraction layer between the Kerberos protocol and related protocols, and the actual mechanisms themselves. The document also defines several mechanisms. Some are taken from RFC 1510, modified in form to fit this new framework and occasionally modified in content when the old specification was incorrect. New mechanisms are presented here as well. This document does NOT indicate which mechanisms may be considered "required to implement". [STANDARDS-TRACK]
Document record
- Document ID
- RFC3961
- Published
- February 2005
- Authors
- K. Raeburn
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 50
- Also known as
- —
- Updated by:
- RFC 8429
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 3962Advanced Encryption Standard (AES) Encryption for Kerberos 5Updated
February 2005
- RFC 3948UDP Encapsulation of IPsec ESP PacketsCurrent
January 2005
- RFC 3947Negotiation of NAT-Traversal in the IKECurrent
January 2005
- RFC 4010Use of the SEED Encryption Algorithm in Cryptographic Message Syntax (CMS)Current
February 2005
- RFC 4013SASLprep: Stringprep Profile for User Names and PasswordsObsoleted
March 2005
- RFC 4025A Method for Storing IPsec Keying Material in DNSCurrent
March 2005
- RFC 4043Internet X.509 Public Key Infrastructure Permanent IdentifierCurrent
May 2005
- RFC 4046Multicast Security (MSEC) Group Key Management ArchitectureCurrent
May 2005
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?