DNS Delete-Confirm Mechanism with Multi-DHCP-Servers
draft-que-dhc-dns-multi-dhcp-servers-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Xirong Que , Wenhong Wang , Lanshan Zhang , Linhui Sun | ||
| Last updated | 2015-10-17 (Latest revision 2015-04-15) | ||
| 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
[I-D.ietf-dhc-addr-registration] specifies how a host register its self-generated addresses in DNS through DHCPv6 server. [RFC3315] allows multiple DHCPv6 servers working in an administrative domain. There exists a scenario that the client may register its addresses in multiple servers for some reasons such as higher availability and etc. This document defines a mechanism to ensure the multiple servers could work properly during updating DNS.
Authors
Xirong Que
Wenhong Wang
Lanshan Zhang
Linhui Sun
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)