draft-ietf-6man-default-iids-05.txt   draft-ietf-6man-default-iids-06.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: January 7, 2016 Huawei Technologies Expires: February 20, 2016 Huawei Technologies
July 6, 2015 August 19, 2015
Recommendation on Stable IPv6 Interface Identifiers Recommendation on Stable IPv6 Interface Identifiers
draft-ietf-6man-default-iids-05 draft-ietf-6man-default-iids-06
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 January 7, 2016. This Internet-Draft will expire on February 20, 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 2, line 31 skipping to change at page 2, line 31
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 . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . 7 10.2. Informative References . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
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
address). address).
skipping to change at page 4, line 32 skipping to change at page 4, line 32
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.
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. schemes that embed the underlying link-layer address in the IID. In
some cases, embedding the link-layer address in the IID may reduce
resource requirements such as energy, bandwidth and number of frames
to carry a given IPv6 packet by facilitating header compression in
constrained devices. In such cases, future specifications MAY
include IPv6 address generation schemes that embed the link-layer
address in the IID, but MUST also specify an alternative IPv6 address
generation scheme that provides mitigation of the security and
privacy implications discussed in Section 1.
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 5, line 44 skipping to change at page 5, line 51
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
Hinden, Jahangir Hossain, Jonathan Hui, Ray Hunter, Sheng Jiang, Hinden, Philip Homburg, Jahangir Hossain, Jonathan Hui, Christian
Roger Jorgensen, Dan Luedtke, Kerry Lynn, George Mitchel, Erik Huitema, Ray Hunter, Sheng Jiang, Roger Jorgensen, Dan Luedtke, Kerry
Nordmark, Simon Perreault, Tom Petch, Alexandru Petrescu, Michael Lynn, George Mitchel, Gabriel Montenegro, Erik Nordmark, Simon
Richardson, Arturo Servin, Mark Smith, Tom Taylor, Ole Troan, Tina Perreault, Tom Petch, Alexandru Petrescu, Michael Richardson, Arturo
Tsou, Glen Turner, Randy Turner, and James Woodyatt, for providing Servin, Mark Smith, Tom Taylor, Ole Troan, Tina Tsou, Glen Turner,
valuable comments on earlier versions of this document. Randy Turner, and James Woodyatt, for providing valuable comments on
earlier versions of this document.
10. References 10. References
10.1. Normative References 10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, December 1998. (IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460,
December 1998, <http://www.rfc-editor.org/info/rfc2460>.
[RFC2464] Crawford, M., "Transmission of IPv6 Packets over Ethernet [RFC2464] Crawford, M., "Transmission of IPv6 Packets over Ethernet
Networks", RFC 2464, December 1998. Networks", RFC 2464, DOI 10.17487/RFC2464, December 1998,
<http://www.rfc-editor.org/info/rfc2464>.
[RFC2467] Crawford, M., "Transmission of IPv6 Packets over FDDI [RFC2467] Crawford, M., "Transmission of IPv6 Packets over FDDI
Networks", RFC 2467, December 1998. Networks", RFC 2467, DOI 10.17487/RFC2467, December 1998,
<http://www.rfc-editor.org/info/rfc2467>.
[RFC2470] Crawford, M., Narten, T., and S. Thomas, "Transmission of [RFC2470] Crawford, M., Narten, T., and S. Thomas, "Transmission of
IPv6 Packets over Token Ring Networks", RFC 2470, December IPv6 Packets over Token Ring Networks", RFC 2470,
1998. DOI 10.17487/RFC2470, December 1998,
<http://www.rfc-editor.org/info/rfc2470>.
[RFC2492] Armitage, G., Schulter, P., and M. Jork, "IPv6 over ATM [RFC2492] Armitage, G., Schulter, P., and M. Jork, "IPv6 over ATM
Networks", RFC 2492, January 1999. Networks", RFC 2492, DOI 10.17487/RFC2492, January 1999,
<http://www.rfc-editor.org/info/rfc2492>.
[RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., [RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins,
and M. Carney, "Dynamic Host Configuration Protocol for C., and M. Carney, "Dynamic Host Configuration Protocol
IPv6 (DHCPv6)", RFC 3315, July 2003. for IPv6 (DHCPv6)", RFC 3315, DOI 10.17487/RFC3315, July
2003, <http://www.rfc-editor.org/info/rfc3315>.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006. Architecture", RFC 4291, DOI 10.17487/RFC4291, February
2006, <http://www.rfc-editor.org/info/rfc4291>.
[RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless [RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless
Address Autoconfiguration", RFC 4862, September 2007. Address Autoconfiguration", RFC 4862,
DOI 10.17487/RFC4862, September 2007,
<http://www.rfc-editor.org/info/rfc4862>.
[RFC7217] Gont, F., "A Method for Generating Semantically Opaque [RFC7217] Gont, F., "A Method for Generating Semantically Opaque
Interface Identifiers with IPv6 Stateless Address Interface Identifiers with IPv6 Stateless Address
Autoconfiguration (SLAAC)", RFC 7217, April 2014. Autoconfiguration (SLAAC)", RFC 7217,
DOI 10.17487/RFC7217, April 2014,
<http://www.rfc-editor.org/info/rfc7217>.
[RFC2491] Armitage, G., Schulter, P., Jork, M., and G. Harter, "IPv6 [RFC2491] Armitage, G., Schulter, P., Jork, M., and G. Harter, "IPv6
over Non-Broadcast Multiple Access (NBMA) networks", RFC over Non-Broadcast Multiple Access (NBMA) networks",
2491, January 1999. RFC 2491, DOI 10.17487/RFC2491, January 1999,
<http://www.rfc-editor.org/info/rfc2491>.
[RFC2497] Souvatzis, I., "Transmission of IPv6 Packets over ARCnet [RFC2497] Souvatzis, I., "Transmission of IPv6 Packets over ARCnet
Networks", RFC 2497, January 1999. Networks", RFC 2497, DOI 10.17487/RFC2497, January 1999,
<http://www.rfc-editor.org/info/rfc2497>.
[RFC2590] Conta, A., Malis, A., and M. Mueller, "Transmission of [RFC2590] Conta, A., Malis, A., and M. Mueller, "Transmission of
IPv6 Packets over Frame Relay Networks Specification", RFC IPv6 Packets over Frame Relay Networks Specification",
2590, May 1999. RFC 2590, DOI 10.17487/RFC2590, May 1999,
<http://www.rfc-editor.org/info/rfc2590>.
[RFC3146] Fujisawa, K. and A. Onoe, "Transmission of IPv6 Packets [RFC3146] Fujisawa, K. and A. Onoe, "Transmission of IPv6 Packets
over IEEE 1394 Networks", RFC 3146, October 2001. over IEEE 1394 Networks", RFC 3146, DOI 10.17487/RFC3146,
October 2001, <http://www.rfc-editor.org/info/rfc3146>.
[RFC3572] Ogura, T., Maruyama, M., and T. Yoshida, "Internet [RFC3572] Ogura, T., Maruyama, M., and T. Yoshida, "Internet
Protocol Version 6 over MAPOS (Multiple Access Protocol Protocol Version 6 over MAPOS (Multiple Access Protocol
Over SONET/SDH)", RFC 3572, July 2003. Over SONET/SDH)", RFC 3572, DOI 10.17487/RFC3572, July
2003, <http://www.rfc-editor.org/info/rfc3572>.
[RFC4338] DeSanti, C., Carlson, C., and R. Nixon, "Transmission of [RFC4338] DeSanti, C., Carlson, C., and R. Nixon, "Transmission of
IPv6, IPv4, and Address Resolution Protocol (ARP) Packets IPv6, IPv4, and Address Resolution Protocol (ARP) Packets
over Fibre Channel", RFC 4338, January 2006. over Fibre Channel", RFC 4338, DOI 10.17487/RFC4338,
January 2006, <http://www.rfc-editor.org/info/rfc4338>.
[RFC4391] Chu, J. and V. Kashyap, "Transmission of IP over [RFC4391] Chu, J. and V. Kashyap, "Transmission of IP over
InfiniBand (IPoIB)", RFC 4391, April 2006. InfiniBand (IPoIB)", RFC 4391, DOI 10.17487/RFC4391, April
2006, <http://www.rfc-editor.org/info/rfc4391>.
[RFC4944] Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler, [RFC4944] Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler,
"Transmission of IPv6 Packets over IEEE 802.15.4 "Transmission of IPv6 Packets over IEEE 802.15.4
Networks", RFC 4944, September 2007. Networks", RFC 4944, DOI 10.17487/RFC4944, September 2007,
<http://www.rfc-editor.org/info/rfc4944>.
[RFC5121] Patil, B., Xia, F., Sarikaya, B., Choi, JH., and S. [RFC5121] Patil, B., Xia, F., Sarikaya, B., Choi, JH., and S.
Madanapalli, "Transmission of IPv6 via the IPv6 Madanapalli, "Transmission of IPv6 via the IPv6
Convergence Sublayer over IEEE 802.16 Networks", RFC 5121, Convergence Sublayer over IEEE 802.16 Networks", RFC 5121,
February 2008. DOI 10.17487/RFC5121, February 2008,
<http://www.rfc-editor.org/info/rfc5121>.
[RFC5072] Varada, S., Haskins, D., and E. Allen, "IP Version 6 over [RFC5072] Varada, S., Ed., Haskins, D., and E. Allen, "IP Version 6
PPP", RFC 5072, September 2007. over PPP", RFC 5072, DOI 10.17487/RFC5072, September 2007,
<http://www.rfc-editor.org/info/rfc5072>.
[RFC5453] Krishnan, S., "Reserved IPv6 Interface Identifiers", RFC [RFC5453] Krishnan, S., "Reserved IPv6 Interface Identifiers",
5453, February 2009. RFC 5453, DOI 10.17487/RFC5453, February 2009,
<http://www.rfc-editor.org/info/rfc5453>.
[RFC6282] Hui, J. and P. Thubert, "Compression Format for IPv6 [RFC6282] Hui, J., Ed. and P. Thubert, "Compression Format for IPv6
Datagrams over IEEE 802.15.4-Based Networks", RFC 6282, Datagrams over IEEE 802.15.4-Based Networks", RFC 6282,
September 2011. DOI 10.17487/RFC6282, September 2011,
<http://www.rfc-editor.org/info/rfc6282>.
[RFC6775] Shelby, Z., Chakrabarti, S., Nordmark, E., and C. Bormann, [RFC6775] Shelby, Z., Ed., Chakrabarti, S., Nordmark, E., and C.
"Neighbor Discovery Optimization for IPv6 over Low-Power Bormann, "Neighbor Discovery Optimization for IPv6 over
Wireless Personal Area Networks (6LoWPANs)", RFC 6775, Low-Power Wireless Personal Area Networks (6LoWPANs)",
November 2012. RFC 6775, DOI 10.17487/RFC6775, November 2012,
<http://www.rfc-editor.org/info/rfc6775>.
10.2. Informative References 10.2. Informative References
[IEEE-802] [IEEE-802]
IEEE, "802-2014 - IEEE Standard for Local and Metropolitan IEEE, "802-2014 - IEEE Standard for Local and Metropolitan
Area Networks: Overview and Architecture", 2014, Area Networks: Overview and Architecture", 2014,
<https://standards.ieee.org/findstds/ <https://standards.ieee.org/findstds/
standard/802-2014.html>. standard/802-2014.html>.
[IEEE-802.3] [IEEE-802.3]
skipping to change at page 8, line 43 skipping to change at page 9, line 28
in progress), June 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,
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. 33 change blocks. 
49 lines changed or deleted 85 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/