IPv6 Address Usage Recommendations
draft-gont-6man-address-usage-recommendations-02
|
| 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
Intended status: Best Current Practice G. Gont
Expires: September 14, 2017 SI6 Networks
M. Garcia Corbo
SITRANS
C. Huitema
Private Octopus Inc.
March 13, 2017
IPv6 Address Usage Recommendations
draft-gont-6man-address-usage-recommendations-02
Abstract
This document analyzes the security and privacy implications of IPv6
addresses based on a number of properties such as address scope,
stability, and usage type. It analyzes what properties are desirable
for some popular scenarios, and provides advice regarding the
configuration and usage of such 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
Gont, et al. Expires September 14, 2017 [Page 1]
Internet-Draft IPv6 Address Recommendations March 2017
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
3.1. Testing for the Presence of Node in the Network . . . . . 4
3.2. Unexpected Address Discovery . . . . . . . . . . . . . . 4
3.3. Availability Outside the Expected Scope . . . . . . . . . 4
3.4. Limited Address Selection API . . . . . . . . . . . . . . 5
4. Predictability Considerations . . . . . . . . . . . . . . . . 5
5. Address Scope Considerations . . . . . . . . . . . . . . . . 6
6. Address Stability Considerations . . . . . . . . . . . . . . 6
7. Usage Type Considerations . . . . . . . . . . . . . . . . . . 8
8. Advice on IPv6 Address Configuration . . . . . . . . . . . . 9
9. Advice on IPv6 Address Usage . . . . . . . . . . . . . . . . 9
10. Future Work . . . . . . . . . . . . . . . . . . . . . . . . . 10
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
12. Security Considerations . . . . . . . . . . . . . . . . . . . 10
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10
14. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
14.1. Normative References . . . . . . . . . . . . . . . . . . 10
14.2. Informative References . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction
IPv6 hosts typically configure a number of IPv6 addresses, which may
differ in multiple aspects, such as address scope and stability (e.g.
stable addresses vs. temporary addresses). For example, a host may
configure one stable and one temporary address per each
autoconfiguration prefix advertised on the local network. The
addresses to be configured typically depend on local system policy
configuration, with the aforementioned policy being static and
irrespective of the network the host attaches to.
There are three parameters that affect the security and privacy
Show full document text