Recommendation on Temporary IPv6 Interface Identifiers
draft-gont-6man-non-stable-iids-04

Document Type Active Internet-Draft (individual)
Last updated 2018-03-24
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
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                              C. Huitema
Expires: September 25, 2018                         Private Octopus Inc.
                                                             S. Krishnan
                                                       Ericsson Research
                                                                 G. Gont
                                                            SI6 Networks
                                                         M. Garcia Corbo
                                                                 SITRANS
                                                          March 24, 2018

         Recommendation on Temporary IPv6 Interface Identifiers
                   draft-gont-6man-non-stable-iids-04

Abstract

   This document specifies a set of requirements for generating
   temporary addresses, and clarifies the stability requirements for
   IPv6 addresses, allowing for the use of only temporary addresses.

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 September 25, 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

Gont, et al.           Expires September 25, 2018               [Page 1]
Internet-Draft           Temporary Interface-IDs              March 2018

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Problem statement . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Stability Requirements for IPv6 Addresses . . . . . . . . . .   4
   5.  Requirements for Temporary IPv6 Addresses . . . . . . . . . .   4
   6.  Future Work . . . . . . . . . . . . . . . . . . . . . . . . .   6
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   IPv6 StateLess Address AutoConfiguration (SLAAC) [RFC4862] has
   traditionally resulted in stable addresses, since the Interface
   Identifier (IID) has been generated by embedding a stable layer-2
   numeric identifier (e.g., a MAC address).  [RFC4941] originally
   implied, throughout the specification, that temporary addresses are
   generated and employed along with stable addresses.

   While the use of stable addresses (only) or mixed stable and
   temporary addresses can be desirable in a number of scenarios, there
   are other scenarios in which, for security and privacy reasons, a
   node may want to use only temporary address (e.g., a temporary
   address).

   On the other hand, the lack of a formal set of requirements for
   temporary addresses led to a number of flaws in popular
   implementations and in the protocol specification itself, such as
   allowing for the correlation of network activity carried out with
   different addresses, reusing randomized identifiers across different
   networks, etc.

   This document clarifies the requirements for stability of IPv6
   addresses, such that nodes are not required to configure stable
   addresses, and may instead employ only temporary addresses.  It also
   specifies a set of requirements for the generation of temporary
   addresses.

Gont, et al.           Expires September 25, 2018               [Page 2]
Internet-Draft           Temporary Interface-IDs              March 2018
Show full document text