Minimal ESP
draft-ietf-lwig-minimal-esp-00
| Document | Type | Expired Internet-Draft (lwig WG) | |
|---|---|---|---|
| Authors | Daniel Migault , Tobias Guggemos | ||
| Last updated | 2019-10-09 (Latest revision 2019-04-07) | ||
| Replaces | draft-mglt-lwig-minimal-esp | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
| Reviews |
TSVART Last Call review
(of
-06)
On the Right Track
GENART Last Call review
(of
-04)
Ready with Issues
SECDIR Last Call review
(of
-03)
Has Nits
IOTDIR Last Call review
(of
-03)
Ready with Issues
OPSDIR Last Call Review
Incomplete, due 2021-08-26
|
||
| Stream | WG state | WG Document | |
| Associated WG milestone |
|
||
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-ietf-lwig-minimal-esp-00.txt
Abstract
This document describes a minimal implementation of the IP Encapsulation Security Payload (ESP) defined in RFC 4303. Its purpose is to enable implementation of ESP with a minimal set of options to remain compatible with ESP as described in RFC 4303. A minimal version of ESP is not intended to become a replacement of the RFC 4303 ESP, but instead to enable a limited implementation to interoperate with implementations of RFC 4303 ESP. This document describes what is required from RFC 4303 ESP as well as various ways to optimize compliance with RFC 4303 ESP. This document does not update or modify RFC 4303, but provides a compact description of how to implement the minimal version of the protocol. If this document and RFC 4303 conflicts then RFC 4303 is the authoritative description.
Authors
Daniel Migault
Tobias Guggemos
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)