draft-ietf-6man-default-iids-06.txt   draft-ietf-6man-default-iids-07.txt 
skipping to change at page 1, line 14 skipping to change at page 1, line 14
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: February 20, 2016 Huawei Technologies Expires: February 20, 2016 Huawei Technologies
August 19, 2015 August 19, 2015
Recommendation on Stable IPv6 Interface Identifiers Recommendation on Stable IPv6 Interface Identifiers
draft-ietf-6man-default-iids-06 draft-ietf-6man-default-iids-07
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 5, line 22 skipping to change at page 5, line 22
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 RFC 6282 [RFC6282]
o RFC 4944 [RFC4944] o RFC 4944 [RFC4944]
o RFC 6755 [RFC6775] o RFC 6775 [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
 End of changes. 2 change blocks. 
2 lines changed or deleted 2 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/