RFC 4537 on Kerberos Cryptosystem Negotiation Extension

[rfc-editor]

A new Request for Comments is now available in online RFC libraries.


RFC 4537

Title:  Kerberos Cryptosystem Negotiation Extension 
Author: L. Zhu, P. Leach,
K. Jaganathan
Status: Standards Track
Date:   June 2006
Mailbox:[EMAIL PROTECTED], 
[EMAIL PROTECTED], 
[EMAIL PROTECTED]
Pages:  6
Characters: 11166
Updates:RFC4120
See-Also:   

I-D Tag:draft-zhu-kerb-enctype-nego-04.txt

URL:http://www.rfc-editor.org/rfc/rfc4537.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 
unlimited.

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 [EMAIL PROTECTED]  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [EMAIL PROTECTED]

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [EMAIL PROTECTED] with the message body 

help: ways_to_get_rfcs. For example:

To: [EMAIL PROTECTED]
Subject: getting rfcs

help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [EMAIL PROTECTED]  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[EMAIL PROTECTED]  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...



___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce

Open mailing list for the discussion of Independent RFC Submissions Process

[Leslie Daigle]

As part its role in supporting the RFC Editor function, the Internet
Architecture Board (IAB) has created a public mailing list for the discussion of
the RFC Independent Submissions process.  

The purpose of this discussion is to achieve consensus, in the coming weeks, on
a process for fair and appropriate approval of independent submissions to the
RFC series.  These are separate from IETF, IAB or IRTF approved submissions. 

Individuals familiar with the RFC series and working in the Internet research
and engineering community are invited to join this mailing list and participate.

  independentietf.org

  https://www1.ietf.org/mailman/listinfo/independent


There is an initial draft proposal, available at

  http://www.ietf.org/internet-drafts/draft-klensin-rfc-independent-02.txt


Leslie Daigle,
Chair, IAB.

___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce

Last Call: 'The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)' to Proposed Standard (draft-ietf-simple-xcap)

[The IESG]

The IESG has received a request from the SIP for Instant Messaging and Presence
 
Leveraging Extensions WG to consider the following document:

- 'The Extensible Markup Language (XML) Configuration Access Protocol (XCAP) '
as a Proposed Standard

On 2005-6-21, the IESG approved draft-ietf-simple-xcap-07.txt. Prior to its
being published as an RFC, new issues were raised which required revision. The
IESG solicits review of this new version, in particular of Sections 7.10, 7.11 &
8.23 where the major changes were made.

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by 2006-06-21.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-simple-xcap-11.txt


___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce