draft-ietf-6man-default-iids-09.txt   draft-ietf-6man-default-iids-10.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, 3315, 3572, Cisco 2497, 2590, 3146, 3315, 3572, Cisco
4291, 4338, 4391, 5072, 5121 D. Thaler 4291, 4338, 4391, 5072, 5121 D. Thaler
(if approved) Microsoft (if approved) Microsoft
Intended status: Standards Track W. Liu Intended status: Standards Track W. Liu
Expires: July 28, 2016 Huawei Technologies Expires: August 20, 2016 Huawei Technologies
January 25, 2016 February 17, 2016
Recommendation on Stable IPv6 Interface Identifiers Recommendation on Stable IPv6 Interface Identifiers
draft-ietf-6man-default-iids-09 draft-ietf-6man-default-iids-10
Abstract Abstract
This document changes the recommended default Interface Identifier This document changes the default Interface Identifier generation
generation scheme for SLAAC to that specified in RFC7217, and scheme for SLAAC to that specified in RFC7217, and recommends against
recommends against embedding link-layer addresses in IPv6 Interface embedding link-layer addresses in IPv6 Interface Identifiers. It
Identifiers. It formally updates RFC2464, RFC2467, RFC2470, RFC2491, formally updates RFC2464, RFC2467, RFC2470, RFC2491, RFC2492,
RFC2492, RFC2497, RFC2590, RFC3146, RFC3572, RFC4291, RFC4338, RFC2497, RFC2590, RFC3146, RFC3572, RFC4291, RFC4338, RFC4391,
RFC4391, RFC5072, and RFC5121, which require IPv6 Interface RFC5072, and RFC5121, by removing the text in these RFCs that
Identifiers to be derived from the underlying link-layer address. required the IPv6 Interface Identifiers to be derived from the
Additionally, this document provides advice about the generation of underlying link-layer address, and replacing the aforementioned text
Interface Identifiers with Dynamic Host Configuration Protocol with a pointer to this document. Additionally, this document updates
version 6 (DHCPv6) (thus updating RFC3315) and manual configuration. RFC3315 by specifying additional requirements on the generation of
Interface Identifiers used in Dynamic Host Configuration Protocol
version 6 (DHCPv6). It also provides advice to system administrators
who employ 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 July 28, 2016. This Internet-Draft will expire on August 20, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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 3, line 19 skipping to change at page 3, line 19
o Location tracking o Location tracking
o Address scanning o Address scanning
o Device-specific vulnerability exploitation o Device-specific vulnerability exploitation
Some popular IPv6 implementations have already deviated from the Some popular IPv6 implementations have already deviated from the
traditional stable IID generation scheme to mitigate the traditional stable IID generation scheme to mitigate the
aforementioned security and privacy implications [Microsoft]. aforementioned security and privacy implications [Microsoft].
As a result of the aforementioned issues, this document recommends As a result of the aforementioned issues, this document changes the
the implementation of an alternative scheme ([RFC7217]) as the default Interface Identifier generation scheme for SLAAC to that
default stable IID generation scheme for SLAAC, such that the specified in [RFC7217], and recommends against embedding link-layer
aforementioned issues are mitigated. addresses in IPv6 Interface Identifiers, such that the aforementioned
issues are mitigated.
NOTE: [RFC4291] defines the "Modified EUI-64 format" for IIDs. NOTE: [RFC4291] defines the "Modified EUI-64 format" for IIDs.
Appendix A of [RFC4291] then describes how to transform an IEEE Appendix A of [RFC4291] then describes how to transform an IEEE
EUI-64 identifier, or an IEEE 802 48-bit MAC address from which an EUI-64 identifier, or an IEEE 802 48-bit MAC address from which an
EUI-64 identifier is derived, into an IID in the Modified EUI-64 EUI-64 identifier is derived, into an IID in the Modified EUI-64
format. format.
Finally this document provides advice about the generation of Finally this document updates [RFC3315] by specifying additional
Interface Identifiers with other address configuration mechanisms, requirements on the generation of Interface Identifiers used in
such as Dynamic Host Configuration Protocol version 6 (DHCPv6) and Dynamic Host Configuration Protocol version 6 (DHCPv6), and also
manual configuration. provides advice to system administrators who employ manual
configuration.
2. Terminology 2. Terminology
Stable address: Stable address:
An address that does not vary over time within the same network An address that does not vary over time within the same network
(as defined in [I-D.ietf-6man-ipv6-address-generation-privacy]). (as defined in [I-D.ietf-6man-ipv6-address-generation-privacy]).
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
skipping to change at page 18, line 38 skipping to change at page 18, line 38
The authors would like to thank (in alphabetical order) Bob Hinden, The authors would like to thank (in alphabetical order) Bob Hinden,
Ray Hunter and Erik Nordmark, for providing a detailed review of this Ray Hunter and Erik Nordmark, for providing a detailed review of this
document. 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, Philip Ralph Droms, David Farmer, Brian Haberman, Ulrich Herberg, Philip
Homburg, Jahangir Hossain, Jonathan Hui, Christian Huitema, Ray Homburg, Jahangir Hossain, Jonathan Hui, Christian Huitema, Ray
Hunter, Sheng Jiang, Roger Jorgensen, Dan Luedtke, Kerry Lynn, George Hunter, Erik Kline, Sheng Jiang, Roger Jorgensen, Dan Luedtke, Kerry
Mitchel, Gabriel Montenegro, Erik Nordmark, Simon Perreault, Tom Lynn, George Mitchel, Gabriel Montenegro, Erik Nordmark, Simon
Petch, Alexandru Petrescu, Michael Richardson, Arturo Servin, Mark Perreault, Tom Petch, Alexandru Petrescu, Michael Richardson, Arturo
Smith, Tom Taylor, Ole Troan, Tina Tsou, Glen Turner, Randy Turner, Servin, Mark Smith, Tom Taylor, Ole Troan, Tina Tsou, Glen Turner,
and James Woodyatt, for providing valuable comments on earlier Randy Turner, and James Woodyatt, for providing valuable comments on
versions of this document. earlier versions of this document.
11. References 11. References
11.1. Normative References 11.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, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
 End of changes. 8 change blocks. 
33 lines changed or deleted 38 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/