< draft-ietf-6lo-privacy-considerations-01.txt   draft-ietf-6lo-privacy-considerations-02.txt >
Network Working Group D. Thaler Network Working Group D. Thaler
Internet-Draft Microsoft Internet-Draft Microsoft
Intended status: Informational July 6, 2016 Intended status: Informational July 29, 2016
Expires: January 7, 2017 Expires: January 30, 2017
Privacy Considerations for IPv6 over Networks of Resource-Constrained Privacy Considerations for IPv6 over Networks of Resource-Constrained
Nodes Nodes
draft-ietf-6lo-privacy-considerations-01 draft-ietf-6lo-privacy-considerations-02
Abstract Abstract
This document discusses how a number of privacy threats apply to This document discusses how a number of privacy threats apply to
technologies designed for IPv6 over networks of resource-constrained technologies designed for IPv6 over networks of resource-constrained
nodes, and provides advice to protocol designers on how to address nodes, and provides advice to protocol designers on how to address
such threats in adaptation layer specifications for IPv6 over such such threats in adaptation layer specifications for IPv6 over such
links. links.
Status of This Memo Status of This Memo
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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, 2017. This Internet-Draft will expire on January 30, 2017.
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 7, line 16 skipping to change at page 7, line 16
o Technologies should define a way to include sufficient bits of o Technologies should define a way to include sufficient bits of
entropy in the IPv6 interface identifier, based on the maximum entropy in the IPv6 interface identifier, based on the maximum
link lifetime. Specifying that randomized link-layer addresses link lifetime. Specifying that randomized link-layer addresses
can be used is one easy way to do so, for technologies that can be used is one easy way to do so, for technologies that
support such identifiers. support such identifiers.
o Specifications should not simply construct an IPv6 interface o Specifications should not simply construct an IPv6 interface
identifier by padding a short address with a set of other well- identifier by padding a short address with a set of other well-
known constant bits, unless the link lifetime is guaranteed to be known constant bits, unless the link lifetime is guaranteed to be
extremely short. extremely short. This also applies to link-local addresses if the
same short address is used independent of network and is unique
enough to allow location tracking.
o Specifications should make sure that an IPv6 address can change o Specifications should make sure that an IPv6 address can change
over long periods of time. For example, the interface identifier over long periods of time. For example, the interface identifier
might change each time a device connects to the network (if might change each time a device connects to the network (if
connections are short), or might change each day (if connections connections are short), or might change each day (if connections
can be long). This is necessary to mitigate correlation over can be long). This is necessary to mitigate correlation over
time. time.
o If a device can roam between networks, and more than a few bits of o If a device can roam between networks, and more than a few bits of
entropy exist in the IPv6 interface identifier, then make sure entropy exist in the IPv6 interface identifier, then make sure
skipping to change at page 9, line 33 skipping to change at page 9, line 33
<http://www.rfc-editor.org/info/rfc7668>. <http://www.rfc-editor.org/info/rfc7668>.
[RFC7721] Cooper, A., Gont, F., and D. Thaler, "Security and Privacy [RFC7721] Cooper, A., Gont, F., and D. Thaler, "Security and Privacy
Considerations for IPv6 Address Generation Mechanisms", Considerations for IPv6 Address Generation Mechanisms",
RFC 7721, DOI 10.17487/RFC7721, March 2016, RFC 7721, DOI 10.17487/RFC7721, March 2016,
<http://www.rfc-editor.org/info/rfc7721>. <http://www.rfc-editor.org/info/rfc7721>.
[I-D.ietf-6man-default-iids] [I-D.ietf-6man-default-iids]
Gont, F., Cooper, A., Thaler, D., and S. (Will), Gont, F., Cooper, A., Thaler, D., and S. (Will),
"Recommendation on Stable IPv6 Interface Identifiers", "Recommendation on Stable IPv6 Interface Identifiers",
draft-ietf-6man-default-iids-11 (work in progress), April draft-ietf-6man-default-iids-13 (work in progress), July
2016. 2016.
[I-D.ietf-6lo-6lobac] [I-D.ietf-6lo-6lobac]
Lynn, K., Martocci, J., Neilson, C., and S. Donaldson, Lynn, K., Martocci, J., Neilson, C., and S. Donaldson,
"Transmission of IPv6 over MS/TP Networks", draft-ietf- "Transmission of IPv6 over MS/TP Networks", draft-ietf-
6lo-6lobac-05 (work in progress), June 2016. 6lo-6lobac-05 (work in progress), June 2016.
[I-D.ietf-6lo-dect-ule] [I-D.ietf-6lo-dect-ule]
Mariager, P., Petersen, J., Shelby, Z., Logt, M., and D. Mariager, P., Petersen, J., Shelby, Z., Logt, M., and D.
Barthel, "Transmission of IPv6 Packets over DECT Ultra Low Barthel, "Transmission of IPv6 Packets over DECT Ultra Low
Energy", draft-ietf-6lo-dect-ule-05 (work in progress), Energy", draft-ietf-6lo-dect-ule-05 (work in progress),
May 2016. May 2016.
[I-D.ietf-6lo-nfc] [I-D.ietf-6lo-nfc]
Hong, Y. and J. Youn, "Transmission of IPv6 Packets over Hong, Y. and J. Youn, "Transmission of IPv6 Packets over
Near Field Communication", draft-ietf-6lo-nfc-03 (work in Near Field Communication", draft-ietf-6lo-nfc-04 (work in
progress), March 2016. progress), July 2016.
[I-D.huitema-6man-random-addresses] [I-D.huitema-6man-random-addresses]
Huitema, C., "Implications of Randomized Link Layers Huitema, C., "Implications of Randomized Link Layers
Addresses for IPv6 Address Assignment", draft-huitema- Addresses for IPv6 Address Assignment", draft-huitema-
6man-random-addresses-03 (work in progress), March 2016. 6man-random-addresses-03 (work in progress), March 2016.
[BTCorev4.1] [BTCorev4.1]
Bluetooth Special Interest Group, "Bluetooth Core Bluetooth Special Interest Group, "Bluetooth Core
Specification Version 4.1", December 2013, Specification Version 4.1", December 2013,
<https://www.bluetooth.org/DocMan/handlers/ <https://www.bluetooth.org/DocMan/handlers/
 End of changes. 6 change blocks. 
8 lines changed or deleted 10 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/