RFC 7670 on Generic Raw Public-Key Support for IKEv2
rfc-editor@rfc-editor.org Thu, 21 January 2016 03:58 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 CEFCF1B2E26 for <ietf-announce@ietfa.amsl.com>; Wed, 20 Jan 2016 19:58:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.903
X-Spam-Level:
X-Spam-Status: No, score=-106.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 phT_GS3kXf9P for <ietf-announce@ietfa.amsl.com>; Wed, 20 Jan 2016 19:58:26 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id CAAD41B2E27 for <ietf-announce@ietf.org>; Wed, 20 Jan 2016 19:58:26 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 715F418000D; Wed, 20 Jan 2016 19:57:13 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7670 on Generic Raw Public-Key Support for IKEv2
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160121035713.715F418000D@rfc-editor.org>
Date: Wed, 20 Jan 2016 19:57:13 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/krtxeLEOfAswOKLPIOGTpy9_J60>
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: Thu, 21 Jan 2016 03:58:29 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7670
Title: Generic Raw Public-Key Support for IKEv2
Author: T. Kivinen, P. Wouters, H. Tschofenig
Status: Standards Track
Stream: IETF
Date: January 2016
Mailbox: kivinen@iki.fi,
pwouters@redhat.com,
Hannes.Tschofenig@gmx.net
Pages: 10
Characters: 21350
Updates: RFC 7296
I-D Tag: draft-kivinen-ipsecme-oob-pubkey-14.txt
URL: https://www.rfc-editor.org/info/rfc7670
DOI: http://dx.doi.org/10.17487/RFC7670
The Internet Key Exchange Version 2 (IKEv2) protocol did have support
for raw public keys, but it only supported RSA raw public keys. In
constrained environments, it is useful to make use of other types of
public keys, such as those based on Elliptic Curve Cryptography.
This document updates RFC 7296, adding support for other types of raw
public keys to IKEv2.
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