Special-Purpose IP Address Registries
draft-bchv-rfc6890bis-05

Document Type Active Internet-Draft (individual in int area)
Last updated 2017-03-16 (latest revision 2017-03-10)
Stream IETF
Intended RFC status Best Current Practice
Formats plain text pdf html bibtex
Reviews GENART will not review this version
Stream WG state (None)
Document shepherd Daniel Migault
Shepherd write-up Show (last changed 2017-02-10)
IESG IESG state IESG Evaluation::Revised I-D Needed
Consensus Boilerplate Yes
Telechat date
Needs a YES. Has a DISCUSS. Needs 2 more YES or NO OBJECTION positions to pass.
Responsible AD Suresh Krishnan
Send notices to (None)
IANA IANA review state IANA - Not OK
IANA action state None
Network Working Group                                          R. Bonica
Internet-Draft                                          Juniper Networks
Obsoletes: 6890 (if approved)                                  M. Cotton
Intended status: Best Current Practice                             ICANN
Expires: September 11, 2017                                  B. Haberman
                                                Johns Hopkins University
                                                               L. Vegoda
                                                                   ICANN
                                                          March 10, 2017

                 Special-Purpose IP Address Registries
                        draft-bchv-rfc6890bis-05

Abstract

   This memo updates the IANA IPv6 Special-Purpose Address Registries to
   address issues raised by the definition of a global prefix.  For
   completeness, this memo contains all the assignments made to the IANA
   Special-Purpose Address Registries.

   This memo obsoletes RFC 6890.

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 September 11, 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

Bonica, et al.         Expires September 11, 2017               [Page 1]
Internet-Draft     Special Purpose Address Registries         March 2017

   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.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Assignment of an IPv4 Address Block to IANA . . . . . . .   3
     3.2.  Restructuring of the IPv4 and IPv6 Special-Purpose
           Address Registries  . . . . . . . . . . . . . . . . . . .   3
       3.2.1.  Information Requirements  . . . . . . . . . . . . . .   4
       3.2.2.  IPv4 Special-Purpose Address Registry Entries . . . .   5
       3.2.3.  IPv6 Special-Purpose Address Registry Entries . . . .  15
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  25
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  25
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  26
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .  26
     6.2.  Informative References  . . . . . . . . . . . . . . . . .  26
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  29

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) to represent link-scoped
   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 reiterates the assignments made to the IPv4 and IPv6
   Special-Purpose Address Registries and augments the fields contained
   within the registries in order to address the confusion raised by the
Show full document text