DHCPv6 Redundancy Deployment Considerations
draft-jjmb-dhc-dhcpv6-redundancy-consider-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | John Jason Brzozowski , Jean-Francois Tremblay , Jack Chen , Tomek Mrugalski | ||
| Last updated | 2013-02-19 (Latest revision 2010-07-12) | ||
| Replaced by | draft-ietf-dhc-dhcpv6-redundancy-consider | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-dhc-dhcpv6-redundancy-consider | |
| 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
This document documents some deployment considerations for those who wishing to use DHCPv6 to support their deployment of IPv6. Specifically, providing semi-redundant DHCPv6 services is discussed in this document.
Authors
John Jason Brzozowski
Jean-Francois Tremblay
Jack Chen
Tomek Mrugalski
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)