Use of IPsec for Securing DHCPv4 Messages Exchanged Between Relay Agents and Servers
draft-droms-dhcp-relay-agent-ipsec-00
This document is an Internet-Draft (I-D).
Anyone may submit an I-D to the IETF.
This I-D is not endorsed by the IETF and has no formal standing in the
IETF standards process.
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Ralph Droms | ||
| Last updated | 2002-10-25 | ||
| RFC stream | (None) | ||
| Intended RFC status | (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
'DHCP Relay Agent Information Option' (RFC 3046) assumes that DHCP messages exchanged between relay agents and servers are not subject to attack. This document describes how IPsec can be used to protect messages exchanged between relay agents and servers.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)