RFC 3531: A Flexible Method for Managing the Assignment of Bits of an IPv6 Address Block
In plain English — editorial summary, not part of the RFC
This document proposes a method to manage the assignment of bits of an IPv6 address block or range. When an organisation needs to make an address plan for its subnets or when an ISP needs to make an address plan for its customers, this method enables the organisation to postpone the final decision on the number of bits to partition in the address space they have. It does it by keeping the bits around the borders of the partition to be free as long as possible. This scheme is applicable to any bits addressing scheme using bits with partitions in the space, but its first intended use is for IPv6. It is a generalization of RFC 1219 and can be used for IPv6 assignments. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3531
- Published
- April 2003
- Authors
- M. Blanchet
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3543Registration Revocation in Mobile IPv4Current
August 2003
- RFC 3519Mobile IP Traversal of Network Address Translation (NAT) DevicesCurrent
May 2003
- RFC 3590Source Address Selection for the Multicast Listener Discovery (MLD) ProtocolCurrent
September 2003
- RFC 3596DNS Extensions to Support IP Version 6Current
October 2003
- RFC 3678Socket Interface Extensions for Multicast Source FiltersCurrent
January 2004
- RFC 3315Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Obsoleted
July 2003
- RFC 3314Recommendations for IPv6 in Third Generation Partnership Project (3GPP) StandardsCurrent
September 2002
- RFC 3306Unicast-Prefix-based IPv6 Multicast AddressesUpdated
September 2002
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?