IP Encapsulating Security Payload (ESP)
draft-kent-ipsecme-esp-rfc4303bis-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Stephen Kent | ||
| Last updated | 2014-05-23 (Latest revision 2013-11-19) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| 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 can be found at:
https://www.ietf.org/archive/id/draft-kent-ipsecme-esp-rfc4303bis-00.txt
https://www.ietf.org/archive/id/draft-kent-ipsecme-esp-rfc4303bis-00.txt
Abstract
This document describes an updated version of the Encapsulating Security Payload (ESP) protocol, which is designed to provide a mix of security services in IPv4 and IPv6. 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 obsoletes RFC 4303.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)