[TLS] RFC 7507 on TLS Fallback Signaling Cipher Suite Value (SCSV) for Preventing Protocol Downgrade Attacks

rfc-editor@rfc-editor.org Fri, 24 April 2015 22:20 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82B411AD0B4; Fri, 24 Apr 2015 15:20:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p1IZSNp6DzRF; Fri, 24 Apr 2015 15:20:25 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 1841E1AD0B3; Fri, 24 Apr 2015 15:20:25 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C4DB7180208; Fri, 24 Apr 2015 15:19:18 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150424221918.C4DB7180208@rfc-editor.org>
Date: Fri, 24 Apr 2015 15:19:18 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/vo2k1WoiRdBCiLOLakUfx2nlL7Y>
Cc: drafts-update-ref@iana.org, tls@ietf.org, rfc-editor@rfc-editor.org
Subject: [TLS] RFC 7507 on TLS Fallback Signaling Cipher Suite Value (SCSV) for Preventing Protocol Downgrade Attacks
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Apr 2015 22:20:26 -0000

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

        
        RFC 7507

        Title:      TLS Fallback Signaling Cipher Suite Value (SCSV)
                    for Preventing Protocol Downgrade Attacks 
        Author:     B. Moeller, A. Langley
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2015
        Mailbox:    bmoeller@acm.org, agl@google.com
        Pages:      8
        Characters: 17165
        Updates:    RFC 2246, RFC 4346, RFC 4347, RFC 5246, RFC 6347

        I-D Tag:    draft-ietf-tls-downgrade-scsv-05.txt

        URL:        https://www.rfc-editor.org/info/rfc7507

This document defines a Signaling Cipher Suite Value (SCSV) that
prevents protocol downgrade attacks on the Transport Layer Security
(TLS) and Datagram Transport Layer Security (DTLS) protocols.  It
updates RFCs 2246, 4346, 4347, 5246, and 6347.  Server update
considerations are included.

This document is a product of the Transport Layer Security Working Group of the IETF.

This is now a Proposed Standard.

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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://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