RFC 2078: Generic Security Service Application Program Interface, Version 2
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2743.
Current document in this lineage: RFC 2743 — Generic Security Service Application Program Interface Version 2, Update 1
In plain English — editorial summary, not part of the RFC
The Generic Security Service Application Program Interface (GSS-API), as defined in RFC-1508, provides security services to callers in a generic fashion, supportable with a range of underlying mechanisms and technologies and hence allowing source-level portability of applications to different environments. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2078
- Published
- January 1997
- Authors
- J. Linn
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 85
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 1508 (1993)
- RFC 2078 (1997)
- RFC 2743 (2000) ✓
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 2479Independent Data Unit Protection Generic Security Service Application Program Interface (IDUP-GSS-API)Current
December 1998
- RFC 2528Internet X.509 Public Key Infrastructure Representation of Key Exchange Algorithm (KEA) Keys in Internet X.509 Public Key Infrastructure CertificatesCurrent
March 1999
- RFC 2539Storage of Diffie-Hellman Keys in the Domain Name System (DNS)Updated
March 1999
- RFC 2744Generic Security Service API Version 2 : C-bindingsUpdated
January 2000
- RFC 4302IP Authentication HeaderCurrent
December 2005
- RFC 4303IP Encapsulating Security Payload (ESP)Current
December 2005
- RFC 5403RPCSEC_GSS Version 2Updated
February 2009
- RFC 8915Network Time Security for the Network Time ProtocolCurrent
September 2020
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?