RFC 8062: Anonymity Support for Kerberos
In plain English — editorial summary, not part of the RFC
This document defines extensions to the Kerberos protocol to allow a Kerberos client to securely communicate with a Kerberos application service without revealing its identity, or without revealing more than its Kerberos realm. It also defines extensions that allow a Kerberos client to obtain anonymous credentials without revealing its identity to the Kerberos Key Distribution Center (KDC). This document updates RFCs 4120, 4121, and 4556. This document obsoletes RFC 6112 and reclassifies that document as Historic. RFC 6112 contained errors, and the protocol described in that specification is not interoperable with any known implementation. This specification describes a protocol that interoperates with multiple implementations.
Document record
- Document ID
- RFC8062
- Published
- February 2017
- Authors
- L. Zhu; P. Leach; S. Hartman; S. Emery
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 18
- Also known as
- —
- Obsoletes:
- RFC 6112
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8070Public Key Cryptography for Initial Authentication in Kerberos (PKINIT) Freshness ExtensionCurrent
February 2017
- RFC 8053HTTP Authentication Extensions for Interactive ClientsCurrent
January 2017
- RFC 8045RADIUS Extensions for IP Port Configuration and ReportingCurrent
January 2017
- RFC 8080Edwards-Curve Digital Security Algorithm (EdDSA) for DNSSECCurrent
February 2017
- RFC 8044Data Types in RADIUSCurrent
January 2017
- RFC 8037CFRG Elliptic Curve Diffie-Hellman (ECDH) and Signatures in JSON Object Signing and Encryption (JOSE)Updated
January 2017
- RFC 8031Curve25519 and Curve448 for the Internet Key Exchange Protocol Version 2 (IKEv2) Key AgreementCurrent
December 2016
- RFC 8103Using ChaCha20-Poly1305 Authenticated Encryption in the Cryptographic Message Syntax (CMS)Current
February 2017
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?