Deprecating EUI-64 Based IPv6 Addresses
draft-gont-6man-deprecate-eui64-based-addresses-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2014-04-24 (latest revision 2013-10-21) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-gont-6man-deprecate-eui64-based-addresses-00.txt
Abstract
Stateless Address Autoconfiguration (SLAAC) for IPv6 typically results in hosts configuring one or more stable addresses composed of a network prefix advertised by a local router, and an Interface Identifier that typically embeds a hardware address (e.g., an IEEE LAN MAC address). The security and privacy implications of embedding hardware addresses in the Interface Identifier have been known and understood for some time now, and some popular IPv6 implementations have already deviated from such scheme to mitigate these issues. This document deprecates the use of hardware addresses in IPv6 Interface Identifiers, and recommends the use of an alternative scheme ([I-D.ietf-6man-stable-privacy-addresses]) for the generation of IPv6 stable addresses.
Authors
Fernando Gont
(fgont@si6networks.com)
Alissa Cooper
(acooper@cdt.org)
Dave Thaler
(dthaler@microsoft.com)
Will LIU
(liushucheng@huawei.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)