RFC 5746 on Transport Layer Security (TLS) Renegotiation Indication Extension

rfc-editor@rfc-editor.org Fri, 12 February 2010 20:42 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 []) by core3.amsl.com (Postfix) with ESMTP id B6AA728C21D; Fri, 12 Feb 2010 12:42:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.272
X-Spam-Status: No, score=-2.272 tagged_above=-999 required=5 tests=[AWL=-0.272, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id O9IWKfVdEwbl; Fri, 12 Feb 2010 12:42:24 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 4678528C21A; Fri, 12 Feb 2010 12:42:21 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 4EBA2130007; Fri, 12 Feb 2010 12:43:41 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5746 on Transport Layer Security (TLS) Renegotiation Indication Extension
From: rfc-editor@rfc-editor.org
Message-Id: <20100212204341.4EBA2130007@rfc-editor.org>
Date: Fri, 12 Feb 2010 12:43:41 -0800
Cc: tls@ietf.org, 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: Fri, 12 Feb 2010 20:42:24 -0000

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

        RFC 5746

        Title:      Transport Layer Security (TLS) Renegotiation 
                    Indication Extension 
        Author:     E. Rescorla, M. Ray,
                    S. Dispensa, N. Oskov
        Status:     Standards Track
        Date:       February 2010
        Mailbox:    ekr@rtfm.com, 
                    dispensa@phonefactor.com,  nasko.oskov@microsoft.com
        Pages:      15
        Characters: 33790
        Updates:    RFC5246, RFC4366, RFC4347, RFC4346, RFC2246

        I-D Tag:    draft-ietf-tls-renegotiation-03.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5746.txt

Secure Socket Layer (SSL) and Transport Layer Security (TLS)
renegotiation are vulnerable to an attack in which the attacker forms
a TLS connection with the target server, injects content of his
choice, and then splices in a new TLS connection from a client.  The
server treats the client's initial TLS handshake as a renegotiation
and thus believes that the initial data transmitted by the attacker is
from the same entity as the subsequent client data.  This
specification defines a TLS extension to cryptographically tie
renegotiations to the TLS connections they are being performed over,
thus preventing this attack.  [STANDARDS TRACK]

This document is a product of the Transport Layer Security 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

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