Hi all, While reviewing draft-ietf-ipsecme-ikev2-reliable-transport, I was thinking about the broader transport design space for IKEv2.
The current work extends IKEv2 over TCP to improve reliability for large exchanges (e.g., post-quantum key material), which is very useful and well aligned with current deployment constraints. As a potential direction for future work (not for this document), it may be worth considering whether QUIC could also serve as an alternative reliable transport for IKEv2. Compared to TCP, QUIC provides: - built-in stream multiplexing - avoidance of TCP head-of-line blocking - better behavior under NAT and loss-prone networks - integrated congestion control over UDP This is not a suggestion to change the current specification scope, but rather to highlight a possible future design option for discussion. Best regards, Wang Xi *** Please note that this message and any attachments may contain confidential and proprietary material and information and are intended only for the use of the intended recipient(s). If you are not the intended recipient, you are hereby notified that any review, use, disclosure, dissemination, distribution or copying of this message and any attachments is strictly prohibited. If you have received this email in error, please immediately notify the sender and destroy this e-mail and any attachments and all copies, whether electronic or printed. Please also note that any views, opinions, conclusions or commitments expressed in this message are those of the individual sender and do not necessarily reflect the views of Fortinet, Inc., its affiliates, and emails are not binding on Fortinet and only a writing manually signed by Fortinet's General Counsel can be a binding commitment of Fortinet to Fortinet's customers or partners. Thank you. ***
_______________________________________________ IPsec mailing list -- [email protected] To unsubscribe send an email to [email protected]
