Recommendation on Stable IPv6 Interface Identifiers
draft-ietf-6man-default-iids-10

The information below is for an old version of the document
Document Type Active Internet-Draft (6man WG)
Last updated 2016-02-17
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Additional URLs
- Mailing list discussion
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
IPv6 maintenance Working Group (6man)                            F. Gont
Internet-Draft                                    SI6 Networks / UTN-FRH
Updates: 2464, 2467, 2470,  2491, 2492,                        A. Cooper
         2497, 2590, 3146, 3315, 3572,                             Cisco
         4291, 4338, 4391, 5072, 5121                          D. Thaler
         (if approved)                                         Microsoft
Intended status: Standards Track                                  W. Liu
Expires: August 20, 2016                             Huawei Technologies
                                                       February 17, 2016

          Recommendation on Stable IPv6 Interface Identifiers
                    draft-ietf-6man-default-iids-10

Abstract

   This document changes the default Interface Identifier generation
   scheme for SLAAC to that specified in RFC7217, and recommends against
   embedding link-layer addresses in IPv6 Interface Identifiers.  It
   formally updates RFC2464, RFC2467, RFC2470, RFC2491, RFC2492,
   RFC2497, RFC2590, RFC3146, RFC3572, RFC4291, RFC4338, RFC4391,
   RFC5072, and RFC5121, by removing the text in these RFCs that
   required the IPv6 Interface Identifiers to be derived from the
   underlying link-layer address, and replacing the aforementioned text
   with a pointer to this document.  Additionally, this document updates
   RFC3315 by specifying additional requirements on the generation of
   Interface Identifiers used in Dynamic Host Configuration Protocol
   version 6 (DHCPv6).  It also provides advice to system administrators
   who employ manual configuration.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August 20, 2016.

Gont, et al.             Expires August 20, 2016                [Page 1]
Internet-Draft            Default Interface-IDs            February 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 in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Generation of IPv6 Interface Identifiers with SLAAC . . . . .   3
   4.  Generation of IPv6 Interface Identifiers with DHCPv6  . . . .   4
   5.  Generation of IPv6 Interface Identifiers with Manual
       Configuration . . . . . . . . . . . . . . . . . . . . . . . .   5
   6.  Update to existing RFCs . . . . . . . . . . . . . . . . . . .   5
   7.  Future Work . . . . . . . . . . . . . . . . . . . . . . . . .  17
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  18
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  18
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  18
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  18
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  21

1.  Introduction

   [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 link-layer address (e.g., an IEEE LAN MAC
   address).

   In some network technologies and adaptation layers, the use of an IID
   based on a link-layer address may offer some advantages.  For
   example, the IP-over-IEEE802.15.4 standard in [RFC6775] allows for
   compression of IPv6 addresses when the IID is based on the underlying
   link-layer address.

   The security and privacy implications of embedding a link-layer
   address in an IPv6 IID have been known for some time now, and are

Gont, et al.             Expires August 20, 2016                [Page 2]
Show full document text