IPv6 CE Device DHCPv6 Option Transparency
draft-smith-v6ops-ce-dhcpv6-transparency-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Mark Smith | ||
| Last updated | 2014-01-31 (Latest revision 2013-07-30) | ||
| 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
[RFC6204] defines basic requirements for IPv6 Customer Edge Routers, to suit residential or small office IPv6 deployments. It describes a WAN interface DHCPv6 client and LAN interface DHCPv6 server implementation model. This model constrains the set of DHCPv6 options that can be conveyed between the upstream service provider and the hosts downstream of the CE device, to those supported by both the CE device's DHCPv6 client and server. To support further current and future DHCPv6 options, this memo instead proposes a DHCPv6 option "transparent" implementation model for CE devices, primarily using DHCPv6 message relaying.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)