[rpd] New Draft Policy Proposal - Amendment of Utilisation in Soft Landing AFPUB-2026-IPv4-002-DRAFT01.

Tue Jun 16 07:53:56 UTC 2026

Hi Alain,

While I agree that the problem of MDNs may also happen in the region, this is not the one being tried to fix in this proposal.

The examples provided in the proposal don’t need different ASNs. In fact, you want a single ASN and provide HA.

For example, I’ve run into the problem, in one country in Africa, when doing a 464XLAT network design. The customer has 4 BGP PoPs, the need to be redundant in case of failure, but normally, each one covers nearby customers in that region. This imply having 4 new IPv4 blocks for the NAT64 boxes (2 of them in each PoP to increase the HA). And of course, they are under a single ASN.

Regards,
Jordi

@jordipalet

> El 16 jun 2026, a las 1:34, ALAIN AINA via RPD <rpd at afrinic.net> escribió:
> 
> Dear PDWG
> 
> The problem we are trying to solve here seems to be an issue with organisation running Multiple Discrete Networks (MDNs) and willing to manage the associated number resources in one account (Org-Id).
> 
> This goes beyond the IPv4 soft landing and the 90% usage requirements. It is also valid for other resources (IPv6 and ASN)
> 
> How to address this?
> 
> We need clear definitions and eligibility criteria, appropriate requests evaluation and allocation/assignment rules.
> 
> Below is a proposed policy text (*)
> 
> =========================
> Definitions and eligibility
> ---------------------------
> 
> Definition:
> 
> A Multiple Discrete Network is a network architecture in which a single organisation operates two or more autonomous and non‑interconnected networks that cannot practically share number resources.
> 
> Eligibility:
> ------------
> 
> Organisations with Multiple Discrete Networks desiring to request a new or additional IP address space allocation under a single Organisation ID must meet the following criteria:
> 
> - It is a single legal entity, not a consortium of smaller independent entities.
> 
> - It operates two or more networks that cannot share address space due to one or more of the following:
> 
> + regulatory or legal restrictions;
> + significant geographic separation and diversity between networks;
> + autonomous routing policies (e.g., independent multi‑homing);
> + operational or security constraints requiring strict separation.
> 
> 1- IPv4 requirements for MDNs
> 
> The organisation must keep detailed records on how it has allocated IP addresses to each location, including the date of each sub-allocations or assignments.
> 
> When applying for additional IP address allocations from AFRINIC,
> 
> - the organisation must demonstrate utilisation greater than 50% of both the last IP addresses allocated or assigned and the aggregate sum of all IP addresses from AFRINIC to that organisation.
> 
> - If an organisation is unable to satisfy this 50% minimum utilisation criteria, the organisation may alternatively qualify for additional IP address by having all unused IP address blocks smaller than AFRINIC's current minimum allocation or assignment size.
> 
> - The organisation must not sub-allocate or assign additional IP address space to a location until each of that location’s IP address allocations are 90% utilised.
> 
> The organisation must notify AFRINIC at the time of the request of their desire to apply this policy to their account.
> 
> 2- IPv6 requirements for MDNs
> 
> - The organisation must keep detailed records on how it has allocated IPv6 addresses to each location, including the date of each IPv6 address allocation.
> 
> - When an organisation is requesting additional IPv6 address allocations under this policy, the organisation must specify on the application which discrete network(s) the IPv6 address request applies to.
> 
> - A request for additional space will be judged against the existing utilisation criteria specified in 6.5.1 and 6.5.2 of the CPM as if it were a separate organisation, rather than collectively as would be done for requests outside of this policy.
> 
> - The organisation must notify AFRINIC  at the time of the request their desire to apply this policy to their account.
> 
> 3- ASN requirements for MDNs
> 
> Organizations that have space issued under Multiple Discrete Networks policy may be issued one ASN per discrete network upon request.
> 
> Additional ASN requests should include proof of the requestor’s need for a unique routing policy, or other technical justification for the need for more than one ASN.
> 
> (*) adapted from ARIN Policy Manual
> 
> HTH
> 
> —Alain(sorry for coming a bit late..)
> 
>> On 15 May 2026, at 15:51, dacostadarwin at gmail.com wrote:
>> 
>> Dear PDWG,
>> 
>> We have received a new draft policy proposal - Amendment of Utilisation in Soft Landing, ID AFPUB-2026-IPv4-002-DRAFT01 from author Jordi Palet Martinez. The proposal contents are published at:  
>> 
>> https://afrinic.net/policy/proposals/afpub-2026-ipv4-002-draft01
>> 
>> We encourage you to take some time to go through the proposal contents and  provide feedback as follows :
>> 
>> a) Do you support or oppose the proposal?
>> b) If you oppose the proposal, state your reasons?
>> c) Is there anything in the proposal that is not clear?
>> d) What changes could be made to this proposal to make it more effective?
>> 
>> Regards,
>> Vincent Ngundi & Darwin Da Costa
>> AFRINIC PDWG Co-Chairs
>> 
>> 
>> _______________________________________________
>> RPD mailing list
>> RPD at afrinic.net
>> https://lists.afrinic.net/mailman/listinfo/rpd
> 
> _______________________________________________
> RPD mailing list
> RPD at afrinic.net
> https://lists.afrinic.net/mailman/listinfo/rpd

**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.