RFC 2853: Generic Security Service API Version 2 : Java Bindings
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5653.
Current document in this lineage: RFC 8353 — Generic Security Service API Version 2: Java Bindings Update
In plain English — editorial summary, not part of the RFC
This document specifies the Java bindings for GSS-API (Generic Security Service Application Program Interface) which is described at a language independent conceptual level in RFC 2743. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2853
- Published
- June 2000
- Authors
- J. Kabat; M. Upadhyay
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 96
- Also known as
- —
- Obsoleted by:
- RFC 5653
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 2853 (2000)
- RFC 5653 (2009)
- RFC 8353 (2018) ✓
Read the full history of Generic Security Service API Version 2: Java Bindings Update →
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 2744Generic Security Service API Version 2 : C-bindingsUpdated
January 2000
- RFC 2743Generic Security Service Application Program Interface Version 2, Update 1Updated
January 2000
- RFC 5554Clarifications and Extensions to the Generic Security Service Application Program Interface (GSS-API) for the Use of Channel BindingsCurrent
May 2009
- RFC 5587Extended Generic Security Service Mechanism Inquiry APIsCurrent
July 2009
- RFC 5588Generic Security Service Application Program Interface (GSS-API) Extension for Storing Delegated CredentialsCurrent
July 2009
- RFC 6595A Simple Authentication and Security Layer (SASL) and GSS-API Mechanism for the Security Assertion Markup Language (SAML)Current
April 2012
- RFC 7546Structure of the Generic Security Service (GSS) Negotiation LoopCurrent
May 2015
- RFC 7804Salted Challenge Response HTTP Authentication MechanismCurrent
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?