RFC 1881 INFORMATIONAL IPV6 · IANA · ALLOCATION

IPv6 Address Allocation Management

A proposed management and delegation structure for IPv6 address space.

On rfc-editor.org ↗
PUBLISHED
December 1995
AUTHORS
IAB, IESG
STREAM
IETF
DOI
10.17487/RFC1881

RFC text

Contents
Original text · RFC Editor View on rfc-editor.org ↗
Network Working Group                                       IAB and IESG
Request for Comments: 1881                                 December 1995
Category: Informational


                   IPv6 Address Allocation Management

Status of this Memo

   This memo provides information for the Internet community.  This memo
   does not specify an Internet standard of any kind.  Distribution of
   this memo is unlimited.

Abstract

   The IPv6 address space will be managed by the IANA for the good of
   the Internet community, with advice from the IAB and the IESG, by
   delegation to the regional registries.

Statement

   The IPv6 address space must be managed for the good of the Internet
   community.  Good management requires at least a small element of
   central authority over the delegation and allocation of the address
   space.

   The Internet community recognizes the Internet Assigned Numbers
   Authority (IANA) as the appropriate entity to have the responsibility
   for the management of the IPv6 address space.

   The IANA will rely on the advice of the Internet Architecture Board
   (IAB) and the Internet Engineering Steering Group (IESG) in the
   management of the IPv6 address space.

   The IANA will delegate to regional (and other) registries the task of
   making specific address allocations to network service providers and
   other subregional registries.  Individuals and organizations may
   obtain address allocations directly from the appropriate regional (or
   other) registry, or from their service provider.

   Delegation of address space by the IANA is not irrevocable. If, in
   the judgement of the IANA, a registry has seriously mishandled the
   address space delegated to it, the IANA may revoke the delegation,
   with due notice and with due consideration of the operational
   implications.  IANA will make every effort in such a case not to
   revoke addresses that are in active use, unless there are
   overwhelming technical reasons for doing so.

   Any revenues (such as transaction fees) received with respect to the
   IPv6 address space should be used only for expenses related to
   registry activities, and not to subsidize any other activities.
   There will be no charges for the address space itself, only fees to
   recover the registry costs.

   Any situation in the management of the IPv6 address space that leads
   to monopoly control or predatory practices must be avoided.

   The IANA will develop a plan for the initial IPv6 address allocation,
   including a provision for the automatic allocation of IPv6 addresses
   to holders of IPv4 addresses. IANA will also develop mediation and
   appeals procedures concerning delegation and revocation.

Security Considerations

   Security issues are not discussed in this memo.

Contact Information:

   Internet Architecture Board
   EMail: <iab@isi.edu>

   Internet Engineering Steering Group
   EMail: <iesg@cnri.reston.va.us>

ISO Plain Language

On this page
PROBLEMIPv6 address space needed a management structure for delegation and allocation on behalf of the Internet community.
MECHANISMThe memo assigns management responsibility to IANA, with advice from the IAB and IESG, and delegates specific allocations to regional and other registries.
THE PROPOSED STRUCTUREIt sets out principles for allocation, delegation, revocation, registry fees, and a plan for initial IPv6 allocation.

§1Who Manages IPv6 Address Space

The memo says IPv6 address space must be managed for the good of the Internet community and that good management requires some central authority over delegation and allocation. It identifies IANA as the appropriate entity, with advice from the Internet Architecture Board and Internet Engineering Steering Group.

IANA delegates specific allocations to regional and other registries, which in turn allocate addresses to network service providers and other subregional registries. Individuals and organizations may obtain allocations through a registry or service provider.

IANA oversees the address space and delegates allocation work to registries. Organizations can obtain an allocation from a registry or through a service provider.

§2Delegation and Fees

The RFC says an IANA delegation to a registry is not irrevocable. If IANA judges that a registry has seriously mishandled its delegated space, it may revoke the delegation after notice and consideration of operational effects. It says IANA will try not to revoke addresses in active use unless there are overwhelming technical reasons.

Any revenue related to the address space should cover registry expenses only; the address space itself is not charged for, though cost-recovery fees may apply. The memo also says monopoly control and predatory practices must be avoided.

A registry can lose its delegated authority if it seriously mishandles the space. Fees may cover registry costs, but the address space itself is not sold.

§3Initial Allocation and Appeals

The RFC says IANA will develop a plan for initial IPv6 allocation, including automatic allocation to holders of IPv4 addresses. It also says IANA will develop mediation and appeals procedures for delegation and revocation.

The memo calls for an initial allocation plan and procedures to handle disputes about delegation and revocation.

§4Status of the Memo

RFC 1881 provides information to the Internet community and does not specify an Internet standard.

This document describes allocation-management principles. It does not define an Internet standard.