[IPsec] RFC 8247 on Algorithm Implementation Requirements and Usage Guidance for the Internet Key Exchange Protocol Version 2 (IKEv2)
rfc-editor@rfc-editor.org Wed, 13 September 2017 18:06 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 83ED213292F; Wed, 13 Sep 2017 11:06:06 -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 ZEeU1ZJ0Ij_G; Wed, 13 Sep 2017 11:06:04 -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 BCD73132403; Wed, 13 Sep 2017 11:06:04 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 1DFEFB811AA; Wed, 13 Sep 2017 11:05:52 -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
Message-Id: <20170913180552.1DFEFB811AA@rfc-editor.org>
Date: Wed, 13 Sep 2017 11:05:52 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/d71quYbK_hDE69hm-jXHM9vDpqM>
Subject: [IPsec] RFC 8247 on Algorithm Implementation Requirements and Usage Guidance for the Internet Key Exchange Protocol Version 2 (IKEv2)
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 13 Sep 2017 18:06:06 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8247
Title: Algorithm Implementation Requirements and Usage
Guidance for the Internet Key Exchange
Protocol Version 2 (IKEv2)
Author: Y. Nir,
T. Kivinen,
P. Wouters,
D. Migault
Status: Standards Track
Stream: IETF
Date: September 2017
Mailbox: ynir.ietf@gmail.com,
kivinen@iki.fi,
pwouters@redhat.com,
daniel.migault@ericsson.com
Pages: 19
Characters: 44739
Obsoletes: RFC 4307
Updates: RFC 7296
I-D Tag: draft-ietf-ipsecme-rfc4307bis-18.txt
URL: https://www.rfc-editor.org/info/rfc8247
DOI: 10.17487/RFC8247
The IPsec series of protocols makes use of various cryptographic
algorithms in order to provide security services. The Internet Key
Exchange (IKE) protocol is used to negotiate the IPsec Security
Association (IPsec SA) parameters, such as which algorithms should be
used. To ensure interoperability between different implementations,
it is necessary to specify a set of algorithm implementation
requirements and usage guidance to ensure that there is at least one
algorithm that all implementations support. This document updates RFC
7296 and obsoletes RFC 4307 in defining the current algorithm
implementation requirements and usage guidance for IKEv2, and does
minor cleaning up of the IKEv2 IANA registry. This document does not
update the algorithms used for packet encryption using IPsec
Encapsulating Security Payload (ESP).
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