ND Support to trigger the nodes refresh the other configuration
draft-vijay-ipv6-icmp-refresh-otherconf-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | a Vijayabhaskar | ||
| Last updated | 2003-11-25 | ||
| 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
Neighbor Discovery for IPv6 [RFC2461] provides a way by which the nodes can determine whether to use administered protocol for address autoconfiguration and other non-address information through M and O bits in the Router Advertisements. Though RAs can notify nodes of a change in the address prefixes, currently there is no way the nodes can learn that there is a change in the non-address configuration parameters. This will make the nodes unable to learn about new or changed configuration parameters like DNS server addresses. This specification extends the Neighbor Discovery protocol [RFC2461] to notify the nodes that the other information obtained through an administered protocol has been changed.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)