RFC 1508: Generic Security Service Application Program Interface
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2078.
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
This Generic Security Service Application Program Interface (GSS-API) definition 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
- RFC1508
- Published
- September 1993
- Authors
- J. Linn
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 49
- Also known as
- —
- Obsoleted by:
- RFC 2078
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 1509Generic Security Service API : C-bindingsObsoleted
September 1993
- RFC 1507DASS - Distributed Authentication Security ServiceCurrent
September 1993
- RFC 1510The Kerberos Network Authentication Service (V5)Obsoleted
September 1993
- RFC 4120The Kerberos Network Authentication Service (V5)Updated
July 2005
- RFC 5554Clarifications and Extensions to the Generic Security Service Application Program Interface (GSS-API) for the Use of Channel BindingsCurrent
May 2009
- RFC 8429Deprecate Triple-DES (3DES) and RC4 in KerberosCurrent
October 2018
- RFC 2133Basic Socket Interface Extensions for IPv6Obsoleted
April 1997
- RFC 2203RPCSEC_GSS Protocol SpecificationUpdated
September 1997
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?