Browse Prior Art Database

Significance of IPv6 Interface Identifiers (RFC7136) Disclosure Number: IPCOM000234857D
Original Publication Date: 2014-Feb-01
Included in the Prior Art Database: 2014-Feb-12
Document File: 20 page(s) / 23K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

B. Carpenter: AUTHOR [+2]


IPv6 unicast addresses consist of a prefix followed by an Interface Identifier (IID). The IID is supposed to be unique on the links reached by routing to that prefix, giving an IPv6 address that is unique within the applicable scope (link local or global). According to the IPv6 addressing architecture [RFC4291], when a 64-bit IPv6 unicast IID is formed on the basis of an IEEE EUI-64 address, usually itself expanded from a 48-bit MAC address, a particular format must be used:

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

Internet Engineering Task Force (IETF)                      B. Carpenter Request for Comments: 7136                             Univ. of Auckland Updates: 4291                                                   S. Jiang Category: Standards Track                   Huawei Technologies Co., Ltd ISSN: 2070-1721                                            February 2014

                Significance of IPv6 Interface Identifiers


   The IPv6 addressing architecture includes a unicast interface    identifier that is used in the creation of many IPv6 addresses.    Interface identifiers are formed by a variety of methods.  This    document clarifies that the bits in an interface identifier have no    meaning and that the entire identifier should be treated as an opaque    value.  In particular, RFC 4291 defines a method by which the    Universal and Group bits of an IEEE link-layer address are mapped    into an IPv6 unicast interface identifier.  This document clarifies    that those two bits are significant only in the process of deriving    interface identifiers from an IEEE link-layer address, and it updates    RFC 4291 accordingly.

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

Carpenter & Jiang            Standards Track                    [Page 1]
 RFC 7136                  IPv6 IID Significance            February 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    ( 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...