Minimal ESP
draft-mglt-lwig-minimal-esp-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Daniel Migault , Tobias Guggemos , Daniel Palomares | ||
| Last updated | 2015-01-03 (Latest revision 2014-07-02) | ||
| Replaced by | draft-ietf-lwig-minimal-esp, draft-ietf-lwig-minimal-esp, RFC 9333 | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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 describes a minimal version of the IP Encapsulation Security Payload (ESP) described in RFC 4303 which is part of the IPsec suite. ESP is used to provide confidentiality, data origin authentication, connectionless integrity, an anti-replay service (a form of partial sequence integrity), and limited traffic flow confidentiality. This document does not update or modify RFC 4303, but provides a compact description of 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
Daniel Palomares
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)