[rfc-dist] RFC 4537 on Kerberos Cryptosystem Negotiation Extension
rfc-editor at rfc-editor.org
Wed Jun 7 16:33:00 PDT 2006
A new Request for Comments is now available in online RFC libraries.
Title: Kerberos Cryptosystem Negotiation Extension
Author: L. Zhu, P. Leach,
Status: Standards Track
Date: June 2006
Mailbox: lzhu at microsoft.com,
paulle at microsoft.com,
karthikj at microsoft.com
I-D Tag: draft-zhu-kerb-enctype-nego-04.txt
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]
This document is a product of the Kerberos WG
Working Group of the IETF.
This is now a Proposed Standard Protocol.
STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and
suggestions for improvements.Please refer to the current edition of
the Internet Official Protocol Standards (STD 1) for the standardization
state and status of this protocol. Distribution of this memo is
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at RFC-EDITOR.ORG
Subject: getting rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
More information about the rfc-dist