Kerberos Cryptosystem Negotiation Extension

Metadata

Publisher: IETF
Doc Type: Standard
Pages: 6
Abstract: 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]
Publication Date: 2006-06-01
Status Note: Proposed Standard
DOI: 10.17487/RFC4537
Link: https://doi.org/10.17487/RFC4537
Author(s): Larry Zhu
Paul J. Leach
Karthik Jaganathan

Latest version of IETF RFC 4537

Document Versions — IETF RFC 4537

▶ IETF RFC 4537 (2006-06-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

ISO 8824-1:2002 (ITU-T X.680) [Withdrawn]
ISO 8825-1:2002 [Withdrawn]
IETF RFC 2119 [Active*]
IETF RFC 3961 [Active*]
IETF RFC 4120 [Active*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC4537.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 4537, Kerberos Cryptosystem Negotiation Extension. Available at https://doi.org/10.17487/RFC4537

Snippet:

IETF RFC 4537, Kerberos Cryptosystem Negotiation Extension. Available at https://doi.org/10.17487/RFC4537

HTML (ISO 690 compliant)

Preview:

IETF RFC 4537, Kerberos Cryptosystem Negotiation Extension. Available at https://doi.org/10.17487/RFC4537

Snippet:

<span class="citation"><cite>IETF RFC 4537</cite>, Kerberos Cryptosystem Negotiation Extension. Available at <a href="https://doi.org/10.17487/RFC4537" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4537</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 4537, Kerberos Cryptosystem Negotiation Extension
doi: 10.17487/RFC4537
url: https://doi.org/10.17487/RFC4537

Snippet:

<li>
<cite id="bib-rfc4537">IETF RFC 4537</cite>, Kerberos Cryptosystem Negotiation Extension
<span class="doi">10.17487/RFC4537</span>
</li>

Referenced By

IETF RFC 4757 [Active*]