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

Document Type Active Internet-Draft (individual)
Last updated 2017-03-13
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
Updates: RFC4941 (if approved)                                C. Huitema
Intended status: Standards Track                    Private Octopus Inc.
Expires: September 14, 2017                                      G. Gont
                                                            SI6 Networks
                                                         M. Garcia Corbo
                                                                 SITRANS
                                                          March 13, 2017

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

Abstract

   This document clarifies the stability requirements for IPv6
   addresses, and provides recommendations regarding the generation of
   Temporary addresses.  Finally, it formally updates RFC4941 such that
   nodes are allowed to configure 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 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 September 14, 2017.

Copyright Notice

   Copyright (c) 2017 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, et al.           Expires September 14, 2017               [Page 1]
Internet-Draft           Temporary Interface-IDs              March 2017

   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 . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Problem statement . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Generation of Temporary IPv6 Addresses  . . . . . . . . . . .   6
   5.  Update to existing RFCs . . . . . . . . . . . . . . . . . . .   8
   6.  Future Work . . . . . . . . . . . . . . . . . . . . . . . . .   9
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

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] implies,
   throughout the specification, that temporary addresses are generated
   and employed along with temporary 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).

   This document clarifies the requirements for stability of IPv6
   addresses, such that nodes are not required to configure stable
   addresses.  It also specifies a set of requirements for the
   generation of Temporary addresses, and also specifies some sample
   algorithms that may be employed to generate temporary addresses that
   comply with the aforementioned requirements.  Finally, it formally
   updates [RFC4941] such that temporary addresses can be employed
   without the need to configure a stable address along side.

2.  Terminology

   This document employs the terms defined in [RFC7721].

Gont, et al.           Expires September 14, 2017               [Page 2]
Show full document text