Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Obsoletes:

RFC 4307

Updates:

RFC 7296

Updated by:

RFC 9395

Authors:

Y. Nir
T. Kivinen
P. Wouters
D. Migault

Stream:

IETF

Source:

ipsecme (sec)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC8247

Discuss this RFC: Send questions or comments to the mailing listipsec@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 8247

Abstract

The IPsec series of protocols makes use of various cryptographicalgorithms in order to provide security services. The Internet KeyExchange (IKE) protocol is used to negotiate the IPsec SecurityAssociation (IPsec SA) parameters, such as which algorithms should beused. To ensure interoperability between different implementations,it is necessary to specify a set of algorithm implementationrequirements and usage guidance to ensure that there is at least onealgorithm that all implementations support. This document updates RFC7296 and obsoletes RFC 4307 in defining the current algorithmimplementation requirements and usage guidance for IKEv2, and doesminor cleaning up of the IKEv2 IANA registry. This document does notupdate the algorithms used for packet encryption using IPsecEncapsulating Security Payload (ESP).

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.