BCP 195, RFC 7525 on Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
rfc-editor@rfc-editor.org Tue, 05 May 2015 01:46 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04A181B2D5E; Mon, 4 May 2015 18:46:13 -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 wrW3M465hvPF; Mon, 4 May 2015 18:46:10 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 8EE9C1AC3D9; Mon, 4 May 2015 18:46:10 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 3495918046C; Mon, 4 May 2015 18:44:51 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 195, RFC 7525 on Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150505014451.3495918046C@rfc-editor.org>
Date: Mon, 04 May 2015 18:44:51 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/28DS7QXREptdPT8mVUlgvoC7198>
Cc: uta@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
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: Tue, 05 May 2015 01:46:13 -0000
A new Request for Comments is now available in online RFC libraries.
BCP 195
RFC 7525
Title: Recommendations for Secure Use of
Transport Layer Security (TLS) and Datagram
Transport Layer Security (DTLS)
Author: Y. Sheffer, R. Holz,
P. Saint-Andre
Status: Best Current Practice
Stream: IETF
Date: May 2015
Mailbox: yaronf.ietf@gmail.com,
ralph.ietf@gmail.com,
peter@andyet.com
Pages: 27
Characters: 60283
See Also: BCP 195
I-D Tag: draft-ietf-uta-tls-bcp-11.txt
URL: https://www.rfc-editor.org/info/rfc7525
Transport Layer Security (TLS) and Datagram Transport Layer Security
(DTLS) are widely used to protect data exchanged over application
protocols such as HTTP, SMTP, IMAP, POP, SIP, and XMPP. Over the
last few years, several serious attacks on TLS have emerged,
including attacks on its most commonly used cipher suites and their
modes of operation. This document provides recommendations for
improving the security of deployed services that use TLS and DTLS.
The recommendations are applicable to the majority of use cases.
This document is a product of the Using TLS in Applications Working Group of the IETF.
BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. 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