Privacy Extensions for Stateless Address Autoconfiguration in IPv6
draft-ietf-6man-rfc4941bis-00

Document Type Active Internet-Draft (6man WG)
Last updated 2018-07-02
Replaces draft-fgont-6man-rfc4941bis
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
IPv6 Maintenance (6man) Working Group                            F. Gont
Internet-Draft                                    SI6 Networks / UTN-FRH
Obsoletes: rfc4941 (if approved)                             S. Krishnan
Intended status: Standards Track                       Ericsson Research
Expires: January 3, 2019                                       T. Narten
                                                         IBM Corporation
                                                               R. Draves
                                                      Microsoft Research
                                                            July 2, 2018

   Privacy Extensions for Stateless Address Autoconfiguration in IPv6
                     draft-ietf-6man-rfc4941bis-00

Abstract

   Nodes use IPv6 stateless address autoconfiguration to generate
   addresses using a combination of locally available information and
   information advertised by routers.  Addresses are formed by combining
   network prefixes with an interface identifier.  This document
   describes an extension that causes nodes to generate global scope
   addresses from interface identifiers that change over time.  Changing
   the interface identifier (and the global scope addresses generated
   from it) over time makes it more difficult for eavesdroppers and
   other information collectors to identify when different addresses
   used in different transactions actually correspond to the same node.

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 https://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 January 3, 2019.

Gont, et al.             Expires January 3, 2019                [Page 1]
Internet-Draft       Privacy Extensions to Autoconf            July 2018

Copyright Notice

   Copyright (c) 2018 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
   (https://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
   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
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Problem Statement . . . . . . . . . . . . . . . . . . . .   3
   2.  Background  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Extended Use of the Same Identifier . . . . . . . . . . .   4
     2.2.  Possible Approaches . . . . . . . . . . . . . . . . . . .   5
   3.  Protocol Description  . . . . . . . . . . . . . . . . . . . .   6
     3.1.  Assumptions . . . . . . . . . . . . . . . . . . . . . . .   7
     3.2.  Generation of Randomized Interface Identifiers  . . . . .   7
       3.2.1.  Simple Randomized Interface Identifiers . . . . . . .   8
       3.2.2.  Hash-based Generation of Randomized Interface
               Identifiers . . . . . . . . . . . . . . . . . . . . .   8
     3.3.  Generating Temporary Addresses  . . . . . . . . . . . . .  10
     3.4.  Expiration of Temporary Addresses . . . . . . . . . . . .  11
     3.5.  Regeneration of Randomized Interface Identifiers  . . . .  12
     3.6.  Deployment Considerations . . . . . . . . . . . . . . . .  13
   4.  Implications of Changing Interface Identifiers  . . . . . . .  14
   5.  Defined Constants . . . . . . . . . . . . . . . . . . . . . .  14
   6.  Future Work . . . . . . . . . . . . . . . . . . . . . . . . .  15
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  15
   8.  Significant Changes from RFC4941  . . . . . . . . . . . . . .  16
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  16
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  17
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  17
     10.2.  Informative References . . . . . . . . . . . . . . . . .  18
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  19

Gont, et al.             Expires January 3, 2019                [Page 2]
Show full document text