RFC 2743: Generic Security Service Application Program Interface Version 2, Update 1
In plain English — editorial summary, not part of the RFC
This memo obsoletes [STANDARDS-TRACK]
Document record
- Document ID
- RFC2743
- Published
- January 2000
- Authors
- J. Linn
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 101
- Also known as
- —
- Obsoletes:
- 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
2 later RFCs formally update or obsolete 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 2853Generic Security Service API Version 2 : Java BindingsObsoleted
June 2000
- RFC 2539Storage of Diffie-Hellman Keys in the Domain Name System (DNS)Updated
March 1999
- 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 7546Structure of the Generic Security Service (GSS) Negotiation LoopCurrent
May 2015
- RFC 5403RPCSEC_GSS Version 2Updated
February 2009
- RFC 7861Remote Procedure Call (RPC) Security Version 3Current
November 2016
- RFC 2712Addition of Kerberos Cipher Suites to Transport Layer Security (TLS)Current
October 1999
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?