RFC 8734 on Elliptic Curve Cryptography (ECC) Brainpool Curves for Transport Layer Security (TLS) Version 1.3
rfc-editor@rfc-editor.org Fri, 21 February 2020 22:36 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CB051200E0 for <ietf-announce@ietfa.amsl.com>; Fri, 21 Feb 2020 14:36:13 -0800 (PST)
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 5s_Sj1ubmuNq for <ietf-announce@ietfa.amsl.com>; Fri, 21 Feb 2020 14:36:10 -0800 (PST)
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 78F5F12008F for <ietf-announce@ietf.org>; Fri, 21 Feb 2020 14:36:10 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id BEA98F40719; Fri, 21 Feb 2020 14:36:03 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8734 on Elliptic Curve Cryptography (ECC) Brainpool Curves for Transport Layer Security (TLS) Version 1.3
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200221223603.BEA98F40719@rfc-editor.org>
Date: Fri, 21 Feb 2020 14:36:03 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/uAbc43rVKwIjTg-Enl3fg9SrTVw>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Fri, 21 Feb 2020 22:36:13 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8734
Title: Elliptic Curve Cryptography (ECC) Brainpool
Curves for Transport Layer Security (TLS)
Version 1.3
Author: L. Bruckert,
J. Merkle,
M. Lochter
Status: Informational
Stream: Independent
Date: February 2020
Mailbox: leonie.bruckert@secunet.com,
johannes.merkle@secunet.com,
manfred.lochter@bsi.bund.de
Pages: 11
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-bruckert-brainpool-for-tls13-07.txt
URL: https://www.rfc-editor.org/info/rfc8734
DOI: 10.17487/RFC8734
Elliptic Curve Cryptography (ECC) Brainpool curves were an option for
authentication and key exchange in the Transport Layer Security (TLS)
protocol version 1.2 but were deprecated by the IETF for use with TLS
version 1.3 because they had little usage. However, these curves have
not been shown to have significant cryptographical weaknesses, and
there is some interest in using several of these curves in TLS 1.3.
This document provides the necessary protocol mechanisms for using
ECC Brainpool curves in TLS 1.3. This approach is not endorsed by the
IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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