An Authentication-only Profile for ESP with an IP Protocol Identifier
draft-hoffman-esp-null-protocol-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Paul Hoffman , David McGrew | ||
| Last updated | 2007-08-24 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-hoffman-esp-null-protocol-00.txt
Abstract
It is desirable to allow firewalls and intrusion detection systems to be able to inspect the payload of an ESP packet that has been encrypted with the NULL cipher. This would allow a firewall to read the contents and apply the normal policies to it. However, a device in the network cannot reliably determine which ESP packets are NULL encrypted, and cannot easily determine other ESP format parameters such as the ICV length. These issues can cause misclassification of packets and wasted computational resources. This document solves this problem by defining an authentication-only profile of ESP and reserving IP protocol numbers for it.
Authors
Paul Hoffman
(paul.hoffman@vpnc.org)
David McGrew
(mcgrew@cisco.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)