RFC 5587: Extended Generic Security Service Mechanism Inquiry APIs
In plain English — editorial summary, not part of the RFC
This document introduces new application programming interfaces (APIs) to the Generic Security Services API (GSS-API) for extended mechanism attribute inquiry. These interfaces are primarily intended to reduce instances of hardcoding of mechanism identifiers in GSS applications. These interfaces include mechanism attributes and attribute sets, a function for inquiring the attributes of a mechanism, a function for indicating mechanisms that possess given attributes, and a function for displaying mechanism attributes. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5587
- Published
- July 2009
- Authors
- N. Williams
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 16
- 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 7861Remote Procedure Call (RPC) Security Version 3Current
November 2016
- RFC 5588Generic Security Service Application Program Interface (GSS-API) Extension for Storing Delegated CredentialsCurrent
July 2009
- RFC 5554Clarifications and Extensions to the Generic Security Service Application Program Interface (GSS-API) for the Use of Channel BindingsCurrent
May 2009
- RFC 5653Generic Security Service API Version 2: Java Bindings UpdateObsoleted
August 2009
- RFC 4305Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)Obsoleted
December 2005
- RFC 7499Support of Fragmentation of RADIUS PacketsCurrent
April 2015
- RFC 7546Structure of the Generic Security Service (GSS) Negotiation LoopCurrent
May 2015
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?