DNS update for MIPv6
draft-yan-mext-dnsmip-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jong-Hyouk Lee , Zhiwei Yan | ||
| Last updated | 2012-04-26 (Latest revision 2011-10-24) | ||
| 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
In order to update the DNS (Domain Name System)[1] resource records (RRs) for the node when its name or address changes, the DDNS (Dynamic DNS) protocol[2] has been standardized as an extension of basic DNS protocol. Then the security DDNS scheme[3] was proposed to enhance the security of DDNS. Based on these two protocols, the DNS update can be used in many scenarios, for example in the DHCP (Dynamic Host Configuration Protocol)[4] deployed environment. Based on these specifications, this document defines the extension in MIPv6 (Mobile IPv6)[5] to achieve DNS update for the named MN (Mobile Node). Specifically speaking, the FQND Option defined in the RFC4704[6] is included in the MIPv6 BU (Binding Update) signaling message. Then the PTR RR or AAAA and PTR RRs may be updated by the HA (Home Agent) when the HoA (Home Address) or name of MN changes.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)