Problem Statement for DHCP Relay Agent
draft-huang-dhc-relay-ps-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Lu Huang , DENG Hui , Pavan Kurapati , Bharat Joshi | ||
| Last updated | 2009-07-05 | ||
| 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
RFC 3046 allows only the first Relay Agent to append Relay Agent Information option. In some networks, Layer 2 Relay Agents and Layer 3 Relay Agents are deployed but only Layer 2 Relay Agent appends the Relay Agent Information option. This document describes two pretty common network scenarios that uses Layer 2 and Layer 3 Relay Agents and their unique requirements where either DHCP server or Relay Agent need more information to handle DHCP messages.
Authors
Lu Huang
DENG Hui
Pavan Kurapati
Bharat Joshi
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)