Browse Prior Art Database

Recommendation on Stable IPv6 Interface Identifiers (RFC8064)

IP.com Disclosure Number: IPCOM000249388D
Original Publication Date: 2017-Feb-01
Included in the Prior Art Database: 2017-Feb-23
Document File: 18 page(s) / 19K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

F. Gont: AUTHOR [+4]

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) [RFC4291] that typically embeds a stable link-layer address (e.g., an IEEE LAN MAC address).

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

Internet Engineering Task Force (IETF)                           F. Gont Request for Comments: 8064                        SI6 Networks / UTN-FRH Updates: 2464, 2467, 2470, 2491, 2492,                         A. Cooper          2497, 2590, 3146, 3572, 4291,                             Cisco          4338, 4391, 5072, 5121                                D. Thaler Category: Standards Track                                      Microsoft ISSN: 2070-1721                                                   W. Liu                                                      Huawei Technologies                                                            February 2017

           Recommendation on Stable IPv6 Interface Identifiers

Abstract

   This document changes the recommended default Interface Identifier    (IID) generation scheme for cases where Stateless Address    Autoconfiguration (SLAAC) is used to generate a stable IPv6 address.    It recommends using the mechanism specified in RFC 7217 in such    cases, and recommends against embedding stable link-layer addresses    in IPv6 IIDs.  It formally updates RFC 2464, RFC 2467, RFC 2470, RFC    2491, RFC 2492, RFC 2497, RFC 2590, RFC 3146, RFC 3572, RFC 4291, RFC    4338, RFC 4391, RFC 5072, and RFC 5121.  This document does not    change any existing recommendations concerning the use of temporary    addresses as specified in RFC 4941.

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 7841.

   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/rfc8064.

 Gont, et al.                 Standards Track                    [Page 1]
 RFC 8064              Default Interface Identifiers        February 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    carefully,...