RFC 7136 on Significance of IPv6 Interface Identifiers

rfc-editor@rfc-editor.org Tue, 11 February 2014 04:26 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC9401A08C6; Mon, 10 Feb 2014 20:26:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level:
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gung6XQUzKou; Mon, 10 Feb 2014 20:26:19 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id E26AB1A08CC; Mon, 10 Feb 2014 20:26:16 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id AC9767FC3AA; Mon, 10 Feb 2014 20:26:16 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7136 on Significance of IPv6 Interface Identifiers
From: rfc-editor@rfc-editor.org
Message-Id: <20140211042616.AC9767FC3AA@rfc-editor.org>
Date: Mon, 10 Feb 2014 20:26:16 -0800
Cc: drafts-update-ref@iana.org, ipv6@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Feb 2014 04:26:22 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7136

        Title:      Significance of IPv6 Interface Identifiers 
        Author:     B. Carpenter, S. Jiang
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2014
        Mailbox:    brian.e.carpenter@gmail.com, 
                    jiangsheng@huawei.com
        Pages:      10
        Characters: 23172
        Updates:    RFC 4291

        I-D Tag:    draft-ietf-6man-ug-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7136.txt

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.

This document is a product of the IPv6 Maintenance Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/search/rfc_search.php
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC