datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

A Method for Generating Semantically Opaque Interface Identifiers with IPv6 Stateless Address Autoconfiguration (SLAAC)
draft-ietf-6man-stable-privacy-addresses-17

Document type: Active Internet-Draft (6man WG)
Document stream: IETF
Last updated: 2014-01-31 (latest revision 2014-01-27)
Intended RFC status: Proposed Standard
Other versions: plain text, pdf, html

IETF State: Submitted to IESG for Publication
Consensus: Yes
Document shepherd: Bob Hinden
Shepherd Write-Up: Last changed 2013-10-17

IESG State: RFC Ed Queue
IANA Action State: No IC
RFC Editor State: RFC-EDITOR
Responsible AD: Brian Haberman
Send notices to: 6man-chairs@tools.ietf.org, draft-ietf-6man-stable-privacy-addresses@tools.ietf.org

IPv6 maintenance Working Group (6man)                            F. Gont
Internet-Draft                                    SI6 Networks / UTN-FRH
Intended status: Standards Track                        January 27, 2014
Expires: July 31, 2014

 A Method for Generating Semantically Opaque Interface Identifiers with
            IPv6 Stateless Address Autoconfiguration (SLAAC)
              draft-ietf-6man-stable-privacy-addresses-17

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.  This method is meant to be an
   alternative to generating Interface Identifiers based on hardware
   addresses (e.g., IEEE LAN MAC addresses), such that the benefits of
   stable addresses can be achieved without sacrificing the privacy of
   users.  The method specified in this document applies to all prefixes
   a host may be employing, including link-local, global, and unique-
   local 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 July 31, 2014.

Copyright Notice

   Copyright (c) 2014 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

Gont                      Expires July 31, 2014                 [Page 1]
Internet-Draft      Stable and Opaque IIDs with SLAAC       January 2014

   (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
   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 . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Relationship to Other standards . . . . . . . . . . . . . . .   5
   4.  Design goals  . . . . . . . . . . . . . . . . . . . . . . . .   5
   5.  Algorithm specification . . . . . . . . . . . . . . . . . . .   6
   6.  Resolving Duplicate Address Detection (DAD) conflicts . . . .  11
   7.  Specified Constants . . . . . . . . . . . . . . . . . . . . .  12
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  14
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  15
     11.2.  Informative References . . . . . . . . . . . . . . . . .  16
   Appendix A.  Possible sources for the Net_Iface parameter . . . .  18
     A.1.  Interface Index . . . . . . . . . . . . . . . . . . . . .  18
     A.2.  Interface Name  . . . . . . . . . . . . . . . . . . . . .  18
     A.3.  Link-layer Addresses  . . . . . . . . . . . . . . . . . .  19
     A.4.  Logical Network Service Identity  . . . . . . . . . . . .  19
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  19

1.  Introduction

   [RFC4862] specifies 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., an IEEE LAN MAC address) [RFC4291].
   Cryptographically Generated Addresses (CGAs) [RFC3972] are yet
   another method for generating Interface Identifiers, which bind a
   public signature key to an IPv6 address in the SEcure Neighbor
   Discovery (SEND) [RFC3971] protocol.

   Generally, the traditional SLAAC addresses are thought to simplify

[include full document text]