[rpd] AfriNIC's CPM section 5.5 - IPv4 LIR/ISP Allocations (5.5.1 Allocation policies and guidelines)

[Sylvain Baya]

{warning! long email, so apologies please :'-(}
Dear PDWG,

Please apologies for the pasting action :'-(

<tl;dr>
Yes! i took the responsibility to bring the CPM section 5.5 | IPv4 LIR/ISP
Allocations (5.5.1 Allocation policies and guidelines) to you, in case it
might have been a too hard task to go it the location of that content.
Please accept to read it...

...i did it with the naive expectation that it
could help the PDWG to move forward
on some recuring topics, such as
Internet number resources (at least for
IPv4 types) utilisation and responsibilities
thereof, within the AfriNIC's service region.

Therefore permit me to recommend the following subventions to your
particular attention:

¿°?
• 5.5.1.1.3 If an LIR plans to exchange or transfer address space, it needs
to contact AFRINIC so that the changes are properly registered.
• 5.5.1.2.3 Must show an existing efficient utilization of IP addresses
from their upstream provider.
• 5.5.1.3 Slow start mechanism for first allocations
• 5.5.1.4.1 An LIR may receive an additional allocation when about 80% of
all the address space currently allocated to it has been used in valid
assignments and/or sub-allocations.
• 5.5.1.4.2 Reservations are not considered as valid assignments or
sub-allocations.
• 5.5.1.7 Documentation
• 5.5.1.8 Network infrastructure (of LIR) vs End-User networks
• 5.5.1.9 Utilisation
• 5.5.1.10 Reservations not supported
• 5.5.1.11 Validity of an assignment
• 5.5.1.13 Sub-Allocation Window (SAW)
• 5.5.1.13.1 A sub-allocation window (SAW) refers to the maximum number of
IPv4 addresses that the LIR may sub-allocate to the end-users without
seeking approval from AFRINIC.
• 5.5.1.13.2 AFRINIC will review sub-allocation made by the LIR's using
their SAW to ensure that policies are followed correctly.
• 5.5.1.13.3 Below are a few guidelines for the SAW:
• 5.5.1.14 Recordkeeping by LIRs
¿°?

Please let me know if it was a bad initiative :-/

Thanks.
</tl;dr>

Source: <https://afrinic.net/policy/manual#lir-isp-allocation>

~°~
...
5.5 IPv4 LIR/ISP Allocations

5.5.1 Allocation policies and guidelines

5.5.1.1 Introduction

5.5.1.1.1 AFRINIC allocates ranges of IPv4 addresses to Local Internet
Registries (LIRs).

LIRs reassign or sub-allocated that space to their customers. All LIR's
assigning address space allocated from AFRINIC are also advised to adopt a
set of policies that are consistent with the policies described in this
document.

5.5.1.1.2 Determination of IP address space allocation size is the
responsibility of AFRINIC staff.

In an effort to ensure that Classless Inter-Domain Routing (CIDR) is
implemented and utilized as efficiently as possible, AFRINIC will issue
blocks of IPv4 addresses on appropriate "CIDR-supported" bit boundaries.
(CIDR - "Classless Inter-Domain Routing", is explained in RFC1517-1959,
https://www.ietf.org/standards/rfcs/).

5.5.1.1.3 If an LIR plans to exchange or transfer address space, it needs
to contact AFRINIC so that the changes are properly registered.

The LIR remains responsible for all the allocations registered in the
AFRINIC database until they have been transferred to another LIR or
returned to AFRINIC. LIR's must ensure that all policies are applied.

5.5.1.2 First IPv4 Allocation

5.5.1.2.1 AFRINIC's minimum allocation is /22 or 1024 IPv4 addresses.

5.5.1.2.2 The organisation must be an AFRINIC member in good standing, and;

5.5.1.2.3 Must show an existing efficient utilization of IP addresses from
their upstream provider.

Justification may be based on a combination of immediate need and existing
usage, in which case, the existing assignments must be renumbered into the
LIR's new allocation. The verification of previous efficient utilisation is
based on assignments (and sub-allocations) registered in the RIPE, ARIN,
LACNIC and APNIC databases and only these registered assignments will be
considered valid.

5.5.1.3 Slow start mechanism for first allocations

AFRINIC shall apply a slow start mechanism to all new LIRs. With respect to
allocations made by AFRINIC, the first allocation an LIR receives will be
the size of the minimum practical allocation unless otherwise justified.

The slow start policy is used by all RIR's to prevent allocations of large
blocks of address space that may then remain substantially unassigned.
AFRINIC will implement the slow start mechanism in a consistent and fair
manner for every LIR and will apply the same principles and standards to
every applicant for address space.

5.5.1.4 Additional Allocation

5.5.1.4.1 An LIR may receive an additional allocation when about 80% of all
the address space currently allocated to it has been used in valid
assignments and/or sub-allocations.

A new allocation can also be made if a single assignment or sub-allocation
requires more addresses than those currently held by the LIR.

5.5.1.4.2 Reservations are not considered as valid assignments or
sub-allocations.

It may be useful for internal aggregation to keep some IP blocks free for
future growth. These internal reservations are however not counted as valid
usage and must be assigned or sub-allocated before requesting for
additional allocation.

5.5.1.4.3 AFRINIC will always try to allocate contiguous address ranges,
allowing the LIR to minimise the number of route announcements it makes.

However, it will not always be possible to allocate a range of contiguous
with the LIR's previous allocation.

5.5.1.5 Sub-Allocations

The minimum size of a sub-allocation is /24. It allows a reasonable number
of small assignments to be made by a downstream ISP. An LIR may not
sub-allocate IPv4 space above its sub-allocation window (see 5.5.1.13 for
sub-allocation windows).

LIR's may make sub-allocations to multiple downstream ISP's. (Downstream
ISP's efficiently using a sub-allocation qualify to receive a /22
allocation should they want to become an LIR).

The LIR is responsible for ensuring that address space allocated to it, and
subsequently, the address space that it sub-allocates is used in accordance
with the community's policies and guidelines.

LIRs are advised to make use of the slow-start mechanism when making
sub-allocations to downstream ISPs. Here, the LIR ensures that space
sub-allocated is efficiently used and the LIR can also monitor and
determine the ability of the downstream ISP to operate within the policies
set by the community.

Sub-allocations form part of an LIR's aggregatable space. Therefore, an LIR
should ensure that IP space is not retained by the downstream ISP if the
reseller ceases to obtain connectivity from the LIR's network
(sub-allocations are non-portable).

5.5.1.6 PA Assignment policies and guidelines

LIR's must request approval from AFRINIC for all sub-allocations above
their Sub-Allocation Window.

The following guidelines are intended to help LIRs and end-users in their
search for equitable compromises:

5.5.1.7 Documentation

The information required by AFRINIC to justify an end-user's IP address
requirements includes addressing needs, network infrastructure and future
plans. Such information is required when an LIR is requesting IP space for
their end-users at the time of sending in the request. In order to ensure
that previous sub-allocations are not duplicated, the current address space
usage is also required. This information is essential in making the
appropriate sub-allocation approvals, and the level of detail will depend
on the size of the request and complexity of the network. The LIR should
ensure that the necessary information is completed before making a
sub-allocation request to AFRINIC.

When making sub-allocation from their SAW, LIR's should also ensure that
such information is given by the end-user.

5.5.1.8 Network infrastructure (of LIR) vs End-User networks

IP addresses used solely for connecting an end-user to a service provider
(e.g., point-to-point links) are considered as part of the service
provider's infrastructure. Such addresses should only be registered as part
of the service provider's infrastructure. When an end-user has a network
using public address space, this space must be registered with the contacts
of the end-user. If the end-user is an individual rather than an
organisation, space may be registered with the contact information of the
service provider but with the end-user referenced in the AFRINIC whois
database object.

5.5.1.9 Utilisation

Immediate utilisation of assignments should be at least 25% of the assigned
space. After one year, unless special circumstances are defined, it should
be at least 50%.

5.5.1.10 Reservations not supported

End-users are not permitted to reserve address space based on long term
plans. This violates the goal of conservation and fragments the address
space when initial forecasts are not met. If an LIR wants to assign address
space for customers, it must make the assignments from any unallocated or
unassigned address space it currently holds. For the purposes evaluating
allocation requests, space reserved by an LIR for other customers is
considered unused.

5.5.1.11 Validity of an assignment

Assignments remain valid as long as the original criteria on which the
assignment was based are still in place and the assignment is registered in
the AFRINIC database. An assignment is therefore invalid if it is not
registered in the database and if the purpose for which it was registered
has changed or no longer holds.

5.5.1.12 Re-numbering

This is replacing IP addresses on a one-to-one basis. Valid assignments can
be replaced with the same number of addresses if the original assignment
criteria are still met. The addresses to be replaced must still be in use.
When a renumbering request exceeds the LIR's sub-allocation window, the
request should be sent to AFRINIC for approval.

A period of three months is normally considered sufficient to migrate a
network to the new IP space. Once a network has been renumbered, AFRINIC
staff will remove the old assignment from the AFRINIC database. In case the
three monthsÕ period is not sufficient, the LIR should inform AFRINIC about
the additional time they might take to completely renumber.

5.5.1.13 Sub-Allocation Window (SAW)

5.5.1.13.1 A sub-allocation window (SAW) refers to the maximum number of
IPv4 addresses that the LIR may sub-allocate to the end-users without
seeking approval from AFRINIC. The SAW size is expressed in CIDR notation.

5.5.1.13.2 AFRINIC will review sub-allocation made by the LIR's using their
SAW to ensure that policies are followed correctly. LIR's should also
ensure that documentation for sub-allocation made using the SAW be similar
to that requested for larger requests.

5.5.1.13.3 Below are a few guidelines for the SAW:

All new LIRs have a SAW of zero. All sub-allocations will need prior
approval by AFRINIC.
The LIR cannot make any sub-allocation to the end-user above their SAW in a
12 monthsÕ period (1 year). At the end of a calendar year from the approval
of a SAW, the SAW is refreshed for one more year. In case the LIR's SAW is
exhausted for a particular end-user, approval must be sought from AFRINIC
for any other sub-allocation to the same end-user.
LIR's are welcome to approach AFRINIC for a review of their SAW. They may
also seek a second opinion from AFRINIC even for a sub-allocation that
could be made with their SAW if they chose. Before a SAW is raised, the
following will be considered:
All required documentation is normally presented.
Previous sub-allocation assignments from this sub-allocation are all
registered in the database correctly.
Current SAW has not been misused/abused.
New LIR's are advised to train their contacts to handle address space
assignments according to the policies and procedures in this document. If
due to inexperienced contacts at the LIR, errors due to poor judgement
consistently happen, the SAW may be lowered or removed to allow AFRINIC
staff to assist in training the LIR's staff in the AFRINIC community's
policies.

5.5.1.14 Recordkeeping by LIRs

LIR's must keep and maintain records of any documentation regarding
assignments and sub-allocations to end-users. It is needed for future
reference when evaluating requests from the same organisation and for any
audits by AFRINIC. These documents should be kept electronically for easier
access. It's advisable that these records should include but not be limited
to:

The original request.
Supporting documentation.
Related correspondence between LIR and end-user.
The decision of the assignment, and the reasons behind any unusual decision.
Role of the person that made the decision.

5.6 IPv4 End-User (PI) Assignments
 ...
~°~


Shalom,
--sb.




-- 
--

Best Regards !
__
baya.sylvain[AT cmNOG DOT cm]|<https://cmnog.cm/dokuwiki/Structure>
Subscribe to Mailing List: <https://lists.cmnog.cm/mailman/listinfo/cmnog/>
__
#‎LASAINTEBIBLE‬|#‎Romains15‬:33«Que LE ‪#‎DIEU‬ de ‪#‎Paix‬ soit avec vous
tous! ‪#‎Amen‬!»
‪#‎MaPrière‬ est que tu naisses de nouveau. #Chrétiennement‬
«Comme une biche soupire après des courants d’eau, ainsi mon âme soupire
après TOI, ô DIEU!»(#Psaumes42:2)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/rpd/attachments/20210702/6139d648/attachment-0001.html>