DHCPv4 Relay Agent Flags Suboption
draft-kinnear-dhc-relay-agent-flags-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Kim Kinnear | ||
| Last updated | 2008-03-03 (Latest revision 2006-06-08) | ||
| Replaced by | draft-ietf-dhc-relay-agent-flags | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-dhc-relay-agent-flags | |
| 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 memo defines a new suboption of the DHCP relay agent information option that allows the DHCP relay to specify flags for the forwarded packet. One flag is defined to indicate whether the DHCP relay received the packet via a unicast or broadcast packet. This information may be used by the DHCP server to better serve clients based on whether their request was originally broadcast or unicast.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)