draft-ietf-6man-default-iids-04.txt   draft-ietf-6man-default-iids-05.txt 
IPv6 maintenance Working Group (6man) F. Gont IPv6 maintenance Working Group (6man) F. Gont
Internet-Draft SI6 Networks / UTN-FRH Internet-Draft SI6 Networks / UTN-FRH
Updates: 2464, 2467, 2470, 2491, 2492, A. Cooper Updates: 2464, 2467, 2470, 2491, 2492, A. Cooper
2497, 2590, 3146, 3572, 4291, Cisco 2497, 2590, 3146, 3572, 4291, Cisco
4338, 4391, 4944, 5072, 5121 D. Thaler 4338, 4391, 4944, 5072, 5121 D. Thaler
(if approved) Microsoft (if approved) Microsoft
Intended status: Standards Track W. Liu Intended status: Standards Track W. Liu
Expires: December 27, 2015 Huawei Technologies Expires: January 7, 2016 Huawei Technologies
June 25, 2015 July 6, 2015
Recommendation on Stable IPv6 Interface Identifiers Recommendation on Stable IPv6 Interface Identifiers
draft-ietf-6man-default-iids-04 draft-ietf-6man-default-iids-05
Abstract Abstract
The IPv6 addressing architecture defines Modified EUI-64 format The IPv6 addressing architecture defines Modified EUI-64 format
Interface Identifiers, and the existing IPv6 over various link-layers Interface Identifiers, and the existing IPv6 over various link-layers
specify how such identifiers are derived from the underlying link- specify how such identifiers are derived from the underlying link-
layer address (e.g., an IEEE LAN MAC address) when employing IPv6 layer address (e.g., an IEEE LAN MAC address) when employing IPv6
Stateless Address Autoconfiguration (SLAAC). The security and Stateless Address Autoconfiguration (SLAAC). The security and
privacy implications of embedding link-layer addresses in the privacy implications of embedding link-layer addresses in the
Interface Identifier have been known and understood for some time Interface Identifier have been known and understood for some time
skipping to change at page 2, line 7 skipping to change at page 2, line 7
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 27, 2015. This Internet-Draft will expire on January 7, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 4, line 31 skipping to change at page 4, line 31
[RFC4338], [RFC4391], [RFC4944], [RFC5121], and [RFC5072], and [RFC4338], [RFC4391], [RFC4944], [RFC5121], and [RFC5072], and
updates these documents with this recommendation. updates these documents with this recommendation.
Some link-layers support locally assigned link-layer addresses Some link-layers support locally assigned link-layer addresses
[IEEE-802], such as [IEEE-802.3] and [IEEE-802.11], or random [IEEE-802], such as [IEEE-802.3] and [IEEE-802.11], or random
addresses [BLUETOOTH]. Where IPv6 IIDs are to be derived from link- addresses [BLUETOOTH]. Where IPv6 IIDs are to be derived from link-
layer addresses, it is RECOMMENDED that the random addresses layer addresses, it is RECOMMENDED that the random addresses
supported by the link-layer are used, or that pseudo-random locally supported by the link-layer are used, or that pseudo-random locally
assigned link-layer addresses are generated, assigned and used. assigned link-layer addresses are generated, assigned and used.
It is RECOMMENDED by this document that future specifications do not Future specifications SHOULD NOT specify IPv6 address generation
specify IPv6 address generation schemes that embed the underlying schemes that embed the underlying link-layer address in the IID.
link-layer address in the IID. Future specifications MAY use an IID
based on a node's link-layer address if design and engineering
considerations warrant.
4. Generation of IPv6 Interface Identifiers with DHCPv6 4. Generation of IPv6 Interface Identifiers with DHCPv6
By default, DHCPv6 server implementations SHOULD NOT generate By default, DHCPv6 server implementations SHOULD NOT generate
predictable IPv6 addresses (such as IPv6 addresses where the IIDs are predictable IPv6 addresses (such as IPv6 addresses where the IIDs are
consecutive small numbers). [I-D.ietf-dhc-stable-privacy-addresses] consecutive small numbers). [I-D.ietf-dhc-stable-privacy-addresses]
specifies one possible algorithm that could be employed to comply specifies one possible algorithm that could be employed to comply
with this requirement. Another possible algorithm would be to select with this requirement. Another possible algorithm would be to select
a pseudo-random value chosen from a discrete uniform distribution, a pseudo-random value chosen from a discrete uniform distribution,
while avoiding the reserved IPv6 Interface Identifiers [RFC5453] while avoiding the reserved IPv6 Interface Identifiers [RFC5453]
skipping to change at page 8, line 32 skipping to change at page 8, line 32
2014, <https://www.bluetooth.org/DocMan/handlers/ 2014, <https://www.bluetooth.org/DocMan/handlers/
DownloadDoc.ashx?doc_id=286439>. DownloadDoc.ashx?doc_id=286439>.
[IANA-RESERVED-IID] [IANA-RESERVED-IID]
IANA, "Reserved IPv6 Interface Identifiers", IANA, "Reserved IPv6 Interface Identifiers",
<http://www.iana.org/assignments/ipv6-interface-ids>. <http://www.iana.org/assignments/ipv6-interface-ids>.
[I-D.ietf-6man-ipv6-address-generation-privacy] [I-D.ietf-6man-ipv6-address-generation-privacy]
Cooper, A., Gont, F., and D. Thaler, "Privacy Cooper, A., Gont, F., and D. Thaler, "Privacy
Considerations for IPv6 Address Generation Mechanisms", Considerations for IPv6 Address Generation Mechanisms",
draft-ietf-6man-ipv6-address-generation-privacy-05 (work draft-ietf-6man-ipv6-address-generation-privacy-07 (work
in progress), April 2015. in progress), June 2015.
[I-D.ietf-dhc-stable-privacy-addresses] [I-D.ietf-dhc-stable-privacy-addresses]
Gont, F. and S. LIU, "A Method for Generating Semantically Gont, F. and S. LIU, "A Method for Generating Semantically
Opaque Interface Identifiers with Dynamic Host Opaque Interface Identifiers with Dynamic Host
Configuration Protocol for IPv6 (DHCPv6)", draft-ietf-dhc- Configuration Protocol for IPv6 (DHCPv6)", draft-ietf-dhc-
stable-privacy-addresses-02 (work in progress), April stable-privacy-addresses-02 (work in progress), April
2015. 2015.
[Microsoft] [Microsoft]
Davies, J., "Understanding IPv6, 3rd. ed", page 83, Davies, J., "Understanding IPv6, 3rd. ed", page 83,
 End of changes. 5 change blocks. 
11 lines changed or deleted 8 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/