Browse Prior Art Database

Security and Privacy Considerations for IPv6 Address Generation Mechanisms (RFC7721)

IP.com Disclosure Number: IPCOM000245436D
Original Publication Date: 2016-Mar-01
Included in the Prior Art Database: 2016-Mar-10
Document File: 36 page(s) / 43K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A. Cooper: AUTHOR [+3]

Abstract

IPv6 was designed to improve upon IPv4 in many respects, and mechanisms for address assignment were one such area for improvement. In addition to static address assignment and DHCP, stateless autoconfiguration was developed as a less intensive, fate-shared means of performing address assignment. With stateless autoconfiguration, routers advertise on-link prefixes and hosts generate their own Interface Identifiers (IIDs) to complete their addresses. [RFC7136] clarifies that the IID should be treated as an opaque value, while [RFC7421] provides an analysis of the 64-bit boundary in IPv6 addressing (e.g., the implications of the IID length on security and privacy). Over the years, many IID generation techniques have been defined, both standardized and non-standardized:

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 6% of the total text.

Internet Engineering Task Force (IETF)                         A. Cooper Request for Comments: 7721                                         Cisco Category: Informational                                          F. Gont ISSN: 2070-1721                                      Huawei Technologies                                                                D. Thaler                                                                Microsoft                                                               March 2016

                 Security and Privacy Considerations for                    IPv6 Address Generation Mechanisms

Abstract

   This document discusses privacy and security considerations for    several IPv6 address generation mechanisms, both standardized and    non-standardized.  It evaluates how different mechanisms mitigate    different threats and the trade-offs that implementors, developers,    and users face in choosing different addresses or address generation    mechanisms.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Not all documents    approved by the IESG are a candidate for any level of Internet    Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7721.

Cooper, et al.                Informational                     [Page 1]
 RFC 7721             IPv6 Address Generation Privacy          March 2016

 Copyright Notice

   Copyright (c) 2016 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    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 i...