Temporary Address Extensions for Stateless Address Autoconfiguration in IPv6
draft-ietf-6man-rfc4941bis-09

The information below is for an old version of the document
Document Type Active Internet-Draft (6man WG)
Authors Fernando Gont  , Suresh Krishnan  , Thomas Narten  , Richard Draves 
Last updated 2020-08-16 (latest revision 2020-04-06)
Replaces draft-fgont-6man-rfc4941bis
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Ole Trøan
Shepherd write-up Show (last changed 2020-06-04)
IESG IESG state AD Evaluation::Revised I-D Needed
Consensus Boilerplate Yes
Telechat date
Responsible AD Erik Kline
Send notices to =?utf-8?q?Ole_Tr=C3=B8an?= <otroan@employees.org>
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: October 8, 2020                                       T. Narten
                                                         IBM Corporation
                                                               R. Draves
                                                      Microsoft Research
                                                           April 6, 2020

Temporary Address Extensions for Stateless Address Autoconfiguration in
                                  IPv6
                     draft-ietf-6man-rfc4941bis-09

Abstract

   This document describes an extension that causes nodes to generate
   global scope addresses with randomized interface identifiers that
   change over time.  Changing global scope addresses over time limits
   the window of time during which eavesdroppers and other information
   collectors may trivially perform address-based network activity
   correlation when the same address is employed for multiple
   transactions by the same node.  Additionally, it reduces the window
   of exposure of a node via an addresses that becomes revealed as a
   result of active communication.  This document obsoletes RFC4941.

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 October 8, 2020.

Gont, et al.             Expires October 8, 2020                [Page 1]
Internet-Draft  Temporary Address Extensions to Autoconf      April 2020

Copyright Notice

   Copyright (c) 2020 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 . . . . . . . . . . . . . . . . . . . .   4
   2.  Background  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Extended Use of the Same Identifier . . . . . . . . . . .   4
     2.2.  Possible Approaches . . . . . . . . . . . . . . . . . . .   6
   3.  Protocol Description  . . . . . . . . . . . . . . . . . . . .   6
     3.1.  Design Guidelines . . . . . . . . . . . . . . . . . . . .   6
     3.2.  Assumptions . . . . . . . . . . . . . . . . . . . . . . .   7
     3.3.  Generation of Randomized Interface Identifiers  . . . . .   8
       3.3.1.  Simple Randomized Interface Identifiers . . . . . . .   8
       3.3.2.  Hash-based Generation of Randomized Interface
               Identifiers . . . . . . . . . . . . . . . . . . . . .   9
     3.4.  Generating Temporary Addresses  . . . . . . . . . . . . .  10
     3.5.  Expiration of Temporary Addresses . . . . . . . . . . . .  12
     3.6.  Regeneration of Temporary Addresses . . . . . . . . . . .  12
     3.7.  Implementation Considerations . . . . . . . . . . . . . .  13
     3.8.  Defined Constants . . . . . . . . . . . . . . . . . . . .  14
   4.  Implications of Changing Interface Identifiers  . . . . . . .  15
   5.  Significant Changes from RFC4941  . . . . . . . . . . . . . .  15
   6.  Future Work . . . . . . . . . . . . . . . . . . . . . . . . .  16
   7.  Implementation Status . . . . . . . . . . . . . . . . . . . .  17
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  17
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  18
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  18
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  18
     10.2.  Informative References . . . . . . . . . . . . . . . . .  20
Show full document text