Internet Key Exchange Protocol Version 2 Support for Per- Resource Child Security Associations
RFC 9611, “Internet Key Exchange Protocol Version 2 Support for Per- Resource Child Security Associations”, is a Proposed Standard document published in July 2024 by A. Antony, T. Brunner, S. Klassert, P. Wouters. The canonical text is published by the RFC Editor.
Abstract
In order to increase the bandwidth of IPsec traffic between peers, this document defines one Notify Message Status Types and one Notify Message Error Types payload for the Internet Key Exchange Protocol Version 2 (IKEv2) to support the negotiation of multiple Child Security Associations (SAs) with the same Traffic Selectors used on different resources, such as CPUs.
The SA_RESOURCE_INFO notification is used to convey information that the negotiated Child SA and subsequent new Child SAs with the same Traffic Selectors are a logical group of Child SAs where most or all of the Child SAs are bound to a specific resource, such as a specific CPU. The TS_MAX_QUEUE notify conveys that the peer is unwilling to create more additional Child SAs for this particular negotiated Traffic Selector combination.
Using multiple Child SAs with the same Traffic Selectors has the benefit that each resource holding the Child SA has its own Sequence Number Counter, ensuring that CPUs don't have to synchronize their cryptographic state or disable their packet replay protection.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 9611 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 9610 JSON Meta Application Protocol for Contacts
- RFC 9612 Bidirectional Forwarding Detection Reverse Path for MPLS Label Switched Paths
- RFC 9613 Requirements for Solutions that Support MPLS Network Actions
- RFC 9608 No Revocation Available for X.509 Public Key Certificates
- RFC 9614 Partitioning as an Architecture for Privacy
- RFC 9607 RTP Payload Format for the Secure Communication Interoperability Protocol Codec
- RFC 9615 Automatic DNSSEC Bootstrapping Using Authenticated Signals from the Zone's Operator
- RFC 9606 DNS Resolver Information