Layer 2 Relay Agent
draft-joshi-dhc-layer2-relay-agent-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Bharat Joshi | ||
| Last updated | 2007-06-15 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| 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) |
https://www.ietf.org/archive/id/draft-joshi-dhc-layer2-relay-agent-01.txt
Abstract
In Layer 2 Access Networks, Access Concentrators are present between DHCP Clients and Relay Agent. In this case, the Relay Agent can not uniquely identify the end host and hence can not add unique 'Relay Agent Information' option corresponding to the end hosts in DHCP messages. As the Access concentrators are closer to the end hosts, they can uniquely identify the end hosts and add the Relay Agent Information option in the DHCP message. Access concentrators do not set the 'giaddr' field. Access Concentrators in this mode are typically known as Layer 2 Relay agents. This document provides insight to the behavior of the Access Concentrators which act as DHCP Layer 2 Relay Agents in Access Networks.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)