RFC 5554: Clarifications and Extensions to the Generic Security Service Application Program Interface (GSS-API) for the Use of Channel Bindings
In plain English — editorial summary, not part of the RFC
This document clarifies and generalizes the Generic Security Service Application Programming Interface (GSS-API) "channel bindings" facility, and imposes requirements on future GSS-API mechanisms and programming language bindings of the GSS-API. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5554
- Published
- May 2009
- Authors
- N. Williams
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 4
- Also known as
- —
- Updates:
- RFC 2743
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8429Deprecate Triple-DES (3DES) and RC4 in KerberosCurrent
October 2018
- RFC 5403RPCSEC_GSS Version 2Updated
February 2009
- RFC 7861Remote Procedure Call (RPC) Security Version 3Current
November 2016
- 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 5653Generic Security Service API Version 2: Java Bindings UpdateObsoleted
August 2009
- RFC 5998An Extension for EAP-Only Authentication in IKEv2Current
September 2010
- 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?