Recommendation on Stable IPv6 Interface Identifiers
draft-ietf-6man-default-iids-09
The information below is for an old version of the document | |||||
---|---|---|---|---|---|
Document | Type | None Internet-Draft (6man WG) | |||
Last updated | 2016-01-25 | ||||
Stream | IETF | ||||
Intended RFC status | Proposed Standard | ||||
Formats |
Expired & archived
pdf
htmlized
bibtex
|
||||
Reviews | |||||
Additional URLs |
|
||||
Stream | WG state | (None) | |||
Document shepherd | No shepherd assigned | ||||
IESG | IESG state | Unknown state | |||
Consensus Boilerplate | Unknown | ||||
Telechat date | |||||
Responsible AD | (None) | ||||
Send notices to | (None) |
https://www.ietf.org/archive/id/draft-ietf-6man-default-iids-09.txt
Abstract
This document changes the recommended default Interface Identifier generation scheme for SLAAC to that specified in RFC7217, and recommends against embedding link-layer addresses in IPv6 Interface Identifiers. It formally updates RFC2464, RFC2467, RFC2470, RFC2491, RFC2492, RFC2497, RFC2590, RFC3146, RFC3572, RFC4291, RFC4338, RFC4391, RFC5072, and RFC5121, which require IPv6 Interface Identifiers to be derived from the underlying link-layer address. Additionally, this document provides advice about the generation of Interface Identifiers with Dynamic Host Configuration Protocol version 6 (DHCPv6) (thus updating RFC3315) and manual configuration.
Authors
Fernando Gont
(fgont@si6networks.com)
Alissa Cooper
(alcoop@cisco.com)
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.)