RFC 4537: Kerberos Cryptosystem Negotiation Extension
In plain English — editorial summary, not part of the RFC
This document specifies an extension to the Kerberos protocol as defined in RFC 4120, in which the client can send a list of supported encryption types in decreasing preference order, and the server then selects an encryption type that is supported by both the client and the server. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4537
- Published
- June 2006
- Authors
- L. Zhu; P. Leach; K. Jaganathan
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 6
- Also known as
- —
- Updates:
- RFC 4120
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4535GSAKMP: Group Secure Association Key Management ProtocolCurrent
June 2006
- RFC 4534Group Security Policy Token v1Current
June 2006
- RFC 4555IKEv2 Mobility and Multihoming Protocol (MOBIKE)Current
June 2006
- RFC 4556Public Key Cryptography for Initial Authentication in Kerberos (PKINIT)Updated
June 2006
- RFC 4557Online Certificate Status Protocol (OCSP) Support for Public Key Cryptography for Initial Authentication in Kerberos (PKINIT)Current
June 2006
- RFC 4563The Key ID Information Type for the General Extension Payload in Multimedia Internet KEYing (MIKEY)Updated
June 2006
- RFC 4505Anonymous Simple Authentication and Security Layer (SASL) MechanismCurrent
June 2006
- RFC 4492Elliptic Curve Cryptography (ECC) Cipher Suites for Transport Layer Security (TLS)Obsoleted
May 2006
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?