IPv6 DAD Enhancements for handling Layer1 Loopbacks
draft-asati-v6ops-dad-loopback-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Rajiv Asati , Eli Dart | ||
| Last updated | 2012-04-06 (Latest revision 2011-10-04) | ||
| 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
It is a common practice to install a (soft or hard) loopback on a circuit interface for various purposes (e.g. circuit turn-up test). However, this practice results in disabling IPv6 on an interface even after the loopback is removed, due to the way IPv6 duplicate address detection is performed. This document describes a mechanism to allow IPv6 to self-heal after such a loopback is placed & removed.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)