<div dir="auto"><div dir="auto">Dear Jordi,</div><div dir="auto"><br></div><div dir="auto">Thank you for your response.</div><div dir="auto"><br></div><div dir="auto">I agree that AFRINIC is not required to follow the same approach as other RIRs. Every region should make decisions that suit its own community.</div><div dir="auto"><br></div><div dir="auto">My point, however, is slightly different. I wasn't suggesting that AFRINIC should copy another RIR simply because they did it that way.</div><div dir="auto"><br></div><div dir="auto">Rather, I'm asking what specific problem is solved by making this a policy instead of implementing it operationally. If both approaches achieve the same technical outcome, then what additional value does the policy itself provide?</div><div dir="auto"><br></div><div dir="auto">I think that's an important distinction. The fact that the community can choose policy doesn't necessarily mean policy is the most appropriate mechanism in every case.</div><div dir="auto"><br></div><div dir="auto">I'd be interested to hear what practical or technical benefit you believe is only possible through policy and not through an operational implementation.</div><div dir="auto"><br></div><div dir="auto">Kind regards,</div><div dir="auto"><br></div><div dir="auto">Fundiswa</div><div dir="auto"><br></div><div dir="auto"><br></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Tue, 21 Jul 2026, 11:57 , <<a href="mailto:rpd-request@afrinic.net">rpd-request@afrinic.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send RPD mailing list submissions to<br>
<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:rpd-owner@afrinic.net" target="_blank" rel="noreferrer">rpd-owner@afrinic.net</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of RPD digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: RPD Digest, Vol 222, Issue 111 (Nia Petronella)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 21 Jul 2026 11:56:49 +0200<br>
From: Nia Petronella <<a href="mailto:nonhlanhlapetronella85@gmail.com" target="_blank" rel="noreferrer">nonhlanhlapetronella85@gmail.com</a>><br>
To: Andrew Alston <<a href="mailto:aa@alstonnetworks.net" target="_blank" rel="noreferrer">aa@alstonnetworks.net</a>><br>
Cc: <a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a><br>
Subject: Re: [rpd] RPD Digest, Vol 222, Issue 111<br>
Message-ID:<br>
<CA+mDOg0DqqBO74UVnd9mEr-P=<a href="mailto:itGtjGx5Uh4vYJ8e95YZ1ooRg@mail.gmail.com" target="_blank" rel="noreferrer">itGtjGx5Uh4vYJ8e95YZ1ooRg@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Dear Andrew,<br>
<br>
I do not accept the binary you have presented.<br>
<br>
No one is suggesting that AFRINIC should make operational changes in secret<br>
or without community input. An operational change can be published,<br>
consulted on, tested, documented, and reviewed. The real question is<br>
whether that input must be converted into binding policy enforced by the<br>
registry.<br>
<br>
Calling AFRINIC ?community-driven? does not answer who the community is or<br>
what it is authorised to bind. A self-selecting group of mailing-list<br>
participants can provide expertise, support, and objection. It does not<br>
automatically represent every member, resource holder, network, customer,<br>
or other affected party.<br>
<br>
The institutional reality also remains unchanged: participants discuss the<br>
policy, but AFRINIC interprets and enforces it. Community participation<br>
therefore does not eliminate registry power. It can become the language<br>
used to legitimise that power.<br>
<br>
This is why Kone?s examples matter. If LACNIC, RIPE NCC, and ARIN can<br>
achieve the same technical outcome through operational mechanisms, then<br>
policy is not technically inevitable. Proponents should explain what<br>
additional technical result binding policy provides, beyond converting an<br>
IRR setting into an enforceable obligation.<br>
<br>
I also disagree that an objection is valid only if it proves immediate<br>
operational harm or implementation failure. The choice of instrument,<br>
proportionality, reversibility, and expansion of enforcement authority are<br>
legitimate policy concerns. Last Call is not limited to asking whether<br>
software will break. It must also ask whether the proposed power is greater<br>
than the problem requires.<br>
<br>
Rough consensus does not require every objection to be accommodated. But an<br>
objection is not ?addressed? merely because supporters repeat that the<br>
community prefers policy. That is the very assumption being challenged.<br>
Procedure cannot be used to prove its own mandate.<br>
<br>
The fact that the RIR system has operated this way for decades demonstrates<br>
continuity of practice. It does not establish unlimited legitimacy of scope.<br>
<br>
I support Kone?s questions and remain opposed to AFPUB-2026-ASN-001-DRAFT02.<br>
<br>
Regards,<br>
Nonhlanhla<br>
<br>
<br>
<br>
On Tue, 21 Jul 2026, 10:26 am Andrew Alston <<a href="mailto:aa@alstonnetworks.net" target="_blank" rel="noreferrer">aa@alstonnetworks.net</a>> wrote:<br>
<br>
> The answer to this is simple. AfriNiC is a community driven organisation<br>
> - and anything done with regard to address allocation and management is<br>
> done as per policy provided by the community. It is through policy that<br>
> the community tells AfriNIC how to do things in regards to the allocation<br>
> and handling of resources.<br>
><br>
> Without policy, the discretion and rules are entirely in the hands of the<br>
> registry, and the community voice is removed.<br>
><br>
> This has been the way the RIR system has operated for decades and it<br>
> works. The community exercises its voice and its right as to how things<br>
> are done in relation to resource management through policy.<br>
><br>
> Arguing that just because something can be done another way, is not in my<br>
> view a valid argument against policy. Objections to policy need to be<br>
> technically grounded and demonstrate that the policy would either cause<br>
> harm or alternatively be impractical to implement. Anything else is simply<br>
> arguing that policy should not exist because someone doesn?t like AfriNIC<br>
> being told how the community wants things done - and that isn?t an argument<br>
> that I believe rises to the level of a block on consensus.<br>
><br>
> Please note - consensus does not require that the issue you raise have<br>
> been fixed, it requires that they have been addressed, and should the<br>
> community feel that despite the objections, the policy is something that<br>
> should proceed based on the fact that the questions have been addressed if<br>
> not necessarily accommodated, rough consensus still exists.<br>
><br>
> Again, I support the policy and I see no technical or evidence/fact-based<br>
> arguments against said policy.<br>
><br>
> Andrew<br>
><br>
> On Tue, Jul 21, 2026 at 09:34, Nia Petronella <<br>
> <a href="mailto:nonhlanhlapetronella85@gmail.com" target="_blank" rel="noreferrer">nonhlanhlapetronella85@gmail.com</a>> wrote:<br>
><br>
>> Dear PDWG,<br>
>><br>
>> Kone is asking the right question.<br>
>><br>
>> The issue is no longer whether hierarchical AS-SET naming is technically<br>
>> possible or useful. It already exists. The issue is why AFRINIC needs a<br>
>> binding policy to enforce what other RIRs largely treat as an operational<br>
>> IRR matter.<br>
>><br>
>> That distinction matters. An operational change adjusts how a service is<br>
>> implemented. A policy creates an enforceable obligation and enlarges the<br>
>> registry?s authority. If the same technical result can be achieved through<br>
>> a community-reviewed implementation plan, then policy is not the minimum<br>
>> necessary instrument.<br>
>><br>
>> Saying that ?the community prefers policy? is not enough. Participation<br>
>> may guide technical work, but it does not turn every preference into a<br>
>> mandate. A mailing list is not a legislature, and the availability of the<br>
>> PDP should not make policy the default answer to every operational setting.<br>
>><br>
>> This is how gatekeeping expands: the registry begins with a useful<br>
>> technical function, then policy converts that function into permission and<br>
>> enforcement. The recordkeeper gradually becomes the rule-maker.<br>
>><br>
>> The proponents should therefore answer Kone directly: what technical<br>
>> outcome can mandatory policy achieve here that an operational<br>
>> implementation cannot?<br>
>><br>
>> Until that is clearly demonstrated, I support Kone?s questions and remain<br>
>> opposed to the policy route.<br>
>><br>
>> Regards,<br>
>> Nonhlanhla<br>
>><br>
>><br>
>><br>
>> On Tue, 21 Jul 2026, 8:20 am <<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a>> wrote:<br>
>><br>
>>> Send RPD mailing list submissions to<br>
>>> <a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a><br>
>>><br>
>>> To subscribe or unsubscribe via the World Wide Web, visit<br>
>>> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
>>> or, via email, send a message with subject or body 'help' to<br>
>>> <a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a><br>
>>><br>
>>> You can reach the person managing the list at<br>
>>> <a href="mailto:rpd-owner@afrinic.net" target="_blank" rel="noreferrer">rpd-owner@afrinic.net</a><br>
>>><br>
>>> When replying, please edit your Subject line so it is more specific<br>
>>> than "Re: Contents of RPD digest..."<br>
>>><br>
>>><br>
>>> Today's Topics:<br>
>>><br>
>>> 1. Re: RPD Digest, Vol 222, Issue 110 (Tshepo Masuku)<br>
>>><br>
>>><br>
>>> ----------------------------------------------------------------------<br>
>>><br>
>>> Message: 1<br>
>>> Date: Tue, 21 Jul 2026 06:19:05 +0000<br>
>>> From: Tshepo Masuku <<a href="mailto:TshepoMasuku26@hotmail.com" target="_blank" rel="noreferrer">TshepoMasuku26@hotmail.com</a>><br>
>>> To: "<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>" <<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>><br>
>>> Subject: Re: [rpd] RPD Digest, Vol 222, Issue 110<br>
>>> Message-ID:<br>
>>> <<br>
>>> <a href="mailto:VI2PR04MB10545A0FC740F5DC6041F6C75CAC22@VI2PR04MB10545.eurprd04.prod.outlook.com" target="_blank" rel="noreferrer">VI2PR04MB10545A0FC740F5DC6041F6C75CAC22@VI2PR04MB10545.eurprd04.prod.outlook.com</a><br>
>>> ><br>
>>><br>
>>> Content-Type: text/plain; charset="windows-1252"<br>
>>><br>
>>> Dear All,<br>
>>><br>
>>> Kone?s point is directly relevant. If LACNIC, RIPE NCC, and ARIN can<br>
>>> implement hierarchical AS-SET naming through operational mechanisms, then<br>
>>> proponents must explain why AFRINIC needs a binding policy to achieve the<br>
>>> same technical result.<br>
>>><br>
>>> Saying that each RIR works differently does not answer that question.<br>
>>> Nor does saying that ?the community is on top of the RIR.? A community may<br>
>>> advise, object, and coordinate. It does not acquire unlimited authority to<br>
>>> convert every operational preference into policy. A mailing list is not a<br>
>>> legislature.<br>
>>><br>
>>> If AFRINIC can solve this through an operational change, policy adds<br>
>>> governance where technical administration would be sufficient. Speed and<br>
>>> preference do not create mandate.<br>
>>><br>
>>> Kone provided specific examples. Those should be answered with evidence,<br>
>>> not by questioning whether he has worked in every RIR for many years.<br>
>>> Experience is relevant, but it is not authority and it is not a substitute<br>
>>> for argument.<br>
>>><br>
>>> The unanswered question remains: what technical necessity requires<br>
>>> policy rather than operational implementation?<br>
>>><br>
>>> Until that is answered, Kone?s objection stands, and I support it.<br>
>>><br>
>>> Regards,<br>
>>> Tshepo<br>
>>><br>
>>><br>
>>> ________________________________<br>
>>> From: <a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a> <<a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a>><br>
>>> Sent: Monday, July 20, 2026 11:10:57 pm<br>
>>> To: <a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a> <<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>><br>
>>> Subject: RPD Digest, Vol 222, Issue 110<br>
>>><br>
>>> Send RPD mailing list submissions to<br>
>>> <a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a><br>
>>><br>
>>> To subscribe or unsubscribe via the World Wide Web, visit<br>
>>> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
>>> or, via email, send a message with subject or body 'help' to<br>
>>> <a href="mailto:rpd-request@afrinic.net" target="_blank" rel="noreferrer">rpd-request@afrinic.net</a><br>
>>><br>
>>> You can reach the person managing the list at<br>
>>> <a href="mailto:rpd-owner@afrinic.net" target="_blank" rel="noreferrer">rpd-owner@afrinic.net</a><br>
>>><br>
>>> When replying, please edit your Subject line so it is more specific<br>
>>> than "Re: Contents of RPD digest..."<br>
>>><br>
>>><br>
>>> Today's Topics:<br>
>>><br>
>>> 1. Re: Writing tools (Ben Roberts - AfriNIC)<br>
>>> 2. Re: [Last Call] Draft Policy Proposal - Hierarchical Names<br>
>>> for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02) (Kone)<br>
>>> 3. Re: [Last Call] Draft Policy Proposal - Hierarchical Names<br>
>>> for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02)<br>
>>> (<a href="mailto:jordi.palet@consulintel.es" target="_blank" rel="noreferrer">jordi.palet@consulintel.es</a>)<br>
>>><br>
>>><br>
>>> ----------------------------------------------------------------------<br>
>>><br>
>>> Message: 1<br>
>>> Date: Mon, 20 Jul 2026 21:26:40 +0200<br>
>>> From: Ben Roberts - AfriNIC <<a href="mailto:ben.roberts@afrinic.net" target="_blank" rel="noreferrer">ben.roberts@afrinic.net</a>><br>
>>> To: Nonjabulo Sphilile <<a href="mailto:nonjabulosphilile@gmail.com" target="_blank" rel="noreferrer">nonjabulosphilile@gmail.com</a>><br>
>>> Cc: <a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a><br>
>>> Subject: Re: [rpd] Writing tools<br>
>>> Message-ID: <<a href="mailto:09EB63D0-2FBC-48F9-B752-43E842D85096@afrinic.net" target="_blank" rel="noreferrer">09EB63D0-2FBC-48F9-B752-43E842D85096@afrinic.net</a>><br>
>>> Content-Type: text/plain; charset="us-ascii"<br>
>>><br>
>>> An HTML attachment was scrubbed...<br>
>>> URL: <<br>
>>> <a href="https://lists.afrinic.net/pipermail/rpd/attachments/20260720/33c3ac9e/attachment-0001.html" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20260720/33c3ac9e/attachment-0001.html</a><br>
>>> ><br>
>>><br>
>>> ------------------------------<br>
>>><br>
>>> Message: 2<br>
>>> Date: Mon, 20 Jul 2026 20:34:20 +0000<br>
>>> From: Kone <<a href="mailto:bakenon.kone@sancfis.net" target="_blank" rel="noreferrer">bakenon.kone@sancfis.net</a>><br>
>>> To: Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com" target="_blank" rel="noreferrer">seun.ojedeji@gmail.com</a>><br>
>>> Cc: rpd <<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>><br>
>>> Subject: Re: [rpd] [Last Call] Draft Policy Proposal - Hierarchical<br>
>>> Names for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02)<br>
>>> Message-ID:<br>
>>> <CADHquJpYPT91G8hHPsnXDJKp=<br>
>>> <a href="mailto:3cyspC-xR5t8iHs0EN4tTMhwQ@mail.gmail.com" target="_blank" rel="noreferrer">3cyspC-xR5t8iHs0EN4tTMhwQ@mail.gmail.com</a>><br>
>>> Content-Type: text/plain; charset="utf-8"<br>
>>><br>
>>> Hello Seun,<br>
>>> You may have misread my earlier mail. I clearly stated that LACNIC, RIPE<br>
>>> NCC, and ARIN do not require policy to enforce hierarchical AS?SET<br>
>>> naming.<br>
>>><br>
>>> To help close the ongoing discussions, I believe addressing the<br>
>>> questions I<br>
>>> raised would bring clarity:<br>
>>> * LACNIC enforces hierarchical AS?SET naming operationally, as part of<br>
>>> their IRR design from inception.<br>
>>> * RIPE NCC handles IRR changes through their Numbered Work Items (NWI)<br>
>>> process, not through policy.<br>
>>> * ARIN uses the ACSP (Consultation and Suggestion Process) for IRR<br>
>>> operational matters, again without policy.<br>
>>><br>
>>><br>
>>> These examples show that other RIRs (except APNIC) treat AS?SET naming as<br>
>>> an operational IRR matter, not a policy obligation.<br>
>>><br>
>>> This is why I asked whether AFRINIC could address this operationally<br>
>>> rather<br>
>>> than through policy, and why Last Call discussions would benefit from<br>
>>> clear<br>
>>> answers to these points.<br>
>>><br>
>>> Thanks.<br>
>>> ---<br>
>>> Kone<br>
>>><br>
>>><br>
>>><br>
>>> Le dim. 19 juil. 2026 ? 00:21, Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com" target="_blank" rel="noreferrer">seun.ojedeji@gmail.com</a>> a<br>
>>> ?crit :<br>
>>><br>
>>> > Hello Bakenon,<br>
>>> ><br>
>>> > Do refer to the proposal as it references URL to other RIR's policies<br>
>>> for<br>
>>> > thiis:<br>
>>> ><br>
>>> > <a href="https://www.afrinic.net/afpub-2026-asn-001-draft02.html" rel="noreferrer noreferrer" target="_blank">https://www.afrinic.net/afpub-2026-asn-001-draft02.html</a><br>
>>> ><br>
>>> > Regards<br>
>>> ><br>
>>> > ----<br>
>>> > Sent from my mobile<br>
>>> > kindly excuse typos<br>
>>> ><br>
>>> > On Sat, 18 Jul 2026, 6:34?pm Bakenon KONE, <<a href="mailto:bakenon.kone@sancfis.net" target="_blank" rel="noreferrer">bakenon.kone@sancfis.net</a>><br>
>>> > wrote:<br>
>>> ><br>
>>> >> Dear PDWG,<br>
>>> >><br>
>>> >> I have been following the discussions on the hierarchical AS?SET<br>
>>> naming<br>
>>> >> scheme and would like clarification on a few points:<br>
>>> >><br>
>>> >> 1. Could this matter be addressed operationally, as is done in ARIN,<br>
>>> >> LACNIC, and RIPE NCC, without requiring policy changes?<br>
>>> >><br>
>>> >> 2. If yes, why are we taking the policy route? Is it because AFRINIC<br>
>>> >> currently lacks a defined process for handling operational issues that<br>
>>> >> affect IRR services?<br>
>>> >><br>
>>> >> 3. Given that the hierarchical naming scheme is already supported and<br>
>>> >> currently exists within the IRR, this proposal represents an<br>
>>> enforcement<br>
>>> >> change rather than the introduction of a new technical standard. Why<br>
>>> is a<br>
>>> >> formal policy required to change an operational enforcement setting,<br>
>>> rather<br>
>>> >> than a community-vetted technical implementation plan?"<br>
>>> >><br>
>>> >> Thank you.<br>
>>> >> ---<br>
>>> >> Kone<br>
>>> >><br>
>>> >><br>
>>> >><br>
>>> >> Le jeu. 16 juil. 2026 ? 22:10, Hytham El-Nakhal <<a href="mailto:hytham@tra.gov.eg" target="_blank" rel="noreferrer">hytham@tra.gov.eg</a>> a<br>
>>> >> ?crit :<br>
>>> >><br>
>>> >>> Dear PDWG,<br>
>>> >>><br>
>>> >>><br>
>>> >>> The Policy Development Working Group (PDWG) Chairs have initiated a<br>
>>> Last<br>
>>> >>> Call for this proposal, following rough consensus at the AFRINIC-37<br>
>>> Public<br>
>>> >>> Policy Meeting held in hybrid format in Nairobi, Kenya on 24 June<br>
>>> 2026.<br>
>>> >>><br>
>>> >>> * Proposal Name: Hierarchical Names for New AS-SETs<br>
>>> >>><br>
>>> >>> * Proposal ID: AFPUB-2026-ASN-001-DRAFT02<br>
>>> >>><br>
>>> >>> * Proposal URL:<br>
>>> >>> <a href="https://www.afrinic.net/afpub-2026-asn-001-draft02.html" rel="noreferrer noreferrer" target="_blank">https://www.afrinic.net/afpub-2026-asn-001-draft02.html</a><br>
>>> >>><br>
>>> >>> Last Call closes on: July 31, 2026, at 23:59 UTC.<br>
>>> >>><br>
>>> >>><br>
>>> >>> Please note the staff observation regarding implementation<br>
>>> constraints:<br>
>>> >>> due to the current prioritization of the MyAFRINIC v2 deployment,<br>
>>> physical<br>
>>> >>> database implementation of this policy will be scheduled once the<br>
>>> MyAFRINIC<br>
>>> >>> v2 deployment is concluded.<br>
>>> >>><br>
>>> >>><br>
>>> >>> As always, we kindly request that all participants adhere to the<br>
>>> AFRINIC<br>
>>> >>> Code of Conduct<<a href="https://www.afrinic.net/code" rel="noreferrer noreferrer" target="_blank">https://www.afrinic.net/code</a>> to maintain a<br>
>>> respectful<br>
>>> >>> and professional environment on the mailing list.<br>
>>> >>><br>
>>> >>><br>
>>> >>> Kind regards,<br>
>>> >>><br>
>>> >>><br>
>>> >>> Haitham el Nakhal<br>
>>> >>><br>
>>> >>> AFRINIC PDWG Co-Chair<br>
>>> >>><br>
>>> >>><br>
>>> >>><br>
>>> >>> _______________________________________________<br>
>>> >>> RPD mailing list<br>
>>> >>> <a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a><br>
>>> >>> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
>>> >>><br>
>>> >> _______________________________________________<br>
>>> >> RPD mailing list<br>
>>> >> <a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a><br>
>>> >> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
>>> >><br>
>>> ><br>
>>> -------------- next part --------------<br>
>>> An HTML attachment was scrubbed...<br>
>>> URL: <<br>
>>> <a href="https://lists.afrinic.net/pipermail/rpd/attachments/20260720/4563e1d5/attachment-0001.html" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20260720/4563e1d5/attachment-0001.html</a><br>
>>> ><br>
>>><br>
>>> ------------------------------<br>
>>><br>
>>> Message: 3<br>
>>> Date: Mon, 20 Jul 2026 23:10:04 +0200<br>
>>> From: "<a href="mailto:jordi.palet@consulintel.es" target="_blank" rel="noreferrer">jordi.palet@consulintel.es</a>" <<a href="mailto:jordi.palet@consulintel.es" target="_blank" rel="noreferrer">jordi.palet@consulintel.es</a>><br>
>>> To: rpd <<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>><br>
>>> Subject: Re: [rpd] [Last Call] Draft Policy Proposal - Hierarchical<br>
>>> Names for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02)<br>
>>> Message-ID: <<a href="mailto:F22A09CF-A827-4D7F-B077-E0B9C774AF00@consulintel.es" target="_blank" rel="noreferrer">F22A09CF-A827-4D7F-B077-E0B9C774AF00@consulintel.es</a>><br>
>>> Content-Type: text/plain; charset="utf-8"<br>
>>><br>
>>> Hi Kone,<br>
>>><br>
>>> And what is the relevance of that?<br>
>>><br>
>>> If you have a good understanding about all the RIRs, you will know that<br>
>>> each RIR has their own ways to do things. In many senses they act very<br>
>>> similarly and in general we end up with very similarly policies, but not<br>
>>> always. Some RIRs have decided that some aspects are operational and don?t<br>
>>> need a policy proposal.<br>
>>><br>
>>> However, despite that, the community is on top of the RIR, and the<br>
>>> community sometimes, may decide that they prefer a policy if the RIR hasn?t<br>
>>> been proactive in advance in any specific topic, or even if the RIR was<br>
>>> proactive, the community may prefer to speed up things, or to show the way<br>
>>> the community prefers.<br>
>>><br>
>>> For example, if AFRINIC has any specific operational aspect already in<br>
>>> place, and the community prefer to manage that in a different way, the<br>
>>> community may opt either for suggesting the RIR to modify that operational<br>
>>> aspect or to do actually enforce it by means of a policy proposal.<br>
>>><br>
>>> I think is important to know, by personal experience, how the other 4<br>
>>> RIRs work before stating something that is not correct, because if you<br>
>>> don?t work in all the RIRs for many years, it will be difficult for you to<br>
>>> know the past and I?m sure IA will not be able to be precise as well.<br>
>>><br>
>>> Regards,<br>
>>> Jordi<br>
>>><br>
>>> @jordipalet<br>
>>><br>
>>> > El 20 jul 2026, a las 22:34, Kone <<a href="mailto:bakenon.kone@sancfis.net" target="_blank" rel="noreferrer">bakenon.kone@sancfis.net</a>> escribi?:<br>
>>> ><br>
>>> > Hello Seun,<br>
>>> > You may have misread my earlier mail. I clearly stated that LACNIC,<br>
>>> RIPE NCC, and ARIN do not require policy to enforce hierarchical AS?SET<br>
>>> naming.<br>
>>> ><br>
>>> > To help close the ongoing discussions, I believe addressing the<br>
>>> questions I raised would bring clarity:<br>
>>> > * LACNIC enforces hierarchical AS?SET naming operationally, as part of<br>
>>> their IRR design from inception.<br>
>>> > * RIPE NCC handles IRR changes through their Numbered Work Items (NWI)<br>
>>> process, not through policy.<br>
>>> > * ARIN uses the ACSP (Consultation and Suggestion Process) for IRR<br>
>>> operational matters, again without policy.<br>
>>> ><br>
>>> ><br>
>>> > These examples show that other RIRs (except APNIC) treat AS?SET naming<br>
>>> as an operational IRR matter, not a policy obligation.<br>
>>> ><br>
>>> > This is why I asked whether AFRINIC could address this operationally<br>
>>> rather than through policy, and why Last Call discussions would benefit<br>
>>> from clear answers to these points.<br>
>>> ><br>
>>> > Thanks.<br>
>>> > ---<br>
>>> > Kone<br>
>>> ><br>
>>> ><br>
>>> ><br>
>>> > Le dim. 19 juil. 2026 ? 00:21, Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com" target="_blank" rel="noreferrer">seun.ojedeji@gmail.com</a><br>
>>> <mailto:<a href="mailto:seun.ojedeji@gmail.com" target="_blank" rel="noreferrer">seun.ojedeji@gmail.com</a>>> a ?crit :<br>
>>> >> Hello Bakenon,<br>
>>> >><br>
>>> >> Do refer to the proposal as it references URL to other RIR's policies<br>
>>> for thiis:<br>
>>> >><br>
>>> >> <a href="https://www.afrinic.net/afpub-2026-asn-001-draft02.html" rel="noreferrer noreferrer" target="_blank">https://www.afrinic.net/afpub-2026-asn-001-draft02.html</a><br>
>>> >><br>
>>> >> Regards<br>
>>> >><br>
>>> >> ----<br>
>>> >> Sent from my mobile<br>
>>> >> kindly excuse typos<br>
>>> >><br>
>>> >> On Sat, 18 Jul 2026, 6:34?pm Bakenon KONE, <<a href="mailto:bakenon.kone@sancfis.net" target="_blank" rel="noreferrer">bakenon.kone@sancfis.net</a><br>
>>> <mailto:<a href="mailto:bakenon.kone@sancfis.net" target="_blank" rel="noreferrer">bakenon.kone@sancfis.net</a>>> wrote:<br>
>>> >>> Dear PDWG,<br>
>>> >>><br>
>>> >>> I have been following the discussions on the hierarchical AS?SET<br>
>>> naming scheme and would like clarification on a few points:<br>
>>> >>><br>
>>> >>> 1. Could this matter be addressed operationally, as is done in ARIN,<br>
>>> LACNIC, and RIPE NCC, without requiring policy changes?<br>
>>> >>><br>
>>> >>> 2. If yes, why are we taking the policy route? Is it because AFRINIC<br>
>>> currently lacks a defined process for handling operational issues that<br>
>>> affect IRR services?<br>
>>> >>><br>
>>> >>> 3. Given that the hierarchical naming scheme is already supported<br>
>>> and currently exists within the IRR, this proposal represents an<br>
>>> enforcement change rather than the introduction of a new technical<br>
>>> standard. Why is a formal policy required to change an operational<br>
>>> enforcement setting, rather than a community-vetted technical<br>
>>> implementation plan?"<br>
>>> >>><br>
>>> >>> Thank you.<br>
>>> >>> ---<br>
>>> >>> Kone<br>
>>> >>><br>
>>> >>><br>
>>> >>><br>
>>> >>> Le jeu. 16 juil. 2026 ? 22:10, Hytham El-Nakhal <<a href="mailto:hytham@tra.gov.eg" target="_blank" rel="noreferrer">hytham@tra.gov.eg</a><br>
>>> <mailto:<a href="mailto:hytham@tra.gov.eg" target="_blank" rel="noreferrer">hytham@tra.gov.eg</a>>> a ?crit :<br>
>>> >>>> Dear PDWG,<br>
>>> >>>><br>
>>> >>>><br>
>>> >>>> The Policy Development Working Group (PDWG) Chairs have initiated a<br>
>>> Last Call for this proposal, following rough consensus at the AFRINIC-37<br>
>>> Public Policy Meeting held in hybrid format in Nairobi, Kenya on 24 June<br>
>>> 2026.<br>
>>> >>>><br>
>>> >>>> * Proposal Name: Hierarchical Names for New AS-SETs<br>
>>> >>>><br>
>>> >>>> * Proposal ID: AFPUB-2026-ASN-001-DRAFT02<br>
>>> >>>><br>
>>> >>>> * Proposal URL:<br>
>>> <a href="https://www.afrinic.net/afpub-2026-asn-001-draft02.html" rel="noreferrer noreferrer" target="_blank">https://www.afrinic.net/afpub-2026-asn-001-draft02.html</a><br>
>>> >>>><br>
>>> >>>> Last Call closes on: July 31, 2026, at 23:59 UTC.<br>
>>> >>>><br>
>>> >>>><br>
>>> >>>> Please note the staff observation regarding implementation<br>
>>> constraints: due to the current prioritization of the MyAFRINIC v2<br>
>>> deployment, physical database implementation of this policy will be<br>
>>> scheduled once the MyAFRINIC v2 deployment is concluded.<br>
>>> >>>><br>
>>> >>>><br>
>>> >>>> As always, we kindly request that all participants adhere to the<br>
>>> AFRINIC Code of Conduct<<a href="https://www.afrinic.net/code" rel="noreferrer noreferrer" target="_blank">https://www.afrinic.net/code</a>> to maintain a<br>
>>> respectful and professional environment on the mailing list.<br>
>>> >>>><br>
>>> >>>><br>
>>> >>>> Kind regards,<br>
>>> >>>><br>
>>> >>>><br>
>>> >>>> Haitham el Nakhal<br>
>>> >>>><br>
>>> >>>> AFRINIC PDWG Co-Chair<br>
>>> >>>><br>
>>> >>>><br>
>>> >>>><br>
>>> >>>> _______________________________________________<br>
>>> >>>> RPD mailing list<br>
>>> >>>> <a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>><br>
>>> >>>> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
>>> >>> _______________________________________________<br>
>>> >>> RPD mailing list<br>
>>> >>> <a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a> <mailto:<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a>><br>
>>> >>> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
>>> > _______________________________________________<br>
>>> > RPD mailing list<br>
>>> > <a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a><br>
>>> > <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
>>><br>
>>><br>
>>><br>
>>> **********************************************<br>
>>> IPv4 is over<br>
>>> Are you ready for the new Internet ?<br>
>>> <a href="http://www.theipv6company.com" rel="noreferrer noreferrer" target="_blank">http://www.theipv6company.com</a><br>
>>> The IPv6 Company<br>
>>><br>
>>> This electronic message contains information which may be privileged or<br>
>>> confidential. The information is intended to be for the exclusive use of<br>
>>> the individual(s) named above and further non-explicilty authorized<br>
>>> disclosure, copying, distribution or use of the contents of this<br>
>>> information, even if partially, including attached files, is strictly<br>
>>> prohibited and will be considered a criminal offense. If you are not the<br>
>>> intended recipient be aware that any disclosure, copying, distribution or<br>
>>> use of the contents of this information, even if partially, including<br>
>>> attached files, is strictly prohibited, will be considered a criminal<br>
>>> offense, so you must reply to the original sender to inform about this<br>
>>> communication and delete it.<br>
>>><br>
>>> -------------- next part --------------<br>
>>> An HTML attachment was scrubbed...<br>
>>> URL: <<br>
>>> <a href="https://lists.afrinic.net/pipermail/rpd/attachments/20260720/b6777fa7/attachment.html" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20260720/b6777fa7/attachment.html</a><br>
>>> ><br>
>>><br>
>>> ------------------------------<br>
>>><br>
>>> Subject: Digest Footer<br>
>>><br>
>>> _______________________________________________<br>
>>> RPD mailing list<br>
>>> <a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a><br>
>>> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
>>><br>
>>><br>
>>> ------------------------------<br>
>>><br>
>>> End of RPD Digest, Vol 222, Issue 110<br>
>>> *************************************<br>
>>><br>
>>> -------------- next part --------------<br>
>>> An HTML attachment was scrubbed...<br>
>>> URL: <<br>
>>> <a href="https://lists.afrinic.net/pipermail/rpd/attachments/20260721/e492c668/attachment.html" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20260721/e492c668/attachment.html</a><br>
>>> ><br>
>>><br>
>>> ------------------------------<br>
>>><br>
>>> Subject: Digest Footer<br>
>>><br>
>>> _______________________________________________<br>
>>> RPD mailing list<br>
>>> <a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a><br>
>>> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
>>><br>
>>><br>
>>> ------------------------------<br>
>>><br>
>>> End of RPD Digest, Vol 222, Issue 111<br>
>>> *************************************<br>
>>><br>
>> _______________________________________________<br>
>> RPD mailing list<br>
>> <a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a><br>
>> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
>><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://lists.afrinic.net/pipermail/rpd/attachments/20260721/9c41424a/attachment.html" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20260721/9c41424a/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
RPD mailing list<br>
<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a><br>
<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
<br>
<br>
------------------------------<br>
<br>
End of RPD Digest, Vol 222, Issue 119<br>
*************************************<br>
</blockquote></div>