Browse Prior Art Database

Host Address Availability Recommendations (RFC7934)

IP.com Disclosure Number: IPCOM000246995D
Original Publication Date: 2016-Jul-01
Included in the Prior Art Database: 2016-Jul-21
Document File: 30 page(s) / 37K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

L. Colitti: AUTHOR [+4]

Abstract

In most aspects, the IPv6 protocol is very similar to IPv4. This similarity can create a tendency to think of IPv6 as 128-bit IPv4, and thus lead network designers and operators to apply identical configurations and operational practices to both. This is generally a good thing because it eases the transition to IPv6 and the operation of dual-stack networks. However, in some design and operational areas, it can lead to carrying over IPv4 practices that are limiting or not appropriate in IPv6 due to differences between the protocols.

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

Internet Engineering Task Force (IETF)                        L. Colitti Request for Comments: 7934                                       V. Cerf BCP: 204                                                          Google Category: Best Current Practice                              S. Cheshire ISSN: 2070-1721                                              D. Schinazi                                                               Apple Inc.                                                                July 2016

                Host Address Availability Recommendations

Abstract

   This document recommends that networks provide general-purpose end    hosts with multiple global IPv6 addresses when they attach, and it    describes the benefits of and the options for doing so.

Status of This Memo

   This memo documents an Internet Best Current Practice.

   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    BCPs 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/rfc7934.

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.

 Colitti, et al.           Best Current Practice                 [Page 1]
 RFC 7934        Host Address Availability Recommendations      July 2016

 Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2

     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3

   2.  Common IPv6 Deployment Model  . . . . . . . . . . . . . . . .   3

   3.  Benefits of Providing Multiple Addresses  . . . . . . . . . .   3

   4.  Problems with Res...