Client Link-Layer Address Option (CLLAO) Updates
draft-templin-dhc-cllao-updates-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Fred Templin | ||
| Last updated | 2015-09-04 (Latest revision 2015-03-03) | ||
| 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
RFC6939 specifies a method for DHCPv6 relay agents to insert a Client Link Layer Address Option (CLLAO) in a DHCPv6 Relay-Forward message as informational material for the DHCPv6 server. The server in turn is not required to echo the CLLAO back in its replies. In some cases, however, the DHCPv6 client may be interested to receive the CLLAO, e.g., to determine if there are L2 devices (e.g., L2 proxies) that rewrite the link-layer address. This document discusses updates to RFC6939 to allow the server to echo the CLLAO back to the client.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)