Separate Transports for IKE and ESP
draft-smyslov-ipsecme-ikev2-reliable-transport-04
| Document | Type |
Replaced Internet-Draft
(ipsecme WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Valery Smyslov , Tirumaleswar Reddy.K | ||
| Last updated | 2025-10-05 (Latest revision 2025-04-15) | ||
| Replaced by | draft-ietf-ipsecme-ikev2-reliable-transport | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-ipsecme-ikev2-reliable-transport | |
| Consensus boilerplate | Yes | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The Internet Key Exchange protocol version 2 (IKEv2) can operate either over unreliable (UDP) transport or over reliable (TCP) transport. If TCP is used, then IPsec tunnels created by IKEv2 also use TCP. This document specifies how to decouple IKEv2 and IPsec transports so that IKEv2 can operate over TCP, while IPsec tunnels use unreliable transport. This feature allows IKEv2 to effectively exchange large blobs of data (e.g., when post-quantum algorithms are employed) while avoiding performance problems that arise when IPsec uses TCP.
Authors
Valery Smyslov
Tirumaleswar Reddy.K
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)