Browse Prior Art Database

A Method for Generating Semantically Opaque Interface Identifiers with IPv6 Stateless Address Autoconfiguration (SLAAC) (RFC7217)

IP.com Disclosure Number: IPCOM000236516D
Original Publication Date: 2014-Apr-01
Included in the Prior Art Database: 2014-May-01
Document File: 40 page(s) / 47K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

F. Gont: AUTHOR

Abstract

[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; CGAs bind a public signature key to an IPv6 address in the SEcure Neighbor Discovery (SEND) [RFC3971] protocol.

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)                           F. Gont Request for Comments: 7217                        SI6 Networks / UTN-FRH Category: Standards Track                                     April 2014 ISSN: 2070-1721

    A Method for Generating Semantically Opaque Interface Identifiers          with IPv6 Stateless Address Autoconfiguration (SLAAC)

Abstract

   This document specifies a method for generating IPv6 Interface    Identifiers to be used with IPv6 Stateless Address Autoconfiguration    (SLAAC), such that an IPv6 address configured using this method is    stable within each subnet, but the corresponding Interface Identifier    changes when the host moves 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 Media Access Control    (MAC) addresses), such that the benefits of stable addresses can be    achieved without sacrificing the security and 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 prefixes    (and their corresponding addresses).

Status of This Memo

   This is an Internet Standards Track document.

   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).  Further information on    Internet Standards is available in 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/rfc7217.

 Gont                         Standards Track                    [Page 1]
 RFC 7217            Stable and Opaque IIDs with SLAAC         April 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    (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.  Terminology ....