Network Working Group G. Huston
Request for Comments: 4147 APNIC
Category: Informational August 2005
Proposed Changes to the Format of the IANA IPv6 Registry
Status of This Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2005).
Abstract
This document proposes a revised format for the IANA IPv6 address
registries. Rather than providing a formal definition of the format,
it is described by giving examples of the (current as of preparation
of this document) contents of the registries in the proposed format.
The proposed format would bring the IANA IPv6 address registries into
alignment with the current IPv6 Address Architecture specification,
as well as update it to a more useful and generally accepted format.
1. Introduction
This document proposes a revised format for the IANA IPv6 address
registries. The proposed format would bring the IANA IPv6 address
registries into alignment with the current IPv6 Address Architecture
specification, as well as update it to a more useful and generally
accepted format.
The current (as of preparation of this document) IANA IPv6 registries
[iana-ipv6-registry] [iana-ipv6-tla] are based on a now-deprecated
address architecture that used the concept of Top Level Aggregation
Identifiers (TLAs) and sub-TLAs. The current IPv6 Address
Architecture [RFC3513] uses the terminology of Global Identifiers
instead of TLAs and sub-TLAs.
Huston Informational [Page 1]RFC 4147 IANA IPv6 Registry August 20052. IPv6 Address Registry
The proposed format for the IPv6 address registry is indicated by
example, using the registry state that is current as of preparation
of this document, in Figure 1. The registry explicitly notes which
entity is placing a reservation on an address block and notes the
defining RFC document for each allocation.
The proposed format of the registry is a title line, the date of the
last change to the registry, the registry in a tabular format, notes
and references.
The table uses 4 columns. Within the table, the first column
contains an IPv6 address prefix, using a hexadecimal notation of the
address prefix and a prefix length. There are no overlapping address
blocks in the first column, and the set of address blocks in the
registry spans the entire IPv6 address space. The second column
denotes the current disposition of the address block, using notation
derived from the defining RFC document. The third column contains a
reference to the RFC that describes the current disposition of the
address block. The fourth column uses numeric footnote notation to
reference any additional text associated with the address block.
The notes in the registry may include a summary of previous
disposition status values associated with an address block, as this
summary is specifically not included in the registry table. The
notes are numbered sequentially.
The reference section uses a conventional citation format. The
references include documents referenced in the registry table and
documents referenced in the notes.
-----------------------------------------------------
INTERNET PROTOCOL VERSION 6 ADDRESS SPACE
[last updated 13 January 2005]
IPv6 Prefix Allocation Reference Note
----------- ---------- --------- ----
0000::/8 Reserved by IETF RFC3513 [1]
0100::/8 Reserved by IETF RFC3513
0200::/7 Reserved by IETF RFC4048 [2]
0400::/6 Reserved by IETF RFC3513
0800::/5 Reserved by IETF RFC3513
1000::/4 Reserved by IETF RFC3513
2000::/3 Global Unicast RFC3513 [3]
4000::/3 Reserved by IETF RFC3513
Huston Informational [Page 2]RFC 4147 IANA IPv6 Registry August 2005
6000::/3 Reserved by IETF RFC3513
8000::/3 Reserved by IETF RFC3513
A000::/3 Reserved by IETF RFC3513
C000::/3 Reserved by IETF RFC3513
E000::/4 Reserved by IETF RFC3513
F000::/5 Reserved by IETF RFC3513
datatracker.ietf.org