RFC 5929 on Channel Bindings for TLS
rfc-editor@rfc-editor.org Tue, 13 July 2010 04:25 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DEC813A6B80 for <ietf-announce@core3.amsl.com>; Mon, 12 Jul 2010 21:25:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.547
X-Spam-Level:
X-Spam-Status: No, score=-1.547 tagged_above=-999 required=5 tests=[AWL=-0.159, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, J_CHICKENPOX_93=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W93QN+3TUuor for <ietf-announce@core3.amsl.com>; Mon, 12 Jul 2010 21:25:28 -0700 (PDT)
Received: from rfc-editor.org (rfcpa [64.170.98.47]) by core3.amsl.com (Postfix) with ESMTP id D159A3A6B78 for <ietf-announce@ietf.org>; Mon, 12 Jul 2010 21:25:26 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 8C94EE06DC; Mon, 12 Jul 2010 21:25:35 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5929 on Channel Bindings for TLS
From: rfc-editor@rfc-editor.org
Message-Id: <20100713042535.8C94EE06DC@rfc-editor.org>
Date: Mon, 12 Jul 2010 21:25:35 -0700
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 13 Jul 2010 04:25:29 -0000
A new Request for Comments is now available in online RFC libraries. RFC 5929 Title: Channel Bindings for TLS Author: J. Altman, N. Williams, L. Zhu Status: Standards Track Stream: IETF Date: July 2010 Mailbox: jaltman@secure-endpoints.com, Nicolas.Williams@oracle.com, larry.zhu@microsoft.com Pages: 15 Characters: 34061 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-altman-tls-channel-bindings-10.txt URL: http://www.rfc-editor.org/rfc/rfc5929.txt This document defines three channel binding types for Transport Layer Security (TLS), tls-unique, tls-server-end-point, and tls-unique-for-telnet, in accordance with RFC 5056 (On Channel Binding). Note that based on implementation experience, this document changes the original definition of 'tls-unique' channel binding type in the channel binding type IANA registry. [STANDARDS TRACK] 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
- RFC 5929 on Channel Bindings for TLS rfc-editor