draft-ietf-6man-default-iids-07.txt   draft-ietf-6man-default-iids-08.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, 3315, 3572, Cisco
4338, 4391, 4944, 5072, 5121 D. Thaler 4291, 4338, 4391, 4944, 5072, D. Thaler
(if approved) Microsoft 5121 (if approved) Microsoft
Intended status: Standards Track W. Liu Intended status: Standards Track W. Liu
Expires: February 20, 2016 Huawei Technologies Expires: April 16, 2016 Huawei Technologies
August 19, 2015 October 14, 2015
Recommendation on Stable IPv6 Interface Identifiers Recommendation on Stable IPv6 Interface Identifiers
draft-ietf-6man-default-iids-07 draft-ietf-6man-default-iids-08
Abstract Abstract
The IPv6 addressing architecture defines Modified EUI-64 format This document changes the recommended default Interface Identifier
Interface Identifiers, and the existing IPv6 over various link-layers generation scheme for SLAAC to that specified in RFC7217, and
specify how such identifiers are derived from the underlying link- recommends against embedding link-layer addresses in IPv6 Interface
layer address (e.g., an IEEE LAN MAC address) when employing IPv6 Identifiers. It formally updates RFC2464, RFC2467, RFC2470, RFC2491,
Stateless Address Autoconfiguration (SLAAC). The security and RFC2492, RFC2497, RFC2590, RFC3146, RFC3572, RFC4291, RFC4338,
privacy implications of embedding link-layer addresses in the RFC4391, RFC4944, RFC5072, and RFC5121, which require IPv6 Interface
Interface Identifier have been known and understood for some time Identifiers to be derived from the underlying link-layer address.
now, and some popular IPv6 implementations have already deviated from Additionally, this document provides advice about the generation of
such schemes to mitigate these issues. This document changes the Interface Identifiers with Dynamic Host Configuration Protocol
recommended default Interface Identifier generation scheme for SLAAC version 6 (DHCPv6) (thus updating RFC3315) and manual configuration.
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, RFC4944, 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
other address configuration mechanisms, such as Dynamic Host
Configuration Protocol version 6 (DHCPv6) and manual configuration.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 February 20, 2016. This Internet-Draft will expire on April 16, 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Generation of IPv6 Interface Identifiers with SLAAC . . . . . 4 3. Generation of IPv6 Interface Identifiers with SLAAC . . . . . 3
4. Generation of IPv6 Interface Identifiers with DHCPv6 . . . . 4 4. Generation of IPv6 Interface Identifiers with DHCPv6 . . . . 4
5. Generation of IPv6 Interface Identifiers with Manual 5. Generation of IPv6 Interface Identifiers with Manual
Configuration . . . . . . . . . . . . . . . . . . . . . . . . 5 Configuration . . . . . . . . . . . . . . . . . . . . . . . . 5
6. Future Work . . . . . . . . . . . . . . . . . . . . . . . . . 5 6. Future Work . . . . . . . . . . . . . . . . . . . . . . . . . 5
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
8. Security Considerations . . . . . . . . . . . . . . . . . . . 5 8. Security Considerations . . . . . . . . . . . . . . . . . . . 5
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
10.1. Normative References . . . . . . . . . . . . . . . . . . 6 10.1. Normative References . . . . . . . . . . . . . . . . . . 6
10.2. Informative References . . . . . . . . . . . . . . . . . 8 10.2. Informative References . . . . . . . . . . . . . . . . . 8
skipping to change at page 4, line 22 skipping to change at page 4, line 16
security and privacy considerations discussed in Section 1. The security and privacy considerations discussed in Section 1. The
choice of whether to enable privacy or not SHOULD be configurable in choice of whether to enable privacy or not SHOULD be configurable in
such a case. such a case.
By default, nodes SHOULD NOT employ IPv6 address generation schemes By default, nodes SHOULD NOT employ IPv6 address generation schemes
that embed the underlying link-layer address in the IID. In that embed the underlying link-layer address in the IID. In
particular, this document RECOMMENDS that nodes do not generate IIDs particular, this document RECOMMENDS that nodes do not generate IIDs
with the schemes specified in [RFC2464], [RFC2467], [RFC2470], with the schemes specified in [RFC2464], [RFC2467], [RFC2470],
[RFC2491], [RFC2492], [RFC2497], [RFC2590], [RFC3146], [RFC3572], [RFC2491], [RFC2492], [RFC2497], [RFC2590], [RFC3146], [RFC3572],
[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. The
recommendations in this document override any other recommendations
on the generation of IIDs in the updated RFCs.
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.
Future specifications SHOULD NOT specify IPv6 address generation Future specifications SHOULD NOT specify IPv6 address generation
schemes that embed the underlying link-layer address in the IID. In schemes that embed the underlying link-layer address in the IID. In
skipping to change at page 5, line 18 skipping to change at page 5, line 18
of predictable Interface Identifiers of predictable Interface Identifiers
[I-D.ietf-6man-ipv6-address-generation-privacy], and avoid the use of [I-D.ietf-6man-ipv6-address-generation-privacy], and avoid the use of
predictable addresses when the aforementioned issues are of concern. predictable addresses when the aforementioned issues are of concern.
6. Future Work 6. Future Work
At the time of this writing, the mechanisms specified in the At the time of this writing, the mechanisms specified in the
following documents might require updates to be fully compatible with following documents might require updates to be fully compatible with
the recommendations in this document: the recommendations in this document:
o RFC 6282 [RFC6282] o "Compression Format for IPv6 Datagrams over IEEE 802.15.4-Based
Networks" [RFC6282]
o RFC 4944 [RFC4944] o "Transmission of IPv6 Packets over IEEE 802.15.4 Networks"
[RFC4944]
o RFC 6775 [RFC6775] o "Neighbor Discovery Optimization for IPv6 over Low-Power Wireless
Personal Area Networks (6LoWPANs)"[RFC6775]
Future revisions or updates of these documents should take the issues Future revisions or updates of these documents should take the issues
of privacy and security mentioned in Section 1 and explain any design of privacy and security mentioned in Section 1 and explain any design
and engineering considerations that lead to the use of IIDs based on and engineering considerations that lead to the use of IIDs based on
a node's link-layer address. a node's link-layer address.
7. IANA Considerations 7. IANA Considerations
There are no IANA registries within this document. The RFC-Editor There are no IANA registries within this document. The RFC-Editor
can remove this section before publication of this document as an can remove this section before publication of this document as an
RFC. RFC.
8. Security Considerations 8. Security Considerations
This document recommends [RFC7217] as the default scheme for This recommends against the (default) use of predictable Interface
generating IPv6 stable addresses with SLAAC, such that the security Identifiers in IPv6 addresses. It recommends [RFC7217] as the
and privacy issues of IIDs that embed link-layer addresses are default scheme for generating IPv6 stable addresses with SLAAC, such
mitigated. that the security and privacy issues of IIDs that embed link-layer
addresses are mitigated, and recommends against predictable IIDs in
DHCPv6 and manual configuration
9. Acknowledgements 9. Acknowledgements
The authors would like to thank Erik Nordmark and Ray Hunter for The authors would like to thank Erik Nordmark and Ray Hunter for
providing a detailed review of this document. providing a detailed review of this document.
The authors would like to thank (in alphabetical order) Fred Baker, The authors would like to thank (in alphabetical order) Fred Baker,
Carsten Bormann, Scott Brim, Brian Carpenter, Samita Chakrabarti, Tim Carsten Bormann, Scott Brim, Brian Carpenter, Samita Chakrabarti, Tim
Chown, Lorenzo Colitti, Jean-Michel Combes, Greg Daley, Esko Dijk, Chown, Lorenzo Colitti, Jean-Michel Combes, Greg Daley, Esko Dijk,
Ralph Droms, David Farmer, Brian Haberman, Ulrich Herberg, Bob Ralph Droms, David Farmer, Brian Haberman, Ulrich Herberg, Bob
skipping to change at page 9, line 17 skipping to change at page 9, line 27
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-07 (work draft-ietf-6man-ipv6-address-generation-privacy-08 (work
in progress), June 2015. in progress), September 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. 12 change blocks. 
37 lines changed or deleted 35 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/