<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.pwouters-ipsecme-multi-sa-performance" target="https://datatracker.ietf.org/doc/html/draft-pwouters-ipsecme-multi-sa-performance-05">
   <front>
      <title>IKEv2 support for per-queue Child SAs</title>
      <author initials="A." surname="Antony" fullname="Antony Antony">
         <organization>secunet Security Networks AG</organization>
      </author>
      <author initials="T." surname="Brunner" fullname="Tobias Brunner">
         <organization>codelabs GmbH</organization>
      </author>
      <author initials="S." surname="Klassert" fullname="Steffen Klassert">
         <organization>secunet Security Networks AG</organization>
      </author>
      <author initials="P." surname="Wouters" fullname="Paul Wouters">
         <organization>Aiven</organization>
      </author>
      <date month="November" day="8" year="2022" />
      <abstract>
	 <t>   This document defines three Notify Message Type Payloads for the
   Internet Key Exchange Protocol Version 2 (IKEv2) indicating support
   for the negotiation of multiple identical Child SAs to optimize
   performance.

   The CPU_QUEUES notification indicates support for multiple queues or
   CPUs.  The CPU_QUEUE_INFO notification is used to confirm and
   optionally convey information about the specific queue.  The
   TS_MAX_QUEUE notify conveys that the peer is unwilling to create more
   additional Child SAs for this particular Traffic Selector set.

   Using multiple identical Child SAs has the benefit that each stream
   has its own Sequence Number Counter, ensuring that CPUs don&#x27;t have to
   synchronize their crypto state or disable their packet replay
   protection.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-pwouters-ipsecme-multi-sa-performance-05" />
   
</reference>
