RFC 4752: The Kerberos V5 ("GSSAPI") Simple Authentication and Security Layer (SASL) Mechanism
In plain English — editorial summary, not part of the RFC
The Simple Authentication and Security Layer (SASL) is a framework for adding authentication support to connection-based protocols. This document describes the method for using the Generic Security Service Application Program Interface (GSS-API) Kerberos V5 in the SASL. This document replaces Section 7.2 of RFC 2222, the definition of the "GSSAPI" SASL mechanism. This document, together with RFC 4422, obsoletes RFC 2222. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4752
- Published
- November 2006
- Authors
- A. Melnikov
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 10
- Also known as
- —
- Obsoletes:
- RFC 2222
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 2222 (1997)
- RFC 4422 (2006)
- RFC 4752 (2006)
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4422Simple Authentication and Security Layer (SASL)Current
June 2006
- RFC 2104HMAC: Keyed-Hashing for Message AuthenticationUpdated
February 1997
- RFC 2085HMAC-MD5 IP Authentication with Replay PreventionCurrent
February 1997
- RFC 1829The ESP DES-CBC TransformCurrent
August 1995
- RFC 2082RIP-2 MD5 AuthenticationObsoleted
January 1997
- RFC 4491Using the GOST R 34.10-94, GOST R 34.10-2001, and GOST R 34.11-94 Algorithms with the Internet X.509 Public Key Infrastructure Certificate and CRL ProfileCurrent
May 2006
- RFC 4490Using the GOST 28147-89, GOST R 34.11-94, GOST R 34.10-94, and GOST R 34.10-2001 Algorithms with Cryptographic Message Syntax (CMS)Current
May 2006
- RFC 4366Transport Layer Security (TLS) ExtensionsObsoleted
April 2006
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?