Interoperability Problems of StateLess Address Auto-Configuration (SLAAC) Arising from Duplicate Link-layer Addresses
draft-gont-v6ops-slaac-issues-with-duplicate-macs-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Fernando Gont | ||
| Last updated | 2013-04-18 (Latest revision 2012-10-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
Traditional Stateless Address Auto-Configuration (SLAAC) typically involves producing a Modified-EU64 format identifier to be employed as the Interface-ID of the resulting address. In the case of Ethernet network interface cards, such identifier derived from the corresponding IEEE 802 address. IEEE 802 addresses are generally expected to be globally unique, thus resulting in non-duplicate addresses. However, in many real-world scenarios, these identifiers fail to be unique, thus resulting in duplicate IPv6 addresses. This document discusses the interoperability problems arising from duplicate IEEE 802 addresses with IPv6 Stateless Address Auto- Configuration (SLAAC), and how some popular implementations react when the such problems arise. Finally, it discusses possible mitigations for the aforementioned issue.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)