Search RPD Archives
Limit search to: Subject & Body Subject Author
Sort by:

[rpd] PIER presentation from yesterday

jordi.palet at theipv6company.com jordi.palet at theipv6company.com
Thu Nov 19 19:01:48 UTC 2026


Hi all,

Looking at the PIER slides from yesterday.

1. ASN Eligibility

The problem seems to me the text in 7.2. It should be shortened to allow non-members to get ASNs, *if we want to keep 7.4*.

So “In order to qualify for an AS number, the requesting entity must fulfil any of the following requirements”.

This way we:
1) Avoid conflict with 7.4
2) Replacing organization with “entity” allows non-organizations that may also require an ASN.

A different discussion is why 7.4 has the text “and non-members”. I fail to recall if that was on purpose of this, or was left from other policy changes and we lost track of that. Both LIRs and end-users (non-LIRs) are very clear.

Could the staff identify if there are cases of non-members ? In the fees table, I can’t see how this is invoiced.

If “non-members” was left from previous proposal changes, in addition to the change suggested for the 7.2, we shall remove “and non-members”.

In fact, I may be in part “responsible" (with the community consensus) of this mistake in 7.2, as I believe the actual text comes from my policy proposal AFPUB-2019-ASN-001-DRAFT04 - Multihoming not required for ASN. I can’t find a way for finding the previous CPM versions, and the policy archive also doesn’t help, because it doesn’t clarify if a proposal reached consensus, what CPM version implemented it, etc. I believe I overlooked section 7.4 of the CPM (which had a different numbering on that time or maybe this was added later?), because what today is 7.2 was 7.4 and we had this text there "7.4.4 Be an AFRINIC member in a good standing (End-User or LIR type)”, so I just rephrased it to shorten the text, allow obtaining ASNs even if there is no multihoming (that was the main proposal intent) and we all (staff and community) missed the sections after 7.4.

Could the staff provide a link to previous CPM versions?

2. IPv6 Rectification

I proposed first the rectification for IPv6 PA, and then in a different proposal for IPv6 PI, as I noticed the same problem because members were getting the default prefix size without doing a proper addressing plan (it happened also in other RIRs, so I did the same in several of them).

This comes from another of my policy proposals “IPv6 PI Update”, which unfortunately can’t find the correct text in the AFRINIC web site. It will be nice if the staff can correct the links which seem to be broken or bring to nowhere. I can see the emails with the discussion, and when Sami and Dewole declared consensus and sent it to the board for ratification, etc.

In any case, in my own archives I’ve the text that reached consensus (relevant part):

AFPUB-2018-V6-004-DRAFT01 - "receive a new block with the new requested prefix size, with the commitment to renumber its network and return the original block within a period of 6 months;"

So both the PA and PI were matching in a 6-months period for the return of the previous prefix.

However, we overlooked something and we updated it by means of "AFPUB-2019-V6-001-DRAFT02: IPv6 PI Clarification”. As part of this change the community discussed the 6 months return for the case of IPv6 PI (we will need to dig into the mailing list archive for understanding the point), and the conclusion was (I believe this is the reason for v2, can’t check it because lack of archive in the web site, neither can see the staff IA for v1), we agreed to change this *on purpose*:

from:
Receive a new block with the new requested prefix size, with the commitment to renumber its network and return the original block within a period of 6 months

to:
Receive a new block with the new requested prefix size, with the agreement to utilize the new block for all future deployment and deprecate the old block through attrition, returning when empty. There is no deadline for return at this time

So, in conclusion, this was done on purpose! I don’t agree with the slide of the staff that indicate that this creates a difference between PA and PI holders, because it is a different type of IPv6 prefix, so they aren’t members in the “same” situation.

Of course, if the community changed his mind and believes that we should have a deadline for the return of the old prefix, I will suggest to change it for both the IPv6 PA and IPv6 PI to 12 months, as in my experience this worked better in several RIRs where I had the same proposal reaching consensus.


3. Multi-site End-User PI: Multi-country Challenge

This is how I see this by means of an example. An end-user has multiple locations, in multiple countries. They request, for example a /44, but each end-site-location uses a /48. At least this was the intent of the policy change (also same proposals as those that I mention in 2 above).

What we are missing is that in the case of the IPv6 PA, we have explicit requirements for whois registration. However in IPv6 PI we don’t have that. I believe if we explicitly indicate that each /48 for each end-site location must be registered, that will be fixed.

Could the staff clarify if this is the problem or if not, with examples how they see it? Also if the problem I described is the right one, if they agree that ensuring that each end-site location is correctly registered will solve the problem?

Regards,
Jordi

@jordipalet


**********************************************
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.






More information about the RPD mailing list