[IPsec] RFC 8420 on Using the Edwards-Curve Digital Signature Algorithm (EdDSA) in the Internet Key Exchange Protocol Version 2 (IKEv2)

rfc-editor@rfc-editor.org Mon, 20 August 2018 23:56 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97430130E06; Mon, 20 Aug 2018 16:56:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 Hv_WuBaXabjQ; Mon, 20 Aug 2018 16:56:31 -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 D9337130DF7; Mon, 20 Aug 2018 16:56:31 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 0986AB804DA; Mon, 20 Aug 2018 16:56:19 -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, drafts-update-ref@iana.org, ipsec@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180820235619.0986AB804DA@rfc-editor.org>
Date: Mon, 20 Aug 2018 16:56:19 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/ms7R4vhl8_KxLQfRqxTzS7SC_kw>
Subject: [IPsec] RFC 8420 on Using the Edwards-Curve Digital Signature Algorithm (EdDSA) in the Internet Key Exchange Protocol Version 2 (IKEv2)
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipsec/>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Aug 2018 23:56:34 -0000

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

        
        RFC 8420

        Title:      Using the Edwards-Curve Digital Signature 
                    Algorithm (EdDSA) in the Internet Key 
                    Exchange Protocol Version 2 (IKEv2) 
        Author:     Y. Nir
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2018
        Mailbox:    ynir.ietf@gmail.com
        Pages:      5
        Characters: 9023
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ipsecme-eddsa-04.txt

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

        DOI:        10.17487/RFC8420

This document describes the use of the Edwards-curve Digital
Signature Algorithm (EdDSA) in the Internet Key Exchange Protocol
Version 2 (IKEv2).

This document is a product of the IP Security Maintenance and Extensions 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/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