<div dir="auto"><div dir="auto"><div dir="auto"><div>Jordi,</div><div dir="auto"><br></div><div dir="auto">Also to add that the technical community's support for the proposal is based on our recognition, that, hierarchical naming improves attribution of the objects.</div><div dir="auto"><br></div><div dir="auto">The issue of validating the members inside the as-set is a separate one and I for one dont dispute that changamoto. Its also a fact that the specific, documented problem of unattributable as-set names in multi-source irr environments remains real. It needs a fix.</div><div dir="auto"><br></div><div dir="auto">Technical communities across the five Registy's are chosing to close that gap at creation time are doing so based on experienced operational incidents, some through policy (apnic) and others through techops implementation.</div><div dir="auto"><br></div><div dir="auto">The policy route will suffice at afrinic...</div><div><br></div><div data-smartmail="gmail_signature"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>Ahsante sana</div><div dir="auto">Noah</div></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 21 Jul 2026, 12:17 am jordi.palet--- via RPD, <<a href="mailto:rpd@afrinic.net" rel="noreferrer noreferrer" target="_blank">rpd@afrinic.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="line-break:after-white-space">Hi Kone,<div><br></div><div>And what is the relevance of that?</div><div><br></div><div>If you have a good understanding about all the RIRs, you will know that each RIR has their own ways to do things. In many senses they act very similarly and in general we end up with very similarly policies, but not always. Some RIRs have decided that some aspects are operational and don’t need a policy proposal.</div><div><br></div><div>However, despite that, the community is on top of the RIR, and the community sometimes, may decide that they prefer a policy if the RIR hasn’t been proactive in advance in any specific topic, or even if the RIR was proactive, the community may prefer to speed up things, or to show the way the community prefers.</div><div><br></div><div>For example, if AFRINIC has any specific operational aspect already in place, and the community prefer to manage that in a different way, the community may opt either for suggesting the RIR to modify that operational aspect or to do actually enforce it by means of a policy proposal.</div><div><br></div><div>I think is important to know, by personal experience, how the other 4 RIRs work before stating something that is not correct, because if you don’t work in all the RIRs for many years, it will be difficult for you to know the past and I’m sure IA will not be able to be precise as well.</div><div><br id="m_-3721135802356594828m_-3821244288818879692m_-27882461219902457lineBreakAtBeginningOfMessage"><div>
<div>Regards,<br>Jordi<br><br>@jordipalet<br></div>
</div>
<div><br><blockquote type="cite"><div>El 20 jul 2026, a las 22:34, Kone <<a href="mailto:bakenon.kone@sancfis.net" rel="noreferrer noreferrer noreferrer" target="_blank">bakenon.kone@sancfis.net</a>> escribió:</div><br><div><div dir="ltr"><div dir="ltr"><div>Hello Seun,</div><div>You may have misread my earlier mail. I clearly stated that LACNIC, RIPE NCC, and ARIN do not require policy to enforce hierarchical AS‑SET naming.</div><div><br></div><div>To help close the ongoing discussions, I believe addressing the questions I raised would bring clarity:<br>* LACNIC enforces hierarchical AS‑SET naming operationally, as part of their IRR design from inception.<br>* RIPE NCC handles IRR changes through their Numbered Work Items (NWI) process, not through policy.<br>* ARIN uses the ACSP (Consultation and Suggestion Process) for IRR operational matters, again without policy.<br><br><br>These examples show that other RIRs (except APNIC) treat AS‑SET naming as an operational IRR matter, not a policy obligation.<br><br>This is why I asked whether AFRINIC could address this operationally rather than through policy, and why Last Call discussions would benefit from clear answers to these points.<br><br>Thanks.</div><div>---</div><div>Kone</div><div><div dir="ltr" class="gmail_signature"><div dir="ltr"><br></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le dim. 19 juil. 2026 à 00:21, Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com" rel="noreferrer noreferrer noreferrer" target="_blank">seun.ojedeji@gmail.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div>Hello Bakenon,</div><div dir="auto"><br></div><div dir="auto">Do refer to the proposal as it references URL to other RIR's policies for thiis:</div><div dir="auto"><br></div><div dir="auto"><a href="https://www.afrinic.net/afpub-2026-asn-001-draft02.html" rel="noreferrer noreferrer noreferrer" target="_blank">https://www.afrinic.net/afpub-2026-asn-001-draft02.html</a></div><div dir="auto"><br></div><div dir="auto">Regards</div><div><br></div><div>----<br>Sent from my mobile<br>kindly excuse typos </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, 18 Jul 2026, 6:34 pm Bakenon KONE, <<a href="mailto:bakenon.kone@sancfis.net" rel="noreferrer noreferrer noreferrer" target="_blank">bakenon.kone@sancfis.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div>Dear PDWG,<br><br>I have been following the discussions on the hierarchical AS‑SET naming scheme and would like clarification on a few points:<br><br>1. Could this matter be addressed operationally, as is done in ARIN, LACNIC, and RIPE NCC, without requiring policy changes?<br><br>2. If yes, why are we taking the policy route? Is it because AFRINIC currently lacks a defined process for handling operational issues that affect IRR services?<br><br>3. Given that the hierarchical naming scheme is already supported and currently exists within the IRR, this proposal represents an enforcement change rather than the introduction of a new technical standard. Why is a formal policy required to change an operational enforcement setting, rather than a community-vetted technical implementation plan?"<br><br>Thank you.</div><div>---</div><div>Kone</div><div><div dir="ltr" class="gmail_signature"><div dir="ltr"><br></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le jeu. 16 juil. 2026 à 22:10, Hytham El-Nakhal <<a href="mailto:hytham@tra.gov.eg" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">hytham@tra.gov.eg</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Dear PDWG,<br>
<br>
<br>
The Policy Development Working Group (PDWG) Chairs have initiated a Last Call for this proposal, following rough consensus at the AFRINIC-37 Public Policy Meeting held in hybrid format in Nairobi, Kenya on 24 June 2026.<br>
<br>
* Proposal Name: Hierarchical Names for New AS-SETs<br>
<br>
* Proposal ID: AFPUB-2026-ASN-001-DRAFT02<br>
<br>
* Proposal URL: <a href="https://www.afrinic.net/afpub-2026-asn-001-draft02.html" rel="noreferrer noreferrer noreferrer 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 constraints: due to the current prioritization of the MyAFRINIC v2 deployment, physical database implementation of this policy will be scheduled once the MyAFRINIC v2 deployment is concluded.<br>
<br>
<br>
As always, we kindly request that all participants adhere to the AFRINIC Code of Conduct<<a href="https://www.afrinic.net/code" rel="noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">https://www.afrinic.net/code</a>> to maintain a 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" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">RPD@afrinic.net</a><br>
<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
</blockquote></div></div>
_______________________________________________<br>
RPD mailing list<br>
<a href="mailto:RPD@afrinic.net" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">RPD@afrinic.net</a><br>
<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
</blockquote></div>
</blockquote></div></div>
_______________________________________________<br>RPD mailing list<br><a href="mailto:RPD@afrinic.net" rel="noreferrer noreferrer noreferrer" target="_blank">RPD@afrinic.net</a><br><a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br></div></blockquote></div><br></div><br>**********************************************<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
<a href="http://www.theipv6company.com" rel="noreferrer 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 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.<br>
<br>
</div>_______________________________________________<br>
RPD mailing list<br>
<a href="mailto:RPD@afrinic.net" rel="noreferrer noreferrer noreferrer" target="_blank">RPD@afrinic.net</a><br>
<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
</blockquote></div>
<br><br></div>
<br><br></div>