RFC 7802: A Pseudo-Random Function (PRF) for the Kerberos V Generic Security Service Application Program Interface (GSS-API) Mechanism
In plain English — editorial summary, not part of the RFC
This document defines the Pseudo-Random Function (PRF) for the Kerberos V mechanism for the Generic Security Service Application Program Interface (GSS-API), based on the PRF defined for the Kerberos V cryptographic framework, for keying application protocols given an established Kerberos V GSS-API security context. This document obsoletes RFC 4402 and reclassifies that document as Historic. RFC 4402 starts the PRF+ counter at 1; however, a number of implementations start the counter at 0. As a result, the original specification would not be interoperable with existing implementations.
Document record
- Document ID
- RFC7802
- Published
- March 2016
- Authors
- S. Emery; N. Williams
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 8
- Also known as
- —
- Obsoletes:
- RFC 4402
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7804Salted Challenge Response HTTP Authentication MechanismCurrent
March 2016
- RFC 7800Proof-of-Possession Key Semantics for JSON Web Tokens (JWTs)Current
April 2016
- RFC 7797JSON Web Signature (JWS) Unencoded Payload OptionCurrent
February 2016
- RFC 7817Updated Transport Layer Security (TLS) Server Identity Check Procedure for Email-Related ProtocolsCurrent
March 2016
- RFC 7831Application Bridging for Federated Access Beyond Web (ABFAB) ArchitectureCurrent
May 2016
- RFC 7832Application Bridging for Federated Access Beyond Web (ABFAB) Use CasesCurrent
May 2016
- RFC 7833A RADIUS Attribute, Binding, Profiles, Name Identifier Format, and Confirmation Methods for the Security Assertion Markup Language (SAML)Current
May 2016
- RFC 7751Kerberos Authorization Data Container Authenticated by Multiple Message Authentication Codes (MACs)Current
March 2016
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?