A method for Generating Stable Privacy-Enhanced Addresses with IPv6 Stateless Address Autoconfiguration (SLAAC)
draft-ietf-6man-stable-privacy-addresses-11
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (6man WG)
|
|
Last updated |
|
2013-08-08
|
|
Replaces |
|
draft-gont-6man-stable-privacy-addresses
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Bob Hinden
|
|
Shepherd write-up |
|
Show
(last changed 2013-04-08)
|
| IESG |
IESG state |
|
AD is watching
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Brian Haberman
|
|
Send notices to |
|
6man-chairs@tools.ietf.org, draft-ietf-6man-stable-privacy-addresses@tools.ietf.org
|
| IANA |
IANA review state |
|
Version Changed - Review Needed
|
|
IANA action state |
|
None
|
IPv6 maintenance Working Group (6man) F. Gont
Internet-Draft SI6 Networks / UTN-FRH
Intended status: Standards Track August 8, 2013
Expires: February 9, 2014
A method for Generating Stable Privacy-Enhanced Addresses with IPv6
Stateless Address Autoconfiguration (SLAAC)
draft-ietf-6man-stable-privacy-addresses-11
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
address (e.g., using IEEE identifiers), 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 February 9, 2014.
Copyright Notice
Copyright (c) 2013 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 February 9, 2014 [Page 1]
Internet-Draft Stable Privacy Addresses August 2013
(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 . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Design goals . . . . . . . . . . . . . . . . . . . . . . . . . 7
3. Algorithm specification . . . . . . . . . . . . . . . . . . . 9
4. Resolving Duplicate Address Detection (DAD) conflicts . . . . 14
5. Specified Constants . . . . . . . . . . . . . . . . . . . . . 15
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
7. Security Considerations . . . . . . . . . . . . . . . . . . . 17
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 19
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
9.1. Normative References . . . . . . . . . . . . . . . . . . . 20
9.2. Informative References . . . . . . . . . . . . . . . . . . 21
Appendix A. Possible sources for the Net_Iface parameter . . . . 23
A.1. Interface Index . . . . . . . . . . . . . . . . . . . . . 23
A.2. Interface Name . . . . . . . . . . . . . . . . . . . . . . 23
A.3. Link-layer Addresses . . . . . . . . . . . . . . . . . . . 23
A.4. Logical Network Service Identity . . . . . . . . . . . . . 24
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 25
Gont Expires February 9, 2014 [Page 2]
Internet-Draft Stable Privacy Addresses August 2013
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., using IEEE identifiers) [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
network management, since they simplify Access Control Lists (ACLs)
and logging. However, they have a number of drawbacks:
o since the resulting Interface Identifiers do not vary over time,
Show full document text