RFC 6542 on Kerberos Version 5 Generic Security Service Application Program Interface (GSS-API) Channel Binding Hash Agility
rfc-editor@rfc-editor.org Thu, 08 March 2012 01:43 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7985821E8049 for <ietf-announce@ietfa.amsl.com>; Wed, 7 Mar 2012 17:43:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.898
X-Spam-Level:
X-Spam-Status: No, score=-103.898 tagged_above=-999 required=5 tests=[AWL=1.179, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, J_CHICKENPOX_93=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WovBokbK8Ic1 for <ietf-announce@ietfa.amsl.com>; Wed, 7 Mar 2012 17:43:25 -0800 (PST)
Received: from rfc-editor.org (rfcpa.amsl.com [12.22.58.47]) by ietfa.amsl.com (Postfix) with ESMTP id 001D821E8053 for <ietf-announce@ietf.org>; Wed, 7 Mar 2012 17:43:24 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id C80D472E06D; Wed, 7 Mar 2012 17:43:14 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6542 on Kerberos Version 5 Generic Security Service Application Program Interface (GSS-API) Channel Binding Hash Agility
From: rfc-editor@rfc-editor.org
Message-Id: <20120308014314.C80D472E06D@rfc-editor.org>
Date: Wed, 07 Mar 2012 17:43:14 -0800
Cc: ietf-krb-wg@lists.anl.gov, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Mar 2012 01:43:25 -0000
A new Request for Comments is now available in online RFC libraries. RFC 6542 Title: Kerberos Version 5 Generic Security Service Application Program Interface (GSS-API) Channel Binding Hash Agility Author: S. Emery Status: Standards Track Stream: IETF Date: March 2012 Mailbox: shawn.emery@oracle.com Pages: 6 Characters: 11080 Updates: RFC4121 I-D Tag: draft-ietf-krb-wg-gss-cb-hash-agility-10.txt URL: http://www.rfc-editor.org/rfc/rfc6542.txt 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] 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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC