RFC 4401: A Pseudo-Random Function (PRF) API Extension for the Generic Security Service Application Program Interface (GSS-API)
In plain English — editorial summary, not part of the RFC
This document defines a Pseudo-Random Function (PRF) extension to the Generic Security Service Application Program Interface (GSS-API) for keying application protocols given an established GSS-API security context. The primary intended use of this function is to key secure session layers that do not or cannot use GSS-API per-message message integrity check (MIC) and wrap tokens for session protection. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4401
- Published
- February 2006
- Authors
- N. Williams
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5403RPCSEC_GSS Version 2Updated
February 2009
- RFC 1544The Content-MD5 Header FieldObsoleted
November 1993
- RFC 4402A Pseudo-Random Function (PRF) for the Kerberos V Generic Security Service Application Program Interface (GSS-API) MechanismObsoleted
February 2006
- RFC 4387Internet X.509 Public Key Infrastructure Operational Protocols: Certificate Store Access via HTTPUpdated
February 2006
- RFC 4386Internet X.509 Public Key Infrastructure Repository Locator ServiceUpdated
February 2006
- RFC 4383The Use of Timed Efficient Stream Loss-Tolerant Authentication (TESLA) in the Secure Real-time Transport Protocol (SRTP)Current
February 2006
- RFC 4419Diffie-Hellman Group Exchange for the Secure Shell (SSH) Transport Layer ProtocolUpdated
March 2006
- RFC 4422Simple Authentication and Security Layer (SASL)Current
June 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?