Faster cleanup of invalid NCE
draft-kella-6man-cache-invalid-purge-02
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Kiran Kella | ||
Last updated | 2015-07-01 (Latest revision 2014-12-28) | ||
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
When an IPv6 address is moved or removed or when it becomes invalid on an interface of an IPv6 node, the old neighbor cache entry for this address on the neighboring nodes sharing the interface link continues to be used for data forwarding till the STALE entry time- out happens or till the neighbor unreachability detection algorithm runs in order to rediscover the correct link layer address or purge the incorrect neighbor cache entry. This document specifies a mechanism for the faster removal of invalid neighbor cache entries on the neighboring nodes. This document updates RFC 4861.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)