Skip to content
This repository was archived by the owner on Jul 2, 2020. It is now read-only.

Commit a4074c6

Browse files
committed
Reflect production usage
Updated readme to reflect the tool's first use in production on 2014-05-20.
1 parent 0ce99fe commit a4074c6

File tree

2 files changed

+15
-18
lines changed

2 files changed

+15
-18
lines changed

readme.txt

Lines changed: 13 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,27 +1,24 @@
1-
IPv4 Reclamation Algorithm (Beta)
2-
=================================
1+
IPv4 Reclamation Algorithm
2+
==========================
33

44
OVERVIEW
55

6-
In May 2012, the ICANN Board ratified a global policy Global Policy for
7-
Post Exhaustion IPv4 Allocation by IANA. This policy called for the
8-
establishment of a Recovered IPv4 Pool, which contains fragments leftover
9-
in the IANA and space that has been returned to the IANA by other means.
10-
The policy also called for IANA to make allocations from the Recovered
11-
IPv4 Pool once the pool is declared active.
6+
In May 2012, the ICANN Board ratified the Global Policy for Post Exhaustion
7+
IPv4 Allocation by IANA. This policy called for the establishment of a
8+
Recovered IPv4 Pool, which contains fragments leftover in the IANA and
9+
space that has been returned to the IANA by other means. The policy also
10+
called for IANA to make allocations from the Recovered IPv4 Pool once the
11+
pool is declared active.
1212

13-
The pool will initially be declared active as soon as the first RIR has
14-
less than a /9 of IPv4 space in its inventory. The pool will also be
15-
declared active during “IPv4 allocation periods”, 6-month periods
16-
following 1 March or 1 September in each year.
13+
The pool was initially be declared active as soon as the first RIR has
14+
less than a /9 of IPv4 space in its inventory. This occurred on 20 May
15+
2014. The pool will also be declared active during “IPv4 allocation
16+
periods”, 6-month periods following 1 March or 1 September in each year.
1717

1818
ICANN reported that we will use an open-source software program to
1919
perform the address selection process. This code implements the IPv4
2020
reclamation policy.
2121

22-
This code is provisional and may be revised based on feedback from the
23-
community prior to its initial invocation by the Global Policy.
24-
2522
REQUIREMENTS
2623

2724
The Global Policy calls for the following:
@@ -102,4 +99,4 @@ SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
10299
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
103100
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
104101
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
105-
THE POSSIBILITY OF SUCH DAMAGE.
102+
THE POSSIBILITY OF SUCH DAMAGE.

sample-output.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@ Sample outputs
22
==============
33

44
Here are sample outputs based on the IPv4 recovered registry as at
5-
2014-04-22. The algorithm can run through 9 generations of alloctions
5+
2014-04-22. The algorithm can run through 9 generations of allocations
66
before the pool is exhausted to the point it no longer meets the
77
minimums set in the Global Policy.
88

@@ -2104,4 +2104,4 @@ Available Pool:
21042104
IP addresses available to allocate: 1,024 (10.0 bits)
21052105
Each allocatee receives: 128 (/25 equivalent)
21062106
Recipient allocations not large enough to satisfy global policy minimums. Nothing to do.
2107-
$
2107+
$

0 commit comments

Comments
 (0)