draft-ietf-6man-default-iids-03.txt   draft-ietf-6man-default-iids-04.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: November 7, 2015 Huawei Technologies Expires: December 27, 2015 Huawei Technologies
May 6, 2015 June 25, 2015
Recommendation on Stable IPv6 Interface Identifiers Recommendation on Stable IPv6 Interface Identifiers
draft-ietf-6man-default-iids-03 draft-ietf-6man-default-iids-04
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 November 7, 2015. This Internet-Draft will expire on December 27, 2015.
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 2, line 32 skipping to change at page 2, line 32
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 . . . . . 4
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 . . . . . . . . . . . . . . . . . . . . . . . . 4 Configuration . . . . . . . . . . . . . . . . . . . . . . . . 4
6. Future Work . . . . . . . . . . . . . . . . . . . . . . . . . 4 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 . . . . . . . . . . . . . . . . . . . . . . . . . 5 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
10.1. Normative References . . . . . . . . . . . . . . . . . . 5 10.1. Normative References . . . . . . . . . . . . . . . . . . 6
10.2. Informative References . . . . . . . . . . . . . . . . . 7 10.2. Informative References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
[RFC4862] specifies Stateless Address Autoconfiguration (SLAAC) for [RFC4862] specifies Stateless Address Autoconfiguration (SLAAC) for
IPv6 [RFC2460], which typically results in hosts configuring one or IPv6 [RFC2460], which typically results in hosts configuring one or
more "stable" addresses composed of a network prefix advertised by a more "stable" addresses composed of a network prefix advertised by a
local router, and an Interface Identifier (IID) [RFC4291] that local router, and an Interface Identifier (IID) [RFC4291] that
typically embeds a link-layer address (e.g., an IEEE LAN MAC typically embeds a link-layer address (e.g., an IEEE LAN MAC
skipping to change at page 4, line 24 skipping to change at page 4, line 24
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.
Some link-layers support locally assigned link-layer addresses
[IEEE-802], such as [IEEE-802.3] and [IEEE-802.11], or random
addresses [BLUETOOTH]. Where IPv6 IIDs are to be derived from link-
layer addresses, it is RECOMMENDED that the random addresses
supported by the link-layer are used, or that pseudo-random locally
assigned link-layer addresses are generated, assigned and used.
It is RECOMMENDED by this document that future specifications do not It is RECOMMENDED by this document that future specifications do not
specify IPv6 address generation schemes that embed the underlying specify IPv6 address generation schemes that embed the underlying
link-layer address in the IID. Future specifications MAY use an 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 based on a node's link-layer address if design and engineering
considerations warrant. 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
skipping to change at page 7, line 38 skipping to change at page 7, line 45
Datagrams over IEEE 802.15.4-Based Networks", RFC 6282, Datagrams over IEEE 802.15.4-Based Networks", RFC 6282,
September 2011. September 2011.
[RFC6775] Shelby, Z., Chakrabarti, S., Nordmark, E., and C. Bormann, [RFC6775] Shelby, Z., Chakrabarti, S., Nordmark, E., and C. Bormann,
"Neighbor Discovery Optimization for IPv6 over Low-Power "Neighbor Discovery Optimization for IPv6 over Low-Power
Wireless Personal Area Networks (6LoWPANs)", RFC 6775, Wireless Personal Area Networks (6LoWPANs)", RFC 6775,
November 2012. November 2012.
10.2. Informative References 10.2. Informative References
[IEEE-802]
IEEE, "802-2014 - IEEE Standard for Local and Metropolitan
Area Networks: Overview and Architecture", 2014,
<https://standards.ieee.org/findstds/
standard/802-2014.html>.
[IEEE-802.3]
IEEE, "802.3-2012 - IEEE Standard for Ethernet", 2012,
<https://standards.ieee.org/findstds/
standard/802.3-2012.html>.
[IEEE-802.11]
IEEE, "IEEE Standard for Information technology --
Telecommunications and information exchange between
systems -- Local and metropolitan area networks --
Specific requirements -- Part 11: Wireless LAN Medium
Access Control (MAC) and Physical Layer (PHY)
Specifications", 2012,
<http://standards.ieee.org/getieee802/
download/802.11-2012.pdf>.
[BLUETOOTH]
Bluetooth SIG, "BLUETOOTH SPECIFICATION Version 4.2",
2014, <https://www.bluetooth.org/DocMan/handlers/
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-05 (work
in progress), April 2015. in progress), April 2015.
[I-D.ietf-dhc-stable-privacy-addresses] [I-D.ietf-dhc-stable-privacy-addresses]
Gont, F. and W. Will, "A Method for Generating Gont, F. and S. LIU, "A Method for Generating Semantically
Semantically Opaque Interface Identifiers with Dynamic Opaque Interface Identifiers with Dynamic Host
Host Configuration Protocol for IPv6 (DHCPv6)", draft- Configuration Protocol for IPv6 (DHCPv6)", draft-ietf-dhc-
ietf-dhc-stable-privacy-addresses-02 (work in progress), stable-privacy-addresses-02 (work in progress), April
April 2015. 2015.
[Microsoft] [Microsoft]
Davies, J., "Understanding IPv6, 3rd. ed", page 83, Davies, J., "Understanding IPv6, 3rd. ed", page 83,
Microsoft Press, 2012, <http://it-ebooks.info/book/1022/>. Microsoft Press, 2012, <http://it-ebooks.info/book/1022/>.
Authors' Addresses Authors' Addresses
Fernando Gont Fernando Gont
SI6 Networks / UTN-FRH SI6 Networks / UTN-FRH
Evaristo Carriego 2644 Evaristo Carriego 2644
Haedo, Provincia de Buenos Aires 1706 Haedo, Provincia de Buenos Aires 1706
Argentina Argentina
Phone: +54 11 4650 8472 Phone: +54 11 4650 8472
Email: fgont@si6networks.com Email: fgont@si6networks.com
URI: http://www.si6networks.com URI: http://www.si6networks.com
 End of changes. 9 change blocks. 
13 lines changed or deleted 45 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/