RFC 6542: Kerberos Version 5 Generic Security Service Application Program Interface (GSS-API) Channel Binding Hash Agility
In plain English — editorial summary, not part of the RFC
Currently, channel bindings are implemented using an MD5 hash in the Kerberos Version 5 Generic Security Service Application Programming Interface (GSS-API) mechanism (RFC 4121). This document updates RFC 4121 to allow channel bindings using algorithms negotiated based on Kerberos crypto framework as defined in RFC 3961. In addition, because this update makes use of the last extensible field in the Kerberos client-server exchange message, extensions are defined to allow future protocol extensions. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6542
- Published
- March 2012
- Authors
- S. Emery
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 6
- Also known as
- —
- Updates:
- RFC 4121
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6545Real-time Inter-network Defense (RID)Current
April 2012
- RFC 6546Transport of Real-time Inter-network Defense (RID) Messages over HTTP/TLSCurrent
April 2012
- RFC 6560One-Time Password (OTP) Pre-AuthenticationCurrent
April 2012
- RFC 6520Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) Heartbeat ExtensionUpdated
February 2012
- RFC 6595A Simple Authentication and Security Layer (SASL) and GSS-API Mechanism for the Security Assertion Markup Language (SAML)Current
April 2012
- RFC 6613RADIUS over TCPUpdated
May 2012
- RFC 6614Transport Layer Security (TLS) Encryption for RADIUSUpdated
May 2012
- RFC 6616A Simple Authentication and Security Layer (SASL) and Generic Security Service Application Program Interface (GSS-API) Mechanism for OpenIDCurrent
May 2012
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?