[TLS] Moved to Proposed Standard: RFC 5289 on TLS Elliptic Curve Cipher Suites with SHA-256/384 and AES Galois Counter Mode (GCM)
rfc-editor@rfc-editor.org Tue, 10 July 2018 19:51 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36E7A1311A3; Tue, 10 Jul 2018 12:51:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 zWFxuHhKixX6; Tue, 10 Jul 2018 12:51:42 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A64F913104C; Tue, 10 Jul 2018 12:51:42 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C2556B80101; Tue, 10 Jul 2018 12:51:41 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, tls@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180710195141.C2556B80101@rfc-editor.org>
Date: Tue, 10 Jul 2018 12:51:41 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/A1cTeBZ9NPhTRgoZcHywdfIDcRQ>
Subject: [TLS] Moved to Proposed Standard: RFC 5289 on TLS Elliptic Curve Cipher Suites with SHA-256/384 and AES Galois Counter Mode (GCM)
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.27
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 10 Jul 2018 19:51:47 -0000
RFC 5289 has been reclassified as Proposed Standard.
RFC 5289
Title: TLS Elliptic Curve Cipher Suites
with SHA-256/384 and AES Galois Counter
Mode (GCM)
Author: E. Rescorla
Status: Standards Track
Stream: IETF
Date: August 2008
Mailbox: ekr@rtfm.com
Pages: 6
Characters: 12195
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-tls-ecc-new-mac-07.txt
URL: https://www.rfc-editor.org/info/rfc5289
DOI: 10.17487/RFC5289
RFC 4492 describes elliptic curve cipher suites for Transport Layer
Security (TLS). However, all those cipher suites use HMAC-SHA-1 as
their Message Authentication Code (MAC) algorithm. This document
describes sixteen new cipher suites for TLS that specify stronger MAC
algorithms. Eight use Hashed Message Authentication Code (HMAC) with
SHA-256 or SHA-384, and eight use AES in Galois Counter Mode (GCM).
This memo provides information for the Internet community.
This document is a product of the Transport Layer Security Working Group of the IETF.
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/retrieve/bulk
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