A Bound End-to-End Tunnel (BEET) mode for ESP
draft-antony-ipsecme-beet-mode-00
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Antony Antony , Steffen Klassert | ||
Last updated | 2023-10-23 | ||
Replaced by | draft-antony-ipsecme-iekv2-beet-mode | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-antony-ipsecme-iekv2-beet-mode | |
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
This document specifies a new mode for IPsec ESP, known as Bound End- to-End Tunnel (BEET) mode. This mode complements the existing ESP tunnel and transport modes, while enhancing end-to-end IPsec usage. It offers the characteristics of the tunnel mode but without its usual overhead. The BEET mode is designed to accommodate evolving applications of ESP, such as minimalist end-to-end tunnel, mobility and multi-address multi-homing. Additionally, this document proposes a new Notify Message, USE_BEET_MODE, for the Internet Key Exchange Protocol Version 2 (IKEv2) specified in [RFC7296], to facilitate BEET mode Security Association negotiation.
Authors
Antony Antony
Steffen Klassert
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)