I think it would be sufficient to include a paragraph that mentions that this solution can introduce packet reordering and variable delays and that packet scheduling/load-balancing implementations should take this into consideration. Without going into details on how to solve it. Marcus -----Original Message----- From: Paul Wouters <paul@xxxxxxxxx> Sent: Friday, 12 April 2024 17:00 To: Marcus Ihlar <marcus.ihlar@xxxxxxxxxxxx> Cc: tsv-art@xxxxxxxx; draft-ietf-ipsecme-multi-sa-performance.all@xxxxxxxx; ipsec@xxxxxxxx; last-call@xxxxxxxx Subject: Re: [Last-Call] Tsvart last call review of draft-ietf-ipsecme-multi-sa-performance-06 On Wed, 10 Apr 2024, Marcus Ihlar via Datatracker wrote: Thanks for your review. > Load balancing algorithms and policies are likely best left as > implementation details but I do think a paragraph in the operational > considerations section could be warranted. We had some Linux details in there before but were asked to remove those and some people wouldn't implement it similarly. So I am not sure what you would want to add in the operational considerations section. Paul -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
