Layer 2 Relay Agent Information
draft-ietf-dhc-l2ra-06
| Document | Type | Expired Internet-Draft (dhc WG) | |
|---|---|---|---|
| Last updated | 2012-07-30 (latest revision 2012-01-25) | ||
| Replaces | draft-joshi-dhc-l2ra | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-dhc-l2ra-06.txt
Abstract
In some networks, DHCP servers rely on Relay Agent Information option appended by Relay Agents for IP address and other parameter assignment policies. This works fine when end hosts are directly connected to Relay Agents. In some network configurations, one or more Layer 2 devices may reside between DHCP clients and Relay agent. In these network scenarios, it is difficult to use the Relay Agent Information option for IP address and other parameter assignment policies effectively. So there is a need for the device that is closest to the end hosts to append a Relay Agent Information option in DHCP messages. These devices are typically known as Layer 2 Relay Agents. This document aims to describe the network scenarios where a Layer 2 Relay Agent is in use and also how it handles DHCP messages.
Authors
Bharat Joshi
(bharat_joshi@infosys.com)
Pavan Kurapati
(kurapati@juniper.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)