Security of Messages Exchanged Between Servers and Relay Agents
draft-volz-dhc-relay-server-security-02
| Document | Type | Replaced Internet-Draft (candidate for dhc WG) | |
|---|---|---|---|
| Last updated | 2016-09-14 (latest revision 2016-09-08) | ||
| Replaced by | draft-ietf-dhc-relay-server-security | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | WG state | Call For Adoption By WG Issued | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-dhc-relay-server-security | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-volz-dhc-relay-server-security-02.txt
Abstract
The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) has no guidance for how to secure messages exchanged between servers and relay agents. The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) states that IPsec should be used to secure messages exchanged between servers and relay agents, but does not recommend encryption. And, with recent concerns about pervasive monitoring it is appropriate to provide recommendations for DHCPv4 and also improve the recommendations for DHCPv6. This document updates RFC1542 and RFC3315.
Authors
Bernie Volz
(volz@cisco.com)
Yogendra Pal
(yogpal@cisco.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)