Updates to the Special-Purpose IP Address Registries
RFC 8190

Document Type RFC - Best Current Practice (June 2017; No errata)
Updates RFC 6890
Was draft-bchv-rfc6890bis (individual in int area)
Last updated 2017-06-27
Stream IETF
Formats plain text pdf html bibtex
Reviews
Stream WG state (None)
Document shepherd Daniel Migault
Shepherd write-up Show (last changed 2017-02-10)
IESG IESG state RFC 8190 (Best Current Practice)
Consensus Boilerplate Yes
Telechat date
Responsible AD Suresh Krishnan
Send notices to (None)
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
Internet Engineering Task Force (IETF)                         R. Bonica
Request for Comments: 8190                              Juniper Networks
BCP: 153                                                       M. Cotton
Updates: 6890                                                        PTI
Category: Best Current Practice                              B. Haberman
ISSN: 2070-1721                                 Johns Hopkins University
                                                               L. Vegoda
                                                                   ICANN
                                                               June 2017

          Updates to the Special-Purpose IP Address Registries

Abstract

   This memo updates the IANA IPv4 and IPv6 Special-Purpose Address
   Registries to address issues raised by the definition of a "global"
   prefix.  It also corrects several errors in registry entries to
   ensure the integrity of the IANA Special-Purpose Address Registries.

   This memo updates RFC 6890.

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

Bonica, et al.            Best Current Practice                 [Page 1]
RFC 8190           Special-Purpose Address Registries          June 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, 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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Definition of Globally Reachable  . . . . . . . . . . . .   3
     2.2.  Updates to the IPv4 Special-Purpose Address Registry  . .   4
     2.3.  Updates to the IPv6 Special-Purpose Address Registry  . .   4
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   4.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     4.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     4.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

Bonica, et al.            Best Current Practice                 [Page 2]
RFC 8190           Special-Purpose Address Registries          June 2017

1.  Introduction

   In order to support new protocols and practices, the IETF
   occasionally reserves an address block for a special purpose.  For
   example, [RFC1122] reserves an IPv4 address block (0.0.0.0/8) to
   represent the local (i.e., "this") network.  Likewise, [RFC4291]
   reserves an IPv6 address block (fe80::/10) for link-local unicast
   addresses.

   Several issues have been raised with the documentation of some of the
   special-purpose address blocks in [RFC6890].  Specifically, the
   definition of "global" provided in [RFC6890] was misleading as it
   slightly differed from the generally accepted definition of "global
   scope" (i.e., the ability to forward beyond the boundaries of an
   administrative domain, described as "global unicast" in the IPv6
   addressing architecture [RFC4291]).

   This memo updates the definition of "global" from [RFC6890] for the
   IPv4 and IPv6 Special-Purpose Address Registries, augments the fields
   contained within the registries in order to address the confusion
   raised by the definition of "global", and corrects some errors in
   some of the entries in the Special-Purpose Address Registries.

   This memo updates [RFC6890].

2.  IANA Considerations

Show full document text