RFC 7633 on X.509v3 Transport Layer Security (TLS) Feature Extension
rfc-editor@rfc-editor.org Wed, 14 October 2015 23:50 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 94B9B1A9058 for <ietf-announce@ietfa.amsl.com>; Wed, 14 Oct 2015 16:50:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 Dgg8lKd1RCAv for <ietf-announce@ietfa.amsl.com>; Wed, 14 Oct 2015 16:50:24 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 4F3A01A904B for <ietf-announce@ietf.org>; Wed, 14 Oct 2015 16:50:20 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id D2D53187E27; Wed, 14 Oct 2015 16:50:06 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7633 on X.509v3 Transport Layer Security (TLS) Feature Extension
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20151014235006.D2D53187E27@rfc-editor.org>
Date: Wed, 14 Oct 2015 16:50:06 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/CQET6tjoRcMzsNjmrwF23N2nWX4>
Cc: drafts-update-ref@iana.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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 14 Oct 2015 23:50:25 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7633
Title: X.509v3 Transport Layer Security (TLS)
Feature Extension
Author: P. Hallam-Baker
Status: Standards Track
Stream: IETF
Date: October 2015
Mailbox: philliph@comodo.com
Pages: 11
Characters: 21839
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-hallambaker-tlsfeature-10.txt
URL: https://www.rfc-editor.org/info/rfc7633
DOI: http://dx.doi.org/10.17487/RFC7633
The purpose of the TLS feature extension is to prevent downgrade
attacks that are not otherwise prevented by the TLS protocol. In
particular, the TLS feature extension may be used to mandate support
for revocation checking features in the TLS protocol such as Online
Certificate Status Protocol (OCSP) stapling. Informing clients that
an OCSP status response will always be stapled permits an immediate
failure in the case that the response is not stapled. This in turn
prevents a denial-of-service attack that might otherwise be possible.
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