A method for Generating Stable Privacy-Enhanced Addresses with IPv6 Stateless Address Autoconfiguration (SLAAC)
draft-ietf-6man-stable-privacy-addresses-02

The information below is for an old version of the document
Document Type Active Internet-Draft (6man WG)
Last updated 2012-12-29
Replaces draft-gont-6man-stable-privacy-addresses
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state In WG Last Call
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
IPv6 maintenance Working Group (6man)                            F. Gont
Internet-Draft                                    SI6 Networks / UTN-FRH
Intended status: Standards Track                       December 30, 2012
Expires: July 3, 2013

  A method for Generating Stable Privacy-Enhanced Addresses with IPv6
              Stateless Address Autoconfiguration (SLAAC)
              draft-ietf-6man-stable-privacy-addresses-02

Abstract

   This document specifies a method for generating IPv6 Interface
   Identifiers to be used with IPv6 Stateless Address Autoconfiguration
   (SLAAC), such that addresses configured using this method are stable
   within each subnet, but the Interface Identifier changes when hosts
   move from one network to another.  The aforementioned method is meant
   to be an alternative to generating Interface Identifiers based on
   IEEE identifiers, such that the benefits of stable addresses can be
   achieved without sacrificing the privacy of users.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 3, 2013.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect

Gont                      Expires July 3, 2013                  [Page 1]
Internet-Draft          Stable Privacy Addresses           December 2012

   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Design goals . . . . . . . . . . . . . . . . . . . . . . . . .  6
   3.  Algorithm specification  . . . . . . . . . . . . . . . . . . .  7
   4.  Resolving Duplicate Address Detection (DAD) conflicts  . . . . 10
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 11
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 12
   7.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13
   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
     8.1.  Normative References . . . . . . . . . . . . . . . . . . . 14
     8.2.  Informative References . . . . . . . . . . . . . . . . . . 14
   Appendix A.  Privacy issues still present with RFC 4941  . . . . . 16
     A.1.  Host tracking  . . . . . . . . . . . . . . . . . . . . . . 16
       A.1.1.  Tracking hosts across networks #1  . . . . . . . . . . 16
       A.1.2.  Tracking hosts across networks #2  . . . . . . . . . . 16
       A.1.3.  Revealing the identity of devices performing
               server-like functions  . . . . . . . . . . . . . . . . 17
     A.2.  Address scanning attacks . . . . . . . . . . . . . . . . . 17
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 18

Gont                      Expires July 3, 2013                  [Page 2]
Internet-Draft          Stable Privacy Addresses           December 2012

1.  Introduction

   [RFC4862] specifies the Stateless Address Autoconfiguration (SLAAC)
   for IPv6 [RFC2460], which typically results in hosts configuring one
   or more "stable" addresses composed of a network prefix advertised by
   a local router, and an Interface Identifier (IID) that typically
   embeds a hardware address (e.g., using IEEE identifiers) [RFC4291].

   Generally, stable addresses are thought to simplify network
   management, since they simplify Access Control Lists (ACLs) and
   logging.  However, since IEEE identifiers are typically globally
   unique, the resulting IPv6 addresses can be leveraged to track and
   correlate the activity of a node over time and across multiple
   subnets and networks, thus negatively affecting the privacy of users.

   The "Privacy Extensions for Stateless Address Autoconfiguration in
   IPv6" [RFC4941] were introduced to complicate the task of
   eavesdroppers and other information collectors to correlate the
Show full document text